Bug#880055: libatk1.0-dev: File conflict in Multi-Arch: same package [regression]

[Hugh McMaster]

Package: libatk1.0-dev
Version: 2.26.0-2
Severity: important

Dear Maintainer,

Recent versions of libatk1.0-dev conflict in /usr/include/atk-1.0/atk/atk-enum-
types.h.

A diff of the amd64 and i386 packages reveals several conflicts in this
package; for example:

-/* enumerations from "/build/atk1.0-hwBmu9/atk1.0-2.26.1/obj-i686-linux-
gnu/../atk/atkhyperlink.h" */
+/* enumerations from "/build/atk1.0-1sVZm4/atk1.0-2.26.1/obj-x86_64-linux-
gnu/../atk/atkhyperlink.h" */

This is a regression from previous versions, which did not conflict, and causes
issues for other
projects, including Wine.

Please fix this issue by either removing the comment lines or preventing them
from being modified from
/* enumerations from "./atkhyperlink.h" */
or similar.

Thank you.



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

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

Versions of packages libatk1.0-dev depends on:
ii  gir1.2-atk-1.0  2.26.0-2
ii  libatk1.0-0 2.26.0-2
ii  libglib2.0-dev  2.54.1-1
ii  pkg-config  0.29-4+b1

libatk1.0-dev recommends no packages.

libatk1.0-dev suggests no packages.

-- no debconf information

Bug#844779: osmose-emulator FTBFS on armel and armhf: QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope

[Carlos Donizete Froes]

tags 844779 fixed-upstream
thanks

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#879720: RFS: runescape/0.2-1 -- Multiplayer online game set in a fantasy world

[Carlos Donizete Froes]

tags 879720 fixed-upstream
thanks

Hi,

Using mktemp command to temporary directory in script (src/runescape.sh).

See more details here[1].

version: 0.2
  * Fixed desktop file
  * Added initial file transfer progress bar
  * Replaced command line to create temporary directory
  * Makefile version updated to 0.2
  * Removed official icon in format (xpm)
  * Added official icon in format (png) size 256 pixels

debian/changelog:
runescape (0.2-1) unstable; urgency=medium

  * New upstream release
  * Switch to compat level 10
  * debian/control:
+ Changed homepage link
+ Bump debhelper compat to 10
+ Declare compliance with Debian Policy: 4.1.1
  * Fixed d/upstream/metadata
  * Fixed d/watch
  * Updated d/copyright
  * Added autopkgtest
  * Changed icon format and fixed bug in desktop file (Closes: Bug#866227)
  * Replaced command line to create temporary directory (Closes: Bug#879784)

[1] - https://anonscm.debian.org/cgit/pkg-games/runescape.git

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#844779: osmose-emulator FTBFS on armel and armhf: QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope

[Carlos Donizete Froes]

tags 844779 fixed-upstream
thanks

Hi Adrian, 

It has been fixed in the new version of the package.

version: 1.2
  * Fixed bug in audio alsa
  * Fixed installation on architectures 'arm'

[1] - https://anonscm.debian.org/cgit/pkg-games/osmose-emulator.git

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#868499: osmose-emulator: No sound

[Carlos Donizete Froes]

tags 868499 + moreinfo + patch fixed-upstream
thanks

Hi, Diogo

From what I understanded, this library missing ALSA (libasound2), could you give
me more details about what happened?

I made some improvements in the emulator in version (1.2).

See more details here[1].

version: 1.2
  * Fixed bug in audio alsa
  * Fixed installation on architectures 'arm'

[1] - https://anonscm.debian.org/cgit/pkg-games/osmose-emulator.git

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#852721: tunnelx: Non-ASCII character corruption

[Wookey]

On 2017-01-27 03:42 +, Wookey wrote:
> On 2017-01-26 12:40 +, Toby Speight wrote:
> > Package: tunnelx
> > Version: 20160713-3
> > 
> > Characters outside US-ASCII get corrupted when saving and loading
> > tunnel sketches.

> Cheers for that. You missed debian stable deadline by about 1 day, and
> debian is frozen for the time being, so I won't do an upload right
> now, but will forward to Julian.

Just remembered to upload the fixed version to unstable (with a couple more 
updates).

Meanwhile Julian has made some changes, including geotiff support, so
I need to do a new upload with latest upstream. Hopefully not too many
months.


Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#822936: Occurs on Stretch

[Jiann-Ming Su]

linux-image-4.9.0-4-686-pae  4.9.51-1

Oct 27 08:15:19 puar kernel: [26080.447922] INFO: rcu_sched
self-detected stall on CPU
Oct 27 08:15:19 puar kernel: [26080.447946] INFO: rcu_sched
self-detected stall on CPU
Oct 27 08:15:19 puar kernel: [26080.447964] 1-...: (1 GPs behind)
idle=c41/1/0 softirq=1143278/1143279 fqs=0
Oct 27 08:15:19 puar kernel: [26080.447968]
Oct 27 08:15:19 puar kernel: [26080.447976]  (t=9226 jiffies g=487334
c=487333 q=1)
Oct 27 08:15:19 puar kernel: [26080.447988] rcu_sched kthread starved
for 9226 jiffies! g487334 c487333 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x1
Oct 27 08:15:19 puar kernel: [26080.447993] rcu_sched   S
Oct 27 08:15:19 puar kernel: [26080.448001] 0 7  2 0x
Oct 27 08:15:19 puar kernel: 
Oct 27 08:15:19 puar kernel: [26080.448012]  f300a100 f68b8800
f751bed4 c75a9e7e f751bebc c70d4cd7 c78b8280 0051bec4
Oct 27 08:15:19 puar kernel: [26080.448041]  f7518db8 c7767680
f300a100 f79deac0 f75189c0 f751bee0 f75189c0 f79d8900
Oct 27 08:15:19 puar kernel: [26080.448069]  f751bf00 f751bee0
c75aa3ae f79d8900 f751bf28 c75ad08f 0002Call Trace:
Oct 27 08:15:19 puar kernel: [26080.448126]  [] ?
__schedule+0x25e/0x760
Oct 27 08:15:19 puar kernel: [26080.448144]  [] ?
lock_timer_base+0x67/0x80
Oct 27 08:15:19 puar kernel: [26080.448158]  [] ? schedule+0x2e/0x80
Oct 27 08:15:19 puar kernel: [26080.448172]  [] ?
schedule_timeout+0x12f/0x300
Oct 27 08:15:19 puar kernel: [26080.448186]  [] ?
del_timer_sync+0x50/0x50
Oct 27 08:15:19 puar kernel: [26080.448199]  [] ?
rcu_gp_kthread+0x4a1/0x7c0
Oct 27 08:15:19 puar kernel: [26080.448214]  [] ? kthread+0xb4/0xd0
Oct 27 08:15:19 puar kernel: [26080.448225]  [] ?
rcu_note_context_switch+0xf0/0xf0
Oct 27 08:15:19 puar kernel: [26080.448237]  [] ?
kthread_park+0x50/0x50
Oct 27 08:15:19 puar kernel: [26080.448248]  [] ?
ret_from_fork+0x1b/0x28
Oct 27 08:15:19 puar kernel: [26080.448299] Task dump for CPU 0:
Oct 27 08:15:19 puar kernel: [26080.448307] swapper/0   R
Oct 27 08:15:19 puar kernel: [26080.448310]   running task0
 0  0 0x
Oct 27 08:15:19 puar kernel: c77c55f0
Oct 27 08:15:19 puar kernel: [26080.448327]  c7761fbc 
c776007b bc31007b 00d8 c77c00e0 ff5e c7480944
Oct 27 08:15:19 puar kernel: [26080.448355]  0060 0246
1667 bc2ca3cb 17af  c77c54a0 0004
Oct 27 08:15:19 puar kernel: [26080.448382]  ff9d7fe0 bc314afc
17af  ff9d7fe0 c77c54a0 c7761fe4Call Trace:
Oct 27 08:15:19 puar kernel: [26080.448435]  [] ?
cpuidle_enter_state+0x134/0x330
Oct 27 08:15:19 puar kernel: [26080.448451]  [] ?
cpu_startup_entry+0x135/0x220
Oct 27 08:15:19 puar kernel: [26080.448467]  [] ?
start_kernel+0x39d/0x3b4
Oct 27 08:15:19 puar kernel: [26080.448473] Task dump for CPU 1:
Oct 27 08:15:19 puar kernel: [26080.448478] swapper/1   R
Oct 27 08:15:19 puar kernel: [26080.448481]   running task0
 0  1 0x0008
Oct 27 08:15:19 puar kernel: f7527dcc
Oct 27 08:15:19 puar kernel: [26080.448495]  c7091941 c76b35df
  0001 0008 c7782140 c7782140
Oct 27 08:15:19 puar kernel: [26080.448522]  0001 f7527de4
c7166884 0087 f79f3300 c7782140 c7782140 f7527e30
Oct 27 08:15:19 puar kernel: [26080.448550]  c70d20e1 c76a9ed0
240a 00076fa6 00076fa5 0001 603ea661Call Trace:
Oct 27 08:15:19 puar kernel: [26080.448593]  [] ?
sched_show_task+0xf1/0x160
Oct 27 08:15:19 puar kernel: [26080.448612]  [] ?
rcu_dump_cpu_stacks+0x79/0x95
Oct 27 08:15:19 puar kernel: [26080.448633]  [] ?
rcu_check_callbacks+0x631/0x780
Oct 27 08:15:19 puar kernel: [26080.448652]  [] ?
update_process_times+0x28/0x50
Oct 27 08:15:19 puar kernel: [26080.448665]  [] ?
tick_sched_handle.isra.11+0x26/0x60
Oct 27 08:15:19 puar kernel: [26080.448675]  [] ?
tick_sched_timer+0x3a/0x80
Oct 27 08:15:19 puar kernel: [26080.448688]  [] ?
__remove_hrtimer+0x3f/0x80
Oct 27 08:15:19 puar kernel: [26080.448700]  [] ?
__hrtimer_run_queues+0xc0/0x260
Oct 27 08:15:19 puar kernel: [26080.448712]  [] ?
tick_sched_handle.isra.11+0x60/0x60
Oct 27 08:15:19 puar kernel: [26080.448725]  [] ?
hrtimer_interrupt+0x93/0x1a0
Oct 27 08:15:19 puar kernel: [26080.448742]  [] ?
smp_apic_timer_interrupt+0x33/0x50
Oct 27 08:15:19 puar kernel: [26080.448753]  [] ?
apic_timer_interrupt+0x34/0x3c
Oct 27 08:15:19 puar kernel: [26080.448772]  [] ?
cpuidle_enter_state+0x134/0x330
Oct 27 08:15:19 puar kernel: [26080.448787]  [] ?
cpu_startup_entry+0x135/0x220
Oct 27 08:15:19 puar kernel: [26080.448801]  [] ?
start_secondary+0x155/0x1b0
Oct 27 08:15:19 puar kernel: [26080.449772] 0-...: (1 ticks this
GP) idle=3e1/2/0 softirq=1245237/1245237 fqs=0
Oct 27 08:15:19 puar kernel: [26080.450190]  (t=9227 jiffies
g=487334 c=487333 q=3)
Oct 27 08:15:19 puar kernel: [26080.450514] rcu_sched kthread starved
for 9227 jiffies! g487334 c487333 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x0
Oct 27 08:15:19 puar kernel: [26080.451087] rcu_sched   R  running
task0 7  2 0x
Oct 27 

Bug#880054: Debian-live-9.02-lx-amd64

[Paul Rudolph]

Package: installation-reports Boot method: How did you boot the installer? 
CD? floppy? network?USB Image version: Full URL to image you downloaded 
is bestdebian-live-9.2.0-amd64-lxde-+nonfree.iso Date: Date and time of 
the installOct 28 2017
tmpfs 7646640764664   0% /sys/fs/cgroup

/dev/sda5   19092180 11552400   6546912  64% /home

/dev/sda8   32315264 10575780  20074924  35% /media/share

tmpfs 152932   16152916   1% /run/user/1000

/dev/sr0 4432432  4432432 0 100% 
/media/paul/DC_SUPERHERO_GIRLS_BRAIN_DRAIN

/dev/sdb12293760  2293760 0 100% /media

/paul/d-live nf 9.2.0 lx amd64

 Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Advanced 
Micro Devices, Inc. [AMD/ATI] RS480/RS482/RS485 Host Bridge [1002:5950]
Subsystem: Hewlett-Packard Company RS480/RS482/RS485 Host Bridge [103c:3085]

00:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RC4xx/RS4xx 
PCI Bridge [int gfx] [1002:5a3f]

Kernel modules: shpchp

00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RC4xx/RS4xx 
PCI Express Port 1 [1002:5a36]

Kernel driver in use: pcieport

Kernel modules: shpchp

00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 
USB Host Controller [1002:4374]

Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 USB Host 
Controller [1002:4374]

Kernel driver in use: ohci-pci

00:13.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 
USB Host Controller [1002:4375]

Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 USB Host 
Controller [1002:4375]

Kernel driver in use: ohci-pci

00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 
USB2 Host Controller [1002:4373]

Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 USB2 Host 
Controller [1002:4373]

Kernel driver in use: ehci-pci

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 SMBus 
Controller [1002:4372] (rev 10)

Subsystem: Hewlett-Packard Company IXP SB4x0 SMBus Controller [103c:3085]

Kernel driver in use: piix4_smbus

Kernel modules: i2c_piix4

00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 
IDE Controller [1002:4376]

Subsystem: Hewlett-Packard Company IXP SB4x0 IDE Controller [103c:3085]

Kernel driver in use: pata_atiixp

Kernel modules: pata_atiixp, pata_acpi

00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 
PCI-ISA Bridge [1002:4377]

00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 
PCI-PCI Bridge [1002:4371]

00:14.5 Multimedia audio controller [0401]: Advanced Micro Devices, Inc. 
[AMD/ATI] IXP SB400 AC'97 Audio Controller [1002:4370] (rev 01)

Subsystem: Hewlett-Packard Company IXP SB400 AC'97 Audio Controller 
[103c:3085]

Kernel driver in use: snd_atiixp

Kernel modules: snd_atiixp

00:14.6 Modem [0703]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB400 AC'97 
Modem Controller [1002:4378] (rev 01)

Subsystem: Hewlett-Packard Company IXP SB400 AC'97 Modem Controller 
[103c:3085]

Kernel driver in use: snd_atiixp_modem

Kernel modules: snd_atiixp_modem

00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 
[Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]

00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 
[Athlon64/Opteron] Address Map [1022:1101]

00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 
[Athlon64/Opteron] DRAM Controller [1022:1102]

00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 
[Athlon64/Opteron] Miscellaneous Control [1022:1103]

Kernel driver in use: k8temp

Kernel modules: k8temp

01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RS480M [Mobility Radeon Xpress 200] [1002:5955]

Subsystem: Hewlett-Packard Company RS480M [Mobility Radeon Xpress 200] 
[103c:3085]

Kernel driver in use: radeon

Kernel modules: radeonfb, radeon

03:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22A 
IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] [104c:8023]

Subsystem: Hewlett-Packard Company TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] [103c:3085]

Kernel driver in use: firewire_ohci

Kernel modules: firewire_ohci

03:02.0 Network controller [0280]: Broadcom Limited BCM4306 802.11b/g Wireless 
LAN Controller [14e4:4320] (rev 03)

Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN [103c:12f8]

Kernel driver in use: b43-pci-bridge

Kernel modules: ssb

03:04.0 CardBus bridge [0607]: Texas Instruments PCIxx21/x515 Cardbus 
Controller [104c:8031]

Subsystem: Hewlett-Packard Company PCIxx21/x515 Cardbus Controller 
[103c:3085]

Kernel driver in use: yenta_cardbus

Kernel modules: yenta_socket

03:04.3 Mass storage controller 

Bug#880053: [plasma-widgets-addons] Error has corrected itself following the end of the extra Wall-clock hour

[Stephen Lyons]

Package: plasma-widgets-addons
Version: 4:5.8.5-2

--- Please enter the report below this line. ---

It seems that the defect only persists for the duration of the time when
the wall clock is back at the end of DST, at the *end* of the hour the
time zone has been corrected to the expected "GMT" from the "BST" value
- so the bug would seem to be in the logic that changes the timezone
information in that it made the change at the end of the hour not the
beginning...!

The display is still wrong for that hour but I guess one hour out of
approximately four and a half thousands is enough to downgrade the
seriousness a bit?

Stephen



signature.asc
Description: OpenPGP digital signature

Bug#880053: [plasma-widgets-addons] Ending of DST not updating TimeZone display

[Stephen Lyons]

Package: plasma-widgets-addons
Version: 4:5.8.5-2
Severity: important

--- Please enter the report below this line. ---
With the ending of Daylight Saving Time for the TimeZone of
Europe/London at 01:00:00 UTC on 2017/10/29 I noted the displayed time
jumping back from 01:59:50 to 01:00:00 as anticipated however the
timezone information displayed alongside remained as "(BST)" i.e.
"British Summer Time" - this means that the displayed information is
WRONG.  The display should have switched to "GMT" i.e. "Greenwich Mean
Time" at the same time as the clock was adjusted.  With this error it is
possible in the short term (for the remainder of the hour or so) to be
uncertain as to what the time actually is. 8-P

I am not entirely sure this is the correct package to report this bug
against if it is not please advise me and/or move it to the correct
package if possible.

I would note that a command line invocation of date(1) in conjunction
with the line "TZ='Europe/London'; export TZ" in my ~/.profile yields
the expected "GMT".

It may be that a log out and log back in again to restart the KDE
desktop will correct this - if this does *not* happen I will update the
bug-report when I next restart KDE but that may be some days down the
line...

Stephen

--- System information. ---
Architecture: Kernel:   Linux 4.12.0-0.bpo.2-amd64

Debian Release: 9.2
  500 stable-updates  ftp.uk.debian.org   500 stable
