Bug#818905: Steam Controller is not correctly detected

[Michael Pobega]

On May 2nd Valve created a Github repository[0] for the steam-devices
udev rules which is MIT licensed. Unless I'm misunderstanding I
believe this means we can make any modifications we want to these udev
rules now, so this bug should be easily resolvable

[0] https://github.com/ValveSoftware/steam-devices

Bug#901424: mosquitto FTCBFS: cross-bd-uninstallable due to python-all

[Helmut Grohne]

Source: mosquitto
Version: 1.4.15-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

mosquitto cannot install its cross Build-Depends, because installing
python-all (actually python2.7-minimal) fails. The dependency expresses
a host architecture python, something which is not runnable and thus not
installable. The dependency is a relict from earlier times when
mosquitto was building python-mosquitto.

What it really wants now is a python 2.x (not 3.x) for running its
testsuite. So rather than python-all, it just needs python. And rather
than the host architecture python, it needs the build architecture
python:native, and it only needs that for running tests, thus
.

After applying the attached patch, mosquitto cross builds successfully.
Please consider applying it.

Helmut
diff --minimal -Nru mosquitto-1.4.15/debian/changelog 
mosquitto-1.4.15/debian/changelog
--- mosquitto-1.4.15/debian/changelog   2018-04-07 12:16:43.0 +0200
+++ mosquitto-1.4.15/debian/changelog   2018-06-13 06:13:48.0 +0200
@@ -1,3 +1,10 @@
+mosquitto (1.4.15-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Demote Build-Depends: python-all to python:native . (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 13 Jun 2018 06:13:48 +0200
+
 mosquitto (1.4.15-2) unstable; urgency=low
 
   * Replace mentions of 'c_rehash' with 'openssl rehash'. (Closes: #895084).
diff --minimal -Nru mosquitto-1.4.15/debian/control 
mosquitto-1.4.15/debian/control
--- mosquitto-1.4.15/debian/control 2018-02-28 13:33:36.0 +0100
+++ mosquitto-1.4.15/debian/control 2018-06-13 06:13:48.0 +0200
@@ -7,7 +7,7 @@
libssl-dev (>=1.0.0),
libwebsockets-dev (>=2.0),
libwrap0-dev,
-   python-all (>= 2.6.6-3~),
+   python:native (>= 2.6.6-3~) ,
uthash-dev,
uuid-dev
 Standards-Version: 4.1.3

Bug#901420: ksoftirqd/0: page allocation failure: order:1, mode:0x2284020(GFP_ATOMIC|__GFP_COMP|__GFP_NOTRACK)

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 2018-06-12 at 20:04 -0500, Luigi P. Bai wrote:
> Package: src:linux
> Version: 4.9.88-1+deb9u1
> Severity: important
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> Just using the system.
> 
>* 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?
> No kernel oops!

This isn't an "oops".  This is "out of memory".

[...]
> [  845.662225] 21043 total pagecache pages
> [  845.664751] 50 pages in swap cache
> [  845.668148] Swap cache stats: add 4400, delete 4350, find 105/191
> [  845.674216] Free swap  = 3886824kB
> [  845.677612] Total swap = 3903484kB
> [  845.680999] 65536 pages RAM
> [  846.915372] Hardware name: QNAP TS-109/TS-209
[...]

Only 256 MB RAM.  (That big swap partition isn't going to help much.) 
What applications are you running?

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere.
 - Anne Morrow Lindberg



signature.asc
Description: This is a digitally signed message part

Bug#901332: d-i: Offer to shut down / power off instead of reboot at the end

[Ben Hutchings]

On Mon, 2018-06-11 at 17:23 +0200, Thorsten Glaser wrote:
> Package: debian-installer
> Severity: normal
> 
> d-i always insists on rebooting at the end. This is made worse
> by it telling the user to change boot media, which, for virtual
> machines, means reconfiguring the VM.

virt-manager (or maybe the underlying libvirt) seems to handle this:
when you create a VM and provide an installation image, it is
automatically detached when the VM reboots.

> I *generally* wish to reconfigure the VM after first install
> *anyway*.
> 
> So, please, at the end, where it tells the reboot message, add
> a third button that shuts down / powers off the system instead
> of rebooting.

Still, I do agree that this would be useful in general.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere.
 - Anne Morrow Lindberg



signature.asc
Description: This is a digitally signed message part

Bug#901423: Make it more clear in manpage that default action is non destructive

[Witold Baryluk]

Package: rdfind
Version: 1.3.5-1
Severity: normal


It really tooks some time to parse manpage to know if rdfind by default
deletes anything or not. In the end I tested it on a test directory to be
sure. rdfind shouldn't delete anything, as the name suggests it only finds.

IN manpages:


   -deleteduplicates true|false
  Delete (unlink) files.


Add maybe: Default false.

Also the dry run mode is rather weird, and I think it requires some 
clarification.

The existance of dryrun option started the whole problem, as manpage says:


   -n, -dryrun true|(false)
  displays what should have been done, don't actually delete or 
link anything.


suggesting that by default rdfind does delete duplicates.

Adding small snippet in DESCRIPTION section:

  By default `rdfind` only finds duplicates and reports how much space
  would be saved by removing duplicates. To actually remove duplicates
  see OPTIONS for possible actions.

would make it all obvious.




Regards,
Witold


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

Kernel: Linux 4.16.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8), 
LANGUAGE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rdfind depends on:
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-5
ii  libnettle6  3.4-1
ii  libstdc++6  8.1.0-5

rdfind recommends no packages.

rdfind suggests no packages.

-- no debconf information

Bug#815120: rdfind: please use SHA1 by default (instead of MD5)

[Witold Baryluk]

Package: rdfind
Version: 1.3.5-1
Followup-For: Bug #815120


Actually please support sha256

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

Kernel: Linux 4.16.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8), 
LANGUAGE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rdfind depends on:
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-5
ii  libnettle6  3.4-1
ii  libstdc++6  8.1.0-5

rdfind recommends no packages.

rdfind suggests no packages.

-- no debconf information

Bug#901422: gpaste-daemon: random crash (SIGSEGV)

[Paul Wise]

Package: gpaste
Version: 3.28.0-2
Severity: normal
File: /usr/lib/x86_64-linux-gnu/gpaste/gpaste-daemon
Usertags: crash

I got a couple of random crashes (SIGSEGV) in gpaste-daemon.
If the backtraces below are not useful, please close this bug.

$ gdb -batch -n -ex 'set pagination off' -ex bt -ex 'thread apply all bt full' 
--core 
/var/crash/1000/2081-1000-1000-11-1528779084-chianamo--usr-lib-x86_64-linux-gnu-gpaste-gpaste-daemon.core
 /usr/lib/x86_64-linux-gnu/gpaste/gpaste-daemon
[New LWP 2081]
[New LWP 2083]
[New LWP 2082]
[New LWP 2084]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/x86_64-linux-gnu/gpaste/gpaste-daemon'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  fast_validate (str=) at ../../../../glib/gutf8.c:1492
1492../../../../glib/gutf8.c: No such file or directory.
[Current thread is 1 (Thread 0x7fdc65158a80 (LWP 2081))]
#0  0x7fdc638b2b50 in fast_validate (str=) at 
../../../../glib/gutf8.c:1492
#1  0x7fdc638b2b50 in g_utf8_validate (str=str@entry=0x0, 
max_len=max_len@entry=-1, end=end@entry=0x0) at ../../../../glib/gutf8.c:1673
#2  0x7fdc646f0351 in selection_get_text_plain 
(selection_data=0x7fff75a2d8a0) at ../../../../gtk/gtkselection.c:1568
#3  0x7fdc646f0351 in gtk_selection_data_get_text 
(selection_data=selection_data@entry=0x7fff75a2d8a0) at 
../../../../gtk/gtkselection.c:1682
#4  0x7fdc647d1cbb in request_text_received_func (clipboard=0x55dcdb4d3670 
[GtkClipboard], selection_data=0x7fff75a2d8a0, data=0x55dcdb699cd0) at 
../../../../gtk/gtkclipboard.c:1035
#5  0x7fdc647d0fd9 in selection_received (widget=0x55dcdb5833b0 
[GtkInvisible], selection_data=0x7fff75a2d8a0, time=) at 
../../../../gtk/gtkclipboard.c:960
#9  0x7fdc63b772e8 in  (instance=0x55dcdb5833b0, 
detailed_signal=detailed_signal@entry=0x7fdc64857c04 "selection-received") at 
../../../../gobject/gsignal.c:3487
#6  0x7fdc63b5af6d in g_closure_invoke (closure=0x55dcdb551770, 
return_value=0x0, n_param_values=3, param_values=0x7fff75a2d530, 
invocation_hint=0x7fff75a2d4b0) at ../../../../gobject/gclosure.c:804
#7  0x7fdc63b6dd3e in signal_emit_unlocked_R 
(node=node@entry=0x55dcdb45b220, detail=detail@entry=0, 
instance=instance@entry=0x55dcdb5833b0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fff75a2d530) at 
../../../../gobject/gsignal.c:3635
#8  0x7fdc63b763f5 in g_signal_emit_valist 
(instance=instance@entry=0x55dcdb5833b0, signal_id=signal_id@entry=101, 
detail=, var_args=var_args@entry=0x7fff75a2d768) at 
../../../../gobject/gsignal.c:3391
#10 0x7fdc646edd83 in gtk_selection_retrieval_report 
(info=info@entry=0x55dcdb645950, type=, format=, 
buffer=, length=, time=1300254466) at 
../../../../gtk/gtkselection.c:3047
#11 0x7fdc646f2048 in _gtk_selection_property_notify (widget=, event=0x55dcdb4430a0) at ../../../../gtk/gtkselection.c:2935
#12 0x7fdc64661f17 in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x55dcdb45a570, 
return_value=0x7fff75a2db00, instance=, args=, 
marshal_data=, n_params=, 
param_types=0x55dcdb45a5a0) at ../../../../gtk/gtkmarshalers.c:128
#13 0x7fdc63b5b1a6 in _g_closure_invoke_va (closure=0x55dcdb45a570, 
return_value=0x7fff75a2db00, instance=0x55dcdb5833b0, args=0x7fff75a2dbd0, 
n_params=1, param_types=0x55dcdb45a5a0) at ../../../../gobject/gclosure.c:867
#14 0x7fdc63b760ad in g_signal_emit_valist (instance=0x55dcdb5833b0, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fff75a2dbd0) at ../../../../gobject/gsignal.c:3300
#15 0x7fdc63b76e0f in g_signal_emit 
(instance=instance@entry=0x55dcdb5833b0, signal_id=, 
detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
#16 0x7fdc647a9254 in gtk_widget_event_internal 
(widget=widget@entry=0x55dcdb5833b0 [GtkInvisible], 
event=event@entry=0x55dcdb4430a0) at ../../../../gtk/gtkwidget.c:7740
#17 0x7fdc647ab2ca in gtk_widget_event (widget=widget@entry=0x55dcdb5833b0 
[GtkInvisible], event=event@entry=0x55dcdb4430a0) at 
../../../../gtk/gtkwidget.c:7310
#18 0x7fdc64660eee in gtk_main_do_event (event=) at 
../../../../gtk/gtkmain.c:1855
#19 0x7fdc641739b5 in _gdk_event_emit (event=event@entry=0x55dcdb4430a0) at 
../../../../gdk/gdkevents.c:73
#20 0x7fdc641a42f2 in gdk_event_source_dispatch 
(source=source@entry=0x55dcdb42c9b0, callback=, 
user_data=) at ../../../../../gdk/x11/gdkeventsource.c:367
#21 0x7fdc63881287 in g_main_dispatch (context=0x55dcdb440d50) at 
../../../../glib/gmain.c:3177
#22 0x7fdc63881287 in g_main_context_dispatch 
(context=context@entry=0x55dcdb440d50) at ../../../../glib/gmain.c:3830
#23 0x7fdc638814c0 in g_main_context_iterate 
(context=context@entry=0x55dcdb440d50, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
../../../../glib/gmain.c:3903
#24 0x7fdc6388154c in g_main_context_iteration 
(context=context@entry=0x55dcdb440d50, 

Bug#901421: ITP: golang-github-googleapis-gnostic -- compiler for OpenAPI specification

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov 
X-Debbugs-CC: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 docker.io

   Package name: golang-github-googleapis-gnostic
Version: 0.2.0
Upstream Author: Google Inc.
License: Apache-2.0
URL: https://github.com/googleapis/gnostic
Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-googleapis-gnostic
Description: compiler for OpenAPI specification
 Protocol Buffers (https://developers.google.com/protocol-buffers/)
 provide a language-neutral, platform-neutral, extensible mechanism
 for serializing structured data. gnostic's Protocol Buffer models for
 the OpenAPI Specification can be used to generate code that includes
 data structures with explicit fields for the elements of an OpenAPI
 description. This makes it possible for developers to work with
 OpenAPI descriptions in type-safe ways, which is particularly useful in
 strongly-typed languages like Go and Swift.
 .
 gnostic reads OpenAPI descriptions into these generated data structures,
 reports errors, resolves internal dependencies, and writes the results in
 a binary form that can be used in any language that is supported by the
 Protocol Buffer tools.  A plugin interface simplifies integration with
 API tools written in a variety of different languages, and when necessary,
 Protocol Buffer OpenAPI descriptions can be reexported as JSON or YAML.


signature.asc
Description: This is a digitally signed message part.

Bug#901134: RFS: anbox-modules/0.0~git20180608-1 [ITP]

[Shengjing Zhu]

On Wed, Jun 13, 2018 at 02:30:18AM +0200, Adam Borowski wrote:
> > anbox-modules-dkms - Android kernel driver (binder, ashmem) in DKMS 
> > format
> 
> Could you please explain (here and/or in the package's description) reasons
> why an user would prefer this version of the modules over what's in mainline
> kernel trees?
> 

This upstream repo in out-of-tree format can be built against various
kernel versions.

I think upstream creates this repo because many distributions(including
most Debian based) don't enable these modules in their kernel.

Since this repo already exists, then packaging it is more convenient to
enable these modules in kernel(and waiting other Debian derivatives to
sync up, not sure if they just sync with Debian or have own kernel
config).

I don't have good sentence for package description. Suggestions are
welcome.

> Also, you have GPL-3 scripts managing GPL-2 modules, this is borderline and
> I'm not quite sure of which side of the border.
> 

the debian/ directory is split from previous anbox package, which is in
GPL-3. Since all things in debian/ dir are written by myself, it's easy
to change the license.

But I don't think it would be problem. Just to clarify, there's no d/patches
file, so no GPL-3 code is patched to GPL-2 code.

-- 
Regards,
Shengjing Zhu


signature.asc
Description: PGP signature

Bug#901412: ITP: ibmquantumexperience -- A Python library for the IBM Quantum Experience API (Python 3)

[Luciano Bello]

On 06/12/18 16:55, Guus Sliepen wrote:
> If it's a Python 3 library, the package name should have the python3- prefix, 
> and you
> might want to consider naming it (python3-)qiskit instead of 
> (python3-)ibmquantumexperience.

I just realize that python2 is supported too. This is not qiskit, but
the client API for connected to the ibm quantum experience.



signature.asc
Description: OpenPGP digital signature

Bug#892983: [Aptitude-devel] Bug#892983 + Bug#892984: please allow filtering on/displaying the release 'label'/'suite'

[Manuel A. Fernandez Montecelo]

Control: tags 892983 + pending


Hi,

2018-04-02 21:35 GMT+02:00 Manuel A. Fernandez Montecelo
:
> Hi Thomas,
>
> 2018-04-02 15:51 GMT+02:00 Tomas Pospisek :
>> Hi Manuel,
>>
>> I want to ping you on this wishlist ticket.
>>
>> I do not want to stress you out: you have your own life and priorities, just
>> as everybody else, full respect for that.
>>
>> However sometimes stuff falls through the cracks, that's why I'm pinging you
>> on this.
>>[...]

With significant delay (alioth/salsa migrations and other stuff in
between), finally this is added to the repo.

I had to make some changes for the column, but nothing big.

Also, I cannot remember why I didn't add it at the time along with
Origin, if there was an issue, it might be gone now, not sure.

Finally, about the tests, I didn't run them yet, I am going to look at
this along with other changes that I am making that will very likely
cause some breakage, and I also looking into your other patch (didn't
do it yet) and other pending submissions.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#901420: ksoftirqd/0: page allocation failure: order:1, mode:0x2284020(GFP_ATOMIC|__GFP_COMP|__GFP_NOTRACK)

[Luigi P. Bai]

Package: src:linux
Version: 4.9.88-1+deb9u1
Severity: important

Dear Maintainer,

   * What led up to the situation?
Just using the system.

   * 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?
No kernel oops!


-- Package-specific info:
** Version:
Linux version 4.9.0-6-marvell (debian-ker...@lists.debian.org) (gcc version 
6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 Debian 4.9.88-1+deb9u1 (2018-05-07)

** Command line:
console=ttyS0,115200n8 root=/dev/ram rw initrd=0x80,0x3f

** Not tainted

** Kernel log:
[  845.662225] 21043 total pagecache pages
[  845.664751] 50 pages in swap cache
[  845.668148] Swap cache stats: add 4400, delete 4350, find 105/191
[  845.674216] Free swap  = 3886824kB
[  845.677612] Total swap = 3903484kB
[  845.680999] 65536 pages RAM
[  845.683781] 0 pages HighMem/MovableOnly
[  845.687599] 2004 pages reserved
[  846.896499] ksoftirqd/0: page allocation failure: order:1, 
mode:0x2284020(GFP_ATOMIC|__GFP_COMP|__GFP_NOTRACK)
[  846.906531] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.9.0-6-marvell #1 
Debian 4.9.88-1+deb9u1
[  846.915372] Hardware name: QNAP TS-109/TS-209
[  846.919778] [] (unwind_backtrace) from [] 
(show_stack+0x18/0x1c)
[  846.927524] [] (show_stack) from [] 
(warn_alloc+0xe4/0x118)
[  846.934838] [] (warn_alloc) from [] 
(__alloc_pages_nodemask+0x940/0xa5c)
[  846.943281] [] (__alloc_pages_nodemask) from [] 
(cache_alloc_refill+0x280/0x808)
[  846.952411] [] (cache_alloc_refill) from [] 
(kmem_cache_alloc+0xc4/0x12c)
[  846.960943] [] (kmem_cache_alloc) from [] 
(sk_prot_alloc+0x30/0xdc)
[  846.968956] [] (sk_prot_alloc) from [] 
(sk_clone_lock+0x1c/0x244)
[  846.976789] [] (sk_clone_lock) from [] 
(inet_csk_clone_lock+0x18/0xbc)
[  846.985054] [] (inet_csk_clone_lock) from [] 
(tcp_create_openreq_child+0x20/0x3dc)
[  846.994368] [] (tcp_create_openreq_child) from [] 
(tcp_v4_syn_recv_sock+0x38/0x30c)
[  847.003759] [] (tcp_v4_syn_recv_sock) from [] 
(tcp_check_req+0x374/0x3f0)
[  847.012286] [] (tcp_check_req) from [] 
(tcp_v4_rcv+0x4e0/0xba4)
[  847.019960] [] (tcp_v4_rcv) from [] 
(ip_local_deliver_finish+0x280/0x2a0)
[  847.028482] [] (ip_local_deliver_finish) from [] 
(ip_local_deliver+0x70/0xd8)
[  847.037355] [] (ip_local_deliver) from [] 
(ip_rcv+0x3d4/0x450)
[  847.044923] [] (ip_rcv) from [] 
(__netif_receive_skb_core+0x580/0xa88)
[  847.053186] [] (__netif_receive_skb_core) from [] 
(napi_gro_receive+0x74/0xd4)
[  847.062189] [] (napi_gro_receive) from [] 
(mv643xx_eth_poll+0x488/0x560 [mv643xx_eth])
[  847.071866] [] (mv643xx_eth_poll [mv643xx_eth]) from [] 
(net_rx_action+0x10c/0x334)
[  847.081253] [] (net_rx_action) from [] 
(__do_softirq+0x188/0x278)
[  847.089078] [] (__do_softirq) from [] 
(run_ksoftirqd+0x2c/0x5c)
[  847.096750] [] (run_ksoftirqd) from [] 
(smpboot_thread_fn+0x15c/0x164)
[  847.105020] [] (smpboot_thread_fn) from [] 
(kthread+0xe4/0xf4)
[  847.112593] [] (kthread) from [] 
(ret_from_fork+0x14/0x2c)
[  847.119795] Mem-Info:
[  847.122110] active_anon:18271 inactive_anon:18118 isolated_anon:0
 active_file:11628 inactive_file:7405 isolated_file:0
 unevictable:8 dirty:1 writeback:516 unstable:0
 slab_reclaimable:2020 slab_unreclaimable:1925
 mapped:9329 shmem:1425 pagetables:766 bounce:0
 free:1181 free_pcp:33 free_cma:0
[  847.155132] Node 0 active_anon:73084kB inactive_anon:72472kB 
active_file:46512kB inactive_file:29620kB unevictable:32kB isolated(anon):0kB 
isolated(file):0kB mapped:37316kB dirty:4kB writeback:2064kB shmem:5700kB 
writeback_tmp:0kB unstable:0kB pages_scanned:41 all_unreclaimable? no
[  847.180004] Normal free:4724kB min:1996kB low:2492kB high:2988kB 
active_anon:73084kB inactive_anon:72472kB active_file:46512kB 
inactive_file:29620kB unevictable:32kB writepending:2068kB present:262144kB 
managed:254128kB mlocked:32kB slab_reclaimable:8080kB slab_unreclaimable:7700kB 
kernel_stack:1656kB pagetables:3064kB bounce:0kB free_pcp:132kB local_pcp:132kB 
free_cma:0kB
[  847.212860] lowmem_reserve[]: 0 0 0
[  847.216368] Normal: 1181*4kB (U) 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 
0*512kB 0*1024kB 0*2048kB 0*4096kB = 4724kB
[  847.227240] 20691 total pagecache pages
[  847.229766] 233 pages in swap cache
[  847.233250] Swap cache stats: add 4583, delete 4350, find 105/191
[  847.239318] Free swap  = 3886092kB
[  847.242705] Total swap = 3903484kB
[  847.246101] 65536 pages RAM
[  847.248890] 0 pages HighMem/MovableOnly
[  847.252711] 2004 pages reserved
[  847.256192] ksoftirqd/0: page allocation failure: order:1, 
mode:0x2284020(GFP_ATOMIC|__GFP_COMP|__GFP_NOTRACK)
[  847.266220] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.9.0-6-marvell #1 
Debian 4.9.88-1+deb9u1
[  847.275063] Hardware name: QNAP TS-109/TS-209
[  847.279464] [] (unwind_backtrace) from [] 
(show_stack+0x18/0x1c)
[  847.287216] [] (show_stack) from [] 
(warn_alloc+0xe4/0x118)
[  847.294530] [] (warn_alloc) from [] 

Bug#894065: merge request on Salsa

[Adam Borowski]

Hi!
Apparently Salsa doesn't notify maintainers about merge requests, thus
what intended to be a time saver turned out to not quite be one.  Still,
if you could merge it (so your next upload would include the patch) or
NAK it (no support until 1.31 is officially released), it'd be nice.

https://salsa.debian.org/debian/tar/merge_requests/1

} While this has been accepted upstream, it doesn't look like they'll make
} another release before Buster.
}
} You've made two uploads after I filed this patch; I noticed the first but
} not the second, resulting in bloated uncompressed tarballs on my machines
} running unstable.  Thus, giving you a nice git commit you can apply in one
} go would both prevent further mishaps for me (I really shouldn't have been
} this enthusiastic with using this feature yet), and let people use zstd
} tarballs in Buster (rationale in the bug report).
}
} Similar patches have been merged in mc, dircolors and so on.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts
⣾⠁⢰⠒⠀⣿⡁ productivity.  You can read it, too, you just need the
⢿⡄⠘⠷⠚⠋⠀ right music while doing so.  I recommend Skepticism
⠈⠳⣄ (funeral doom metal).