security.debian.org   500 stable  ftp.uk.debian.org   500 stable
 apt.spideroak.com   100 stretch-backports ftp.uk.debian.org
--- Package information. ---
Depends(Version) |
Installed
-+-==
kdeplasma-addons-data  (= 4:5.8.5-2) |
4:5.8.5-2
kpackagetool5|
5.28.1-1
plasma-dataengines-addons  (= 4:5.8.5-2) |
4:5.8.5-2
plasma-framework |
5.28.0-2
plasma-workspace |
4:5.8.6-2.1
qml-module-org-kde-draganddrop   |
5.28.0-1
qml-module-org-kde-purpose   | 1.1-4
qml-module-org-kde-kcoreaddons   |
5.28.0-1
qml-module-org-kde-kio   |
5.28.0-1
qml-module-qtgraphicaleffects|
5.7.1~20161021-3
qml-module-qtwebkit  |
5.7.1+dfsg-1
kio  |
5.28.0-2
libc6  (>= 2.14) |
2.24-11+deb9u1
libkf5archive5   (>= 4.96.0) |
5.28.0-2
libkf5completion5(>= 4.97.0) |
5.28.0-1
libkf5configcore5(>= 4.97.0) |
5.28.0-2
libkf5configgui5 (>= 4.97.0) |
5.28.0-2
libkf5coreaddons5(>= 4.99.0) |
5.28.0-2
libkf5i18n5  (>= 4.97.0) |
5.28.0-2
libkf5iconthemes5(>= 4.96.0) |
5.28.0-2
libkf5kiocore5   (>= 4.96.0) |
5.28.0-2
libkf5kiowidgets5(>= 4.96.0) |
5.28.0-2
libkf5newstuff5   (>= 5.0.0) |
5.28.0-1
libkf5notifications5   (>= 5.8.0+git20150317.0114+15.04) |
5.28.0-1
libkf5plasma5(>= 5.21.0) |
5.28.0-2
libkf5service-bin|
5.28.0-1
libkf5service5   (>= 4.96.0) |
5.28.0-1
libkf5unitconversion5(>= 4.98.0) |
5.28.0-1
libkf5widgetsaddons5 (>= 4.96.0) |
5.28.0-3
libkf5windowsystem5(>= 5.6.0+git20150112.0023+15.04) |
5.28.0-2
libkf5xmlgui5(>= 4.96.0) |
5.28.0-1
libqt5core5a  (>= 5.7.0) |
5.7.1+dfsg-3+b1
libqt5dbus5 (>= 5.4) |
5.7.1+dfsg-3+b1
libqt5gui5(>= 5.7.0) |
5.7.1+dfsg-3+b1
libqt5qml5(>= 5.0.2) |
5.7.1-2+b2
libqt5quick5  (>= 5.1.0) |
5.7.1-2+b2
libqt5widgets5  (>= 5.4) |
5.7.1+dfsg-3+b1
libstdc++6(>= 4.1.1) |
6.3.0-18


Package's Recommends field is empty.

Package's Suggests field is empty.



signature.asc
Description: OpenPGP digital 

Bug#880052: searchandrescue: New upstream release

[nyav]

Package: searchandrescue
Version: 1.5.0-2+b1
Severity: normal

Dear Maintainer, a new version of Search and Rescue was released : 
1.6.0.

Bug#880051: less: please bump priority to important

[Adam Borowski]

Package: less
Version: 481-2.1
Severity: wishlist

Hi!
We're doing a lot to trim down high priorities these days.  I'd like to
propose one step in the other direction: let's make "less" important.

The Policy says:

# important
#   Important programs, including those which one would expect to find on
#   any Unix-like system.  If the expectation is that an experienced Unix
#   person who found it missing would say “What on earth is going on, where
#   is foo?”, it must be an important package.  Other packages without which
#   the system will not run well or be usable must also have priority
#   important.  This does not include Emacs, the X Window System, TeX or any
#   other large applications.  The important packages are just a bare
#   minimum of commonly-expected and necessary tools.

I might be delusional, but I believe my claim to be "an experienced Unix
person" is not totally unbased.  A pager is required for most sysadmin
tasks, especially whenever something goes wrong (which is also when you
might have problems installing additional packages).  There's "more" but it
stopped being adequate at least two decades ago.

This is most visible in d-i (well, bumping severity won't produce an udeb,
but it's a good illustration), where any trouble means reading the
installation log.  Console 4 has the last page, but d-i being spammy, the
culprit is usually on the next-to-the-last page.  Try getting there with
"more" -- after a long bout of holding Space, you're almost guaranteed to
overshoot on the first try.  And this is one of environments where you can't
just utter a short curse and "apt install less".

Thus, while less is not absolutely needed (that's priority:required), it
feels to be way above mere priority:standard.

AFAIK a priority change requires a manual edit of the override file, but
obviously this shouldn't be done without the maintainer's approval -- that's
why I'm bothering you first.


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

Kernel: Linux 4.14.0-rc6-debug-00039-gde7173745fe2 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages less depends on:
ii  debianutils  4.8.2
ii  libc62.24-17
ii  libtinfo56.0+20170902-1

less recommends no packages.

less suggests no packages.

-- no debconf information

Bug#878584: [Pkg-e-devel] Bug#878584: [libevas-dev] Missing dependency for libecore-dev

[Ross Vandegrift]

On Mon, Oct 16, 2017 at 07:55:07PM +0200, Andreas Metzler wrote:
> I have not yet read over the patch in detail, I just have three quick
> notes:

Thanks for the feedback.  I've fixed these issues, but kept the
transitional package for libelementary-dev.  stable & sid have it,
but it comes from the old separate elementary source.

All pending updates plus an upgrade to 1.20.5 have been pushed to:
https://github.com/rvandegrift/efl/tree/debian/experimental

I've tested upgrades from current sid & experimental, including
replacing old -dev packages.  Ready for review when you get a chance.

(mentors isn't accepting my upload right now, I can try again later if
you'd like to see a built package.)

Thanks,
Ross

Bug#880050: No Display port audio with Nvidia driver 375.82

[Chris Elmes]

Package: nvidia-driver
Version: 375.82-1~deb9u1
Severity: important

Hello,

Display port audio stops working after upgrading to version: 375.82, was
working on older version: 375.66

Debian stretch 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28)

Nvidia Quadro k5200

Some more information found on Nvidia Dev talk site:

https://devtalk.nvidia.com/default/topic/1019761/linux/no-sound-using-displayport-audio-with-375-82-384-59-and-384-69/

>From kernel log:
snd_hda_codec_hdmi hdaudioC0D0: invalid ELD data byte 0

Same output:
 monitor_present 0
 eld_valid 0
from:
 cat /proc/asound/card0/eld#0.*
As on Nvidia Dev talk link.


--


Best Regards

ch...@cosmichpc.com

CosmicHPC.com

Cosmic HPC LLC

Bug#879720: RFS: runescape/0.2-1 [QA] -- Multiplayer online game set in a fantasy world

[Carlos Donizete Froes]

bts tag 879720 +confirmed

Em sáb, 2017-10-28 às 10:44 +0200, Tobias Frost escreveu:
> #866227 - ok now. You might also mark it pending though on the BTS

Sorry, it's my first time that I'm checking something pending, if I'm doing it
wrong, correct me or let me know how I do it correctly.

I answered this BTS #866227

> #879784
> Looking at the package at mentors, I do not see a change in the package that
> adresses this. The diff from the last version only changes d/changelog and
> (whitespace change) to d/runescape.8

Strange, because I made changes to the date in the "month / year" part and
removed my email from the "author".

In addition to removing the blanks had in 'd/runescape.6'

> Looking at the comment / BTS: No, this is not how it should be fixed.
> Please make a safe temporary directory or at least ensure that it does
> not exist before you try to create it and bail out with an error if so.
> You can use your PID or the help of mktemp to do the first.
> 
> It is not a valid argument that this behaviour has been the same already
> in the first version.

I changed the line with the 'mktemp' command as suggested.

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#880033: src:libreoffice: FTBFS on hppa - missing symbols

[Rene Engelhard]

retitle 874274 libreoffice: FTBFS on hppa - undefined references linking sv
forcemerge 874274 880033
thanks

Hi,

On Sat, Oct 28, 2017 at 01:18:31PM -0400, John David Anglin wrote:
> Since 1:5.2.7-1, libreoffice has failed to build from source on hppa.  The

That's evidently wrong.

https://buildd.debian.org/status/logs.php?pkg=libreoffice=hppa

1:5.2.7-1 (sid) Maybe-Successful2017-05-08 20:03:36 bell
21h 39m 6.55 GB

so if at all since 1:5.3.0~alpha1-1

And some of these were just internal compiler errors or other toolchain issues.

> following errors occurred in 1:5.4.3~rc1-2 build:

How is this different to

#874274 [n|  |  ] [src:libreoffice] libreoffice: FTBFS on hppa - undefined 
references linking slideshow

actually even filed by yourself? More care, please. It's not hard to do a
simple search for "hppa" in the buglog of src:libreoffice.

(Not to mention this isn't slideshow which fails to link, you get confused by
the parallel build and/or slideshow doing stuff before the svx  link).

> /<>/workdir/CxxObject/svx/source/fmcomp/fmgridcl.o: In function 
> `FmGridHeader::ExecuteDrop(ExecuteDropEvent const&)':
> ././svx/source/fmcomp/fmgridcl.cxx:266: undefined reference to 
> `dbtools::getConnection_withFeedback(rtl::OUString const&, rtl::OUString 
> const&, rtl::OUString const&, 
> com::sun::star::uno::Reference 
> const&)'
> /<>/workdir/CxxObject/svx/source/fmcomp/fmgridcl.o: In function 
> `FmGridHeader::PostExecuteColumnContextMenu(unsigned short, PopupMenu const&, 
> unsigned short)':
> ././svx/source/fmcomp/fmgridcl.cxx:947: undefined reference to 
> `dbtools::TransferFormComponentProperties(com::sun::star::uno::Reference
>  const&, com::sun::star::uno::Reference 
> const&, com::sun::star::lang::Locale const&)'
> /<>/workdir/CxxObject/svx/source/fmcomp/fmgridcl.o: In function 
> `FmGridHeader::OnAsyncExecuteDrop(void*)':
> ././svx/source/fmcomp/fmgridcl.cxx:378: undefined reference to 
> `dbtools::getNumberFormats(com::sun::star::uno::Reference
>  const&, bool, 
> com::sun::star::uno::Reference 
> const&)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `DbFormattedField::GetFormatText(com::sun::star::uno::Reference
>  const&, 
> com::sun::star::uno::Reference 
> const&, Color**)':
> ././svx/source/fmcomp/gridcell.cxx:1486: undefined reference to 
> `dbtools::DBTypeConversion::getValue(com::sun::star::uno::Reference
>  const&, com::sun::star::util::Date const&)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `DbFormattedField::UpdateFromField(com::sun::star::uno::Reference
>  const&, 
> com::sun::star::uno::Reference 
> const&)':
> ././svx/source/fmcomp/gridcell.cxx:1530: undefined reference to 
> `dbtools::DBTypeConversion::getValue(com::sun::star::uno::Reference
>  const&, com::sun::star::util::Date const&)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `FmXGridCell::getLock()':
> ././svx/source/fmcomp/gridcell.cxx:3242: undefined reference to 
> `connectivity::checkDisposed(bool)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `FmXGridCell::addWindowListener(com::sun::star::uno::Reference
>  const&)':
> ././svx/source/fmcomp/gridcell.cxx:3297: undefined reference to 
> `connectivity::checkDisposed(bool)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `FmXGridCell::addFocusListener(com::sun::star::uno::Reference
>  const&)':
> ././svx/source/fmcomp/gridcell.cxx:3311: undefined reference to 
> `connectivity::checkDisposed(bool)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `FmXGridCell::addKeyListener(com::sun::star::uno::Reference
>  const&)':
> ././svx/source/fmcomp/gridcell.cxx:3325: undefined reference to 
> `connectivity::checkDisposed(bool)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `FmXGridCell::addMouseListener(com::sun::star::uno::Reference
>  const&)':
> ././svx/source/fmcomp/gridcell.cxx:3339: undefined reference to 
> `connectivity::checkDisposed(bool)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o:././svx/source/fmcomp/gridcell.cxx:3353:
>  more undefined references to `connectivity::checkDisposed(bool)' follow
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `DbNumericField::implAdjustGenericFieldSetting(com::sun::star::uno::Reference
>  const&)':
> ././svx/source/fmcomp/gridcell.cxx:1902: undefined reference to 
> `dbtools::getConnection(com::sun::star::uno::Reference
>  const&)'
> ././svx/source/fmcomp/gridcell.cxx:1902: undefined reference to 
> `dbtools::getNumberFormats(com::sun::star::uno::Reference
>  const&, bool, 
> com::sun::star::uno::Reference 
> const&)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> `FmXGridCell::onFocusLost(com::sun::star::awt::FocusEvent const&)':
> ././svx/source/fmcomp/gridcell.cxx:3395: undefined reference to 
> `connectivity::checkDisposed(bool)'
> /<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
> 

Bug#880049: RFS: btrfs-progs/4.13.3-1~bpo9+1 [continuing to update the bpo]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my bpo of "btrfs-progs".

  I skipped 4.12-1 because it had a lintian BCP-78 (non DFSG) error;
  this was resolved upstream during the 4.13.x cycle.  Please upload
  to delayed to give Axel Burri time to resolve #878926 "Btrbk
  (>=0.26.0) bpo needed for users of stretch-backports).  Summary:
  btrfs-progs changed subvolume list format breaking btrck's parsing,
  but I'm not sure how many of btrbk's 129 users (popcon installed)
  are using stretch-backports.

 * Package name: btrfs-progs
   Version : 4.13.3-1~bpo9+1
   Upstream Author : linux-bt...@vger.kernel.org
 * URL : http://btrfs.wiki.kernel.org/
 * License : GPL-2
   Section : admin

  It builds these binary packages:

btrfs-progs - Checksumming Copy on Write Filesystem utilities
 btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
(udeb)
 btrfs-tools - transitional dummy package

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

  https://mentors.debian.net/package/btrfs-progs


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

dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.13.3-1~bpo9+1.dsc

  More information about hello can be obtained from 
http://btrfs.wiki.kernel.org/

  Changes since the last upload:

btrfs-progs (4.13.3-1~bpo9+1) stretch-backports; urgency=medium

  * Rebuild for stretch-backports.

 -- Nicholas D Steeves   Tue, 24 Oct 2017 09:43:07 -0400

btrfs-progs (4.13.3-1) unstable; urgency=medium

  [ Dimitri John Ledkov ]
  * New upstream release.
  * Add breaks against incompatible btrbk. Closes: #872836
  * Use noawait trigger variant, updating initramfs is optional, and
doesn't relly matter when it happens, as long as it does, eventually.

  [ Nicholas D Steeves ]
  * Add copyright for tests/sha.h tests/sha224-256.c tests/sha-private.h
  * Drop dh-autoreconf from build-depends, because it's automatic now.

 -- Dimitri John Ledkov   Wed, 18 Oct 2017 13:15:37 +0100

btrfs-progs (4.12-1) unstable; urgency=medium

  [ Dimitri John Ledkov ]
  * New upstream release.
  * Update watch file to v4.

  [ Nicholas D Steeves ]
  * Override dh_auto_clean to work around upstream bug where make clean cannot
be run before ./configure
  * Drop btrfs-convert (Closes: #824895, #854489)
  * Update Source, because Chris Mason's branch hasn't been updated since v4.4
  * 4.6.1-1 did not fix package license Btrfs-progs is explicitly GPL2 and
not GPL2+.
  * Update copyright for new locations of: radix-tree.c and radix-tree.h
  * d/control: add whitespace (cosmetic fix)
  * Switch to debhelper 10 and automatically generated -dbgsym package

 -- Dimitri John Ledkov   Mon, 31 Jul 2017 15:18:39 +0100

btrfs-progs (4.9.1-1) unstable; urgency=medium

  [ Dimitri John Ledkov ]
  * New upstream release Closes: #849353, #817806, #854915, #845473
  * Use dh addon for bash completion (--with bash-completion)
  * Suggest duperemove Closes: #703169

  [ Hideki Yamane ]
  * debian/control
- add Build-Depends: bash-completion to use dh_bash-completion
  * debian/rules
- call dh_bash-completion
  * add debian/btrfs-progs.bash-completion Closes: #840302, #800790.

  [ Helmut Grohne ]
  * Fix FTCBFS: cross.patch: Indirect pkg-config invocations through
$PKG_CONFIG and autoreconf (Closes: #845816)

 -- Dimitri John Ledkov   Mon, 13 Feb 2017 11:45:42 +


  Regards,
   Nicholas D Steeves

Bug#880038: [xml/sgml-pkgs] Bug#880038: libxslt: Adapt to glibc 2.26

[Mattia Rizzolo]

Control: tag -1 pending

On Sat, Oct 28, 2017 at 03:01:05PM -0400, Jeremy Bicha wrote:
> Ubuntu 17.10+ includes glibc 2.26 (glibc 2.25 is currently in Debian
> experimental).
> 
> Please apply this patch for compatibility with glibc 2.26:

wait, but why did ubuntu quickly leaped to glibc 2.26!?

> https://git.gnome.org/browse/libxslt/commit/?id=8b4babb

I applied this to git, will be in the next release.

> The Ubuntu bug that was used for this issue is
> https://launchpad.net/bugs/1715599

Given that I see it is fixed in ubuntu already (by just removing the
include, instead of making it optional), I suppose there is no need for
me do to upload it.
Thank you for taking the time to inform us (rather than just to upload
to ubuntu and forget!).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#866227: runescape: Use a better icon file format

[Carlos Donizete Froes]

bts tag 866227 +confirmed

Hi,

[1] It has been fixed in version 0.2, follows the improvements:

version: 0.2
  * Fixed desktop file
  * Added initial file transfer progress bar
  * Replaced command line to create temporary directory
  * Makefile version updated to 0.2
  * Removed official icon in format (xpm)
  * Added official icon in format (png) size 256 pixels

[1] - https://anonscm.debian.org/cgit/pkg-games/runescape.git

Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#880047: postgrey doesn't start because it can't write its pid

[Paul Lockaby]

Package: postgrey
Version: 1.36-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The default init script that comes with Postgrey on Debian 9 fails to start 
after a reboot. The installer creates /var/run/postgrey and writes its pid 
there but /var/run is a tmpfs file system and so on a reboot /var/run/postgrey 
ceases to exist. The init script for Postgrey does not attempt to create 
/var/run/postgrey and just fails to start when it can't write to 
/var/run/postgrey. When postgrey fails to start then Postfix starts complaining 
that it is misconfigured and begins bouncing emails. I was able to fix this by 
adding these lines to the do_start function in the init script:

# Assure that /var/run/postgrey exists
[ -d /var/run/postgrey ] || mkdir -p /var/run/postgrey

if [ "$DAEMON_USER" != "root" ]; then
chown "$DAEMON_USER" /var/run/postgrey
fi


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

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

Versions of packages postgrey depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
pn  libberkeleydb-perl 
pn  libnet-dns-perl
pn  libnet-server-perl 
pn  libnetaddr-ip-perl 
ii  perl   5.24.1-3+deb9u2
ii  ucf3.0036

Versions of packages postgrey recommends:
pn  libnet-rblclient-perl  
pn  libparse-syslog-perl   
ii  postfix3.1.6-0+deb9u1

postgrey suggests no packages.

Bug#879784: runescape: Hardcoded temporary directory

[Carlos Donizete Froes]

Hi,

Replaces 'mktemp' command in the temporary directory creation line in the script
(src/runescape.sh).

Thanks!


-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#878356: cross-gcc-dev should support gcc-8

[Dima Kogan]

Helmut: are you satisfied that this works? The patch set is in-place,
and it applies. There were problems building the packages, and I haven't
looked into that yet.

I don't know how much of these patches you actually use. If you don't
see these failures, then I'm inclined to close this bug. It'd be great
to get everything working, but since you're the only consumer of these,
as far as I know, I'd rather use my limited cycles to fix something
else.

If, however, that IS getting in your way, do tell me, and I'll fix it.

Bug#880046: fritzing: build problem with boost 1.65.1

[Jeremy Bicha]

Source: fritzing
Version: 0.9.3b+dfsg-4.1
Tags: patch

Ubuntu 18.04 LTS development has begun and boost1.65.1 was uploaded.
(It looks like it's in Debian's NEW queue).

fritzing's boost check didn't seem to work so I am applying this patch
in Ubuntu to work around the issue.

Thanks,
Jeremy Bicha
=== modified file 'debian/patches/series'
--- debian/patches/series	2017-10-28 21:19:08 +
+++ debian/patches/series	2017-10-28 21:19:21 +
@@ -5,3 +5,4 @@
 no-isystem-for-gcc6.patch
 fritzing.desktop.patch
 add-proxy-parameter.diff
+system-boost.patch

=== added file 'debian/patches/system-boost.patch'
--- debian/patches/system-boost.patch	1970-01-01 00:00:00 +
+++ debian/patches/system-boost.patch	2017-10-28 21:21:55 +
@@ -0,0 +1,17 @@
+---
+ pri/utils.pri |4 +---
+ 1 file changed, 1 insertion(+), 3 deletions(-)
+
+--- a/pri/utils.pri
 b/pri/utils.pri
+@@ -47,9 +47,7 @@ contains(LATESTBOOST, 0) {
+ }
+ 
+ contains(LATESTBOOST, 0) {
+-message("Please download the boost library--you can find it at http://www.boost.org/;)
+-message("Note that boost 1.54 has a bug in a function that Fritzing uses, so download some other version")
+-error("Copy the boost library to .../src/lib/, so that you have .../src/lib/boost_1_xx_0")
++INCLUDEPATH += /usr/include/boost
+ }
+ 
+ !contains(LATESTBOOST, installed) {

Bug#880045: RM: python-coffin -- ROM; no reverse dependency

[Thomas Goirand]

Package: ftp.debian.org
Severity: normal


Hi,

The sole reason why I was maintaining coffin was to run unit tests in
django-compressor. Since the last upload of python-django-compressor, that's
no longer necessary, and there's no other package that (build-)depend on it.

Let's remove it.
Cheers,

Thomas Goirand (zigo)

Bug#880044: RM: python-jingo -- ROM; Deprecated, no reverse deps anymore

[Thomas Goirand]

Package: ftp.debian.org
Severity: normal


Hi,

Jingo was used in python-django-compressor, itself used in the OpenStack
Dashboard. Though Jingo is now deprecated, and used nowhere. Plus it doesn't
even support modern Django (upstream stopped at Django 1.8, and I've patched
it heavily to support 1.9, then 1.10 in Stretch).

There's also alternatives like django-jinja, already packaged in Debian and
already in Stretch and Buster.

So there's no reason to to keep python-jingo in Debian any longer. Please
remove it ASAP.

Cheers,

Thomas Goirand (zigo)

Bug#880043: flatpak: Autopkgtests always fail on Ubuntu

[Jeremy Bicha]

Source: flatpak
Version: 0.10.0-1

The autopkgtest for flatpak has never succeeded on Ubuntu. It would be
nice if it were working.

http://autopkgtest.ubuntu.com/packages/f/flatpak/bionic/amd64

http://autopkgtest.ubuntu.com/packages/flatpak

(The armhf and s390x machines don't offer the required machine-level isolation.)

Technically, ppc64el did manage to pass a few times in early September
but maybe the machines were configured differently then:
http://autopkgtest.ubuntu.com/packages/flatpak/artful/ppc64el

Do you think this might be similar to the proxy issue we had with ostree?

Thanks,
Jeremy Bicha

Bug#880042: [l10n]: Update Japanese translation

[Hideki Yamane]

Package: apt-listchanges
Version: 3.14
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

 I've updated Japanese translation for apt-listchanges.
 Could you apply attached ja.po patch, please?

-- 
Regards,

 Hideki Yamane
From 4074650af4007893fe14561680b6ebfec99d2923 Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Sun, 29 Oct 2017 05:57:03 +0900
Subject: [PATCH] update ja.po

---
 po/ja.po | 197 +--
 1 file changed, 90 insertions(+), 107 deletions(-)

diff --git a/po/ja.po b/po/ja.po
index 4a585e0..ee71ea0 100644
--- a/po/ja.po
+++ b/po/ja.po
@@ -1,16 +1,16 @@
 # apt-listchanges Japanese
 # Copyright (C) 2002
 # Junichi Uekawa , 2002, 2005
-#
+# Hideki Yamane , 2017
 msgid ""
 msgstr ""
 "Project-Id-Version: apt-listchanges\n"
 "Report-Msgid-Bugs-To: apt-listchan...@packages.debian.org\n"
 "POT-Creation-Date: 2017-07-08 22:48+0200\n"
-"PO-Revision-Date: 2008-10-03 22:04-0700\n"
-"Last-Translator: Junichi Uekawa \n"
+"PO-Revision-Date: 2017-10-29 05:54+0900\n"
+"Last-Translator: Hideki Yamane \n"
 "Language-Team: Japanese \n"
-"Language: \n"
+"Language: ja\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8-bit\n"
@@ -24,7 +24,7 @@ msgstr "不明なフロントエンド: %s"
 #: ../apt-listchanges.py:79
 #, python-format
 msgid "Cannot reopen /dev/tty for stdin: %s"
-msgstr ""
+msgstr "標準入力に対して /dev/tty を再オープンできません: %s"
 
 #: ../apt-listchanges.py:125
 #, python-format
@@ -59,10 +59,8 @@ msgid "apt-listchanges: changelogs for %s"
 msgstr "apt-listchanges: %s の changelog "
 
 #: ../apt-listchanges.py:151
-#, fuzzy
-#| msgid "didn't find any valid .deb archives"
 msgid "Didn't find any valid .deb archives"
-msgstr "有効な.debアーカイブを見付ける事ができませんでした"
+msgstr "有効な .deb アーカイブを見付ける事ができませんでした"
 
 #: ../apt-listchanges.py:168
 #, python-format
@@ -72,29 +70,29 @@ msgstr "%s: を新規にインストールします"
 #: ../apt-listchanges.py:195
 #, python-format
 msgid "%(pkg)s: Version %(version)s has already been seen"
-msgstr "%(pkg)s: バージョン %(version)s は既にみられています"
+msgstr "%(pkg)s: バージョン %(version)s は閲覧済みです"
 
 #: ../apt-listchanges.py:199
-#, fuzzy, python-format
-#| msgid "%(pkg)s: Version %(version)s has already been seen"
+#, python-format
 msgid ""
 "%(pkg)s: Version %(version)s is lower than version of related packages "
 "(%(maxversion)s)"
-msgstr "%(pkg)s: バージョン %(version)s は既にみられています"
+msgstr "%(pkg)s: バージョン %(version)s は関連するパッケージのバージョン "
+"(%(maxversion)s) より低いです"
 
 #: ../apt-listchanges.py:271
 #, python-format
 msgid "Received signal %d, exiting"
-msgstr ""
+msgstr "シグナル %d を受け取りました、終了します"
 
 #: ../apt-listchanges/apt_listchanges.py:54
 msgid "Aborting"
-msgstr "アボートします"
+msgstr "強制終了します"
 
 #: ../apt-listchanges/apt_listchanges.py:59
-#, fuzzy, python-format
+#, python-format
 msgid "Confirmation failed: %s"
-msgstr "情報メモ"
+msgstr "確認が失敗しました: %s"
 
 #: ../apt-listchanges/apt_listchanges.py:63
 #, python-format
@@ -102,60 +100,58 @@ msgid "Mailing %(address)s: %(subject)s"
 msgstr "%(address)s にメール: %(subject)s"
 
 #: ../apt-listchanges/apt_listchanges.py:82
-#, fuzzy, python-format
-#| msgid "database %s failed to load."
+#, python-format
 msgid "Failed to send mail to %(address)s: %(errmsg)s"
-msgstr "データベース %s をロードするのに失敗しました"
+msgstr "%(address)s 宛メールの送信に失敗しました: %(errmsg)s"
 
 #: ../apt-listchanges/apt_listchanges.py:91
-#, fuzzy, python-format
+#, python-format
 msgid "The mail frontend needs an installed 'sendmail', using %s"
 msgstr ""
-"メールフロントエンドを利用するには sendmail がインストールされている必要があ"
-"ります。pager を使います。"
+"メールフロントエンドは 'sendmail' がインストールされている必要があ"
+"るので、%s を使います"
 
 #: ../apt-listchanges/apt_listchanges.py:97
-#, fuzzy, python-format
+#, python-format
 msgid "The mail frontend needs an e-mail address to be configured, using %s"
 msgstr ""
-"メールフロントエンドを利用するには sendmail がインストールされている必要があ"
-"ります。pager を使います。"
+"メールフロントエンドにはメールアドレスが設定されている必要があるので、%s "
+"を使います"
 
 #: ../apt-listchanges/apt_listchanges.py:110
-#, fuzzy
 msgid "Available apt-listchanges frontends:"
-msgstr "apt-listchanges: ニュース"
+msgstr "利用可能な apt-listchanges のフロントエンド:"
 
 #: ../apt-listchanges/apt_listchanges.py:112
 msgid "Choose a frontend by entering its number: "
-msgstr ""
+msgstr "番号を入力してフロントエンドを選択して下さい:"
 
 #: ../apt-listchanges/apt_listchanges.py:121
 #: ../apt-listchanges/apt_listchanges.py:415
 #, python-format
 msgid "Error: %s"
-msgstr ""
+msgstr "エラー: %s"
 
 #: ../apt-listchanges/apt_listchanges.py:123
-#, fuzzy, python-format
+#, python-format
 msgid "Using default frontend: %s"
-msgstr "不明なフロントエンド: %s\n"
+msgstr "デフォルトのフロントエンドを利用します: %s"
 
 #: ../apt-listchanges/apt_listchanges.py:166
 #, python-format
 msgid "$DISPLAY is not set, falling back to %(frontend)s"
-msgstr ""
+msgstr "$DISPLAY が設定されていません、%(frontend)s にフォールバックします"
 
 #: ../apt-listchanges/apt_listchanges.py:186
-#, fuzzy, python-format
+#, python-format
 msgid ""
 "The gtk frontend needs a working 

Bug#879913: sdlgfx: please make the build reproducible

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi,

2017-10-27 10:38 Chris Lamb:

Source: sdlgfx
Version: 2.0.25-8
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that sdlgfx could not be built reproducibly.

This is because the tar call iterates over the filesystem in a
non-deterministic order to generate the examples archive.

Patch attached that uses --sort=name from GNU tar 1.28, but you could
alternatively `find | LC_ALL=C sort` etc.


Thanks, patch applied, I expect to upload soon.

--
Manuel A. Fernandez Montecelo 

Bug#880041: git: FTBFS on hppa - recipe for target 't6120-describe.sh' failed

[John David Anglin]

Source: git
Version: 1:2.15.0-rc2-1
Severity: normal

Dear Maintainer,

The following test fails:

expecting success: 
git tag -f far-far-away HEAD~7999 &&
echo "far-far-away" >expect &&
git describe --tags --abbrev=0 HEAD~4000 >actual &&
test_cmp expect actual &&
run_with_limited_stack git describe --tags --abbrev=0 HEAD~4000 >actual 
&&
test_cmp expect actual

Updated tag 'far-far-away' (was a01ce62)
Segmentation fault
not ok 61 - describe works in a deep repo
#   
#   git tag -f far-far-away HEAD~7999 &&
#   echo "far-far-away" >expect &&
#   git describe --tags --abbrev=0 HEAD~4000 >actual &&
#   test_cmp expect actual &&
#   run_with_limited_stack git describe --tags --abbrev=0 HEAD~4000 
>actual &&
#   test_cmp expect actual
#   

# still have 1 known breakage(s)
# failed 1 among remaining 60 test(s)
1..61
Makefile:49: recipe for target 't6120-describe.sh' failed
make[4]: *** [t6120-describe.sh] Error 1

Full log is here:
https://buildd.debian.org/status/fetch.php?pkg=git=hppa=1%3A2.15.0%7Erc2-1=1508787104=0

Regards,
Dave Anglin


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

Kernel: Linux 4.13.10+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), 
LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information

Bug#874003: Confirmation bug #874003

[Dion van Oirschot]

I can confirm this behavior on my Debian unstable system with nautilus
3.26.0-1.

However: if I create a new user, for the new user, nautilus works fine
and as expected. So this problem seems somehow related to user
settings. I don't know how though.

Bug#880040: plasma-workspace: PlasmaShell eats a lot of memory and CPU

[Adrian Ban]

Package: plasma-workspace
Version: 4:5.10.5-2
Severity: normal
Tags: upstream

Dear Maintainer,

I've notice that the plasmashell is starting to eat a huge amount of memory and
CPU.
A simple copy of a AVI file from my local HDD to a network storage lead to
this.

Sometimes only keeping the system running with anykind of software opened is
starting to eat memory.
The only way to recover the PC memory is to logout and login.

Here is the TOP command output:

top - 22:18:47 up 11:54,  1 user,  load average: 0.13, 0.65, 1.15
Tasks: 258 total,   1 running, 257 sleeping,   0 stopped,   0 zombie
%Cpu0  :  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu1  :  4.0 us,  0.0 sy,  0.0 ni, 96.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu2  :  5.0 us,  5.0 sy,  0.0 ni, 90.1 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu3  :  1.0 us,  2.0 sy,  0.0 ni, 97.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu4  :  2.0 us,  0.0 sy,  0.0 ni, 98.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu5  :  2.0 us,  3.0 sy,  0.0 ni, 95.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu6  :  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu7  :  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem : 11995152 total,   191884 free,  7161560 used,  4641708 buff/cache
KiB Swap:  4192252 total,  4192252 free,0 used.  4293708 avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
 8340 adrian20   0 10.688g 5.816g 128236 S  16.8 50.8 499:07.38
/usr/bin/plasmashell
 8583 adrian20   0  647900 131692  16152 S   0.0  1.1   0:18.08
/usr/sbin/mysqld --defaults-file=/home/adrian/.local/share/akonadi/mysql.conf
--datadir=+
 8332 adrian20   0 3159180 112652  67012 S   1.0  0.9   9:24.46 kwin_x11
18378 adrian20   0 1030484 104304  41312 S   1.0  0.9   0:49.12
/usr/bin/perl /usr/bin/pac
 5264 root  20   0  661300  99624  43592 S   5.9  0.8 218:17.48
/usr/lib/xorg/Xorg -nolisten tcp -auth
/var/run/sddm/{797df2b6-92bb-4aac-a61b-eb8b20a069+
 8377 adrian20   0 1053044  84748  56504 S   0.0  0.7   0:12.72
/usr/bin/owncloud
 7010 adrian20   0  753164  83576  41608 S   1.0  0.7   0:10.18
/usr/bin/python3 /usr/bin/reportbug --exit-prompt --ui gtk2
13652 adrian20   0  762580  74880  58220 S   3.0  0.6   5:33.55
/usr/bin/systemmonitor
 8337 adrian20   0  765784  68920  52328 S   0.0  0.6   0:29.49
/usr/bin/krunner
 8386 adrian20   0  985492  65476  55188 S   0.0  0.5   0:00.60
/usr/bin/korgac

Adrian



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

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

Versions of packages plasma-workspace depends on:
ii  dbus-x11 1.11.20-1
ii  frameworkintegration 5.37.0-2
ii  gdb  7.12-6+b1
ii  iso-codes3.76-1
ii  kactivitymanagerd5.10.5-2
ii  kde-cli-tools4:5.10.5-2
ii  kded55.37.0-2
ii  kinit5.37.0-2
ii  kio  5.37.0-2
ii  kpackagetool55.37.0-2
ii  kwin-common  4:5.10.5-2
ii  libappstreamqt2  0.11.6-2
ii  libc62.24-17
ii  libcln6  1.3.4-2+b1
ii  libgcc1  1:7.2.0-11
ii  libgps22 3.16-4
ii  libice6  2:1.0.9-2
ii  libkf5activities55.37.0-2
ii  libkf5auth5  5.37.0-2
ii  libkf5baloo5 5.37.0-2
ii  libkf5bookmarks5 5.37.0-2
ii  libkf5calendarevents55.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5coreaddons55.37.0-2
ii  libkf5crash5 5.37.0-2
ii  libkf5dbusaddons55.37.0-2
ii  libkf5declarative5   5.37.0-2
ii  libkf5globalaccel-bin5.37.0-2
ii  libkf5globalaccel5   5.37.0-2
ii  libkf5guiaddons5 5.37.0-2
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5idletime5  5.37.0-2
ii  libkf5itemviews5   

Bug#861656: closed by Thomas Goirand <z...@debian.org> (New version was uploaded)

[Antoine Musso]

I have filled this bug hoping stretch would consider bumping
python-jenkins 0.4.11 to 0.4.12 before it get released.  That did not make.

As a result python-jenkins and jenkins-job-builder are broken whenever
one target a Jenkins that uses a subpath such as https://host/ci/


>From my May 3rd reply
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861656#24  the commit
that would need to be included in stretch are:

---
1)  302eb5d Fixed create_node() Error

Fix the issue I reported in this bug, does not impact Jenkins Job Builder.

2) 2aa1a5f Use TestWithScenarios to add additional url tests

That fix the example I gave above when trying to get_info() from a
remote Jenkins.
---


Meanwhile both packages are unusuable against Jenkins instances with /ci/.


-- 
Antoine "hashar" Musso

Bug#872719: lxc: please use deb.debian.org as default mirror in lxc-debian template

[Salvatore Bonaccorso]

Source: lxc
Source-Version: 1:2.0.9-1

Hi

On Sun, Aug 20, 2017 at 03:15:14PM +0200, Salvatore Bonaccorso wrote:
> Source: lxc
> Severity: wishlist
> 
> Hi
> 
> In #805085 in the debian template, the default mirror was changed to
> httpredir.debian.org, but in meanwhile this service has been
> discontinued in favour of deb.debian.org[1]. Can you consider switching
> the default mirror to deb.debian.org?

This has been fixed in 2.0.9 upstream.

Regards,
Salvatore

Bug#877555: libgegl-dev should supply VAPI bindings

[Al Thomas]

> On Sun, 15 Oct 2017 20:20:00 -0400 Jeremy Bicha wrote:> There doesn't appear 
> to be any .vapi file generated by the build.
The vapigen program needs to be installed on the build machine. The VAPI should 
then be generated.
There is a check in configure.ac for 
vapigen:https://git.gnome.org/browse/gegl/tree/configure.ac#n478
vapigen is part of the valac package, 
e.g.https://packages.debian.org/stretch/i386/valac/filelist


Regards,
Al Thomas

Bug#880039: beara fails without en_US.UTF-8 locale

[luke]

Package: bear
Version: 2.3.7-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,


   A recent update to bear has caused execution of any subprocess to
   fail on my system:

> bear sh -c /bin/echo
bear: newlocale: No such file or directory

It seems this is caused by an inability to load the "en_US.UTF-8"
locale which is not installed on my system (see libear/ear.c:434).

It looks like this has been already been reported, and fixed
upstream in [this

commit](https://github.com/rizsotto/Bear/commit/b5d831ea158a8eff0b5dcb3d863e0046528189e6)

Without this commit it seems like any user of `bear` will have to have
en_US.UTF-8 installed.

Is there any possibilty debian can backport this fix, or do a
version bump?

All the Best

Luke


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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages bear depends on:
ii  libear   2.3.7-1
ii  python3  3.6.3-2

bear recommends no packages.

bear suggests no packages.

-- no debconf information

Bug#880038: libxslt: Adapt to glibc 2.26

[Jeremy Bicha]

Source: libxslt
Version: 1.1.29-2.2
Severity: important
Tags: patch

Ubuntu 17.10+ includes glibc 2.26 (glibc 2.25 is currently in Debian
experimental).

Please apply this patch for compatibility with glibc 2.26:

https://git.gnome.org/browse/libxslt/commit/?id=8b4babb

The Ubuntu bug that was used for this issue is
https://launchpad.net/bugs/1715599

Thanks,
Jeremy Bicha

Bug#879485: vhba-dkms: Upgrade vhba-dkms from vhba-20140928 to vhba-20170610

[debian blue]

Sorry .. realized it was a custom deb package install.

Is there a way for "reportbug" to detect and avoid this ?

On Fri, Oct 27, 2017 at 10:49 PM, Andreas Beckmann  wrote:

> On Sun, 22 Oct 2017 12:36:47 +0530 "debian.blue" 
> wrote:
> > Package: vhba-dkms
> > Version: 20140928-1
>
> Hi,
>
> this package is not part of Debian (nor could I find traces that it was
> in Debian at some point in the past).
> Please report problems to whomever provides this package.
>
>
> Andreas
>

Bug#878665: stretch-pu: package dput-ng/1.13

[Miguel Landaeta]

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

Hi,

I'm proposing to update dput-ng package in stretch.

The version included in stretch ship a default configuration that
doesn't allow to upload package to common suites like
stretch-backports. (#878665)

Please see the attached .debdiff and the inlined relevant changes
below:

diff -Nru dput-ng-1.13/debian/changelog dput-ng-1.15+deb9u1/debian/changelog
--- dput-ng-1.13/debian/changelog   2017-05-30 17:41:14.0 +0100
+++ dput-ng-1.15+deb9u1/debian/changelog2017-10-28 19:08:23.0 
+0100
@@ -1,3 +1,27 @@
+dput-ng (1.15+deb9u1) stretch; urgency=medium
+
+  [ Miguel Landaeta ]
+  * Team upload.
+  * New upstream stable release.
+
+  [ Mattia Rizzolo ]
+  * Fix typo on the jessie-backports-sloppy target.  (Closes: #867245)
+  * Include 'testing' in the rm-managed suites.
+  * Add jessie-backports-sloppy and stretch-backports. (Closes: #878665)
+  * Mark dput-ng-doc as Multi-Arch:foreign.
+  * wrap-and-sort.
+  * Bump Standards-Version to 4.0.0, no changes needed.
+  * doc/man: fix some spelling errors.
+
+  [ James Clarke ]
+  * Add ports-master profile. (Closes: #855154)
+
+  [ Stephan Sürken ]
+  * dput/uploaders/ftp.py: Parse and use optional [:port] part for fqdn.
+(Closes: #814440)
+
+ -- Miguel Landaeta   Sat, 28 Oct 2017 19:08:23 +0100
+
 dput-ng (1.13) unstable; urgency=medium
 
   * Team upload.
diff -Nru dput-ng-1.13/skel/codenames/debian.json 
dput-ng-1.15+deb9u1/skel/codenames/debian.json
--- dput-ng-1.13/skel/codenames/debian.json 2017-05-30 17:39:07.0 
+0100
+++ dput-ng-1.15+deb9u1/skel/codenames/debian.json  2017-10-28 
19:01:15.0 +0100
@@ -2,7 +2,9 @@
 "backport": [
 "stable-backports",
 "oldstable-backports",
+"stretch-backports",
 "jessie-backports",
+"jessie-backports-sloppy",
 "wheezy-backports",
 "wheezy-backports-sloppy",
 "squeeze-backports",
@@ -16,6 +18,7 @@
 "sid"
 ],
 "rm-managed": [
+"testing",
 "stable",
 "oldstable",
 "bullseye",
@@ -42,5 +45,8 @@
 "stretch-security",
 "buster-security",
 "bullseye-security"
+],
+"ports": [
+"unreleased"
 ]
 }


Thanks,

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

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

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche
diff -Nru dput-ng-1.13/debian/changelog dput-ng-1.15+deb9u1/debian/changelog
--- dput-ng-1.13/debian/changelog   2017-05-30 17:41:14.0 +0100
+++ dput-ng-1.15+deb9u1/debian/changelog2017-10-28 19:08:23.0 
+0100
@@ -1,3 +1,27 @@
+dput-ng (1.15+deb9u1) stretch; urgency=medium
+
+  [ Miguel Landaeta ]
+  * Team upload.
+  * New upstream stable release.
+
+  [ Mattia Rizzolo ]
+  * Fix typo on the jessie-backports-sloppy target.  (Closes: #867245)
+  * Include 'testing' in the rm-managed suites.
+  * Add jessie-backports-sloppy and stretch-backports. (Closes: #878665)
+  * Mark dput-ng-doc as Multi-Arch:foreign.
+  * wrap-and-sort.
+  * Bump Standards-Version to 4.0.0, no changes needed.
+  * doc/man: fix some spelling errors.
+
+  [ James Clarke ]
+  * Add ports-master profile. (Closes: #855154)
+
+  [ Stephan Sürken ]
+  * dput/uploaders/ftp.py: Parse and use optional [:port] part for fqdn.
+(Closes: #814440)
+
+ -- Miguel Landaeta   Sat, 28 Oct 2017 19:08:23 +0100
+
 dput-ng (1.13) unstable; urgency=medium
 
   * Team upload.
diff -Nru dput-ng-1.13/debian/control dput-ng-1.15+deb9u1/debian/control
--- dput-ng-1.13/debian/control 2017-05-30 17:39:07.0 +0100
+++ dput-ng-1.15+deb9u1/debian/control  2017-10-28 19:01:15.0 +0100
@@ -2,39 +2,49 @@
 Section: devel
 Priority: extra
 Maintainer: dput-ng Maintainers 
-Uploaders: Arno Töll ,
- Paul Tagliamonte 
-Build-Depends: debhelper (>= 10),
- dh-python,
- python-distro-info,
+Uploaders:
+ Arno Töll ,
+ Paul Tagliamonte ,
+Build-Depends:
+ asciidoc,
  bash-completion,
+ debhelper (>= 10),
+ dh-python,
+ docbook-xml,
+ docbook-xsl,
+ docbook-xsl-ns,
+ libxml2-utils,
  python-all (>= 2.7~),
- python-setuptools,
  python-coverage,
  python-debian,
+ python-distro-info,
  python-nose,
- python-validictory,
  python-paramiko,
+ python-setuptools,
  

Bug#876333: thunderbird: AppArmor profile allows mmap executables from user writable directories

[Carsten Schoenert]

Control: tags -1 + pending
Control: tags 855346 + pending

Hi intrigeri,

On Fri, Oct 27, 2017 at 11:37:33AM +0200, intrigeri wrote:
> Control: tag -1 + fixed-upstream
> 
> Thanks to Vincas this was fixed upstream at the same time as #855346:
> https://git.launchpad.net/apparmor-profiles/tree/ubuntu/17.10/usr.bin.thunderbird
> 
> Carsten, could you please pull this updated profile?

done for this and #855346 in 42f5ab5a35e29718addee693cecaca320b852f2f.

  
https://anonscm.debian.org/cgit/pkg-mozilla/thunderbird.git/commit/?id=42f5ab5a35e29718addee693cecaca320b852f2f

Please let me know if there is still something missing until we have
convinced the Alioth admins of pkg-mozilla to give you access.

Regards
Carsten

Bug#880026: systemd: CVE-2017-15908

[Michael Biebl]

Hi Salvatore!

Am 28.10.2017 um 17:38 schrieb Salvatore Bonaccorso:

> Since systemd-resolved is not enabled by default I think an update via
> an upcoming stretch point release would be enough. Please let us know
> if you disagre.

Seems reasonable to me. I've usertagged this bug report so it shows up
at [1] and we remember to pull this fix into our next stable release.
I think we have enough issues to make a release for 9.3

Regards,
Michael

[1]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintain...@lists.alioth.debian.org;tag=stretch-backport
-- 
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#880036: avahi: FTBFS: dh_systemd_start: Could not open avahai-daemon.socket

[Jeremy Bicha]

Source: avahi
Version: 0.7-3
Severity: serious

avahi fails to build for me in a clean sid chroot.

Build log excerpt
-
dh_installchangelogs -XChangeLog
make[1]: Leaving directory '/<>'
   dh_installexamples
   dh_installman
   dh_installifupdown
   dh_systemd_enable
   dh_python2
   dh_installinit
   dh_systemd_start
dh_systemd_start: Could not find "avahi-daemon.socket" in the
/lib/systemd/system directory of avahi-dnsconfd. This could be a typo,
or using Also= with a service file from another package. Please check
carefully that this message is harmless.
dh_systemd_start: Cannot open(avahi-daemon.socket) for extracting the
Also= line(s): No such file or directory
debian/rules:4: recipe for target 'binary' failed
make: *** [binary] Error 2

Thanks,
Jeremy Bicha

Bug#880035: parted: fails to use negative start value for 'mkpart' command without specyfying FS-TYPE

[Denis Pynkin]

Package: parted
Version: 3.2-18
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Trying to create partition via 'mkpart' with negative START value 
without specyfying optional FS-TYPE.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
parted -a none -s -- /dev/vda mkpart flags_backup -4M -6177s
or with interactive mode:
(parted) mkpart flags_backup -4M -6177s

   * What was the outcome of this action?
Partition is not created with failure message:
 parted: invalid token: -4M
 Error: Expecting a file system type.

   * What outcome did you expect instead?
Partition is created.

-- System Information:
Debian Release: 9.1
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.57-std-def-alt1.1 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages parted depends on:
ii  libc6 2.24-11+deb9u1
ii  libparted23.2-18
ii  libreadline7  7.0-3
ii  libtinfo5 6.0+20161126-1

parted recommends no packages.

Versions of packages parted suggests:
pn  parted-doc  

-- no debconf information

Bug#880034: qtscript-opensource-src: FTBFS on hppa - tst_QScriptEngine::collectGarbageAfterConnect

[John David Anglin]

Source: qtscript-opensource-src
Version: 5.9.1+dfsg-2
Severity: normal

Dear Maintainer,

Since 5.4.2+dfsg-2, this package fails to build on hppa:

FAIL!  : tst_QScriptEngine::collectGarbageAfterConnect() 'widget == 0' returned 
FALSE. ()
   Loc: [tst_qscriptengine.cpp(5701)]

Most recent build log is here:
https://buildd.debian.org/status/fetch.php?pkg=qtscript-opensource-src=hppa=5.9.2%2Bdfsg-1=1509153097=0

Regards,
Dave Anglin

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

Kernel: Linux 4.13.10+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), 
LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#736360: lintian: do not warn about doxygen embedding jquery

[Chris Lamb]

tags 736360 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=3d58ecb4d542530c8ba2a2a6d6ccb4f5246ede0b


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#865671: scotch hides build failures

[Drew Parsons]

tags 865671 moreinfo
thanks

On Fri, 23 Jun 2017 18:07:46 +0200 Helmut Grohne 
wrote:
> Source: scotch
> Version: 5.1.12b.dfsg-2
> 
> When some part of scotch's build fails (e.g. mpicc), the build
continues
> and may produce a broken package. This violates Debian Policy section
> 4.6. The cause is the use of an embedded makefile script without the
> recommended "set -e".
> 

This bug report is unconstructive.

Which makefile?

Which build failure?

Bug#880033: src:libreoffice: FTBFS on hppa - missing symbols

[John David Anglin]

Source: libreoffice
Version: 1:5.4.3~rc1-2
Severity: normal

Dear Maintainer,

Since 1:5.2.7-1, libreoffice has failed to build from source on hppa.  The
following errors occurred in 1:5.4.3~rc1-2 build:

mkdir -p /<>/workdir/ComponentTarget/slideshow/util/ && xsltproc 
--nonet --stringparam uri 'vnd.sun.star.expand:$LO_LIB_DIR/libslideshowlo.so' 
--stringparam cppu_env gcc3 -o 
/<>/workdir/ComponentTarget/slideshow/util/slideshow.component 
/<>/solenv/bin/createcomponent.xslt 
/<>/slideshow/util/slideshow.component
[build BIN] slideshow
S=/<> && I=$S/instdir && W=$S/workdir &&  mkdir -p 
$W/Module/nonl10n/ && touch $W/Module/nonl10n/slideshow
[build MOD] slideshow
S=/<> && I=$S/instdir && W=$S/workdir &&  mkdir -p $W/Module/ && 
touch $W/Module/slideshow
/<>/workdir/CxxObject/svx/source/fmcomp/fmgridcl.o: In function 
`FmGridHeader::ExecuteDrop(ExecuteDropEvent const&)':
././svx/source/fmcomp/fmgridcl.cxx:266: undefined reference to 
`dbtools::getConnection_withFeedback(rtl::OUString const&, rtl::OUString 
const&, rtl::OUString const&, 
com::sun::star::uno::Reference const&)'
/<>/workdir/CxxObject/svx/source/fmcomp/fmgridcl.o: In function 
`FmGridHeader::PostExecuteColumnContextMenu(unsigned short, PopupMenu const&, 
unsigned short)':
././svx/source/fmcomp/fmgridcl.cxx:947: undefined reference to 
`dbtools::TransferFormComponentProperties(com::sun::star::uno::Reference
 const&, com::sun::star::uno::Reference 
const&, com::sun::star::lang::Locale const&)'
/<>/workdir/CxxObject/svx/source/fmcomp/fmgridcl.o: In function 
`FmGridHeader::OnAsyncExecuteDrop(void*)':
././svx/source/fmcomp/fmgridcl.cxx:378: undefined reference to 
`dbtools::getNumberFormats(com::sun::star::uno::Reference
 const&, bool, 
com::sun::star::uno::Reference const&)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`DbFormattedField::GetFormatText(com::sun::star::uno::Reference
 const&, com::sun::star::uno::Reference 
const&, Color**)':
././svx/source/fmcomp/gridcell.cxx:1486: undefined reference to 
`dbtools::DBTypeConversion::getValue(com::sun::star::uno::Reference
 const&, com::sun::star::util::Date const&)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`DbFormattedField::UpdateFromField(com::sun::star::uno::Reference
 const&, com::sun::star::uno::Reference 
const&)':
././svx/source/fmcomp/gridcell.cxx:1530: undefined reference to 
`dbtools::DBTypeConversion::getValue(com::sun::star::uno::Reference
 const&, com::sun::star::util::Date const&)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`FmXGridCell::getLock()':
././svx/source/fmcomp/gridcell.cxx:3242: undefined reference to 
`connectivity::checkDisposed(bool)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`FmXGridCell::addWindowListener(com::sun::star::uno::Reference
 const&)':
././svx/source/fmcomp/gridcell.cxx:3297: undefined reference to 
`connectivity::checkDisposed(bool)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`FmXGridCell::addFocusListener(com::sun::star::uno::Reference
 const&)':
././svx/source/fmcomp/gridcell.cxx:3311: undefined reference to 
`connectivity::checkDisposed(bool)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`FmXGridCell::addKeyListener(com::sun::star::uno::Reference
 const&)':
././svx/source/fmcomp/gridcell.cxx:3325: undefined reference to 
`connectivity::checkDisposed(bool)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`FmXGridCell::addMouseListener(com::sun::star::uno::Reference
 const&)':
././svx/source/fmcomp/gridcell.cxx:3339: undefined reference to 
`connectivity::checkDisposed(bool)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o:././svx/source/fmcomp/gridcell.cxx:3353:
 more undefined references to `connectivity::checkDisposed(bool)' follow
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`DbNumericField::implAdjustGenericFieldSetting(com::sun::star::uno::Reference
 const&)':
././svx/source/fmcomp/gridcell.cxx:1902: undefined reference to 
`dbtools::getConnection(com::sun::star::uno::Reference
 const&)'
././svx/source/fmcomp/gridcell.cxx:1902: undefined reference to 
`dbtools::getNumberFormats(com::sun::star::uno::Reference
 const&, bool, 
com::sun::star::uno::Reference const&)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`FmXGridCell::onFocusLost(com::sun::star::awt::FocusEvent const&)':
././svx/source/fmcomp/gridcell.cxx:3395: undefined reference to 
`connectivity::checkDisposed(bool)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`FmXGridCell::onFocusGained(com::sun::star::awt::FocusEvent const&)':
././svx/source/fmcomp/gridcell.cxx:3388: undefined reference to 
`connectivity::checkDisposed(bool)'
/<>/workdir/CxxObject/svx/source/fmcomp/gridcell.o: In function 
`DbTextField::GetFormatText(com::sun::star::uno::Reference
 const&, com::sun::star::uno::Reference 
const&, Color**)':
././svx/source/fmcomp/gridcell.cxx:1157: undefined reference to 

Bug#877211: ipmiutil: frequent parallel FTBFS

[Adrian Bunk]

On Sat, Oct 28, 2017 at 02:28:11PM +0200, Jörg Frings-Fürst wrote:
> tags 877211 + unreproducible
> thanks
> 
> Hi,
> 
> here and on the buildsystems the FTBFS isn't reproducible.

The buildds are using lower parallelism right now, I can reproduce it with
  while dpkg-buildpackage -B -J100; do true; done

> CU
> Jörg

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#880032: wxpython3.0: Please provide a python3 package for wxpython3.0

[Cedric Boudinet]

Package: wxpython3.0
Severity: wishlist

Dear Maintainer,

Is it possible to provide a package for python3?

I managed to install it with pip (it was python4b2 in fact) but it takes a lot
of time and as a lot of dependencies.

Regards

Cedric



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

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

Bug#880031: gnupg2: FTBFS on hppa - some tests fail

[John David Anglin]

Source: gnupg2
Version: 2.2.1-5
Severity: normal

Dear Maintainer,

Some tests now fail building 2.2.1-5.  For example,

Executing: '/<>/build/tools/gpgconf' '--build-prefix' 
'/<>/build' '--list-components'
Child 15204 returned: ((command ("/<>/build/tools/gpgconf" 
--build-prefix "/<>/build" --list-components)) (status 0) (stdout 
gpg:OpenPGP:/<>/build/g10/gpg
gpg-agent:Private Keys:/<>/build/agent/gpg-agent
scdaemon:Smartcards:/<>/build/scd/scdaemon
gpgsm:S/MIME:/<>/build/sm/gpgsm
dirmngr:Network:/<>/build/dirmngr/dirmngr
pinentry:Passphrase Entry:/usr/bin/pinentry
) (stderr )) 
Executing: '/<>/build/g10/gpg' '--gpgconf-test' '--always-trust'
Child 15252 returned: ((command ("/<>/build/g10/gpg" 
--gpgconf-test --always-trust)) (status 0) (stdout ) (stderr )) 
Creating test environment... 
Creating configuration files 
Executing: '/<>/build/tools/gpgtar' '--extract' '--directory=.' 
'/tmp/gpgscm-20171028T140139-run-tests-Vd72Fg/environment-cache'
Child 15314 returned: ((command ("/<>/build/tools/gpgtar" 
--extract --directory=. 
"/tmp/gpgscm-20171028T140139-run-tests-Vd72Fg/environment-cache")) (status 0) 
(stdout ) (stderr )) 
Starting gpg-agent... 
Executing: '/<>/build/tools/gpgconf' '--build-prefix' 
'/<>/build' '--create-socketdir'
Child 15356 returned: ((command ("/<>/build/tools/gpgconf" 
--build-prefix "/<>/build" --create-socketdir)) (status 1) (stdout 
) (stderr gpgconf: socketdir is '/tmp/gpgscm-20171028T140206-run-tests-Vr5vzR'
gpgconf:no /run/user dir
gpgconf:using homedir as fallback
gpgconf: error creating socket directory
gpgconf: fatal error (exit status 1)
)) 
Warning: Creating socket directory failed: gpgconf: socketdir is 
'/tmp/gpgscm-20171028T140206-run-tests-Vr5vzR'
gpgconf:no /run/user dir
gpgconf:using homedir as fallback
gpgconf: error creating socket directory
gpgconf: fatal error (exit status 1)
 
Executing: '/<>/build/tools/gpg-connect-agent' '--verbose' 
'--agent-program=/<>/build/agent/gpg-agent|--debug-quick-random' 
'/bye'
Child 15387 returned: ((command 
("/<>/build/tools/gpg-connect-agent" --verbose 
"--agent-program=/<>/build/agent/gpg-agent|--debug-quick-random" 
/bye)) (status 1) (stdout ) (stderr gpg-connect-agent: no running gpg-agent - 
starting '/<>/build/agent/gpg-agent|--debug-quick-random'
gpg-connect-agent: waiting for the agent to come up ... (5s)
gpg-connect-agent: waiting for the agent to come up ... (4s)
gpg-connect-agent: waiting for the agent to come up ... (3s)
gpg-connect-agent: waiting for the agent to come up ... (2s)
gpg-connect-agent: waiting for the agent to come up ... (1s)
gpg-connect-agent: can't connect to the agent: IPC connect call failed
gpg-connect-agent: error sending standard options: No agent running
)) 
("/<>/build/tools/gpg-connect-agent" --verbose 
"--agent-program=/<>/build/agent/gpg-agent|--debug-quick-random" 
/bye) failed: gpg-connect-agent: no running gpg-agent - starting 
'/<>/build/agent/gpg-agent|--debug-quick-random'
gpg-connect-agent: waiting for the agent to come up ... (5s)
gpg-connect-agent: waiting for the agent to come up ... (4s)
gpg-connect-agent: waiting for the agent to come up ... (3s)
gpg-connect-agent: waiting for the agent to come up ... (2s)
gpg-connect-agent: waiting for the agent to come up ... (1s)
gpg-connect-agent: can't connect to the agent: IPC connect call failed
gpg-connect-agent: error sending standard options: No agent running

Stopping gpg-agent... 
Executing: '/<>/build/tools/gpgconf' '--build-prefix' 
'/<>/build' '--kill' 'all'
Child 15458 returned: ((command ("/<>/build/tools/gpgconf" 
--build-prefix "/<>/build" --kill all)) (status 0) (stdout ) 
(stderr )) 
Executing: '/<>/build/tools/gpgconf' '--build-prefix' 
'/<>/build' '--remove-socketdir'
Child 15513 returned: ((command ("/<>/build/tools/gpgconf" 
--build-prefix "/<>/build" --remove-socketdir)) (status 0) (stdout 
) (stderr gpgconf: ignoring request to remove non /run/user socket dir
)) 
FAIL: tests/openpgp/multisig.scm 

Full build log is here:
https://buildd.debian.org/status/fetch.php?pkg=gnupg2=hppa=2.2.1-5=1509201883=0

Regards,
Dave Anglin

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

Kernel: Linux 4.13.10+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), 
LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information

Bug#880030: ITP: python3-aiofiles -- Asynchronous file I/O support for Python asyncio

[David Steele]

Package: wnpp
Severity: wishlist
Owner: David Steele 

* Package name: python3-aiofiles
  Version : 0.3.2
  Upstream Author : Tin Tvrtković 
* URL : https://github.com/Tinche/aiofiles
* License : Apache 2.0
  Programming Lang: Python
  Description : Asynchronous file I/O support for Python asyncio

This module includes support for asynchronous file
 operations using the Python asyncio module.

Packaging is at https://github.com/davesteele/aiofiles/tree/debian/debian


-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE


signature.asc
Description: GooPG digital signature

Bug#880019: git-buildpackage: gbp pq export should accept --id-length (and so should the [pq] stanza in gbp.conf)

[Guido Günther]

Hi,
On Sat, Oct 28, 2017 at 03:07:14PM +0200, Daniel Kahn Gillmor wrote:
> Package: git-buildpackage
> Version: 0.9.0
> Severity: normal
> 
> I'm maintaing several patch queues in the gnupg2 source package,
> including (at least) one for stretch and one for unstable.
> 
> At some point, the default git commit ID length written in the
> generated patches moved from 9 hex digits to 7.
> 
> This results in a distracting large-in-bytes change when
> round-tripping through "gbp pq import && gbp pq export".  In
> particular, i'm talking about this kind of change in
> debian/patches/0012-whatever.patch
> 
>  diff --git a/tools/gpgconf-comp.c b/tools/gpgconf-comp.c
> -index a25b5136e..85eb80ab5 100644
> +index a25b513..85eb80a 100644
> 
> Where it shows up for every hunk.
> 
> I understand that gbp (and git itself) may choose for whatever reason
> to change the default styling.
> 
> but it would be nice for me if i could drop a couple lines into the
> [pq] section of debian/gbp.conf to stabilize the styling so that i can
> work with the patch queue without generating this kind of distracting
> noise.  I want reviewers of my debdiffs to be able to focus on the
> actual changes :)
> 
> gbp dch already has an id-length option.  Maybe gbp pq could support
> one as well?
> 
> I tried putting the following two lines in debian/gbp.conf:
> 
> [pq]
> id-length = 9

I think you want:

[pq]
abbrev = 9

Cheers,
 -- Guido

> 
> but it didn't do what i wanted :)
> 
> I'm filing this as normal instead of wishlist because the generated
> noise is actually a problem for me.  if you want, you can retitle this
> bug report "gbp pq export introduces noise in debian/patches by
> varying the commit id length in exported patches".  or if you want,
> you can reset the severity to wishlist.  my feelings won't be hurt
> either way :)
> 
> thanks for maintaining gbp!
> 
>--dkg
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing-debug
>   APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), 
> (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.13.0-1-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)
> 
> Versions of packages git-buildpackage depends on:
> ii  devscripts 2.17.10
> ii  git1:2.14.2-1
> ii  man-db 2.7.6.1-2
> ii  python33.6.3-1
> ii  python3-dateutil   2.6.1-1
> ii  python3-pkg-resources  36.2.7-2
> ii  python3-six1.11.0-1
> 
> Versions of packages git-buildpackage recommends:
> pn  cowbuilder | pbuilder | sbuild  
> ii  pristine-tar1.42
> ii  python3-requests2.18.1-1
> 
> Versions of packages git-buildpackage suggests:
> pn  python3-notify2  
> pn  sudo 
> ii  unzip6.0-21
> 
> -- no debconf information
> 

Bug#872864: Checkout upstream signatures as well when using pristine-tar

[Alexis Murzeau]

Hi,

I got signature file integration working with the orig tarball with the
attached patch.

This implementation is somewhat simple and does not check if
pristine-tar has the signature feature (and thus require pristine-tar 1.41)

I think the check for the presence of a signature file in the
pristine-tar branch might be better, especially for component tarballs
which I'm not sure it will work.

Tell me if you want it as a github PR.

Thanks :)

-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F
From b40ecb07f8734cbe29f28a2e26a44175dd7379d5 Mon Sep 17 00:00:00 2001
From: Alexis Murzeau 
Date: Sat, 28 Oct 2017 18:30:11 +0200
Subject: [PATCH] pristine-tar: handle orig tar signature (.asc)

This require pristine-tar version 1.41.

When commiting a orig tarball, check the existence of a .asc signature.
If present, add it to the pristine-tar commit.

When checkouting a orig tarball, check the presence of a asc signature
in the pristine-tar banch. If present, checkout it along with the tarball.
---
 gbp/pkg/pristinetar.py | 16 ++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/gbp/pkg/pristinetar.py b/gbp/pkg/pristinetar.py
index 1da72bf..25ced9c 100644
--- a/gbp/pkg/pristinetar.py
+++ b/gbp/pkg/pristinetar.py
@@ -86,7 +86,13 @@ class PristineTar(Command):
 @type archive: C{str}
 """
 self.run_error = 'Pristine-tar couldn\'t checkout "%s": {stderr_or_reason}' % os.path.basename(archive)
-self.__call__(['checkout', archive], quiet=quiet)
+signature_file = "%s.asc" % (archive)
+if self.repo.list_tree(self.branch, paths=[os.path.basename(signature_file)]):
+call_options = ['--signature-file', signature_file, 'checkout', archive]
+else:
+call_options = ['checkout', archive]
+
+self.__call__(call_options, quiet=quiet)
 
 def commit(self, archive, upstream, quiet=False):
 """
@@ -100,7 +106,13 @@ class PristineTar(Command):
 """
 self.run_error = ("Couldn't commit to '%s' with upstream '%s': {stderr_or_reason}" %
   (self.branch, upstream))
-self.__call__(['commit', archive, upstream], quiet=quiet)
+signature_file = "%s.asc" % (archive)
+if os.path.isfile(signature_file):
+call_options = ['--signature-file', signature_file, 'commit', archive, upstream]
+else:
+call_options = ['commit', archive, upstream]
+
+self.__call__(call_options, quiet=quiet)
 
 def verify(self, archive, quiet=False):
 """Verify an archive's I{archive} checksum using to the pristine tar branch"""
-- 
2.15.0.rc2



signature.asc
Description: OpenPGP digital signature

Bug#848198: fonts-noto-color-emoji

[Anthony Wong]

On 24 October 2017 at 10:47, Jeremy Bicha  wrote:
> On Sun, Aug 20, 2017 at 1:11 AM, Medical Wei  wrote:
>> I am recently (1-2 weeks ago) into some ITP and RFPs of some Python
>> libraries to build fonts from source, like ufolib, defcon, and henrich is
>> going to update fonttools. This can lead towards to packaging nototools to
>> build this package from source.
>
> This is a priority for me for Ubuntu 18.04 LTS. Please let me know if
> I can help in any way.
>
> It looks like there are several more packages that you need to build
> nototools, some don't even have ITPs yet (like pyclipper).
>
> Do you intend to maintain these packages yourself or with a team?
>
> Do you have git repos for your work so far?
>
> Have you been able to build nototools or the noto-color-emoji font locally 
> yet?
>
> I am usually in Debian IRC in #debian-gnome. Feel free to ping me.
>
> Thanks,
> Jeremy Bicha

Pre-built binary has been pushed to their github repo on Mar 11, 2017:


https://github.com/googlei18n/noto-emoji/blob/master/fonts/NotoColorEmoji.ttf

I think we can use the binary instead of building from source,
fonts-noto and fonts-noto-cjk do the same.

Thanks,
Anthony

Bug#878411: gnome-session-bin doesn't set environmental variable of GTK_IM_MODULE

[Takahide Nojima]

> > It's unclear from your bug report whether this was working before
> > for
> > you ("I can not anymore Japanes language anymore").
> > Are you saying that with older gnome-session-bin versions it
> > worked?
> > 
> 
>  No. 

...snip...
>  I guess , refer to main.c of gnome-session-bin, the best place of
> setting GTK_IM_MODULE env variable is in gnome-session-bin.
> 
>  Would you accept that patch as a temporary resolution?

Dear maintainer,

 I'm totally mistaken.(sorry!) 

 This patch isn't needed anymore.And also, this bug report I sent is
totaly wrong caused by my lack of knowledge about recent GNOME desktop.

 After my trial and error, I found a correct setting of gnome-control-
center, I became able to input Japanese without this patch. And also,
I found that in recent GNOME desktop, gtk applications can communicate 
to ibus without X_MODIFIERS/GTK_IM_MODULE env valiable anymore.

Correct setting and how to input Japanese using ibus:
 
 In gnome-control-center -> Region & Language -> 
  1st prior: Japanese (if you use Japanese layout keyboard)
  2nd prior: Japanese (Mozc)
  in  Input Source form. 
 
  After restarting gdm3 and doing login, press + to switch input source to japanese mozc and  press
"Hankaku/Zenkaku" key,  user can input Japanese 
using mozc-jp engine via ibus.

  I did set "Region & Language" to "Japanese" (notice: "Mozc" isn't 
specified), and I found this setting means simply using Japanese layout
keyboard without using ibus.  

 Then, I mark this bug as done.

Takahide Nojima

Bug#880029: ITP: node-postcss-colormin -- Minify colors in your CSS files with PostCSS

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-postcss-colormin
  Version : 2.2.2
  Upstream Author : Ben Briggs  (http://beneb.info)
* URL : https://github.com/ben-eb/postcss-colormin
* License : Expat
  Programming Lang: JavaScript
  Description : Minify colors in your CSS files with PostCSS

 PostCSS is a tool for transforming styles with JS plugins. These
plugins can
 lint your CSS, support variables and mixins, transpile future CSS syntax,
 inline images, and more.
 .
 Node.js is an event-based server-side JavaScript engine.

In dependency of gitlab 9.5 (dependency of cssnano)



signature.asc
Description: OpenPGP digital signature

Bug#879960: libqt5sql5-psql: [libqt5sql5-psql] basic support postgresql-10

[Diederik de Haas]

On Friday, October 27, 2017 11:34:08 PM CEST Damir R. Islamov wrote:
> Tags: patch
> 
>* QT-5.9.[1,2] (and future QT-5.10?) in the upstram do not support
> PostgreSQL 10.

Thanks for this patch! 
I ran into this problem with https://bugs.debian.org/cgi-bin/bugreport.cgi?
bug=876421 and thus far hadn't received a reply to it.
As PostgreSQL 10 is now the version in both Sid and Testing/Buster, this means 
PostgreSQL can't be used with qt, which is a shame.

Bug#879898: dbus: memory leak in dbus-daemon consumes over 5GB memory

[Simon McVittie]

On Sat, 28 Oct 2017 at 09:32:36 -0400, Nicholas D Steeves wrote:
> In that case does it
> correspond to this upstream bug?  
> https://bugs.freedesktop.org/show_bug.cgi?id=33606#c11

Probably, yes. You'll notice we don't know how to solve that bug without
causing data loss...

dbus-broker is claimed to do better by making use of Linux-specific APIs
and having different concepts of how to assign blame for messages,
fast writing, slow reading etc., but I haven't had time to review it,
and it's possible that it achieves this by (accidentally or deliberately)
not providing invariants/guarantees that dbus-daemon does.

> I'm not sure that it does, because I don't understand how 1.6GB
> becomes 6GB without a leak (see below)

I'm not sure either. Something like memleax might tell you. However,
that 1.6GB is only one of several types of memory allocation in
dbus-daemon (1GB of messages is a separate allocation), so this isn't
a definite leak.

> > The dbus 1.11.x development branch (from which a 1.12.0 stable version
> > will be released soon) does log this information to syslog or the
> > systemd Journal, but 1.10.x didn't.
> 
> Shouldn't this have existed since 1.4.10/1.5.2?
> https://bugs.freedesktop.org/show_bug.cgi?id=35358

Hmm, yes, the addition in 1.11.x is logging when we hit all the other
arbitrary limits.

> org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only 
> object

I don't expect this should cause any particular issues.

> org.kde.kuiserver[20319]: QDBusConnection: session D-Bus connection created 
> before QCoreApplication. Application may misbehave.

I don't know what form the misbehaviour would take, but I doubt the answer
is millions of messages.

> Could dbus-daemon --session send a signal to misbehaving peers...eg:
> "you're misbehaving...slow down send or speed up reads" and then
> finally, if necessary "you seem to be stuck, do an internal reinit but
> maintain connect"?  Do you think dbus-broker (
> https://dvdhrm.github.io/rethinking-the-dbus-message-bus/ ) would have
> avoided this bug?

The signal for "slow down sending" is to throttle reading, so that the
messages that are being sent get delayed until the current batch have been
passed through to a recipient. If a sender is sending messages that are
not necessary, then it should not send them ever, regardless of whether
there is memory pressure. If a sender is sending messages that *are*
necessary, then they're necessary, and it can't just not send them...

There is no signal for "speed up reading". It isn't clear to me that
one would be particularly useful: if an app is not reading fast enough,
it's a sign of either pathological performance issues (either a flood of
messages from a sender, or very slow message processing in a recipient),
or a design flaw (blocking the main loop). If there is something useful
for it to do in response to a signal that said "hurry up", it would be
better for it to do that all the time and not pay attention to the signal.
(It also isn't clear to me that sending an extra message is a good way
to deal with a peer that isn't processing its messages fast enough :-)

There is no generic concept of a re-initialization. Higher-level protocols
that are layered over D-Bus generally assume that every message is
delivered and do not cope with messages being discarded, so if there was
any concept of restarting the connection, it would have to be opt-in and
only used by applications whose higher-level D-Bus protocols had been
(re)designed to accommodate it. The only thing we can do with a general
connection is to disconnect it, which is documented to be interpreted as
"end of session, shut down now".

Designing new protocols that require action by library implementations
and/or opt-in by applications is not something that can happen rapidly -
sorry, I only have enough time available for D-Bus work to keep it going
in approximately the same way it does now.

> How does 1.6G of messages become 6GB of memory usage without a memory
> leak?  Do you mean 1.6G of active memory and ~4.4G of cache?

This is 1.6G of linked-list links (overhead of putting things in
lists), not messages. You also have 1G of actual messages queued to
go to kded alone. I could believe there being 3.4G of other stuff
(hash tables? copies of messages? memory fragmentation between/around
messages? etc.).

> > org.kde.StatusNotifierWatcher, org.kde.plasmanetworkmanagement,
> > org.kde.keyboard, org.kde.kded5, org.kde.kcookiejar5, org.kde.apperd
> > are really all the same connection (you can tell by how they all share
> > UniqueName = :1.7) and they are the worst problem here. Either kded5
> > has not been reading its dbus messages from its socket for a long time,
> > or something has sent it far too many messages, or both.
> > 
> > While I recognise the engineering tradeoffs that lead to bundling
> > several daemons into one process, this might be more robust (or at
> > least more debuggable) if it was a group of smaller 

Bug#880027: exiv2: CVE-2017-14861: stack-overflow vulnerability in Exiv2::Internal::stringFormat[abi:cxx11] (in image.cpp:975)

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/139

Hi,

the following vulnerability was published for exiv2.

CVE-2017-14861[0]:
| There is a stack consumption vulnerability in the
| Exiv2::Internal::stringFormat function of image.cpp in Exiv2 0.26. A
| Crafted input will lead to a remote denial of service attack.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14861
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14861
[1] https://github.com/Exiv2/exiv2/issues/139

Regards,
Salvatore

Bug#880026: systemd: CVE-2017-15908

[Salvatore Bonaccorso]

Source: systemd
Version: 232-1
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/systemd/systemd/pull/7184

Hi,

the following vulnerability was published for systemd.

CVE-2017-15908[0]:
| In systemd 223 through 235, a remote DNS server can respond with a
| custom crafted DNS NSEC resource record to trigger an infinite loop in
| the dns_packet_read_type_window() function of the 'systemd-resolved'
| service and cause a DoS of the affected service.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15908
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15908
[1] https://github.com/systemd/systemd/pull/7184
[2] 
https://github.com/systemd/systemd/commit/9f939335a07085aa9a9663efd1dca06ef6405d62

Please adjust the affected versions in the BTS as needed.

Since systemd-resolved is not enabled by default I think an update via
an upcoming stretch point release would be enough. Please let us know
if you disagre.

Regards,
Salvatore

Bug#880024: radare2: CVE-2017-15932

[Salvatore Bonaccorso]

Source: radare2
Version: 2.0.0+dfsg-1
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/radare/radare2/issues/8743

Hi,

the following vulnerability was published for radare2.

CVE-2017-15932[0]:
| In radare2 2.0.1, an integer exception (negative number leading to an
| invalid memory access) exists in store_versioninfo_gnu_verdef() in
| libr/bin/format/elf/elf.c via crafted ELF files when parsing the ELF
| version on 32bit systems.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15932
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15932
[1] https://github.com/radare/radare2/issues/8743
[2] 
https://github.com/radare/radare2/commit/44ded3ff35b8264f54b5a900cab32ec489d9e5b9

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#880025: radare2: CVE-2017-15931

[Salvatore Bonaccorso]

Source: radare2
Version: 2.0.0+dfsg-1
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/radare/radare2/issues/8731

Hi,

the following vulnerability was published for radare2.

CVE-2017-15931[0]:
| In radare2 2.0.1, an integer exception (negative number leading to an
| invalid memory access) exists in store_versioninfo_gnu_verneed() in
| libr/bin/format/elf/elf.c via crafted ELF files on 32bit systems.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15931
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15931
[1] https://github.com/radare/radare2/issues/8731
[2] 
https://github.com/radare/radare2/commit/c6d0076c924891ad9948a62d89d0bcdaf965f0cd

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#880023: polyml: FTBFS on hppa - error linking poly

[John David Anglin]

Source: polyml
Version: 5.7
Severity: normal

Dear Maintainer,

Build fails here:

Making STRUCT_CONVERSIONALS
Created functor STRUCT_CONVERSIONALS
Created structure StructConversionals
Created structure CInterface
/bin/bash ./libtool  --tag=CC   --mode=link gcc   -Wall -fno-strict-aliasing -g 
-O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security   
-Wl,--as-needed -o poly  polyexport.o  libpolymain/libpolymain.la 
libpolyml/libpolyml.la  -lpthread -lffi -lm -ldl -lstdc++ -lgcc_s -lgcc 
libtool: link: gcc -Wall -fno-strict-aliasing -g -O2 
-fdebug-prefix-map=/<>=. -Wformat -Werror=format-security 
-Wl,--as-needed -o .libs/poly polyexport.o  libpolymain/.libs/libpolymain.a 
libpolyml/.libs/libpolyml.so -lpthread -lffi -lm -ldl -lstdc++ -lgcc_s -lgcc
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.1 internal error, aborting at 
../../bfd/elf32-hppa.c:4054 in elf32_hppa_relocate_section

/usr/bin/ld: Please report this bug.

collect2: error: ld returned 1 exit status
Makefile:588: recipe for target 'poly' failed

Full build log is here:
https://buildd.debian.org/status/fetch.php?pkg=polyml=hppa=5.7-2=1507223380=0

The error was reported to binutils:
https://sourceware.org/bugzilla/show_bug.cgi?id=22300

See "bug 1: polyimport, the producer of polyexport.o is using the wrong os/abi 
for hppa-linux." in comment 4.

The binutils part of this bug should now be fixed by commit 
c0e331c794d6bd75d9be9bea6145513074c33f39.

Regards,
Dave Anglin

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

Kernel: Linux 4.13.10+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), 
LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#852710: closed by Georg Faerber <ge...@riseup.net> (Bug#852710: fixed in schleuder 3.2.1-1)

[Daniel Kahn Gillmor]

On Sat 2017-10-28 12:06:05 +, Debian Bug Tracking System wrote:
>* debian/NEWS: Add note about how to rely on the Debian keyserver defaults.
>* debian/patches:
>  - Add patch to rely on the Debian keyserver defaults in the schleuder
>config. (Closes: #852710)

Thanks for this fix!

fwiw, this isn't specific to Debian. GnuPG ships with a default
keyserver upstream now.  If you're depending on anything reasonably
recent from the 2.1.x branch (or anything from 2.2.x now that it's
stabilized) schleuder really should not ship with an explicit config
that the admin needs to override.  Let the underlying tool choose
sensible defaults, and allow the local administrator to override them
should they need to (if they need to, they'll know).

This even goes for older versions of GnuPG -- if they don't supply a
default, the local admin still ought to be the one to make the decision.
(or the user should upgrade to a modern version of GnuPG that is getting
significant amounts of upstream attention ;)

I think it's best for schleuder be agnostic about this choice.

 --dkg


signature.asc
Description: PGP signature

Bug#880020: stretch-pu: package lxc/1:2.0.7-2+deb9u1

[Antonio Terceiro]

Hi,

On Sat, Oct 28, 2017 at 11:14:04AM -0200, Antonio Terceiro wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Hi, this update brings two changes, both needed for ci.debian.net:
> 
> lxc (1:2.0.7-2+deb9u1) stretch; urgency=medium

Another alternative would be you allowing us to use the upstream 2.0
branch for stable updates, currently at 2.0.9.

LXC 2.0 is an LTS branch upstream, and will be supported until June 1st
2021. It would be really nice if we could use that instead of manually
backporting patches to 2.0.7. What would be the requirements for us
doing that for strecth?


signature.asc
Description: PGP signature

Bug#879999: graphicsmagick: CVE-2017-15930: Null pointer dereference while transferring JPEG scanlines

[Bob Friesenhahn]

On Sat, 28 Oct 2017, Salvatore Bonaccorso wrote:


While testing I was as well not able to reach the NULL pointer
dereference but made the same observation as Bob Friesenhahn, that
graphicsmagick spends a lot of time convertingthe image crating a huge
temporary file, in my case reaching no space left on /tmp and
aborting with


The null pointer dereference can be made to happen by applying a 
pixels resource limit.  Normally limits make things safer but in this 
case it causes an error which results in a null pointer.


The latest version of the code rejects the file supplied as being 
impossibly small given the pixel dimensions.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/

Bug#880005: closed by Gianfranco Costamagna <locutusofb...@debian.org> (unreproducible)

[Ralf Jung]

I think I found the problem:  The virtualbox systemd unit (well, the
init script, really) was disabled.  I am pretty sure that I did not
disable it, so I am not sure how this happened.

Maybe it would be better for virtualbox to use modules-load.d instead of
an init script when systemd is available?  In fact, virtualbox is
currently the *only* legacy init script on my system.

; Ralf

Bug#840710: parted: Fix recognition of FAT file system after resizing

[Matthijs Kooijman]

Package: parted
Version: 3.2-17
Followup-For: Bug #840710

Hi,

I'd also be grateful if this patch could be backported. In the current
situation, resizing of bootable partitions simply is not possible
without breaking things.

I also tried downgrading to (lib)parted 3.1, but that caused segfaults
in fatresize, so that does not seem a feasible workaround either.

Gr.

Matthijs

Bug#880005: closed by Gianfranco Costamagna <locutusofb...@debian.org> (unreproducible)

[Ralf Jung]

Hi,

>> In fact, "modprobe vboxdrv" works, as I indicated in my original email.
>> After doing so, VirtualBox works fine.  But something is wrong if I have
>> to load the module manually.
> 
> 
> well, I install sid/buster machines in VM weekly, and *never* had this issue,
> except for dkms failures.
> Can you please try to see if the module is not blacklisted, or some udev rule
> fails?

It does not seem to be blacklisted:

> $ cat /etc/modprobe.d/*
> # The microcode module attempts to apply a microcode update when
> # it autoloads.  This is not always safe, so we block it by default.
> blacklist microcode
> # modprobe information used for DKMS modules
> #
> # This is a stub file, should be edited when needed,
> # used by default by DKMS.
> # The microcode module attempts to apply a microcode update when
> # it autoloads.  This is not always safe, so we block it by default.
> blacklist microcode

Not sure about udev, where would I check that? "vbox" does not appear
anywhere in syslog or dmesg.

> Can you please try with a clean system?

I installed this laptop just a few weeks ago, it is pretty clean.
VirtualBox has always had that problem on this machine.  On my previous
laptop, things still worked fine.

How and when and by whom *should* vboxdrv get liaded?

Kind regards,
Ralf

Bug#880022: RM: kraken [mips mipsel powerpc] -- RoQA; missing B-D: jellyfish1

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

kraken is no longer built for architectures without jellyfish1


Andreas

Bug#879898: dbus: memory leak in dbus-daemon consumes over 5GB memory

[Nicholas D Steeves]

On Sat, Oct 28, 2017 at 12:22:22AM +0100, Simon McVittie wrote:
> On Fri, 27 Oct 2017 at 13:06:32 -0400, Nicholas D Steeves wrote:
> > Would using memleax help?  I'm 90% done packaging it, in case it looks
> > useful.  Packaged because vagrant can't attach to an existing process.
> 
> From the other information you've given I can tell you with reasonable
> certainty that (at least a large part of) the "leaked" memory is not
> leaked, but is really still in use - the dbus-daemon is genuinely
> trying to process millions of messages to kded5. I can't say why,
> though.

Oh!  My apologies for misunderstanding.  In that case does it
correspond to this upstream bug?  
https://bugs.freedesktop.org/show_bug.cgi?id=33606#c11

I'm not sure that it does, because I don't understand how 1.6GB
becomes 6GB without a leak (see below)

> > Is it possible for dbus-daemon to signal to the calling application
> > that a queue is full?
> 
> In principle it might have been if it was defined 10 years ago, but
> there is no protocol defined for communicating that fact, and it isn't
> clear what an application would do about it anyway. Popping up messages
> to annoy the user is generally frowned upon if there is nothing that
> most users can do about it...

Better than a swap storm and eventual mysterious crash, imho.  Also if
a user could more easily identify which component is precipitating the
issue than he/she can file a more useful bug report against the
correct package.  As it stands, it's extra triaging work for the
Debian dbus maintainer[s].

> > Plasma's NM frontend wouldn't reconnect to the
> > network, and I before I realised it I had killed plasmashell ; sleep
> > 3; kstart plasmashell.  The dbus-daemon and kded5 daemon seem to be
> > unaffected, as expected, but maybe this causes problems with dbus?
> 
> Terminating random processes shouldn't be a problem in general (other
> than to those processes and anything that was relying on them), but
> if some component has a bug and has responded to the unexpected
> disappearance by going into a busy-loop, it's possible that the
> busy-loop could result in it sending a flood of messages.
> 
> Or the inability to reconnect to the network might itself have been a
> symptom of a flood of messages, rather than part of the cause.
> 
> However, I will say this: if you have a serious problem (like a key
> desktop component getting stuck), and you respond to it by killing
> individual components rather than by terminating the whole session
> (e.g. logging out and back in), then you are certainly in uncharted
> territory. This is the sort of thing that in principle ought to work,
> but it is never going to be systematically tested, so it is not at all
> surprising if it has or exposes bugs.
 
I've had to resort to killing individual components, because
KDE5/Plasma Desktop session save/restore is broken.  If I logout or
reboot I lose my session (more specifically a seemingly random
collection of applications sometimes opening old files from old
sessions and sometimes opening no file appear on the first virtual
desktop).  Ksmserver is used for session management and (most? the
successful ones?) applications are restarted using kwrapper5...which
"tries to make the program look like it was actually really started
directly and not via kdeinit"
(https://github.com/KDE/kinit/blob/master/docs/wrapper.txt)

> The dbus 1.11.x development branch (from which a 1.12.0 stable version
> will be released soon) does log this information to syslog or the
> systemd Journal, but 1.10.x didn't.

Shouldn't this have existed since 1.4.10/1.5.2?
https://bugs.freedesktop.org/show_bug.cgi?id=35358

That said, grep -i dbus for files in /var/log (as root)

org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
# repeats 5 to 15 times each time it occurs
org.kde.kuiserver[20319]: QDBusConnection: session D-Bus connection created 
before QCoreApplication. Application may misbehave.
# repeats twice
# then more org.kde.powerdevil.backlighthelper repeats
org.kde.kcontrol.kcmsddm: QDBusArgument: read from a write-only object
# repeats six times

That seems very minor compared to millions of messages, but could it
be part of the problem?  I've seen "QDBusConnection: session D-Bus
connection created before QCoreApplication. Application may
misbehave." many times over the years, but never memory usage like this.

> The system bus (which has finite limits) responds to excessive messages in
> an incoming queue by slowing down reading from that sender, and responds
> to excessive messages in an outgoing queue by dropping messages on the
> floor. It might be a good idea for the session bus to have a rather smaller
> limit on its incoming queues than the 1 GB limit that it has now, perhaps
> the 127 MiB that the system bus uses (which tbh could probably also be
> reduced) - then floods of messages would get slowed down, but eventually
> be processed. Individual messages are allowed to exceed that 

Bug#834714: [xml/sgml-pkgs] Bug#834714: libxslt1-dev: arch-dependent file in "Multi-Arch: same" package

[Manuel A. Fernandez Montecelo]

2017-10-28 15:12 GMT+02:00 Mattia Rizzolo :
> On Sat, Oct 28, 2017 at 12:32:49PM +, Hugh McMaster wrote:
>> On Saturday, 28 October 2017 10:47 PM, Mattia Rizzolo wrote:
>> > I can upload it to experimental.
>> > Given the amount of rdeps I'd prefer if somebody could perform
>> > comparative rebuilds (i.e. first build all rdpes using the current
>> > unstable package, then rebuild using the new exp package and compar what
>> > failed).
>>
>> A quick search shows around 80 reverse dependencies on libxslt1-dev.
>> I'll take this on.
>
> 89, list attached.
>
> I'm about to upload it, then.

Good, thanks Hugh and Mattia :)

I will be able to help with this from the 1st of November onwards if needed.

If it helps, ratt might be handy for this, if you don't know it:

  https://github.com/Debian/ratt

I seem to remember a debian-related served that allowed to do this
just providing the new package as well, but don't know the details.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#880005: closed by Gianfranco Costamagna <locutusofb...@debian.org> (unreproducible)

[Gianfranco Costamagna]

Hello,
>In fact, "modprobe vboxdrv" works, as I indicated in my original email.
>After doing so, VirtualBox works fine.  But something is wrong if I have
>to load the module manually.


well, I install sid/buster machines in VM weekly, and *never* had this issue,
except for dkms failures.
Can you please try to see if the module is not blacklisted, or some udev rule
fails?
Can you please try with a clean system?

I'm pretty sure there is some misconfiguration somewhere...

G.

Bug#880020: stretch-pu: package lxc/1:2.0.7-2+deb9u1

[Antonio Terceiro]

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

Hi, this update brings two changes, both needed for ci.debian.net:

lxc (1:2.0.7-2+deb9u1) stretch; urgency=medium

  * 0003-lxc-debian-don-t-hardcode-valid-releases.patch: don't
hardcode list of valid Debian release. Allows creating stable, buster,
testing, and unstable containers.
  * 0004-lxc-debian-don-t-write-C.-locales-to-etc-locale.gen.patch: don't
insert C.* locales into /etc/locale.gen (Closes: #879595)

 -- Antonio Terceiro   Fri, 27 Oct 2017 15:13:31 -0200

The first will allow to create containers with our "symlink" release
names, i.e. stable, testing, etc, and also removes the need to make a
new change after buster is released to add support for creting bullseye
containers.

The second fixes an issue where the C.UTF-8 locale, used by debci, in
injected into /etc/locale.gen in containers, causing warnings that can
cause bogus test failures under autopkgtest.

The diff is attached.

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index d7d10c1..512a09d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+lxc (1:2.0.7-2+deb9u1) stretch; urgency=medium
+
+  * 0003-lxc-debian-don-t-hardcode-valid-releases.patch: don't
+hardcode list of valid Debian release. Allows creating stable, buster,
+testing, and unstable containers.
+  * 0004-lxc-debian-don-t-write-C.-locales-to-etc-locale.gen.patch: don't
+insert C.* locales into /etc/locale.gen (Closes: #879595)
+
+ -- Antonio Terceiro   Fri, 27 Oct 2017 15:13:31 -0200
+
 lxc (1:2.0.7-2) unstable; urgency=high
 
   * use bash-completion's pkg-config support and don't move files around
diff --git a/debian/patches/0003-lxc-debian-don-t-hardcode-valid-releases.patch b/debian/patches/0003-lxc-debian-don-t-hardcode-valid-releases.patch
new file mode 100644
index 000..b57c3be
--- /dev/null
+++ b/debian/patches/0003-lxc-debian-don-t-hardcode-valid-releases.patch
@@ -0,0 +1,51 @@
+From: Antonio Terceiro 
+Date: Thu, 26 Oct 2017 20:42:49 -0200
+Subject: lxc-debian: don't hardcode valid releases
+
+This avoids the dance of updating the list of valid releases every time
+Debian makes a new release.
+
+It also fixes the following bug: even though lxc-debian will default to
+creating containers of the latest stable by querying the archive, it
+won't allow you to explicitly request `stable` because the current list
+of valid releases don't include it.
+
+Last, but not least, avoid hitting the mirror in the case the desired
+release is one of the ones we know will always be there, i.e. stable,
+testing, sid, and unstable.
+
+Signed-off-by: Antonio Terceiro 
+
+
+
+This is a combination of upstream commits
+61fa13293d735d922ba6e5ceb66f6d8718f1a829 and
+dba285d5dfa7e9f3452dc180e64158d9bedfb410
+---
+ templates/lxc-debian.in | 13 +++--
+ 1 file changed, 7 insertions(+), 6 deletions(-)
+
+diff --git a/templates/lxc-debian.in b/templates/lxc-debian.in
+index 54ada05..f6dbd4f 100644
+--- a/templates/lxc-debian.in
 b/templates/lxc-debian.in
+@@ -623,12 +623,13 @@ if [ "$(id -u)" != "0" ]; then
+ exit 1
+ fi
+ 
+-current_release=$(wget "${MIRROR}/dists/stable/Release" -O - 2> /dev/null | head |awk '/^Codename: (.*)$/ { print $2; }')
+-release=${release:-${current_release}}
+-valid_releases=('wheezy' 'jessie' 'stretch' 'sid')
+-if [[ ! "${valid_releases[*]}" =~ (^|[^[:alpha:]])$release([^[:alpha:]]|$) ]]; then
+-echo "Invalid release ${release}, valid ones are: ${valid_releases[*]}"
+-exit 1
++release=${release:-stable}
++permanent_releases=('stable' 'testing' 'sid' 'unstable')
++if [[ ! "${permanent_releases[*]}" =~ (^|[^[:alpha:]])$release([^[:alpha:]]|$) ]]; then
++if ! wget "${MIRROR}/dists/${release}/Release" -O /dev/null 2> /dev/null; then
++	echo "Invalid release ${release} (not found in mirror)"
++	exit 1
++fi
+ fi
+ 
+ # detect rootfs
diff --git a/debian/patches/0004-lxc-debian-don-t-write-C.-locales-to-etc-locale.gen.patch b/debian/patches/0004-lxc-debian-don-t-write-C.-locales-to-etc-locale.gen.patch
new file mode 100644
index 000..dfcb4d3
--- /dev/null
+++ b/debian/patches/0004-lxc-debian-don-t-write-C.-locales-to-etc-locale.gen.patch
@@ -0,0 +1,24 @@
+From: Antonio Terceiro 
+Date: Fri, 27 Oct 2017 17:13:54 -0200

Bug#880005: closed by Gianfranco Costamagna <locutusofb...@debian.org> (unreproducible)

[Ralf Jung]

Hi,

> This is probably because dkms failed in building.

Nope:

$ sudo dkms status
virtualbox, 5.1.30, 4.13.0-1-amd64, x86_64: installed

In fact, "modprobe vboxdrv" works, as I indicated in my original email.
After doing so, VirtualBox works fine.  But something is wrong if I have
to load the module manually.

Could you please reopen?

Kind regards,
Ralf

Bug#834714: [xml/sgml-pkgs] Bug#834714: libxslt1-dev: arch-dependent file in "Multi-Arch: same" package

[Mattia Rizzolo]

On Sat, Oct 28, 2017 at 12:32:49PM +, Hugh McMaster wrote:
> On Saturday, 28 October 2017 10:47 PM, Mattia Rizzolo wrote:
> > I can upload it to experimental.
> > Given the amount of rdeps I'd prefer if somebody could perform
> > comparative rebuilds (i.e. first build all rdpes using the current
> > unstable package, then rebuild using the new exp package and compar what
> > failed).
> 
> A quick search shows around 80 reverse dependencies on libxslt1-dev.
> I'll take this on.

89, list attached.

I'm about to upload it, then.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
abiword
akonadi
asterisk
chromium-browser
citus
cockpit
compiz
dia
epiphany-browser
eurephia
fwbuilder
gambas3
gnome-doc-utils
gnote
gnucash
gnustep-base
greenbone-security-assistant
gretl
gss-ntlmssp
hhvm
icecast2
idzebra
inkscape
kbibtex
kde4libs
kdepimlibs
kdoctools
kf5-kdepimlibs
kio
kodi
kopete
krecipes
kvkbd
lasso
libembperl-perl
libgda5
libreoffice
libxml-libxslt-perl
liferea
lordsawar
lxml
mapserver
merkaartor
mono
mono-reference-assemblies
morla
nginx
openjfx
opennebula
openscap
osinfo-db-tools
pacemaker
parser
pgadmin3
pglogical
php7.0
php7.1
planner
postgresql-10
postgresql-9.6
pyqt5
qt4-x11
qtwebengine-opensource-src
qtwebkit-examples-opensource-src
qtwebkit-opensource-src
qviaggiatreno
raptor2
repmgr
ruby-libxml
shiboken
shotdetect
signon-ui
swfmill
tclxml
ui-gxmlcpp
umbrello
uwsgi
virtualbox
webkit2gtk
webkitgtk
wine
wine-development
xmlcopyeditor
xmlroff
xmlsec1
xmlstarlet
yaz
yelp
yelp-xsl


signature.asc
Description: PGP signature

Bug#880019: git-buildpackage: gbp pq export should accept --id-length (and so should the [pq] stanza in gbp.conf)

[Daniel Kahn Gillmor]

Package: git-buildpackage
Version: 0.9.0
Severity: normal

I'm maintaing several patch queues in the gnupg2 source package,
including (at least) one for stretch and one for unstable.

At some point, the default git commit ID length written in the
generated patches moved from 9 hex digits to 7.

This results in a distracting large-in-bytes change when
round-tripping through "gbp pq import && gbp pq export".  In
particular, i'm talking about this kind of change in
debian/patches/0012-whatever.patch

 diff --git a/tools/gpgconf-comp.c b/tools/gpgconf-comp.c
-index a25b5136e..85eb80ab5 100644
+index a25b513..85eb80a 100644

Where it shows up for every hunk.

I understand that gbp (and git itself) may choose for whatever reason
to change the default styling.

but it would be nice for me if i could drop a couple lines into the
[pq] section of debian/gbp.conf to stabilize the styling so that i can
work with the patch queue without generating this kind of distracting
noise.  I want reviewers of my debdiffs to be able to focus on the
actual changes :)

gbp dch already has an id-length option.  Maybe gbp pq could support
one as well?

I tried putting the following two lines in debian/gbp.conf:

[pq]
id-length = 9

but it didn't do what i wanted :)

I'm filing this as normal instead of wishlist because the generated
noise is actually a problem for me.  if you want, you can retitle this
bug report "gbp pq export introduces noise in debian/patches by
varying the commit id length in exported patches".  or if you want,
you can reset the severity to wishlist.  my feelings won't be hurt
either way :)

thanks for maintaining gbp!

   --dkg

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

Kernel: Linux 4.13.0-1-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)

Versions of packages git-buildpackage depends on:
ii  devscripts 2.17.10
ii  git1:2.14.2-1
ii  man-db 2.7.6.1-2
ii  python33.6.3-1
ii  python3-dateutil   2.6.1-1
ii  python3-pkg-resources  36.2.7-2
ii  python3-six1.11.0-1

Versions of packages git-buildpackage recommends:
pn  cowbuilder | pbuilder | sbuild  
ii  pristine-tar1.42
ii  python3-requests2.18.1-1

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
pn  sudo 
ii  unzip6.0-21

-- no debconf information

Bug#880018: scummvm: crash with all games with MT-32 emulator on

[Francesco]

Package: scummvm
Version: 1.9.0+dfsg-1+b1
Severity: normal
Tags: patch

Dear Maintainer,

scummvm's crashing when the mt-32 emulation is switched on.



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

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

Versions of packages scummvm depends on:
ii  libasound2  1.1.3-5
ii  libc6   2.24-11+deb9u1
ii  libc6-udeb [libc6]  2.19-18+deb8u6
ii  libfaad22.8.0~cvs20161113-1
ii  libflac81.3.2-1
ii  libfluidsynth1  1.1.6-4
ii  libfreetype62.6.3-3.2
ii  libgcc1 1:6.3.0-18
ii  libjpeg62-turbo 1:1.5.1-2
ii  libmad0 0.15.1b-8
ii  libmpeg2-4  0.5.1-7+b2
ii  libogg0 1.3.2-1
ii  libpng16-16 1.6.28-1
ii  libsdl2-2.0-0   2.0.5+dfsg1-2
ii  libsndio6.1 1.1.0-3
ii  libstdc++6  6.3.0-18
ii  libtheora0  1.1.1+dfsg.1-14+b1
ii  libvorbis0a 1.3.5-4
ii  libvorbisfile3  1.3.5-4
ii  scummvm-data1.9.0+dfsg-1
ii  zlib1g  1:1.2.8.dfsg-5

scummvm recommends no packages.

Versions of packages scummvm suggests:
pn  beneath-a-steel-sky 
pn  drascula
pn  flight-of-the-amazon-queen  
ii  fluidsynth  1.1.6-4
pn  lure-of-the-temptress   

-- no debconf information

Bug#862114: Bug#862115: RFS: xe/0.8-1 (ITP, #862114) & lr/0.4-1 (ITP, #862115)

[Paul Wise]

On Sat, Oct 28, 2017 at 5:38 PM, Nicolas Braud-Santoni wrote:

> As an aside, I find it very weird to close a RFS due to
> the inactivity of would-be sponsors: from the packager's
> side, it feels like a double punishment (getting ignored,
> then getting your RFS closed because you got ignored)...

Even if you haven't got a sponsor yet, RFS submitters should still be
maintaining the packages as they would if they were in the archive.
That means updating to new upstreams, fixing any review comments,
checking with new versions of lintian, running static analysis tools
and fixing issues etc. Those updates should prevent you from ever
hitting the inactivity timeout on mentors. If you really have nothing
to do, you could still bump the changelog and RFS every now and then,
while also spending some more time looking for sponsors.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#876725: -deriving FTBFS with OCaml 4.05.0

[Gianfranco Costamagna]

control: tags -1 patch pending

Patch uploaded.

G.
diff -Nru ppx-deriving-4.1/debian/changelog ppx-deriving-4.1/debian/changelog
--- ppx-deriving-4.1/debian/changelog   2017-07-21 17:37:11.0 +0200
+++ ppx-deriving-4.1/debian/changelog   2017-10-28 13:37:32.0 +0200
@@ -1,3 +1,11 @@
+ppx-deriving (4.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * debian/patches/b6b02c2ba051bde67c2b454724ff0bf36bc11060.patch:
+- upstream fix for ocaml build failure (Closes: #876725)
+
+ -- Gianfranco Costamagna   Sat, 28 Oct 2017 
13:37:32 +0200
+
 ppx-deriving (4.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru 
ppx-deriving-4.1/debian/patches/b6b02c2ba051bde67c2b454724ff0bf36bc11060.patch 
ppx-deriving-4.1/debian/patches/b6b02c2ba051bde67c2b454724ff0bf36bc11060.patch
--- 
ppx-deriving-4.1/debian/patches/b6b02c2ba051bde67c2b454724ff0bf36bc11060.patch  
1970-01-01 01:00:00.0 +0100
+++ 
ppx-deriving-4.1/debian/patches/b6b02c2ba051bde67c2b454724ff0bf36bc11060.patch  
2017-10-28 13:37:32.0 +0200
@@ -0,0 +1,43 @@
+From b6b02c2ba051bde67c2b454724ff0bf36bc11060 Mon Sep 17 00:00:00 2001
+From: Jeremie Dimino 
+Date: Wed, 7 Jun 2017 13:54:44 +0100
+Subject: [PATCH] Fix build with 4.05
+
+---
+ src/ppx_deriving.cppo.ml | 16 
+ 1 file changed, 16 insertions(+)
+
+Index: ppx-deriving/src/ppx_deriving.cppo.ml
+===
+--- ppx-deriving.orig/src/ppx_deriving.cppo.ml
 ppx-deriving/src/ppx_deriving.cppo.ml
+@@ -12,6 +12,21 @@
+ open Ast_helper
+ open Ast_convenience
+ 
++#if OCAML_VERSION >= (4, 05, 0)
++module Typ = struct
++  include Typ
++
++  let poly ?(loc= !Ast_helper.default_loc) ?attrs vars ty =
++let vars = List.map (fun txt -> { Asttypes.loc; txt }) vars in
++Typ.poly ~loc ?attrs vars ty
++end
++
++let rm_poly_locs =
++  List.map (fun x -> x.Asttypes.txt)
++#else
++let rm_poly_locs x = x
++#endif
++
+ type deriver = {
+   name : string ;
+   core_type : (core_type -> expression) option;
+@@ -310,6 +325,7 @@
+   List.map free_in xs |> List.concat
+ | { ptyp_desc = Ptyp_alias (x, name) } -> [name] @ free_in x
+ | { ptyp_desc = Ptyp_poly (bound, x) } ->
++  let bound = rm_poly_locs bound in
+   List.filter (fun y -> not (List.mem y bound)) (free_in x)
+ | { ptyp_desc = Ptyp_variant (rows, _, _) } ->
+   List.map (
diff -Nru ppx-deriving-4.1/debian/patches/series 
ppx-deriving-4.1/debian/patches/series
--- ppx-deriving-4.1/debian/patches/series  2017-07-21 17:35:39.0 
+0200
+++ ppx-deriving-4.1/debian/patches/series  2017-10-28 13:37:32.0 
+0200
@@ -1,2 +1,3 @@
 0001-Fix-install-target.patch
 0002-Fix-typo-in-ppx_deriving_make.mllib.patch
+b6b02c2ba051bde67c2b454724ff0bf36bc11060.patch


signature.asc
Description: OpenPGP digital signature

Bug#878952: [pkg-gnupg-maint] Bug#878952: scdaemon: avoid ptrace on scdaemon?

[Daniel Kahn Gillmor]

Control: found 878952 2.1.18-8~deb9u1

On Wed 2017-10-25 16:46:51 +0900, NIIBE Yutaka wrote:
> Daniel Kahn Gillmor  wrote:
>> Package: scdaemon
>> Version: 2.2.1-2
>> Severity: normal
> [...]
>> Should we add a similar "prctl(PR_SET_DUMPABLE, 0)" to scdaemon as
>> well?
>
> I think we should.  Or else, someone might confuse as if the specific
> attack condition is somehow different for scdaemon.

It looks to me like this hardening change now works:



  ### with scdaemon 2.2.1-4 ###

0 dkg@pty1:~$ strace -p $(pidof scdaemon)
strace: Process 3997 attached
pselect6(4, [3], NULL, NULL, NULL, {[], 8} ) = ?
+++ exited with 2 +++
0 dkg@pty1:~$

  ### upgrade scdaemon and friends to 2.2.1-5 ###

0 dkg@pty1:~$ strace -p $(pidof scdaemon)
strace: attach: ptrace(PTRACE_SEIZE, 17081): Operation not permitted
1 dkg@pty1:~$



I don't think this is security-critical enough to try to push it as a
security update -- it's hardening, and as werner likes to point out,
there are almost certainly ways around it for a motivated attacker with
sufficient control over the victim's user account.  But i do think this
might be worth trying to put into the next stable point release, along
with a few other changes.

Any objection to it going into stretch?

  --dkg


signature.asc
Description: PGP signature

Bug#880017: glusterfs: CVE-2017-15096: Null pointer dereference

[Salvatore Bonaccorso]

Source: glusterfs
Version: 3.12.1-1
Severity: important
Tags: patch security upstream
Forwarded: https://bugzilla.redhat.com/show_bug.cgi?id=1502928

Hi,

the following vulnerability was published for glusterfs.

CVE-2017-15096[0]:
| A flaw was found in GlusterFS in versions prior to 3.10. A null
| pointer dereference in send_brick_req function in
| glusterfsd/src/gf_attach.c may be used to cause denial of service.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15096
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15096
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1502928
[2] 
http://git.gluster.org/cgit/glusterfs.git/commit/?id=1f48d17fee0cac95648ec34d13f038b27ef5c6ac

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#834714: [xml/sgml-pkgs] Bug#834714: libxslt1-dev: arch-dependent file in "Multi-Arch: same" package

[Hugh McMaster]

On Sat, Oct 28, 2017 at 10:33:38AM +0200, Manuel A. Fernandez Montecelo wrote:
> So, in the tests that you mention, did you try to compile packages that
> depend on libxslt, with this change enabled?

I only had time to build Wine and to compile the tutorial files in the libxslt
source package. Some headers, such as xsltutils.h, #include 
,
so if the compiler was unable to find xsltconfig.h, then we'd know the 
patch was immediately incorrect.

Debian searches /usr/include and /usr/include/, so moving the header
into the triplet include path shouldn't break anything (in theory anyway).

On Saturday, 28 October 2017 10:47 PM, Mattia Rizzolo wrote:
> I can upload it to experimental.
> Given the amount of rdeps I'd prefer if somebody could perform
> comparative rebuilds (i.e. first build all rdpes using the current
> unstable package, then rebuild using the new exp package and compar what
> failed).

A quick search shows around 80 reverse dependencies on libxslt1-dev.
I'll take this on.

--
Hugh McMaster

Bug#879895: Really broken

[Gianfranco Costamagna]

control: fixed -1 5.2.0-dfsg-2
control: close -1
On Fri, 27 Oct 2017 11:14:16 -0400 lsore...@csclub.uwaterloo.ca (Lennart 
Sorensen) wrote:
> If you force vboxvideo to build by editing the makefile, you get a
> file that crashes when you try to use it.  Going back to 5.1.x works
> fine however.
> 
> There error given is:
> 
> kernel: [   17.290464] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad 
> 8f5597836400
> 
> So somehow the 5.2.0 version is just plain broken it seems.
> 

I disabled that line, not sure but works for me (at least dmesg is not 
reporting errors

G.



signature.asc
Description: OpenPGP digital signature

Bug#877211: ipmiutil: frequent parallel FTBFS

[Jörg Frings-Fürst]

tags 877211 + unreproducible
thanks

Hi,

here and on the buildsystems the FTBFS isn't reproducible.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  jff

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#880014: Call for (self-)nominations for a Technical Committee seat

[Didier 'OdyX' Raboud]

Dear Debian Contributors,

Our Constitution imposes an expiry on Technical Committee terms, and it's that 
time of the year again: Keith Packard 's term will expire on December 
31st 2017. The Technical Committee would like to thank Keith for serving since 
November 2013, in addition to all the other work he does for Debian.

To fill this seat, we are soliciting nominations, including self-nominations. 
To nominate yourself or someone else, please send an e-mail to
debian-ctte-priv...@debian.org with the subject "TC Nomination of loginname", 
where loginname is the nominee's Debian account login¹. Please let us know in 
the body of the e-mail why the nominee would be a good fit for the TC, 
specifically instances where the nominee was able to help resolve 
disagreements, both technical and non-technical. We would like to start our 
selection process on or about the first of December.

Being a member of the TC does require a time commitment. Members should be 
able to follow e-mail discussions on an ongoing basis and respond within a 
couple of days so that discussions progress. Members should ideally be able to 
spend 10 hours a month for relatively busy months, but typical time 
requirements will be less.

We are in the process of documenting how the TC implements the nomination 
process as outlined in §6.2, including clarifying what is made public (such as 
nominations) and when. Any nominee is of course free to drop off the process 
at any point in time.

Regards,
OdyX, for the TC

¹ See http://db.debian.org/ if you need to look the login up

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

Bug#880016: libextractor: CVE-2017-15922

[Salvatore Bonaccorso]

Source: libextractor
Version: 1:1.6-1
Severity: important
Tags: patch security upstream
Forwarded: 
http://lists.gnu.org/archive/html/bug-libextractor/2017-10/msg8.html

Hi,

the following vulnerability was published for libextractor.

CVE-2017-15922[0]:
| In GNU Libextractor 1.4, there is an out-of-bounds read in the
| EXTRACTOR_dvi_extract_method function in plugins/dvi_extractor.c.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15922
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15922
[1] http://lists.gnu.org/archive/html/bug-libextractor/2017-10/msg8.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#865959: mosquitto: CVE-2017-9868: mosquitto.db can be read by all

[Salvatore Bonaccorso]

Hi

On Mon, Jun 26, 2017 at 07:35:05AM +0200, Salvatore Bonaccorso wrote:
> Source: mosquitto
> Version: 1.3.4-2
> Severity: important
> Tags: security upstream
> Forwarded: https://github.com/eclipse/mosquitto/issues/468
> 
> Hi,
> 
> the following vulnerability was published for mosquitto.
> 
> CVE-2017-9868[0]:
> | In Mosquitto through 1.4.12, mosquitto.db (aka the persistence file) is
> | world readable, which allows local users to obtain sensitive MQTT topic
> | information.

Any news for the fix to unstable?

Regards,
Salvatore

Bug#880015: exiv2: CVE-2017-14866

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/Exiv2/exiv2/issues/140

Hi,

the following vulnerability was published for exiv2.

CVE-2017-14866[0]:
| There is a heap-based buffer overflow in the Exiv2::s2Data function of
| types.cpp in Exiv2 0.26. A Crafted input will lead to a denial of
| service attack.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14866
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14866
[1] https://github.com/Exiv2/exiv2/issues/140

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#880014: 2018 - New TC member

[Didier 'OdyX' Raboud]

Package: tech-ctte
User: tech-c...@packages.debian.org

According to our Constitution's §6.2, Keith's term will expire at the end of
this year, freeing one seat on the TC from January 1st 2018 on.

This bug will track that process.

Bug#879825: game-data-packager: Fails to build tyrian-data

[Voker57]

On Sat, Oct 28, 2017 at 01:54:20PM +0200, Alexandre Detiste wrote:
> 2017-10-28 13:45 GMT+02:00 Voker57 :
> > Command finishes successfully
> 
> So where's the bug ?

It still fails with fakeroot-ng set as alternative for fakeroot.

Bug#880013: sssd crashes on startup because of ldb version

[Audun Gangstø]

Source: sssd
Version: 1.15.3-2
Severity: normal

Dear Maintainer,

On upgrade of SSSD to the current version, libldb was also upgraded from
1.1.29-2 to 1.2.2-2.
This causes a segmentation fault when trying to start SSD (strace shows
segfault shortly after reading a ldap cache file).
As a workaround, downgrading to 1.1.29-2 resolves this and sssd works normally.



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

Kernel: Linux 4.14.0-041400rc5-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#879825: game-data-packager: Fails to build tyrian-data

[Alexandre Detiste]

2017-10-28 13:45 GMT+02:00 Voker57 :
> Command finishes successfully

So where's the bug ?

---

Moreover: from dpkg 1.19.0 we can build the package without fakeroot:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291320
   * Add support to dpkg-deb for rootless builds, by setting the owner and
 group for the control.tar entries to root:root, and making it possible to
 do the same for the data.tar entries via the new --root-owner-group option.
 Based on a patch by Niels Thykier . Closes: #291320

This would reach testing today (maybe),
so we'd still have to keep a depedency on "dpkg (>= 1.19.0) |
fakeroot" for years on
+ check dpkg version it a run-time.

Greets,

Bug#879991: lynx: missing documentation

[Thomas Dickey]

On Sat, Oct 28, 2017 at 02:01:25AM -0400, westlake wrote:
> Package: lynx
> Version: 2.8.9dev16-1
> Severity: normal

This is a problem with the package, not the upstream source.
I regularly compile a test-package which has all of the documentation
links resolved to the local filesystem, e.g.,

file://localhost/usr/share/doc/lynx-dev/help_dir/cattoc.html.gz

> "The requested URL /release/breakout/lynx_help/cattoc.html was not
> found on this server."
> 

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#834714: [xml/sgml-pkgs] Bug#834714: libxslt1-dev: arch-dependent file in "Multi-Arch: same" package

[Mattia Rizzolo]

On Sat, Oct 28, 2017 at 10:33:38AM +0200, Manuel A. Fernandez Montecelo wrote:
> So, in the tests that you mention, did you try to compile packages that
> depend on libxslt, with this change enabled?
> 
> Mattia, will you move this forward?

I can upload it to experimental.
Given the amount of rdeps I'd prefer if somebody could perform
comparative rebuilds (i.e. first build all rdpes using the current
unstable package, then rebuild using the new exp package and compar what
failed).

> > Changelog:
> > Move xsltconfig.h to an arch-specific include directory.

I included something similar (just moved the lines around) in git.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#879063: ipmitool FTBFS with debhelper 10.9.2

[Jörg Frings-Fürst]

tags 879063 + unreproducible


Hi,

here the FTBFS isn't reproducible.

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB
Wire:  @joergfringsfuerst
Skype: joergpenguin
Ring:  jff

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#879825: game-data-packager: Fails to build tyrian-data

[Voker57]

On Sat, Oct 28, 2017 at 01:30:57PM +0200, Alexandre Detiste wrote:
> control: tag -1 +moreinfo
> 
> Hi,
> 
> I can't reproduce this.
> 
> I see you are using "pseudo" instead of the regular fakeroot,
> can you try again with fakeroot ?

In fact I'm using fakeroot-ng. Command finishes successfully with
fakeroot-pseudo, as well as with real root.

> 
> (switchable with update-alternatives, I guess)
> 
> dpkg-deb could benefit from a progress indicator, but no one is working on 
> this:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778451;msg=5
> 
> Greets,
> 

Bug#880012: xandikos: typo in package description

[Roland Hieber]

Package: xandikos
Severity: minor

Dear Maintainer,

the package description gives the greek name of the package as "Δύστρος"
("Dystros"), when it should probably say "Ξανδικός" or "Ξανθικός" (like
mentioned in Xandikos' README.rst) instead.

Cheers,
 - Roland

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

Kernel: Linux 4.11.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.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 xandikos depends on:
ii  python3 3.5.3-3
pn  python3-defusedxml  
pn  python3-dulwich 
pn  python3-icalendar   
pn  python3-jinja2  

xandikos recommends no packages.

xandikos suggests no packages.

Bug#879825: game-data-packager: Fails to build tyrian-data

[Alexandre Detiste]

control: tag -1 +moreinfo

Hi,

I can't reproduce this.

I see you are using "pseudo" instead of the regular fakeroot,
can you try again with fakeroot ?

(switchable with update-alternatives, I guess)

dpkg-deb could benefit from a progress indicator, but no one is working on this:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778451;msg=5

Greets,

2017-10-26 13:34 GMT+02:00 Voker57 :
>
> Package: game-data-packager
> Version: 53
> Severity: important
>
> Dear Maintainer,
>
> I ran `game-data-packager tyrian` to download Tyrian data, but it hang
> up on building package. Log is attached.
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, arm64
>
> Kernel: Linux 4.13.0-1-amd64 (SMP w/8 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: sysvinit (via /sbin/init)
>
> Versions of packages game-data-packager depends on:
> ii  pseudo [fakeroot]  1.8.1+git20161012-2
> ii  python33.6.3-1
> ii  python3-debian 0.1.31
> ii  python3-yaml   3.12-1+b1
>
> Versions of packages game-data-packager recommends:
> pn  game-data-packager-runtime  
>
> Versions of packages game-data-packager suggests:
> pn  arj
> ii  binutils   2.29.1-6
> ii  cabextract 1.6-1+b1
> ii  cdparanoia 3.10.2+debian-11+b2
> pn  dynamite   
> ii  gcc4:7.2.0-1d1
> pn  gdebi | gdebi-kde  
> ii  gir1.2-gdkpixbuf-2.0   2.36.11-1
> pn  innoextract
> pn  lgc-pg 
> pn  lgogdownloader 
> pn  lhasa | jlha-utils | lzh-archiver  
> ii  make   4.1-9.1
> ii  p7zip-full 16.02+dfsg-4
> ii  steam  1.0.0.54-2
> ii  steamcmd   0~20130205-1
> pn  unace-nonfree  
> pn  unar   
> ii  unrar  1:5.5.8-1
> pn  unshield   
> ii  unzip  6.0-21
> ii  vorbis-tools   1.4.0-10+b1
> ii  xdelta 1.1.3-9.1+b1
>
> -- no debconf information

Bug#879990: [Pkg-mozext-maintainers] Bug#879990: Fails to start on first run of Firefox 56

[David Prévot]

Hi Josh,

Thank you for your report!

Le 27/10/2017 à 18:48, Josh Triplett a écrit :
> Package: xul-ext-adblock-plus

> (Filing as "important" rather than "grave" in case this doesn't happen
> for everyone.)

Damn, I didn’t properly test the package on first run. Unfortunately, I
may not have much time to debug this issue in the next few weeks, feel
free to raise the severity if you (or preferably someone else) can
reproduce the issue.

I’m not able to reproduce it with a fresh profile, but on the other
hand, I don’t see the first run page either, so something seems to go
wrong here too.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#879990: [Pkg-mozext-maintainers] Bug#879990: Fails to start on first run of Firefox 56

[David Prévot]

Hi Josh,

Thank you for your report!

Le 27/10/2017 à 18:48, Josh Triplett a écrit :
> Package: xul-ext-adblock-plus

> (Filing as "important" rather than "grave" in case this doesn't happen
> for everyone.)

Damn, I didn’t properly test the package on first run. Unfortunately, I
may not have much time to dig into this issue in the next few weeks,
feel free to raise the severity if you (or preferably someone else) can
reproduce the issue.

I’m not able to reproduce it with a fresh profile, but on the other
hand, I don’t see the first run page either, so something seems to go
wrong here too.

Regards

David



signature.asc
Description: OpenPGP digital signature