Bug#901313: ignoring: Numerical argument out of domain

[積丹尼 Dan Jacobson]

> "MB" == Michael Biebl  writes:
>> Jun 11 17:24:42 jidanni6 systemd[230]: Failed to add rule for system call 
>> gtty() / -10022, ignoring: Numerical argument out of domain
>> Jun 11 17:24:42 jidanni6 systemd[230]: Failed to add rule for system call 
>> prof() / -10039, ignoring: Numerical argument out of domain
>> Jun 11 17:24:42 jidanni6 systemd[230]: Failed to add rule for system call 
>> rtas() / -10187, ignoring: Numerical argument out of domain

MB> That just seems to be a debug message.
MB> Do you have debug logging enabled?
MB> Can you provide your kernel command line as well (cat /proc/cmdline)

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.16.0-2-amd64 root=UUID=50... ro 
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=262144 enforcing=0 
panic=33 earlyprintk=vga

So it seems debugging caught some newly introduced inefficiencies!

Bug#901134: RFS: anbox-modules/0.0~git20180608-1 [ITP]

[Adam Borowski]

On Sat, Jun 09, 2018 at 05:49:58PM +0800, Shengjing Zhu wrote:
>  * Package name: anbox-modules
>Version : 0.0~git20180608-1
>Upstream Author : Simon Fels 
>  * URL : https://github.com/anbox/anbox-modules/
>  * License : GPL-2
>Section : kernel
> 
>   It builds those binary packages:
> 
> anbox-modules-dkms - Android kernel driver (binder, ashmem) in DKMS format

Could you please explain (here and/or in the package's description) reasons
why an user would prefer this version of the modules over what's in mainline
kernel trees?

Also, you have GPL-3 scripts managing GPL-2 modules, this is borderline and
I'm not quite sure of which side of the border.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts
⣾⠁⢰⠒⠀⣿⡁ productivity.  You can read it, too, you just need the
⢿⡄⠘⠷⠚⠋⠀ right music while doing so.  I recommend Skepticism
⠈⠳⣄ (funeral doom metal).

Bug#901136: can't remove if install fails

[KAction]

control: tag -1 +help

> Control: reassign -1 sysuser-helper,sreview-common
> Control: retitle -1 sysuser-helper fails in terrible ways if users exist 
> through NSS modules that are not libnss-unix

> On Sat, Jun 09, 2018 at 09:53:53AM +, Peter Palfrader wrote:
> > Package: sreview-common
> > Version: 0.3.0-1~bpo.1
> > Severity: grave
> > User: debian-ad...@lists.debian.org
> > Usertags: needed-by-DSA-Team
> > 
> > 
> > sreview-common failed to configure.
> > 
> > | Setting up sreview-common (0.3.0-1~bpo.1) ...
> > | usermod: user 'sreview' does not exist in /etc/passwd
[...]

Bad, bad. Oblivious workaround would be create user manually, but let us
dig into the root of problem.

I never worked with NSS, but how did it happen, that useradd {in postinst}
created user in a way, that userdel {in prerm} could not find?

Bug#839239: xserver-xorg-core: slight tearing with Intel modesetting driver

[Leo L. Schwab]

Package: xserver-xorg-core
Version: 2:1.20.0-2
Followup-For: Bug #839239

This issue still exists in the latest version.  It should be noted
that this issue is (usually) papered over if you have window compositing
enabled.

The root cause is obviously that rectangular blits are being
decomposed (by glamor?  By OpenGL itself?) into two triangles, rendered
sequentially.  Thus, there is a brief window of time where half of the
window frame is filled with new pixels (just drawn by the first triangle),
and the other half contains old pixels (shorly to be overdrawn by the second
triangle).  The result is a diagonal "tear" across the window where the
triangle edges meet.

Microsoft made this mistake over a decade ago when they first tried
to leverage Direct3D for their video player.  It looked awful then, too.

If you have a keyboard-driven window manager (such as i3 or
awesome), this is fairly easy to see:
- If you have it enabled, disable window compositing.
- Create two windows -- one containing mostly light-color imagery,
  the other mostly dark imagery.
- Resize both windows to full screen.
- Using the window manager's keyboard shortcuts, cycle between the
  two windows.

If you hold down the keyboard shortcut, the keyboard's auto-repeat
will usually kick in and rapidly ping-pong between the two windows.  The
diagonal "tear" should become apparent.

Note also that, if you resize the window, the "tear" follows the
diagonal axis of the window.

Thank you for your attention to this matter.

Schwab


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 
[8086:1616] (rev 09)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 149 Jul 18  2017 20-intel.conf.disabled

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 43481 Jun 12 15:20 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 6.022] 
X.Org X Server 1.20.0
X Protocol Version 11, Revision 0
[ 6.022] Build Operating System: Linux 4.9.0-6-amd64 x86_64 Debian
[ 6.022] Current Operating System: Linux walkies 4.16.0-2-amd64 #1 SMP 
Debian 4.16.12-1 (2018-05-27) x86_64
[ 6.022] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-2-amd64 
root=UUID=c83db6d8-15bf-493f-9339-a9d6129a7992 ro quiet
[ 6.022] Build Date: 24 May 2018  04:23:27PM
[ 6.022] xorg-server 2:1.20.0-2 (https://www.debian.org/support) 
[ 6.022] Current version of pixman: 0.34.0
[ 6.022]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 6.022] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 6.022] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 12 12:52:19 
2018
[ 6.023] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 6.024] (==) No Layout section.  Using the first Screen section.
[ 6.024] (==) No screen section available. Using defaults.
[ 6.024] (**) |-->Screen "Default Screen Section" (0)
[ 6.024] (**) |   |-->Monitor ""
[ 6.025] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 6.025] (==) Automatically adding devices
[ 6.025] (==) Automatically enabling devices
[ 6.025] (==) Automatically adding GPU devices
[ 6.025] (==) Max clients allowed: 256, resource mask: 0x1f
[ 6.026] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 6.026]Entry deleted from font path.
[ 6.031] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 6.031] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 6.031] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 6.031] (II) Loader magic: 0x55bae1604de0
[ 6.031] (II) Module ABI versions:
[ 

Bug#694965: netcfg: Allow setup of pointopoint routes to reach gateway

[Igor Scheller]

Oh, and here is the patch File ;)

On 12.06.2018 13:49, Igor Scheller wrote:
> Hi,
> i created a merge request [1] that allows to preseed pointopoint
> connections so anyone can use a preseed file or boot parameters to
> define a pointopoint connection.
> -> If a pointopoint connection is preseeded it would be used.
>
> Improvements / thoughts welcome!
>
> Greets
> Igor Scheller
>
>
> [1] https://salsa.debian.org/installer-team/netcfg/merge_requests/2
From 06647bebad8643a1990a98431bfdc4eab80007d8 Mon Sep 17 00:00:00 2001
From: Igor Scheller 
Date: Sat, 2 Jun 2018 17:24:30 +0200
Subject: [PATCH 1/2] Add support for preseeded pointopoint

---
 static.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/static.c b/static.c
index ea12fba4..316f8d8e 100644
--- a/static.c
+++ b/static.c
@@ -557,11 +557,13 @@ int netcfg_get_static(struct debconfclient *client, struct netcfg_interface *ifa
 if (netcfg_get_ipaddress (client, iface)) {
 state = BACKUP;
 } else {
+debconf_get(client, "netcfg/get_pointopoint");
 if (strncmp(iface->name, "plip", 4) == 0
 || strncmp(iface->name, "slip", 4) == 0
 || strncmp(iface->name, "ctc", 3) == 0
 || strncmp(iface->name, "escon", 5) == 0
-|| strncmp(iface->name, "iucv", 4) == 0)
+|| strncmp(iface->name, "iucv", 4) == 0
+|| !empty_str(client->value))
 state = GET_POINTOPOINT;
 else if (iface->masklen == 0) {
 state = GET_NETMASK;
-- 
2.17.1


From 258e0a104c3207ecb723103446c686ad57181f7e Mon Sep 17 00:00:00 2001
From: Igor Scheller 
Date: Tue, 12 Jun 2018 13:12:38 +0200
Subject: [PATCH 2/2] Preseeded pointopoint: Fix routing

---
 static.c  | 2 +-
 write_interface.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/static.c b/static.c
index 316f8d8e..e3d93c79 100644
--- a/static.c
+++ b/static.c
@@ -368,7 +368,7 @@ static int netcfg_activate_static_ipv4(struct debconfclient *client,
 
 if (!empty_str(interface->pointopoint))
 {
-snprintf(buf, sizeof(buf), "ip route add default dev %s", interface->name);
+snprintf(buf, sizeof(buf), "ip route add default via %s dev %s", interface->pointopoint, interface->name);
 rv |= di_exec_shell_log(buf);
 }
 else if (!empty_str(interface->gateway)) {
diff --git a/write_interface.c b/write_interface.c
index 1f683b2a..406513e6 100644
--- a/write_interface.c
+++ b/write_interface.c
@@ -120,7 +120,7 @@ static int nc_wi_static_ipv4(const struct netcfg_interface *interface, FILE *fd)
 	fprintf(fd, "iface %s inet static\n", interface->name);
 	fprintf(fd, "\taddress %s/%i\n", interface->ipaddress,
 	empty_str(interface->pointopoint) ? interface->masklen : 32);
-	if (!empty_str(interface->gateway))
+	if (!empty_str(interface->gateway) || !empty_str(interface->pointopoint))
 		fprintf(fd, "\tgateway %s\n",
 		empty_str(interface->pointopoint) ? interface->gateway : interface->pointopoint);
 	if (!empty_str(interface->pointopoint))
-- 
2.17.1



signature.asc
Description: OpenPGP digital signature

Bug#871835: systemd-setup-machine-id leaving mount behind? (was "Bug#871835: Call for help: review patches for debootstrap")

[Michael Biebl]

Hi Antonio


sorry for the late reply...

Am 13.06.2018 um 01:20 schrieb Michael Biebl:
> Am 22.04.2018 um 15:09 schrieb Antonio Terceiro:
> 
>> # findmnt | grep machine-id
>> ├─/root/patched2/etc/machine-id
>> /dev/mapper/lemur--vg-root[/root/patched2/run/machine-id] ext4
>> ro,relatime,errors=remount-ro,data=ordered
>>
>> This explains the crash in mkosi and points the problem to something
>> that happens during the debootstrap run.
>>
>> I compared the output of debootstrap from unstable with the patched
>> debootstrap, and they are idential, i.e. packages are installed in the
>> same order, but for some reason, when running with the faster
>> debootstrap, the above mount is left over.
>>
>> Looking around, I suspect that this could be left behind by
>> systemd-machine-id-setup, however, I couldn't understand yet why this
>> would happen.
>>
>> systemd team: could you provide any insight? for reference, I am
>> attaching the current diff between debootstrap master branch, and a
>> local branch where I have Thomas Lange's patched applied.
> 
> I just stumbled over this today myself when using vmdebootstrap where I
> ran into the same issue as in [1]
> 
> As I couldn't reproduce the failure with cdebootstrap or debootstrap
> from stretch, I ran a git bisect against debootstrap.
> 
> The first faulty commit is
> https://salsa.debian.org/installer-team/debootstrap/commit/7e533a672ce413fc591b59e83f7c665c1a2e174e
> 
> And sure enough, reverting that commit fixed the dangling machine-id
> mount for me.
> 
> Henrich, do you want a bug report against debootstrap for that?

Fwiw, I didn't use systemd-nspawn or lxc.
All I did was run
# debootstrap sid /tmp/test-sid


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#871835: systemd-setup-machine-id leaving mount behind? (was "Bug#871835: Call for help: review patches for debootstrap")

[Michael Biebl]

Hi

Am 22.04.2018 um 15:09 schrieb Antonio Terceiro:

> # findmnt | grep machine-id
> ├─/root/patched2/etc/machine-id
> /dev/mapper/lemur--vg-root[/root/patched2/run/machine-id] ext4
> ro,relatime,errors=remount-ro,data=ordered
> 
> This explains the crash in mkosi and points the problem to something
> that happens during the debootstrap run.
> 
> I compared the output of debootstrap from unstable with the patched
> debootstrap, and they are idential, i.e. packages are installed in the
> same order, but for some reason, when running with the faster
> debootstrap, the above mount is left over.
> 
> Looking around, I suspect that this could be left behind by
> systemd-machine-id-setup, however, I couldn't understand yet why this
> would happen.
> 
> systemd team: could you provide any insight? for reference, I am
> attaching the current diff between debootstrap master branch, and a
> local branch where I have Thomas Lange's patched applied.

I just stumbled over this today myself when using vmdebootstrap where I
ran into the same issue as in [1]

As I couldn't reproduce the failure with cdebootstrap or debootstrap
from stretch, I ran a git bisect against debootstrap.

The first faulty commit is
https://salsa.debian.org/installer-team/debootstrap/commit/7e533a672ce413fc591b59e83f7c665c1a2e174e

And sure enough, reverting that commit fixed the dangling machine-id
mount for me.

Henrich, do you want a bug report against debootstrap for that?

Regards,
Micahel


[1] https://bugs.debian.org/899155
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#901299: appstream: autopkgtest regression: Package 'libxml-2.0', required by 'appstream', not found

[Matthias Klumpp]

2018-06-11 9:25 GMT+02:00 Paul Gevers :
> Source: appstream
> Version: 0.12.1-1
> User: debian...@lists.debian.org
> Usertags: regression
>
> Hi Matthias,
>
> With the upload of version 0.12.1-1 your autopkgtest¹ started to fail.
> I have copied the output below. Looking at the name of the test and the
> error message, I *assume* you could fix this by putting @builddeps@ in
> the test dependencies (you'll be able to drop the build-essential test
> dependency if you do).
>
> Could you please investigate and fix your autopkgtest? This is currently
> delaying the migration of your package to testing with 13 days.
>
> Paul
>
> ¹ https://ci.debian.net/packages/a/appstream/
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/a/appstream/441084/log.gz
>
> autopkgtest [23:08:34]: test build: [---
> Package libxml-2.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libxml-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libxml-2.0', required by 'appstream', not found
> asbuildtest.c:1:10: fatal error: appstream.h: No such file or directory
>  #include 
>   ^
> compilation terminated.
> autopkgtest [23:08:35]: test build: ---]

Hmm, this makes no sense... The dependencies of the software haven't
changed, and libxml2 is a private library dependency of libas, tools
should not have to link against it when using libappstream.
I'll need to take a closer look at this later, maybe Meson is doing
something weird again.

Cheers,
Matthias


-- 
I welcome VSRE emails. See http://vsre.info/

Bug#875643: firefox-esr: Can't specify external viewer like /usr/bin/emacsclient

[Stefan Monnier]

Ping?

Still seems to be the case with version 52.8.0


Stefan


Stefan  writes:

> Package: firefox-esr
> Version: 52.3.0esr-2
> Severity: normal
>
> Dear Maintainer,
>
> In older versions of Firefox, the dialog box which asked me whether
> I want to downoload the file or pass it to some external viewer
> let me choose the viewer via a file-selector, so I could very easily
> specify a viewer such as /usr/bin/emacsclient.
>
> Now I can't see to be able to do this any more.  All I can do is choose
> among a bunch of applications listed with their icons, emacsclient
> is not among them and I can't see any way to specify the application
> I want by giving its full file name.  This severely restricts the
> choice of external viewer for some file types.

Bug#782287: hw-detect: install open-vm-tools in d-i

[Bernd Zeimetz]

Hi again,

things have changed - thanks VMware - and I'd be happy to support
whatever is needed to make d-i install open-vm-tools when being run in a
VMware environment.

Regarding the suggested extra binary I'm wondering if dmidecode wouldn't
be appropriate to handle the detection of a virtualized environment as
dmidecode is shipping an udeb anyway.


Best regards,


Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#829134: debootstrap: Changes needed to support unprivileged userns debootstrap

[Johannes Schauer]

Hi,

On Thu, 08 Sep 2016 15:39:57 +0200 Johannes Schauer  wrote:
> On Thu, 30 Jun 2016 13:12:16 -0700 Ben Longbons  wrote:
> > Now that the kernel supports user_namespaces(7), it should be possible to
> > debootstrap in them. Some small changes are needed.
> > 
> > Configuration needed:
> > * Kernel 3.8 or later (3.11 recommended)
> > * Set the sysctl kernel.unprivileged_userns_clone to 1
> > (Debian-specific "temporary" patch from years ago).
> > * Install the `uidmap` package and add yourself to /etc/sub[ug]id
> > * Install the `lxc` package (for one helper binary only)
> > * Make sure the current directory is searchable by other.
> > 
> > I have attached the necessary changes as a wrapper script,
> 
> I find your script highly interesting!
> 
> A year ago I tried to write a tool that combined the powers of
> lxc-usernsexec(1) and unshare(1) because I was unable to combine them in a way
> that would give me both: correct mapping of user and group ids as well as
> unsharing the user namespace and others. I blogged about it here:
> 
> https://blog.mister-muffin.de/2015/10/25/unshare-without-superuser-privileges/
> 
> and the code is here:
> 
> https://gitlab.mister-muffin.de/josch/user-unshare/blob/master/user-unshare
> 
> I do not know whether what you demonstrated now in shell already worked one
> year ago (in particular I was not aware of the lxc-unshare tool) but your
> script works fine for me. I'm happy that it seems that I don't have to further
> dabble with the perl code I came up with because lxc-usernsexec and 
> lxc-unshare
> seem to be able to do the major grunt work while the rest can be done in 
> simple
> POSIX shell. Thank you!

The disadvantage of the lxc-usernsexec and lxc-unshare tools is, that they are
part of the lxc package. See bug #847491.

> I wonder though: why would this feature be useful for debootstrap? The
> resulting directory would have all the wrong ownership information. The
> directory would only be useful if its user knows exactly how to map the user
> ids between the host and the unshared user namespace.
> 
> So my practical question:
> 
> How do you use the chroots that you create in this fashion? Which commands do
> you use to work with them?

To answer my own question: by packing up the chroot into a tarball. The files
stored inside the tarball will have the correct permission.

I combined the insights from your tool with the Perl script I wrote and cited
above and added support to sbuild-createchroot to run debootstrap without
needing sudo but using Linux user namespaces.

Since debootstrap does not yet offer this functionality itself, I will carry
the code as part of sbuild. See the following two commits for details:

https://salsa.debian.org/debian/sbuild/commit/f21d63cca448a5fc90338319e2ea507623293060?expanded=1
https://salsa.debian.org/debian/sbuild/commit/53e250cdeb0035663833fa0c8ce80adf96d31c03?expanded=1

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#901419: RFS: streamlink/0.13.0+dfsg-1

[Alexis Murzeau]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "streamlink" for a new
upstream version 0.13.0.

 * Package name: streamlink
   Version : 0.13.0+dfsg-1
   Upstream Author : Streamlink Team
 * URL : https://streamlink.github.io/
 * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
   Section : python

It builds those binary packages:

  livestreamer - transitional package - streamlink
  python3-streamlink - Python module for extracting video streams from
various websites
  python3-streamlink-doc - CLI for extracting video streams from various
websites (documentation)
  streamlink - CLI for extracting video streams from various websites to
a video player

To access further information about this package, please visit the
following URL:
  https://mentors.debian.net/package/streamlink


Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_0.13.0+dfsg-1.dsc

More information about streamlink can be obtained from
https://streamlink.github.io/

Changes since the last upload:
streamlink (0.13.0+dfsg-1) unstable; urgency=low

  * Recommends all supported players (Closes: #898351)
  * Update upstream signing key with 0xE3DB9E282E390FA0
  * New upstream version 0.13.0+dfsg
  * Patches changes:
- Use font-awesome 5 shim
- Use modernizr.js symlink
- Fix tests executions by adding missing mpd files
- Avoid lambda with freezegun to support <= v0.3.9
- rtlxl plugin: use raw string to fix escape sequences
- Forwarded new patches to upstream
- Update patch remove_new_version_check
  * Add new build dependencies freezegun, recommonmark and isodate
  * Update autopkgtests for font files and js symlinks

 -- Alexis Murzeau   Tue, 12 Jun 2018 23:52:56 +0200


Regards,
--
 Alexis Murzeau
 PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F








signature.asc
Description: OpenPGP digital signature

Bug#897308: O: ruby-setup -- the setup.rb install tool for Ruby

[Antonio Terceiro]

On Tue, 01 May 2018 12:17:17 +0200 Vincent Fourmond  wrote:
> Package: wnpp
> Severity: normal
> 
> 
>   Hello,
> 
>   I intend to orphan the ruby-setup package. It is technically
> team-maintained by the Debian Ruby team, but the other listed uploader
> hasn't touched the package for a very long time, so I prefer to mark
> the package as orphaned. It is used by some package for their build
> procedure.
> 
>   Kind regards,
> 
> Vincent
> 
> The package description is:
>  setup.rb is an installation tool widely used for Ruby
>  programs. You can use it to distribute Ruby code you wrote
>  and be sure your users won't have difficulties installing
>  it.

currently only two packages depend on ruby-setup to build: ruby-tioga
and ruby-facets.

given that setup.rb is deprecated for a very long time -- the Ruby
community completely moved to rubygems -- IMO we should:

- migrate those packages away from ruby-setup
- remove support for ruby-setup from gem2deb
- remove ruby-setup from the archive


signature.asc
Description: PGP signature

Bug#901418: RFS: osmose-emulator/1.2-2 -- Sega Master System and Game Gear console emulator

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "osmose-emulator"

 * Package name: osmose-emulator
   Version : 1.2-2
   Upstream Author : Carlos Donizete Froes 
 * URL : https://gitlab.com/coringao/osmose-emulator
 * License : GPL-3+
   Section : games

  It builds those binary packages:

  osmose-emulator - Sega Master System and Game Gear console emulator

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/osmose-emulator

  Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/o/osmose-emulator/osmose-emulator_1.2-2.dsc

  More information about Osmose Emulator can be obtained from 
https://gitlab.com/coringao/osmose-emulator/wikis.

  Changes since the last upload:

  * Switch to compat level 11
  * debian/control:
+ Bump debhelper compat to 11
+ Declare compliance with Debian Policy: 4.1.4
+ Changed homepage URL to GitLab
+ Move Vcs URLs to salsa.d.g
  * debian/copyright:
+ Update source URL move to GitLab
+ Year updated on 'Files: debian/*'
  * Updated d/upstream/metadata URLs move to GitLab
  * Updated d/watch file upstream move to GitLab

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Bug#895482: Bug#895473: Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

[Axel Beckert]

Hi Sebastian,

Sebastian Andrzej Siewior wrote:
> > I don't think so unless a future upload of OpenSSL to unstable fixes
> > this. The recent one to unstable didn't.
> 
> forwarded https://github.com/openssl/openssl/issues/6475
> 
> Just a little question: The missing certificates:
> |rehash: error: skipping Swisscom_Root_CA_1.pem, cannot open file
> |rehash: error: skipping Swisscom_Root_CA_2.pem, cannot open file
> |rehash: error: skipping GeoTrust_Global_CA_2.pem, cannot open file
> |rehash: error: skipping Swisscom_Root_EV_CA_2.pem, cannot open file
> 
> where are they from?

From the ca-certificates package I assume. At least those errors go
away if I downgrade to 20170717 again and they reappear as soon as I
upgrade to 20180409 on that machine. At least the file names are the
same as in my mail from 12th of April[1] (just in different order).

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895482#10

I just checked: All four CAs are CAs I've chosen to be enabled. But
they're by far not the only CAs which are enabled from ca-certificates
on that machine. So I have no idea what makes those four special.

From debconf-get-selections:

ca-certificates ca-certificates/enable_crts multiselect 
CAcert/class3.crt, CAcert/root.crt, 
mozilla/COMODO_RSA_Certification_Authority.crt, 
mozilla/DigiCert_Assured_ID_Root_CA.crt, mozilla/DigiCert_Global_Root_CA.crt, 
mozilla/DigiCert_High_Assurance_EV_Root_CA.crt, mozilla/DST_Root_CA_X3.crt, 
mozilla/GeoTrust_Global_CA_2.crt, mozilla/GeoTrust_Global_CA.crt, 
mozilla/GeoTrust_Primary_Certification_Authority.crt, 
mozilla/GeoTrust_Primary_Certification_Authority_-_G2.crt, 
mozilla/GeoTrust_Primary_Certification_Authority_-_G3.crt, 
mozilla/GeoTrust_Universal_CA_2.crt, mozilla/GeoTrust_Universal_CA.crt, 
mozilla/IdenTrust_Commercial_Root_CA_1.crt, 
mozilla/IdenTrust_Public_Sector_Root_CA_1.crt, mozilla/ISRG_Root_X1.crt, 
mozilla/QuoVadis_Root_CA_1_G3.crt, mozilla/QuoVadis_Root_CA_2.crt, 
mozilla/QuoVadis_Root_CA_2_G3.crt, mozilla/QuoVadis_Root_CA_3.crt, 
mozilla/QuoVadis_Root_CA_3_G3.crt, mozilla/QuoVadis_Root_CA.crt, 
mozilla/Swisscom_Root_CA_1.crt, mozilla/Swisscom_Root_CA_2.crt, 
mozilla/Swisscom_Root_EV_CA_2.crt, mozilla/SwissSign_Gold_CA_-_G2.crt, 
mozilla/SwissSign_Silver_CA_-_G2.crt, mozilla/thawte_Primary_Root_CA.crt, 
mozilla/thawte_Primary_Root_CA_-_G2.crt, 
mozilla/thawte_Primary_Root_CA_-_G3.crt, 
mozilla/Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.crt, 
mozilla/VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.crt, 
mozilla/VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.crt, 
mozilla/VeriSign_Universal_Root_Certification_Authority.crt,

> Is there something specific you did to get those
> symlinks which now don't belong to a real file?

No. As mentioned in the initial report, I have ca-certificates to ask
me every time on new CAs if I want to enable them or not. And I'm
rather conservative with enabling CAs. I also do this on most of my
machines, usually with slight differences in the list of enabled CAs.
Nevertheless this only happened on two of my machines.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#900920: freedink-dfarc 3.12-1+deb9u1 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: freedink-dfarc
Version: 3.12-1+deb9u1

Explanation: fix directory traversal in D-Mod extractor [CVE-2018-0496]

Bug#899006: intel-microcode 3.20180425.1~deb9u1 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: intel-microcode
Version: 3.20180425.1~deb9u1

Explanation: update included microcode, including fixes for Spectre v2 
[CVE-2017-5715]

Bug#901033: postgresql-common 181+deb9u2 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: postgresql-common
Version: 181+deb9u2

Explanation: prevent upgrading/removing server packages from stopping other 
major version clusters when running systemd

Bug#896689: dpdk 16.11.6-1+deb9u1 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: dpdk
Version: 16.11.6-1+deb9u1

Explanation: new upstream stable update

Bug#901381: FTBFS: depend on debhelper >= 9.20160114 for --dbgsym-migration

[Michael Biebl]

Am 12.06.2018 um 12:03 schrieb pmoulder:
> Source: cairo
> Version: 1.14.8-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Building cairo_1.14.8-1 failed for me, giving
> 
>   Unknown option: dbgsym-migration
>   dh_strip: unknown option; aborting
> 
> on stderr (presumably from the line in debian/rules).
> 
> I upgraded debhelper to version 10.2.5, and then the cairo build
> succeeded.
> 
> Searching /usr/share/doc/debhelper/changelog.gz for "dbgsym-migration"
> finds under the debhelper 9.20160114 entry the item
> 
>   * dh_strip: Add "--(no-)automatic-dbgsym" and "--dbgsym-migration"
> options to replace "--(no-)ddebs" and "--ddeb-migration".
> (Closes: #810948)
> 
> Accordingly, I suggest adjusting the Build-Depends from
> "debhelper (>= 9)" to "debhelper (>= 9.20160114)".

I suppose we should just drop that dh_strip override for all those
packages for which the dbgsym migration has been done in stretch.
Keeping that migration code for one release cycle should be enough.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#899014: blktrace 1.1.0-2+deb9u1 flagged for acceptance

['Adam]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: blktrace
Version: 1.1.0-2+deb9u1

Explanation: fix buffer overflow in btt [CVE-2018-10689]

Bug#898090: apt-show-versions

[jeffwinkfein]

i get the same exact error when trying to install apt-show-versions
(.22.7)

running: kali 2018.2; mate; no extra ppas; nvidia-legacy-340; i5;
16gram

Bug#895482: Bug#895473: Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

[Sebastian Andrzej Siewior]

On 2018-06-12 22:29:42 [+0200], Axel Beckert wrote:
> Shall I try the version from Experimental, too?
no.

> > (Should some Breaks be added, Depends made stricter?)
> 
> I don't think so unless a future upload of OpenSSL to unstable fixes
> this. The recent one to unstable didn't.

forwarded https://github.com/openssl/openssl/issues/6475

Just a little question: The missing certificates:
|rehash: error: skipping Swisscom_Root_CA_1.pem, cannot open file
|rehash: error: skipping Swisscom_Root_CA_2.pem, cannot open file
|rehash: error: skipping GeoTrust_Global_CA_2.pem, cannot open file
|rehash: error: skipping Swisscom_Root_EV_CA_2.pem, cannot open file

where are they from? Is there something specific you did to get those
symlinks which now don't belong to a real file?

>   Regards, Axel

Sebastian

Bug#901417: debian-archive-keyring: http://ftp.us.debian.org/debian/dists/buster/Release.gpg has no public key

[Matt Bacchi]

Package: debian-archive-keyring
Version: Unknown
Severity: normal

While trying to sign a chromium package I get an error:

gpgv: Can't check signature: public key not found


I tracked it down and found the buster Release.gpg key indeed doesn't
appear to have a valid public key:

[user@host Downloads]$ wget
http://ftp.us.debian.org/debian/dists/buster/Release.gpg
--2018-06-12 17:36:18--
http://ftp.us.debian.org/debian/dists/buster/Release.gpg
Resolving ftp.us.debian.org (ftp.us.debian.org)... 208.80.154.15,
128.30.2.26, 128.61.240.89, ...
Connecting to ftp.us.debian.org (ftp.us.debian.org)|208.80.154.15|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 2365 (2.3K) [application/octet-stream]
Saving to: ‘Release.gpg’

Release.gpg
100%[===>]
 2.31K  --.-KB/sin 0s

2018-06-12 17:36:18 (96.0 MB/s) - ‘Release.gpg’ saved [2365/2365]

[user@host Downloads]$ gpg --list-keys Release.gpg
gpg: error reading key: public key not found


Thanks for your assistance.
-Matt

Bug#901403: RM: xf86-video-glamo -- ROM; package broken since 2 years

[Gilles Filippini]

Hi,

Luca Capello a écrit le 12/06/2018 à 21:54 :
> Hi there,
> 
> On Tue, 12 Jun 2018 17:24:22 +0200, Sebastian Reichel wrote:
>> The source package does not build for "new" Xorg from 2016,
>> has been removed from testing and was not part of last stable
>> release. Upstream seems to be dead since 2011:
>>
>> https://github.com/openmoko/xf86-video-glamo
>>
>> FWIW I never worked on xf86-video-glamo myself, but I'm one of
>> the last persons who worked on the FSO packages. I Cc'd the
>> persons involved with glamo, so that they can intervene.
> 
> I was responsible back in 2009 for the first upload, but then Timo
> Jyrinki and Gilles Filippini (both Bcc:ed) took care of it.  Also
> because I left the pkg-fso team back in 2012:
> 
>   
> 
> 
> And FWIW I was quite surprised this package was still in Debian, since I
> know no other devices than the OpenMoko Neo FreeRunner using it (on
> Debian).
> 
> I fully support its removal, also because of the two other serious bugs:
> 
> - 
>   FTBFS with xserver 1.19
> 
> - 
>   xf86-video-glamo: Invalid maintainer address 
> pkg-fso-ma...@lists.alioth.debian.org

+1 for removal.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Bug#901289: Drop the `logsave` requirement in `/etc/init.d/checkfs.sh`.

[Adam Borowski]

On Mon, Jun 11, 2018 at 12:01:34AM -0400, Gong S wrote:
> Package: initscripts
> Version: 2.88dsf-59.10
> 
> The current version used `logsave` to save `fsck` results.
> When `logsave` is not present, the script will fail regardless of the actual 
> FS state.
> /etc/init.d/checkfs.sh line 101 and 121:
> logsave -s $FSCK_LOGFILE fsck $spinner -M -A $fix $force $FSCKTYPES_OPT
> `logsave` is a part of `e2fsprogs`. If I do not use EXT filesystems (I use 
> JFS on my PC) I can purge this package.
> 
> My suggestion:
> 1. Do not use `logsave`. The process is not there in previous versions.or:
> 2. If `logsave` is not found just check the FS without using `logsave`.

Or 3. copy or move logsave to the initscripts package (it's arch:any so can
take compiled code).  This is a stand-alone tool that makes no use of any
part of e2fsprogs nor of its build system.  All autoconfage is bogus, too,
re-checking things that are mandated by POSIX.

As for fsck: isn't jfs one of the remaining filesystems that still do fsck
at boot?  Most others (xfs, btrfs, reiserfs, ...) have long since dropped
this, as in-kernel recovery is good enough.  I guess jfs and ext3/4 can
likewise drop fsck this way.  We'd need fsck and thus logsave only for
ancient stuff like ext2 or minix.  Not sure if you can even install Debian
to minix fs; I wish ext2 was gone but Hurd still doesn't support anything
better.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts
⣾⠁⢰⠒⠀⣿⡁ productivity.  You can read it, too, you just need the
⢿⡄⠘⠷⠚⠋⠀ right music while doing so.  I recommend Skepticism
⠈⠳⣄ (funeral doom metal).

Bug#809491: (no subject)

[Daniel Scharrer]

The newly released innoextract 1.7 provides --list-sizes and --list-checksums
options that (together with --silent) print the needed information in a simple
fomrat:

size + space + hash type + space + hash + space + remainder = name

Bug#901238: Acknowledgement (wnorwegian: Both word list files should be in UTF-8, not in ISO-8859 anymore)

[Tollef Fog Heen]

]] Pander 

> But these symbolic links are dubious:
> 
> /usr/share/dict/norsk -> /etc/dictionaries-common/norsk
> /etc/dictionaries-common/norsk -> /usr/share/dict/bokmaal

I'm not sure what you think is dubious about this.

> And the following symbolic link should be used instead:
> 
> /usr/share/dict/norsk -> /usr/share/dict/nynorsk

That's configuration that's up to the admin which of the two different
forms of Norwegian should be used as the Norwegian dictionary on the
system.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#901412: ITP: ibmquantumexperience -- A Python library for the IBM Quantum Experience API (Python 3)

[Guus Sliepen]

> * Package name: ibmquantumexperience
>   Description : A Python library for the IBM Quantum Experience API  
> (Python 3)

If it's a Python 3 library, the package name should have the python3- prefix, 
and you
might want to consider naming it (python3-)qiskit instead of 
(python3-)ibmquantumexperience.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature

Bug#901414: ITP: sxx -- sxx is a tool that allows you to easily run shell commands on multiple hosts, copy ssh keys or transfer files to multiple hosts

[Eric Curtin]

Package: wnpp
Severity: wishlist

sxx -- sxx is a tool that allows you to easily run shell commands on
multiple hosts,  copy ssh keys or transfer files to multiple hosts

thanks

I will adopt sxx package.

Bug#895482: Bug#895473: Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

[Axel Beckert]

Hi Kurt,

Kurt Roeckx wrote:
> > > Given that this openssl update is now in testing, should we close or at
> > > least downgrade this bug so ca-certificates can migrate?
> > 
> > I just unhold ca-certificates 20170717 and upgraded it to 20180409 on
> > one of my affected machines (the i386 one) and unfortunately, the
> > issue (at least mine, which is #895482 with exit status 4, so only
> > Cc'ing that bug report) doesn't seem to fixed:
> 
> Which openssl version do you have installed?

Valid question. I should have mentioned that explicitly.

It's the current version from unstable/testing:

104/0/0 root@loadrunner:pts/3 22:16:35 [~] # apt-cache policy openssl
openssl:
  Installed: 1.1.0h-4
  Candidate: 1.1.0h-4
  Version table:
 1.1.1~~pre7-1 110
110 https://debian.ethz.ch/debian experimental/main i386 Packages
 *** 1.1.0h-4 990
990 https://debian.ethz.ch/debian sid/main i386 Packages
500 https://debian.ethz.ch/debian testing/main i386 Packages
100 /var/lib/dpkg/status
105/0/0 root@loadrunner:pts/3 22:26:00 [~] # 

Shall I try the version from Experimental, too?

> (Should some Breaks be added, Depends made stricter?)

I don't think so unless a future upload of OpenSSL to unstable fixes
this. The recent one to unstable didn't.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#901413: mnemosyne: Mnemosyne 2.6 does not find cheroot module

[Felix Gruber]

Package: mnemosyne
Version: 2.6+ds-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

when starting Mnemosyne 2.6 it immediately exits with the following
error message:

---8<8<8<8<---
Log body An unexpected error has occurred.
Please forward the following info to the developers:

Traceback (innermost last):
  File "/usr/bin/mnemosyne", line 262, in 
debug_file=options.debug_file)
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 200, in initialise
self.activate_components()
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 296, in activate_components
sync_server.activate()
  File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/qt_sync_server.py",
line 196, in activate
component_manager=self.component_manager)
  File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/qt_sync_server.py",
line 67, in __init__
super().__init__(ui=self, **kwds)
  File
"/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/sync_server.py",
line 31, in __init__
port=config["sync_server_port"], **kwds)
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/component.py",
line 57, in __init__
super().__init__(**kwds)  # For parent classes other than 'Object'.
  File "/usr/lib/python3/dist-packages/openSM2sync/server.py", line 98,
in __init__
from cheroot import wsgi
 ModuleNotFoundError: No module named 'cheroot'

An unexpected error has occurred.
Please forward the following info to the developers:

Traceback (innermost last):
  File "/usr/bin/mnemosyne", line 262, in 
debug_file=options.debug_file)
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 200, in initialise
self.activate_components()
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 296, in activate_components
sync_server.activate()
  File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/qt_sync_server.py",
line 196, in activate
component_manager=self.component_manager)
  File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/qt_sync_server.py",
line 67, in __init__
super().__init__(ui=self, **kwds)
  File
"/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/sync_server.py",
line 31, in __init__
port=config["sync_server_port"], **kwds)
  File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/component.py",
line 57, in __init__
super().__init__(**kwds)  # For parent classes other than 'Object'.
  File "/usr/lib/python3/dist-packages/openSM2sync/server.py", line 98,
in __init__
from cheroot import wsgi
 ModuleNotFoundError: No module named 'cheroot'
--->8>8>8>8---

This is doe to the missing cheroot Python package.
See also this discussion upstream:
https://groups.google.com/d/topic/mnemosyne-proj-users/mcuTpPIH61k/discussion

Currently, we do not have packaged cheroot in Debian.
To resolve this bug, we need to create a python3-cheroot package in
Debian and make mnemosyne depend on it. Cheroot can be obtained from
https://pypi.org/project/Cheroot/

Best regards,
Felix



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

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

Versions of packages mnemosyne depends on:
ii  libjs-sphinxdoc 1.7.4-1
ii  libqt5sql5-sqlite   5.10.1+dfsg-7
ii  python3 3.6.5-3
ii  python3-cherrypy3   8.9.1-2
ii  python3-matplotlib  2.2.2-4
ii  python3-pyqt5   5.10.1+dfsg-2
ii  python3-pyqt5.qtsql 5.10.1+dfsg-2
ii  python3-pyqt5.qtwebchannel  5.10.1+dfsg-2
ii  python3-pyqt5.qtwebengine   5.10.1+dfsg-2
ii  python3-webob   1:1.7.3-2

mnemosyne recommends no packages.

mnemosyne suggests no packages.

-- no debconf information

Bug#901409: Very low FPS in Nexuiz after Darkplaces upgrade

[Evgeny Kapun]

On 12.06.2018 22:28, Simon McVittie wrote:

On Tue, 12 Jun 2018 at 21:27:06 +0300, Evgeny Kapun wrote:

After I upgraded Darkplaces to version 0~20180412~beta1-2 (from
0~20140513+svn12208-7), Nexuiz slowed down to about 8 frames per second,
which made it unplayable. With the previous version, I could get 30-40
FPS on most maps.


What video hardware is this on?

Are you using X11 or Wayland or what? Which desktop environment, if any?

Would you be able to try an intermediate version from
?
That might help to locate what has caused that slowdown.

 smcv



Video hardware: Mobile Intel GM45 Express Chipset.
Software: X.Org X Server 1.19.6.
Desktop environment: LXDE.

Version 0~20170829~beta1-1 is also slow, so the regression is between versions 
0~20140513+svn12208-7 and 0~20170829~beta1-1.

Bug#896726: gedit-source-code-browser-plugin: diff for NMU version 3.0.3-5.1

[Pietro Battiston]

Dear Adrian,

Il giorno dom, 10/06/2018 alle 16.44 +0300, Adrian Bunk ha scritto:
> I've prepared an NMU for gedit-source-code-browser-plugin (versioned
> as 
> 3.0.3-5.1) and uploaded it to DELAYED/15. 

Thanks, this is much appreciated.

Pietro

Bug#895936: stretch-pu: package patch/2.7.5-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2018-04-17 at 17:45 +0200, Laszlo Boszormenyi (GCS) wrote:
> I'd like to fix CVE-2018-1000156 in patch for Stretch, which is an
> arbitrary command execution in ed-style patches.
> While it might be used for remote compromise, it would need a setup
> to
> accept patches unconditionally. But then an attacker has an easy path
> already to insert vulnerable code to source files or JavaScript
> injection to HTML pages, etc. Hence it doesn't warrant a DSA on its
> own, but would be good to fix in a point release.
> 

Please go ahead.

Regards,

Adam

Bug#895482: Bug#895473: Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

[Kurt Roeckx]

On Tue, Jun 12, 2018 at 09:57:56PM +0200, Axel Beckert wrote:
> Hi,
> 
> Thijs Kinkhorst wrote:
> > >> I've read about this bug (and the other one) on d-devel. I uploaded
> > >> recently a new version of openssl to unstable (1.1.0h-3)which changes
> > >> the exit code of "openssl rehash" to zero in case of a duplicate or if a
> > >> certificate can no be open.
> > >> I left this bug open in case the maintainer of this package wants to
> > >> investigate why there are duplicates or non-existing certificates.
> > >
> > > Thanks for the update, Sebastian.
> > >
> > > OpenSSL commit for my own reference and for others, if interested:
> > > https://github.com/openssl/openssl/commit/e6a833cb97ed762408b57ea3efa83bd10c1d2a78
> > 
> > Given that this openssl update is now in testing, should we close or at
> > least downgrade this bug so ca-certificates can migrate?
> 
> I just unhold ca-certificates 20170717 and upgraded it to 20180409 on
> one of my affected machines (the i386 one) and unfortunately, the
> issue (at least mine, which is #895482 with exit status 4, so only
> Cc'ing that bug report) doesn't seem to fixed:

Which openssl version do you have installed?

(Should some Breaks be added, Depends made stricter?)


Kurt

Bug#901403: RM: xf86-video-glamo -- ROM; package broken since 2 years

[Luca Capello]

Hi there,

On Tue, 12 Jun 2018 17:24:22 +0200, Sebastian Reichel wrote:
> The source package does not build for "new" Xorg from 2016,
> has been removed from testing and was not part of last stable
> release. Upstream seems to be dead since 2011:
> 
> https://github.com/openmoko/xf86-video-glamo
> 
> FWIW I never worked on xf86-video-glamo myself, but I'm one of
> the last persons who worked on the FSO packages. I Cc'd the
> persons involved with glamo, so that they can intervene.

I was responsible back in 2009 for the first upload, but then Timo
Jyrinki and Gilles Filippini (both Bcc:ed) took care of it.  Also
because I left the pkg-fso team back in 2012:

  


And FWIW I was quite surprised this package was still in Debian, since I
know no other devices than the OpenMoko Neo FreeRunner using it (on
Debian).

I fully support its removal, also because of the two other serious bugs:

- 
  FTBFS with xserver 1.19

- 
  xf86-video-glamo: Invalid maintainer address 
pkg-fso-ma...@lists.alioth.debian.org

Thx, bye,
Gismo / Luca


signature.asc
Description: PGP signature

Bug#899030: intel-microcode 3.20180425.1~deb8u1 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian jessie.

Thanks for your contribution!

Upload details
==

Package: intel-microcode
Version: 3.20180425.1~deb8u1

Explanation: update included microcode, including fixes for Spectre v2 
[CVE-2017-5715]

Bug#895482: Bug#895473: Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

[Axel Beckert]

Hi,

Thijs Kinkhorst wrote:
> >> I've read about this bug (and the other one) on d-devel. I uploaded
> >> recently a new version of openssl to unstable (1.1.0h-3)which changes
> >> the exit code of "openssl rehash" to zero in case of a duplicate or if a
> >> certificate can no be open.
> >> I left this bug open in case the maintainer of this package wants to
> >> investigate why there are duplicates or non-existing certificates.
> >
> > Thanks for the update, Sebastian.
> >
> > OpenSSL commit for my own reference and for others, if interested:
> > https://github.com/openssl/openssl/commit/e6a833cb97ed762408b57ea3efa83bd10c1d2a78
> 
> Given that this openssl update is now in testing, should we close or at
> least downgrade this bug so ca-certificates can migrate?

I just unhold ca-certificates 20170717 and upgraded it to 20180409 on
one of my affected machines (the i386 one) and unfortunately, the
issue (at least mine, which is #895482 with exit status 4, so only
Cc'ing that bug report) doesn't seem to fixed:

Performing actions...
Preconfiguring packages ...
(Reading database ... 936122 files and directories currently installed.)
Preparing to unpack .../ca-certificates_20180409_all.deb ...
Unpacking ca-certificates (20180409) over (20170717) ...
[…]
Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
W: /usr/share/ca-certificates/mozilla/GeoTrust_Global_CA_2.crt not found, but 
listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/Swisscom_Root_CA_1.crt not found, but 
listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/Swisscom_Root_CA_2.crt not found, but 
listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/Swisscom_Root_EV_CA_2.crt not found, but 
listed in /etc/ca-certificates.conf.
rehash: error: skipping Swisscom_Root_CA_1.pem, cannot open file
rehash: error: skipping Swisscom_Root_CA_2.pem, cannot open file
rehash: error: skipping GeoTrust_Global_CA_2.pem, cannot open file
rehash: error: skipping Swisscom_Root_EV_CA_2.pem, cannot open file
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 4
Processing triggers for hicolor-icon-theme (0.17-2) ...
Setting up libcups2:i386 (2.2.8-3) ...
Setting up libcupsimage2:i386 (2.2.8-3) ...
Processing triggers for libc-bin (2.27-3) ...
Errors were encountered while processing:
 ca-certificates
[master c040eace] committing changes in /etc after apt run
 45 files changed, 1039 deletions(-)
 delete mode 12 ssl/certs/00673b5b.0
 delete mode 12 ssl/certs/034868d6.0
 delete mode 12 ssl/certs/12d55845.0
 delete mode 12 ssl/certs/1f58a078.0
 delete mode 12 ssl/certs/27af790d.0
 delete mode 12 ssl/certs/399e7759.0
 delete mode 12 ssl/certs/3c860d51.0
 delete mode 12 ssl/certs/3efd4dc0.0
 delete mode 12 ssl/certs/450c6e38.0
 delete mode 12 ssl/certs/4be590e0.0
 delete mode 12 ssl/certs/5046c355.0
 delete mode 12 ssl/certs/524d9b43.0
 delete mode 12 ssl/certs/52b525c7.0
 delete mode 12 ssl/certs/57692373.0
 delete mode 12 ssl/certs/5cf9d536.0
 delete mode 12 ssl/certs/5d66db40.0
 delete mode 12 ssl/certs/5e4e69e7.0
 delete mode 12 ssl/certs/5ed36f99.0
 delete mode 12 ssl/certs/6187b673.0
 delete mode 12 ssl/certs/667c66d4.0
 delete mode 12 ssl/certs/67495436.0
 delete mode 12 ssl/certs/69105f4f.0
 delete mode 12 ssl/certs/7999be0d.0
 delete mode 12 ssl/certs/7a819ef2.0
 delete mode 12 ssl/certs/7d453d8f.0
 delete mode 12 ssl/certs/8028ce6e.0
 delete mode 12 ssl/certs/81b9768f.0
 delete mode 12 ssl/certs/87753b0d.0
 delete mode 12 ssl/certs/9339512a.0
 delete mode 12 ssl/certs/9772ca32.0
 delete mode 12 ssl/certs/9ab62355.0
 delete mode 12 ssl/certs/9f129ada.0
 delete mode 12 ssl/certs/a7d2cf64.0
 delete mode 12 ssl/certs/c7e2a638.0
 delete mode 100644 ssl/certs/ca-certificates.crt
 delete mode 12 ssl/certs/cbeee9e2.0
 delete mode 12 ssl/certs/d18e9066.0
 delete mode 12 ssl/certs/d4c339cb.0
 delete mode 12 ssl/certs/e442e424.0
 delete mode 12 ssl/certs/e5662767.0
 delete mode 12 ssl/certs/e60bf0c0.0
 delete mode 12 ssl/certs/e775ed2d.0
 delete mode 12 ssl/certs/e9f92b43.0
 delete mode 12 ssl/certs/facacbc6.0
[…]
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
W: /usr/share/ca-certificates/mozilla/GeoTrust_Global_CA_2.crt not found, but 
listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/Swisscom_Root_CA_1.crt not found, but 
listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/Swisscom_Root_CA_2.crt not found, but 
listed in /etc/ca-certificates.conf.
W: 

Bug#885584: ncurses 5.9+20140913-1+deb8u3 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian jessie.

Thanks for your contribution!

Upload details
==

Package: ncurses
Version: 5.9+20140913-1+deb8u3

Explanation: fix buffer overflow in the _nc_write_entry function 
[CVE-2017-16879]

Bug#887047: dh-make-perl 0.84-2+deb8u1 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian jessie.

Thanks for your contribution!

Upload details
==

Package: dh-make-perl
Version: 0.84-2+deb8u1

Explanation: support Contents file without header

Bug#899018: blktrace 1.0.5-1+deb8u1 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian jessie.

Thanks for your contribution!

Upload details
==

Package: blktrace
Version: 1.0.5-1+deb8u1

Explanation: fix buffer overflow in btt [CVE-2018-10689]

Bug#895935: patch 2.7.5-1+deb8u1 flagged for acceptance

['Adam D . Barratt']

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian jessie.

Thanks for your contribution!

Upload details
==

Package: patch
Version: 2.7.5-1+deb8u1

Explanation: fix arbitrary command execution in ed-style patches 
[CVE-2018-1000156]

Bug#901412: ITP: ibmquantumexperience -- A Python library for the IBM Quantum Experience API (Python 3)

[Luciano Bello]

Package: wnpp
Severity: wishlist
Owner: Luciano Bello 

* Package name: ibmquantumexperience
  Version : 1.9.2
  Upstream Author : QISKit 
* URL : https://github.com/QISKit/qiskit-api-py
* License : Apache 2.0
  Programming Lang: Python
  Description : A Python library for the IBM Quantum Experience API  
(Python 3)



This is needed for #880994

Bug#901411: liblasso-perl: SHA256 signature verification fails sometimes, please upgrade to 2.5.1

[Xavier Guimard]

Package: liblasso-perl
Version: 2.5.0-5+b4
Severity: normal
Tags: fixed-upstream

Hi Frederic,

when using SHA256, SLO fails (Redirect+ IdP initiated for example). It
looks like this is fixed with 2.5.1 (verified with Ubuntu which uses
this version). Could you update Debian Lasso version to ≥ 2.5.1 ?

Best regards,
Xavier

NB: if you want some help, my Salsa account is xguimard-guest. I'm just
DM but I can help to prepare packages.

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

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

Versions of packages liblasso-perl depends on:
ii  libc6   2.27-3
ii  libglib2.0-02.56.1-2
ii  liblasso3   2.5.0-5+b4
ii  libssl1.1   1.1.0h-4
ii  libxml2 2.9.4+dfsg1-7
ii  libxmlsec1  1.2.25-2
ii  libxmlsec1-openssl  1.2.25-2
ii  libxslt1.1  1.1.32-2
ii  perl5.26.2-5
ii  perl-base [perlapi-5.26.0]  5.26.2-5
ii  zlib1g  1:1.2.11.dfsg-1

liblasso-perl recommends no packages.

liblasso-perl suggests no packages.

-- no debconf information

Bug#901410: openjdk-11: Please include sparc64 build fixes

[John Paul Adrian Glaubitz]

Source: openjdk-11
Version: 11~17-2
Severity: normal
Tags: patch upstream
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hello!

The two attached patches fix the openjdk-11 build on sparc64:

- JDK-8203301 - https://bugs.openjdk.java.net/browse/JDK-8203301
- JDK-8203787 - https://bugs.openjdk.java.net/browse/JDK-8203787

The latter of the two bugs has already been fixed upstream, the first
patch needs a second reviewer but I assume I can push the fix for the
Flight Recorder regression this week once I have a second ack.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
# HG changeset patch
# User glaubitz
# Date 1528818309 -7200
#  Tue Jun 12 17:45:09 2018 +0200
# Node ID 8e5f28a9bab3fe554a2dc2c2e8970258f27d927a
# Parent  04f4e983c2f77d935641f89668aa3c4ccf8bffdd
8203301: Linux-sparc fails to build after JDK-8199712 (Flight Recorder)

diff -r 04f4e983c2f7 -r 8e5f28a9bab3 
src/hotspot/cpu/sparc/vm_version_ext_sparc.cpp
--- a/src/hotspot/cpu/sparc/vm_version_ext_sparc.cppTue Jun 12 07:52:30 
2018 -0700
+++ b/src/hotspot/cpu/sparc/vm_version_ext_sparc.cppTue Jun 12 17:45:09 
2018 +0200
@@ -31,10 +31,13 @@
 int   VM_Version_Ext::_no_of_threads = 0;
 int   VM_Version_Ext::_no_of_cores = 0;
 int   VM_Version_Ext::_no_of_sockets = 0;
+#if defined(SOLARIS)
 kid_t VM_Version_Ext::_kcid = -1;
+#endif
 char  VM_Version_Ext::_cpu_name[CPU_TYPE_DESC_BUF_SIZE] = {0};
 char  VM_Version_Ext::_cpu_desc[CPU_DETAILED_DESC_BUF_SIZE] = {0};
 
+#if defined(SOLARIS)
 // get cpu information. It takes into account if the kstat chain id
 // has been changed and update the info if necessary.
 bool VM_Version_Ext::initialize_cpu_information(void) {
@@ -144,6 +147,13 @@
   kstat_close(kc);
   return true;
 }
+#elif defined(LINUX)
+// get cpu information.
+bool VM_Version_Ext::initialize_cpu_information(void) {
+  // Not yet implemented.
+  return false;
+}
+#endif
 
 int VM_Version_Ext::number_of_threads(void) {
   initialize_cpu_information();
diff -r 04f4e983c2f7 -r 8e5f28a9bab3 
src/hotspot/cpu/sparc/vm_version_ext_sparc.hpp
--- a/src/hotspot/cpu/sparc/vm_version_ext_sparc.hppTue Jun 12 07:52:30 
2018 -0700
+++ b/src/hotspot/cpu/sparc/vm_version_ext_sparc.hppTue Jun 12 17:45:09 
2018 +0200
@@ -27,8 +27,11 @@
 
 #include "utilities/macros.hpp"
 #include "vm_version_sparc.hpp"
+
+#if defined(SOLARIS)
 #include 
 #include 
+#endif
 
 #define CPU_INFO"cpu_info"
 #define CPU_TYPE"fpu_type"
@@ -45,7 +48,9 @@
   static int   _no_of_threads;
   static int   _no_of_cores;
   static int   _no_of_sockets;
+#if defined(SOLARIS)
   static kid_t _kcid;
+#endif
   static char  _cpu_name[CPU_TYPE_DESC_BUF_SIZE];
   static char  _cpu_desc[CPU_DETAILED_DESC_BUF_SIZE];
 
diff -r 04f4e983c2f7 -r 8e5f28a9bab3 
src/hotspot/os_cpu/linux_sparc/thread_linux_sparc.cpp
--- a/src/hotspot/os_cpu/linux_sparc/thread_linux_sparc.cpp Tue Jun 12 
07:52:30 2018 -0700
+++ b/src/hotspot/os_cpu/linux_sparc/thread_linux_sparc.cpp Tue Jun 12 
17:45:09 2018 +0200
@@ -35,6 +35,13 @@
   return frame(last_Java_sp(), frame::unpatchable, _anchor.last_Java_pc());
 }
 
+bool JavaThread::pd_get_top_frame_for_profiling(frame* fr_addr, void* 
ucontext, bool isInJava) {
+  ucontext_t* uc = (ucontext_t*) ucontext;
+  *fr_addr = frame((intptr_t*)uc->uc_mcontext.mc_i7, frame::unpatchable,
+   (address)uc->uc_mcontext.mc_gregs[MC_PC]);
+  return true;
+}
+
 // For Forte Analyzer AsyncGetCallTrace profiling support - thread is
 // currently interrupted by SIGPROF
 bool JavaThread::pd_get_top_frame_for_signal_handler(frame* fr_addr,
diff -r 04f4e983c2f7 -r 8e5f28a9bab3 
src/hotspot/os_cpu/linux_sparc/thread_linux_sparc.hpp
--- a/src/hotspot/os_cpu/linux_sparc/thread_linux_sparc.hpp Tue Jun 12 
07:52:30 2018 -0700
+++ b/src/hotspot/os_cpu/linux_sparc/thread_linux_sparc.hpp Tue Jun 12 
17:45:09 2018 +0200
@@ -85,8 +85,9 @@
 _base_of_stack_pointer = sp;
   }
 
-  bool pd_get_top_frame_for_signal_handler(frame* fr_addr, void* ucontext,
-bool isInJava);
+  bool pd_get_top_frame_for_signal_handler(frame* fr_addr, void* ucontext, 
bool isInJava);
+
+  bool pd_get_top_frame_for_profiling(frame* fr_addr, void* ucontext, bool 
isInJava);
 
   // These routines are only used on cpu architectures that
   // have separate register stacks (Itanium).
# HG changeset patch
# User glaubitz
# Date 1528196521 -7200
#  Tue Jun 05 13:02:01 2018 +0200
# Node ID ee87876734c930d1dac3adedbcd5830177621e23
# Parent  4d6a5c267541768d62248d81e64cfeb94eeb8f20
8203787: Hotspot build broken on linux-sparc after 8202377
Reviewed-by: dholmes, eosterlund

diff -r 4d6a5c267541 -r ee87876734c9 src/hotspot/share/opto/library_call.cpp
--- a/src/hotspot/share/opto/library_call.cpp   Tue Jun 05 09:29:15 

Bug#885533: soundtouch 1.8.0-1+deb8u1 flagged for acceptance

[Release Managers]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian jessie.

Thanks for your contribution!

Upload details
==

Package: soundtouch
Version: 1.8.0-1+deb8u1

Explanation: security fixes [CVE-2017-9258 CVE-2017-9259 CVE-2017-9260]

Bug#901409: Very low FPS in Nexuiz after Darkplaces upgrade

[Simon McVittie]

On Tue, 12 Jun 2018 at 21:27:06 +0300, Evgeny Kapun wrote:
> After I upgraded Darkplaces to version 0~20180412~beta1-2 (from
> 0~20140513+svn12208-7), Nexuiz slowed down to about 8 frames per second,
> which made it unplayable. With the previous version, I could get 30-40
> FPS on most maps.

What video hardware is this on?

Are you using X11 or Wayland or what? Which desktop environment, if any?

Would you be able to try an intermediate version from
?
That might help to locate what has caused that slowdown.

smcv

Bug#862030: rar 4.2.0+dfsg.1-0.1 flagged for acceptance

[Release Managers]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian .

Thanks for your contribution!

Upload details
==

Package: rar
Version: 4.2.0+dfsg.1-0.1

Explanation: strip statically linked rar and install the dynamically linked 
version instead

Bug#893507: reportbug 6.6.3+deb8u1 flagged for acceptance

[Release Managers]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian jessie.

Thanks for your contribution!

Upload details
==

Package: reportbug
Version: 6.6.3+deb8u1

Explanation: stop CCing secure-testing-t...@lists.alioth.debian.org

Bug#879034: pdfshuffler: port to gir1.2-poppler-0.18

[Andrey Rahmatullin]

On Wed, Oct 18, 2017 at 06:43:07PM +0200, Emilio Pozuelo Monfort wrote:
> In fact, there is a port at https://github.com/jeromerobert/pdfshuffler,
> using new poppler and gtk bindings, and python3. It'd be nice to get
> an updated package.
I wanted to try packaging this and I cannot find the upstream source.
- https://github.com/jeromerobert/pdfshuffler, especially
https://github.com/jeromerobert/pdfshuffler/issues/9, say this is an
unofficial mirror, and it seems the porting work is not specific to that
repo.
- the "old" official repo is at https://gna.org/projects/pdfshuffler/
which is dead.
- the current official project seems to be
https://savannah.nongnu.org/projects/pdfshuffler/ (see issue #9 above and
https://sourceforge.net/p/pdfshuffler/feature-requests/36/ linked there).
- but that seems to not contain any kind of source repo, the builtin SVN
repo is empty.
I've just found https://sourceforge.net/p/pdfshuffler/feature-requests/37/
mentioning all of that and it seems the only surviving repo is actually
that unofficial mirror. Maybe I should just package its HEAD.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#901066: cdpr FTCBFS: upstream Makefile hard codes build architecture compiler gcc

[Matt Zagrabelny]

Thanks for the bug report and patch. I've been somewhat idle on cdpr. I'm
hoping to take care of a few cdpr related tasks soon - one of them being
applying your patch.

Cheers,

-m

On Fri, Jun 8, 2018 at 10:07 AM, Helmut Grohne  wrote:

> Source: cdpr
> Version: 2.4-1
> Tags: patch upstream
> User: helm...@debian.org
> Usertags: rebootstrap
>
> cdpr fails to cross build from source, because the upstream Makefile
> hard codes the build architecture compiler gcc. After making the
> compiler substitutable (aka s/gcc/$(CC)/g), it cross builds
> successfully, because dh_auto_build passes a suitable CC. Please
> consider applying the attached patch.
>
> Helmut
>

Bug#901409: Very low FPS in Nexuiz after Darkplaces upgrade

[Evgeny Kapun]

Package: darkplaces
Version: 0~20180412~beta1-2
Severity: important

After I upgraded Darkplaces to version 0~20180412~beta1-2 (from 
0~20140513+svn12208-7), Nexuiz slowed down to about 8 frames per second, which 
made it unplayable. With the previous version, I could get 30-40 FPS on most 
maps.

Bug#900856: enlightenment: Sound fails to work after upgrade

[Ross Vandegrift]

On Tue, Jun 05, 2018 at 11:01:35PM +0100, Mike Brodbelt wrote:
> Doing some investigation into this, I enabled "PulseAudio Sound System"
> in Settings > Apps > Startup Applications. This didn't work - it seems
> to execute 'start-pulseaudio-x11' at login, which fails because it's
> executed at a point at which there is no pulseaudio daemon running:-

This shouldn't be required - my Startup Applications doesn't include pulse.
What does "systemctl --user status pulseaudio.service" report?  On my buster
laptop, it reports that the service is running and enabled.

> $ start-pulseaudio-x11
> Connection failure: Connection refused
> pa_context_connect() failed: Connection refused

This is curious.  According to start-pulseaudio-x11(1), it should start a
daemon if required.

Ross

Bug#901264: mirror submission for mirror.yannic-bonenberger.com

[Yannic Bonenberger]

The IP is owned by a company from Switzerland which has direct uplink with 
level3, so the physical location of the server is in Switzerland. Due to 
peering practices in Germany, a lot of requests are routed trough level3 (e.g. 
in Frankfurt or Hamburg) which results in fewer hops to and faster responses 
from this mirror located in Switzerland than most mirrors in Germany.
However, I do not object if you prefer to add the mirror for Switzerland.

I will remove the 6to4 address, but it may take some time to be visible.

Thanks,
Yannic

> Am 10.06.2018 um 20:26 schrieb Marco d'Itri :
> 
> On Jun 10, Yannic Bonenberger  wrote:
> 
>> Country: DE Germany
> It looks in Switzerland to me. Can you clarify this please?
> 
> Also, please remove the 6to4 address from the 
> mirror.yannic-bonenberger.com name: it does not help anybody and does 
> not not work anyway.
> 
> -- 
> ciao,
> Marco

Bug#901408: cups-filters: gstoraster orientation problem

[Mark Copper]

Package: cups-filters
Version: 1.11.6-3
Severity: normal

Dear Maintainer,

This problem arose with upgrade from Jessie to Stretch.

The problem I'm seeing seems to be in the CUPS filter gstoraster. That is, all 
is well at the preceding step:

# /usr/sbin/cupsfilter -p /etc/cups/ppd/Zebra.ppd -m application/vnd.cups-pdf 
-o orientation-requested=3 tag_generator.pdf > out.pdf

Well, almost. It was necessary to include the "orientation-requested=3" option 
to keep the document from rotating.

But at the next step, the document is laid on its side no matter the 
orientation requested:

# /usr/sbin/cupsfilter -p /etc/cups/ppd/Zebra.ppd -m 
application/vnd.cups-raster  out.pdf > out.ras


Or, in more detail,

# pdfinfo out.pdf
Producer:   PDF::API2 2.023 [linux]
Tagged: no
UserProperties: no
Suspects:   no
Form:   none
JavaScript: no
Pages:  1
Encrypted:  no
Page size:  90 x 144 pts
Page rot:   0
File size:  14151 bytes
Optimized:  no
PDF version:1.4

output of "/usr/sbin/cupsfilter -p /etc/cups/ppd/Zebra.ppd -m 
application/vnd.cups-raster  out.pdf > out.ras" to standard error says this:

DEBUG: argv[0]="cupsfilter"
DEBUG: argv[1]="1"
DEBUG: argv[2]="root"
DEBUG: argv[3]="out.pdf"
DEBUG: argv[4]="1"
DEBUG: argv[5]=""
DEBUG: argv[6]="out.pdf"
DEBUG: envp[0]=""
DEBUG: envp[1]="CONTENT_TYPE=application/pdf"
DEBUG: envp[2]="CUPS_DATADIR=/usr/share/cups"
DEBUG: envp[3]="CUPS_FONTPATH=/usr/share/cups/fonts"
DEBUG: envp[4]="CUPS_SERVERBIN=/usr/lib/cups"
DEBUG: envp[5]="CUPS_SERVERROOT=/etc/cups"
DEBUG: envp[6]="LANG=en_US.UTF8"
DEBUG: envp[7]="PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin"
DEBUG: envp[8]="PPD=/etc/cups/ppd/Zebra.ppd"
DEBUG: envp[9]="PRINTER_INFO=cupsfilter"
DEBUG: envp[10]="PRINTER_LOCATION=Unknown"
DEBUG: envp[11]="PRINTER=cupsfilter"
DEBUG: envp[12]="RIP_MAX_CACHE=128m"
DEBUG: envp[13]="USER=root"
DEBUG: envp[14]="CHARSET=utf-8"
DEBUG: envp[15]="FINAL_CONTENT_TYPE=application/vnd.cups-raster"
INFO: pdftopdf (PID 8482) started.
INFO: gstoraster (PID 8483) started.
DEBUG: OUTFORMAT="(null)", so output format will be CUPS/PWG Raster
DEBUG: pdftopdf: Last filter determined by the PPD: rastertolabel; 
FINAL_CONTENT_TYPE: application/vnd.cups-raster => pdftopdf will not log pages 
in page_log.
DEBUG: Color Manager: Calibration Mode/Off
DEBUG: Calling FindDeviceById(cups-cupsfilter)
DEBUG: Failed to send: org.freedesktop.ColorManager.NotFound:device id 
'cups-cupsfilter' does not exist
DEBUG: Failed to get find device cups-cupsfilter
DEBUG: Calling FindDeviceById(cups-cupsfilter)
DEBUG: Failed to send: org.freedesktop.ColorManager.NotFound:device id 
'cups-cupsfilter' does not exist
DEBUG: Failed to get device cups-cupsfilter
INFO: Color Manager: no profiles specified in PPD
DEBUG: Color Manager: ICC Profile: None
DEBUG: Ghostscript using Any-Part-of-Pixel method to fill paths.
DEBUG: Ghostscript command line: gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH 
-dNOINTERPOLATE -dNOMEDIAATTRS -sstdout=%stderr -sOutputFile=%stdout 
-sDEVICE=cups -dAdvanceDistance=1000 -r300x300 -dDEVICEWIDTHPOINTS=90 
-dDEVICEHEIGHTPOINTS=162 -dcupsBitsPerColor=1 -dcupsColorOrder=0 
-dcupsColorSpace=3 -dcupsCompression=-1 -dcupsRowStep=200 
-scupsPageSizeName=w90h162 -I/usr/share/cups/fonts -c '<>setpagedevice' -f -_
DEBUG: envp[0]=""
DEBUG: envp[1]="CONTENT_TYPE=application/pdf"
DEBUG: envp[2]="CUPS_DATADIR=/usr/share/cups"
DEBUG: envp[3]="CUPS_FONTPATH=/usr/share/cups/fonts"
DEBUG: envp[4]="CUPS_SERVERBIN=/usr/lib/cups"
DEBUG: envp[5]="CUPS_SERVERROOT=/etc/cups"
DEBUG: envp[6]="LANG=en_US.UTF8"
DEBUG: envp[7]="PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin"
DEBUG: envp[8]="PPD=/etc/cups/ppd/Zebra.ppd"
DEBUG: envp[9]="PRINTER_INFO=cupsfilter"
DEBUG: envp[10]="PRINTER_LOCATION=Unknown"
DEBUG: envp[11]="PRINTER=cupsfilter"
DEBUG: envp[12]="RIP_MAX_CACHE=128m"
DEBUG: envp[13]="USER=root"
DEBUG: envp[14]="CHARSET=utf-8"
DEBUG: envp[15]="FINAL_CONTENT_TYPE=application/vnd.cups-raster"
INFO: pdftopdf (PID 8482) exited with no errors.
INFO: Start rendering...
INFO: Processing page 1...
INFO: Processing page 2...
INFO: Rendering completed
INFO: gstoraster (PID 8483) exited with no errors.

Note that Ghostscript is called with page size 90 by 162. But when one views 
the output with rasterview,

CUPS Raster Page Attributes:

MediaClass = ""
MediaColor = ""
MediaType = ""
OutputType = ""
AdvanceDistance = 1000
AdvanceMedia = 0
Collate = 0
CutMedia = 0
Duplex = 0
HWResolution = [ 300 300 ]
ImagingBoundingBox = [ 0 0 144 90 ]
InsertSheet = 0
Jog = 0
LeadingEdge = 0
Margins = [ 0 0 ]
ManualFeed = 0
MediaPosition = 0
MediaWeight = 0
MirrorPrint = 0
NegativePrint = 0
NumCopies = 1
Orientation = 0
OutputFaceUp = 0
PageSize = [ 144 90 ]
Separations = 0
TraySwitch = 0
Tumble = 0
cupsWidth = 600
cupsHeight = 375
cupsMediaType = 0
cupsBitsPerColor = 1
cupsBitsPerPixel = 1
cupsBytesPerLine = 75
cupsColorOrder = CUPS_ORDER_CHUNKED
cupsColorSpace = CUPS_CSPACE_K

Bug#901030: some context

[Antonio Terceiro]

On Tue, Jun 12, 2018 at 02:34:57PM +0200, Hans-Christoph Steiner wrote:
> 
> I agree that there can't be a Restriction for every config under the
> sun.  I'm thinking more like Ian, where there can be some useful chunks
> with a finer grain than "needs isolation".

Allowing a test definition to cause any side effect to the host that is
running the test opens the doors to a security nightmare.

> I think that autopkgtest will never work well for a lot of packages with
> such a inflexible system for specifying requirements.  What if
> autopkgtest took a more "user generated" approach like gitlab CI
> runners?  That means that anyone can create tags/labels for runners, and
> jobs can specify any label that they require.  Then it is up to the
> people implementing the jobs/runners to make sure that they work.
> 
> We can learn a lot from the various CI services out there (GitLab,
> Travis, Circle, etc).  They are all based on containers, and they
> generally put few restrictions on what can be done in the containers.
> Containers are really well suited for CI builds since they provide an
> easy system for building up throwaway environments.

note that no configuration option in gitlab ci, travis etc allows you to
make changes to the *host* where the tests run. you can specify several
aspects of the *testbed* (container) where the tests run, and
autopkgtest already allows you to do whatever you need inside the
testbeds.

the problem here is that by definition, some types of testbed don't
allow you to test some packages. in this specific case, there is just no
way you can reliably test a feature that depends on a kernel feature in
a container.


signature.asc
Description: PGP signature

Bug#901407: qemu-user: man qemu-aarch64 shows incorrect usage for arguments

[Johann Koenig]

Package: qemu-user
Version: 1:2.11+dfsg-1
Severity: minor

Dear Maintainer,

$ man qemu-aarch64
shows incorrect usage for the -g option:
-g Wait gdb connection to port 1234.

$ qemu-aarch64 --help
shows that -g requires an option:
-g port  QEMU_GDB  wait gdb connection to 'port'

The man page appears to be a Debian-specific addition.

-- System Information:
Debian Release: testing
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-6-amd64 (SMP w/48 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/bash
Init: systemd (via /run/systemd/system)

Versions of packages qemu-user depends on:
ii  libc6 2.24-12
ii  libgcc1   1:8-20180218-1
ii  libglib2.0-0  2.53.4-3
ii  libstdc++68-20180218-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages qemu-user recommends:
ii  qemu-user-binfmt  1:2.11+dfsg-1

Versions of packages qemu-user suggests:
ii  sudo  1.8.19p1-2.1

-- no debconf information

Bug#901233: wbulgarian: Word list file should be in UTF-8, not in ISO-8859 anymore

[Damyan Ivanov]

-=| Pander, 10.06.2018 14:17:39 +0200 |=-
> Package: wbulgarian
> Version: 4.1-3
> Severity: normal
> Tags: l10n
> 
> Word list file should be in UTF-8, not in ISO-8859 anymore

It is in cp1251, not ISO-8859-x, but yeah, using UTF-8 would be 
better.

-=| Pander, 12.06.2018 16:38:30 +0200 |=-
> Also convert /usr/share/doc/wbulgarian/README.gz from ISO-8859 to UTF-8

It already is (since 2005) as well as the rest of the files in 
/usr/share/doc/wbulgarian. Am I missing something?

-- Damyan

Bug#900851: Papirus icon theme in Stretch backports request

[Samuel Henrique]

Hello everyone,

I just sent a Merge request[0] containing the branch for backports.

Thanks for your work on maintaining Deepin packages, a lot of Brazilian
users appreciate that.

[0]
https://salsa.debian.org/pkg-deepin-team/papirus-icon-theme/merge_requests/1

-- 
Samuel Henrique 

Bug#898945: Bug #898945: grub-installer: Installing to a raid 1 set on NVMe devices does not work

[Phil Susi]

It looks like the whole section handling raid arrays is missing from
Debian, so this patch does not apply.  Not sure why the raid handling
patches have not been folded back into Debian.

Bug#901406: haskell-cipher-aes: unaligned access on arm64 kernel (armhf binary) segfauts during testsuite

[Gianfranco Costamagna]

Source: haskell-cipher-aes
Version: 0.2.11-6
Severity: serious
Forwarded: https://github.com/vincenthz/hs-cipher-aes/issues/38

(copy-pasting from upstream ticket)
Hello, I see a bus error with ghc 8.2.2 but not with the previous ghc 8.0
https://launchpad.net/ubuntu/+source/haskell-cipher-aes/0.2.11-6/+build/14904327
Do you have any advice for me?
it seems some misaligment during aes_generic_encrypt_cbc function exit, but I 
can't find it.
to reproduce, just run testsuite on armhf target with arm64 kernel.
(this affects both Debian and Ubuntu, unfortunately debian runs armhf on 32bit 
kernel and user-space)


thanks

Gianfranco

Bug#901030: some context

[Ian Jackson]

Hans-Christoph Steiner writes ("Bug#901030: some context"):
> I agree that there can't be a Restriction for every config under the
> sun.  I'm thinking more like Ian, where there can be some useful chunks
> with a finer grain than "needs isolation".
> 
> I think that autopkgtest will never work well for a lot of packages with
> such a inflexible system for specifying requirements.  What if
> autopkgtest took a more "user generated" approach like gitlab CI
> runners?  That means that anyone can create tags/labels for runners, and
> jobs can specify any label that they require.  Then it is up to the
> people implementing the jobs/runners to make sure that they work.

I'm not sure what you mean.

There is nothing stopping anyone inventing whatever test restriction
labels they like right now.  Except, of course, that no test runner
will provide support for it.

I don't see how this problem can be solved without coordination
between test authors and (as applicable) autopkgtest developers and
virt server developers.

> As for the binfmt_misc module discussion, I know nothing about how that
> works.  If you can fix this issue in the kernel, fine by me.

ISTM that the bug is that the binfmt thing is not properly virtualised
by containers.  We don't have to fix that in the kernel; we could
bodge it by installing binfmt-misc in the host.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#863700: Removal proposed

[Xavier]

retitle 863700 RM: patcher -- unmaintained, orphaned and useless package

reassign 863700 ftp.debian.org

thanks

Hello,

patcher repository no longer exists, and no package depends on it. I
think it can be removed from testing.

Best regards,
Xavier



signature.asc
Description: OpenPGP digital signature

Bug#894131: [pkg-go] Bug#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Daniel Swarbrick]

On 12.06.2018 18:04, Martín Ferrari wrote:


Does it understand that 0.15.0-rc.1 is lower than 0.15.0, for example?
If that is the case, I could replace the tilde in the metadata.
I have not tested it, but looking at the code, it seems to be reasonably 
intelligent and handling major, minor, patch levels, as well as 
prerelease versions.


// Quick comparison if a version has no prerelease versions
if len(v.Pre) == 0 && len(o.Pre) == 0 {
return 0
} else if len(v.Pre) == 0 && len(o.Pre) > 0 {
return 1
} else if len(v.Pre) > 0 && len(o.Pre) == 0 {
return -1
}

So the version number 0.15.0-rc.1 would have len(v.Pre) > 0, and thus be 
considered less than 0.15.0, with len(v.Pre) == 0.

Bug#894131: [pkg-go] Bug#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Martín Ferrari]

On 12/06/18 17:00, Daniel Swarbrick wrote:
> On 12.06.2018 17:50, Martín Ferrari wrote:
>> I had not heard about unsee until now, we should package it too! :) 
> That would totally rock!

I was just taking a look, the main thing would be to be able to build
all the JS stuff, but it does not seem too bad.. Just need to find the
time to do it :)

> There are a couple of other exporters which I think would be of quite
> high interest to a lot of sites, such as the snmp_exporter. Perhaps I
> could assist you packaging some of them.

That would be great! If you want to join, there is an IRC channel (no
mailing list for now) to chat and coordinate the packaging efforts:
#debian-prometheus in OFTC.

>> Yeah, the tilde will be removed once the final release is out.. But it
>> still seems like a bug to panic due to that. I don't know how upstream
>> presents the RC version number, but shouldn't that also break semver
>> parsing?
> The upstream version presents version number "0.15.0-rc.1", which
> doesn't throw any errors in the semver.Parse function
> (https://github.com/blang/semver/blob/master/semver.go). However, the
> Unsee dashboard uses the MustParse() variant of that function, which of
> course panics if Parse() returns an error.

Does it understand that 0.15.0-rc.1 is lower than 0.15.0, for example?
If that is the case, I could replace the tilde in the metadata.


> As you may have seen in the Github issue I opened, somebody is working
> on it to hopefully make it a little more tolerant and robust.

Yeah, but the solution proposed is just to strip everything after the
tilde, which does not seem like a good solution.

-- 
Martín Ferrari (Tincho)

Bug#900449: kpartx -d fails with no error when disk path is using more than 63 characters

[Julien Langlois]

Hello Ritesh,

Yes, the issue occurs with the latest version of kpartx (multipath-tools).
I reproduced it using the same reproductions steps on version 0.7.7 and
even the latest commit on master: 00a54edd.

Minor erratum from my original reproduction steps: according to the given
script the "file" variable to use is **FILE1** and not FILE. As FILE1=t1 /
FILE1=t12.

Thanks,

  Julien

On Mon, Jun 11, 2018 at 10:22 PM Ritesh Raj Sarraf  wrote:

> Hello Julien,
>
> Thank you for the bug report.
>
> You've tagged it upstream. Does the issue occur with the latest version
> (0.7.4) too ?
>
> Thanks,
> Ritesh
>
>

Bug#894131: [pkg-go] Bug#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Daniel Swarbrick]

On 12.06.2018 17:50, Martín Ferrari wrote:
I had not heard about unsee until now, we should package it too! :) 

That would totally rock!

There are a couple of other exporters which I think would be of quite 
high interest to a lot of sites, such as the snmp_exporter. Perhaps I 
could assist you packaging some of them.

Yeah, the tilde will be removed once the final release is out.. But it
still seems like a bug to panic due to that. I don't know how upstream
presents the RC version number, but shouldn't that also break semver
parsing?
The upstream version presents version number "0.15.0-rc.1", which 
doesn't throw any errors in the semver.Parse function 
(https://github.com/blang/semver/blob/master/semver.go). However, the 
Unsee dashboard uses the MustParse() variant of that function, which of 
course panics if Parse() returns an error.


As you may have seen in the Github issue I opened, somebody is working 
on it to hopefully make it a little more tolerant and robust.

Bug#894131: [pkg-go] Bug#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Martín Ferrari]

Hi Daniel,

On 12/06/18 16:42, Daniel Swarbrick wrote:

> We've been running your 0.15.0~rc.1~git20180507.28967e3+ds-1 packages
> from experimental for about a week now, with no issues bar one - the

Oh, great!

> tilde in the version number upsets the semantic version parsing in
> Cloudflare's "unsee" dashboard
> (https://github.com/cloudflare/unsee/issues/263).

I had not heard about unsee until now, we should package it too! :)

> I presume that issue should resolve itself once the final release is
> out... I hope.

Yeah, the tilde will be removed once the final release is out.. But it
still seems like a bug to panic due to that. I don't know how upstream
presents the RC version number, but shouldn't that also break semver
parsing?

-- 
Martín Ferrari (Tincho)

Bug#901310: gitaly hard codes gitlab username and it does not use the same options to adduser as gitlab package

[Pirate Praveen]

On Mon, 11 Jun 2018 22:38:37 +1000 Dmitry Smirnov 
wrote:
> On Monday, 11 June 2018 10:14:28 PM AEST Pirate Praveen wrote:
> > I think the solution is to have a gitlab-common package that will handle
> > the user creation with both gitlab and gitaly depending on it.
> 
> Good idea.

Please review

https://salsa.debian.org/ruby-team/gitlab/commit/6eccbab22731b4fefd53161cf239d106e4ab6038



signature.asc
Description: OpenPGP digital signature

Bug#894131: [pkg-go] Bug#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Daniel Swarbrick]

Hi Martin,

We've been running your 0.15.0~rc.1~git20180507.28967e3+ds-1 packages 
from experimental for about a week now, with no issues bar one - the 
tilde in the version number upsets the semantic version parsing in 
Cloudflare's "unsee" dashboard 
(https://github.com/cloudflare/unsee/issues/263).


I presume that issue should resolve itself once the final release is 
out... I hope.



On 12.06.2018 17:38, Martín Ferrari wrote:

An update to this... I have prepared packages (without any UI) for
0.15-rc.2 and uploaded to experimental. If you can, please test them. I
plan to upload to unstable as soon as 0.15 is released.

Bug#901397: witalian: Convert README from ISO-8859 to UTF-8

[Pander]

Why is this package witalian depending on the perl package? I see no
reason. If there is none, please remove that dependency.

Bug#901391: wpolish: Convert dictionaries-common file to UTF-8

[Pander]

Why is this package depending on the perl package? I see no reason. If
there is none, please remove that dependency.

Bug#901388: wswiss: Convert files from ISO-8859 to UTF-8

[Pander]

Why is this package wswiss and the package wngerman depending on the
perl package? I see no reason. If there is none, please remove that
dependency.

Bug#901405: systemd-shim: Please add a sysvinit service to create directories on /run at boot

[Felipe Sateler]

Package: systemd-shim
Version: 10-3
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: shim-patches-removal

Hello Debian systemd-shim Maintainers,

The Debian systemd package is currently carrying two debian-specific patches
to enable usage of systemd-shim on Debian systems. In particular, we patch
some code to continue even if /run/systemd/machines/ and /run/systemd/machines/
don't exist[1][2].
These two patches could be avoided if systemd-shim would create the relevant
directories during early boot (sometime in rcS). Therefore we would like for
systemd-shim to provide these directories so we can drop these patches.
If you ship such a SysV init script, please make sure to mask that, so it is
not accidentally run when systemd is the active PID 1 (assuming the SysV init
script is called /etc/init.d/systemd-shim, the symlink would be
/lib/systemd/system/systemd-shim.service → /dev/null).

We intend to drop the patches before buster is released in the not too distant
future. When we do that, we will bump the severity of this bug report to 
serious.

[1] 
https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Start-logind-on-demand-via-libpam-systemd.patch
[2] 
https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Make-sd_login_monitor_new-work-for-logind-without-sy.patch

Saludos,
Felipe Sateler

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

Kernel: Linux 4.9.0-6-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-shim depends on:
pn  cgmanager 
ii  libc6 2.27-3
ii  libglib2.0-0  2.56.1-2

systemd-shim recommends no packages.

Versions of packages systemd-shim suggests:
pn  pm-utils  

Bug#901404: systemd-shim: Please dpkg-divert the dbus services you want dbus-activatable

[Felipe Sateler]

Package: systemd-shim
Version: 10-3
Severity: important
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: shim-patches-removal

Hello Debian systemd-shim Maintainers,

The Debian systemd package is currently carrying a debian-specific patch to
enable usage of various systemd daemons via systemd-shim on Debian systems.
In particular, it patches several systemd services to make them activatable
by DBus. [1]

Unfortunately none of the systemd maintainers actively tests the non-systemd
code paths in those daemons anymore, so we don't feel comfortable enabling
those services for sysvinit in the systemd package itself.
systemd-shim already has code to dpkg-divert a dbus service provided by
systemd, so we think systemd-shim should take over the divert of the rest
of the units which it wants to support to run under sysvinit.

We intend to drop the patch before buster is released in the not too distant
future. When we do that, we will bump the severity of this bug report to 
serious.

[1] 
https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Make-logind-hostnamed-localed-timedated-D-Bus-activa.patch

Saludos,
Felipe Sateler

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

Kernel: Linux 4.9.0-6-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-shim depends on:
pn  cgmanager 
ii  libc6 2.27-3
ii  libglib2.0-0  2.56.1-2

systemd-shim recommends no packages.

Versions of packages systemd-shim suggests:
pn  pm-utils  

Bug#901403: RM: xf86-video-glamo -- ROM; package broken since 2 years

[Sebastian Reichel]

Package: ftp.debian.org
Severity: normal

Hi,

The source package does not build for "new" Xorg from 2016,
has been removed from testing and was not part of last stable
release. Upstream seems to be dead since 2011:

https://github.com/openmoko/xf86-video-glamo

FWIW I never worked on xf86-video-glamo myself, but I'm one of
the last persons who worked on the FSO packages. I Cc'd the
persons involved with glamo, so that they can intervene.

-- Sebastian

$ ssh mirror.ftp-master.debian.org "dak rm -Rn xf86-video-glamo"
Will remove the following packages from unstable:

xf86-video-glamo | 0.0.0+20110719.gitcb9ed170-2 | source
xserver-xorg-video-glamo | 0.0.0+20110719.gitcb9ed170-2+b2 | amd64, armel
xserver-xorg-video-glamo | 0.0.0+20110719.gitcb9ed170-2+b3 | i386

Maintainer: Debian freesmartphone.org Team 


--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.

Bug#859130: uploads to mentors, no updates on git repository

[Albert van der Horst]

Geert Stappers schreef op 2018-06-12 15:34:

At https://mentors.debian.net/package/lina
are several uploads of verion 5.3.0-2 of lina.
Some are from may, most are from 11th of june.

However _no changes_ on the git repository
at https://github.com/albertvanderhorst/ciforth


That is not to be expected, as most complaints by lintian
are about what is in the debian directory, not under control
of upstream.



That means the (ab)used .orig.tar.gz still
gets it's forth.lab and makefile from unknown source.


Since when is an upstream author 'unknown source'?
The author is well known, it is me, see the copyright messages.
Besides, where is the requirement in Debian that an upstream source
should be a dump of a git repository?
So I reject this complaint and maintain that the lina
package is fit for sponsoring.

The ciforth archive is not. I'm not aspiring to add a factory for
generating MS-windows and Apple programs to Debian, as
  1. It goes against the spirit of what I want to supply Debian with:
  a simple compiler that will spawn a number of e.g.
  single board computer related utilities.
  A compiler that is by far the most understandable compiler
  in the whole of Debian.
  2. ciforth probably simply doesn't belong in Debian
  3. It would require a tremendous upgrade in quality.
 Where I'm 100% behind the quality of lina, not so
  much for ciforth. I could not promote adding it to Debian.

Even so, if a Debian developer thinks the ciforth compiler
factory is a valuable addition *to a debian distribution*, (s)he is free 
to fork

ciforth and get it accepted.


*   Please note! The famous gcc has no means to generate a native  *
*   windows compiler. so ciforth would beat gcc to it! *
*   Of course chances are better with a compiler designed for  *
*   simplicity but i'm not foolish enough to gamble that ciforth   *
*   could pass Debian's quality checks in my life time.*




See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859130#58
where that was previously reported.

I doubt if this ITP is really about
getting a source from a git repository into a debian package.


Of course it is not.

The git repository contains means to get windows
and apple sources that are specifically not going into the lina
package. So it is plain that you don't understand the difference
between ciforth and lina, and that you don't respect the integrity
of an upstream package c.q. upstream maintainer.
That is the reason you're no longer my sponsor.

Remember how this started?
My source package contains
   lina.fas
   lina.texinfo
   forth.lab
There was not even a Makefile . Build with
fasm  lina.fas
which is mentioned somewhere in lina.fas

The simplicity is a goal made possible with complexity in ciforth.
Then the whole circus gets started with the remark that lina.fas
is not a "proper source" based on a rule that was supposed to contain
malevolent manufacturers, not hold back free software developpers.
Anyway the "preferred source of modification" rule is obeyed by
supplying everything that could be considered "preferred source
of modification", so that point is covered.

See also
https://github.com/albertvanderhorst/ciforth/wiki/Philosophy-behind-ciforth

An example of usage of the compiler including some parallel 
calculations:

   https://github.com/albertvanderhorst/primecounting

I welcome a new sponsor!

You will sponsor a very simple package that is
mature and has a very responsive maintainer.




Groeten
Geert Stappers


Groetjes Albert

--
Suffering is the prerogative of the strong, the weak -- perish.
Albert van der Horst

Bug#901232: wbrazilian: Word list file should be in UTF-8, not in ISO-8859 anymore

[Pander]

Please check if /usr/share/doc/wbrazilian/changelog.gz has also been
converted from ISO-8859 to UTF-8

Bug#901233: wbulgarian: Word list file should be in UTF-8, not in ISO-8859 anymore

[Pander]

Also convert /usr/share/doc/wbulgarian/README.gz from ISO-8859 to UTF-8

Bug#901402: atril: Please add option to highlight text

[Andreas Schmidt]

Package: atril
Version: 1.20.1-1
Severity: wishlist

Dear Maintainer,

would it be possible to implement an option to highlight text? Just yesterday,
a client asked me to correct mistakes directly in a PDF file he sent me, so I
searched around for a PDF viewer that allowed both text annotations and text
highlighting. Turns out I got lucky with evince! As atril is a fork of evince,
I assume it shouldn't be too hard to port this feature to atril. :-)

The following suggestion might be harder to implement as it goes beyond what is
available in evince yet: It would be great if  text could be highlighted not
only with colored backgrounds, but also with differently styled lines. Thus,
one could strike-through text that should be deleted, mark text that is to be
replaced with a full line, or highlight ambiguous text with dotted or curly
lines. (Perhaps there would even be a way to make an obvious "Insert text
here!"-mark?)

Like evince, atril already offers the option to change an annotation's
properties (author, color, opacity, initial window state, and icon). What do
you think about saving these attributes as (predefined and custom) profiles?
Ideally, one could then link these profiles to buttons: If, say, "Mark as
deleted" is pressed, the text could be highlighted with a black (or green, or
yellow) full (or dotted, or curly) line over a red (or whatever) background.

I hope these ideas are not impossible to implement -- after all, I installed
MATE for a reason and would like to always use atril instead of evince. :-)

Thanks for your consideration and best regards

Andreas



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

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

Versions of packages atril depends on:
ii  atril-common 1.20.1-1
ii  dconf-gsettings-backend [gsettings-backend]  0.28.0-2
ii  libatk1.0-0  2.28.1-1
ii  libatrildocument31.20.1-1
ii  libatrilview31.20.1-1
ii  libc62.27-3
ii  libcairo-gobject21.15.10-3
ii  libcairo21.15.10-3
ii  libcaja-extension1   1.20.2-4
ii  libgail-3-0  3.22.30-1
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-1
ii  libice6  2:1.0.9-2
ii  libjavascriptcoregtk-4.0-18  2.20.2-dmo2
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libsecret-1-00.18.6-2
ii  libsm6   2:1.2.2-1+b3
ii  libsoup2.4-1 2.62.2-1
ii  libwebkit2gtk-4.0-37 2.20.2-dmo2
ii  libx11-6 2:1.6.5-1
ii  libxml2  2.9.4+dfsg1-7
ii  mate-desktop-common  1.20.1-2
ii  shared-mime-info 1.9-2
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages atril recommends:
ii  dbus-x11 [dbus-session-bus]  1.12.8-3
ii  gvfs 1.36.1-1

Versions of packages atril suggests:
ii  caja  1.20.2-4
ii  poppler-data  0.4.9-2
ii  unrar 1:5.5.8-1

-- no debconf information

Bug#901401: golly: Please package the latest version (3.1)

[Boyuan Yang]

Source: golly
Version: 2.8-1
Severity: normal

Dear golly maintainer,

Upstream has released a new version of golly (3.1, on 2017-10).

Please consider packaging the new version in Debian.

--
Regards,
Boyuan Yang



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

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

-- no debconf information

Bug#901400: wgalician-minimos: Convert files from ISO-8859 to UTF-8

[Pander]

Package: wgalician-minimos
Version: 0.5-44
Severity: normal
Tags: l10n

Convert follwing files from ISO-8859 to UTF-8
/usr/share/doc/wgalician-minimos/readme.txt
/usr/share/doc/wgalician-minimos/leme.txt.gz
/usr/share/doc/wgalician-minimos/normas.txt.gz
/usr/share/doc/wgalician-minimos/LICENZA.txt.gz


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

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

Versions of packages wgalician-minimos depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  dictionaries-common1.27.2

wgalician-minimos recommends no packages.

wgalician-minimos suggests no packages.

-- debconf information excluded

Bug#901399: wgerman-medical: Convert German medical word list file from ISO-8859 to UTF-8

[Pander]

Package: wgerman-medical
Version: 20160103-1
Severity: normal
Tags: l10n

Convert German medical word list file /usr/share/dict/german-medical from 
ISO-8859 to UTF-8


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

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

Versions of packages wgerman-medical depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  dictionaries-common1.27.2

wgerman-medical recommends no packages.

wgerman-medical suggests no packages.

-- debconf information excluded

Bug#874275: exifprobe: Consistent segmentation fault

[Hubert Figuiere]

[ I'm the upstream maintainer ]

This crash is caused by downstream patch 
https://salsa.debian.org/pkg-security-team/exifprobe/blob/debian/master/debian/patches/fix-makefile.patch


More specifically the added -fPIE compiler flag.

Hub

Bug#901398: bbdb: remove this package?

[David Bremner]

Package: bbdb
Version: 2.36-4.1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

This package hasn't seen an upstream update since 2010. The only
Debian upload since 2014 was an NMU by me almost a year ago. 

It seems superceded upstream by what Debian calls bbdb3, which has an
active maintainer.

I don't think it should be in Buster as effectively a Debian specific
fork.  OTOH, I'm not user of either bbdb or bbdb3, so I'm open to
hearing why we should keep both versions of bbdb, as long as someone
is willing to do the needed ongoing maintence, in particular keeping
up with new versions of emacs.

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

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

Versions of packages bbdb depends on:
ii  emacs25 [emacsen]  25.2+1-6+b2
ii  make   4.1-9.1
ii  perl   5.26.2-5

bbdb recommends no packages.

Versions of packages bbdb suggests:
pn  gnus | t-gnus  
pn  gnuserv
ii  perl   5.26.2-5
ii  vm 8.2.0b-2.1
pn  w3m-el 

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlsf1BEACgkQ8gKXHaSn
niwLzQv+MN7BmcrdiKloxtZLnjGVbS7xew815dv+qJuqLa+NA7KWx0Fz7cvT9G8d
qcO/9tz0t0UEezTdG9dCvPLfN5iOxGwVcG19xFIAQLLRAjubJSX72DrNtAmeg4xA
sKQBy/bN43vfDg9ThP/S3NcCPDEfJfu3jU+fj7GKFT5+ihiWPlUSbU7N/lMcKlHQ
PLDOme3tV5Jc2ljARGldUfzBE8cCIw7cHXvRDoR/ouXSyhkZC8N7J3osBfjIltTh
F2jT7Fe+DhlflaUAlMEJZc/Dsf0YGG27XJj1188wP+G4a5ZGADB4SvM0Fv34+lxF
IdfuWVhiTMI8xSf3R6KQwsIIumZdueLfZ6OjSCbSCSCsNKArKqwdDtUj/SRRbBZl
kZkOVPDO7IbnhCDwj2HaHk6syxUSpRxflWCbAmvlH8AwnrXrJn9a9zTpCy4YLsJr
XtJqsgA0eryCvQP3fLAPEqasMMybVnHzaPtuDOF2jdxJXh8IUsTefyc4cAaoTPYC
84Tf0Hic
=BCG/
-END PGP SIGNATURE-

Bug#901239: wirish: Word list file should be in UTF-8, not in ISO-8859 anymore

[Pander]

Please, also convert /var/lib/dictionaries-common/wordlist/wirish from
ISO-8859 text to UTF-8 Unicode text