Bug#870451: sbuild-update-all is missing the executable bit

[Michael Stapelberg]

Package: sbuild
Version: 0.73.0-4
Severity: normal

The instructions in /usr/share/doc/sbuild/examples/sbuild-update-all recommend
to directly run the script from cron:

# 1. Update all sbuild chroots four times a day (at 00:15/06:15/12:15/18:15):
#
# 15 */6 * * * root /usr/share/doc/sbuild/examples/sbuild-update-all
#

However, when doing that, one gets an error message:

/bin/sh: 1: /usr/share/doc/sbuild/examples/sbuild-update-all: Permission denied

This is because the script is not marked executable:

% ls -l /usr/share/doc/sbuild/examples/sbuild-update-all
-rw-r--r-- 1 root root 3298 2017-01-24 10:58 
/usr/share/doc/sbuild/examples/sbuild-update-all


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

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

Versions of packages sbuild depends on:
ii  adduser 3.115
ii  libsbuild-perl  0.73.0-4
ii  perl5.26.0-4

Versions of packages sbuild recommends:
ii  autopkgtest  4.4
ii  debootstrap  1.0.90
ii  schroot  1.6.10-4

Versions of packages sbuild suggests:
ii  deborphan  1.7.28.8-0.3+b1
ii  kmod   24-1
ii  wget   1.19.1-4

-- Configuration Files:
/etc/sbuild/sbuild.conf [Errno 2] No such file or directory: 
'/etc/sbuild/sbuild.conf'

-- no debconf information

Bug#868255: openjdk-9: Please build with --with-debug-level=slowdebug on Zero-only architectures

[John Paul Adrian Glaubitz]

On 08/01/2017 10:10 PM, John Paul Adrian Glaubitz wrote:
> Hmm, wait a second. I just had the JVM lock up. Will do a clean build
> to re-test.

Ok, I should have just waited :-). Your patch works:

Build Architecture: powerpc
Build Type: any
Build-Space: 4093428
Build-Time: 23425
Distribution: sid
Host Architecture: powerpc
Install-Time: 115
Job: /var/lib/buildd/debian/openjdk-9_9~b179-2.dsc
Machine Architecture: powerpc
Package: openjdk-9
Package-Time: 23548
Source-Version: 9~b179-2
Space: 4093428
Status: successful
Version: 9~b179-2

Finished at 2017-08-02T02:42:34Z
Build needed 06:32:28, 4093428k disk space

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#870406: [pkg-mad-maintainers] Bug#870406: libmad: CVE-2017-11552

[Salvatore Bonaccorso]

Hi Kurt

On Tue, Aug 01, 2017 at 07:48:01PM +0200, Kurt Roeckx wrote:
> On Tue, Aug 01, 2017 at 07:24:56PM +0200, Salvatore Bonaccorso wrote:
> > Source: libmad
> > Version: 0.15.1b-7
> > Severity: important
> > Tags: security upstream
> > 
> > Hi,
> > 
> > the following vulnerability was published for libmad.
> > 
> > CVE-2017-11552[0]:
> > | The mad_decoder_run function in decoder.c in libmad 0.15.1b allows
> > | remote attackers to cause a denial of service (memory corruption) via a
> > | crafted MP3 file.
> > 
> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> I guess you don't have any patch for this?

No unfortunatley not. The report furthermore AFAIK is only found on
the fulldisclosure list, not sure it has been reported "upstream" (if
still active?).

Regards,
Salvatore

Bug#824046: libtkx-perl: FTBFS: Tcl error 'Foo at /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking scalar result call

[gregor herrmann]

On Tue, 01 Aug 2017 18:42:16 -0400, intrigeri wrote:

> I'd rather not do that and thus I'm still in favour of removing this
> package from Debian.
> 
> Thoughts?

+1 for removal.

(And thanks for all your work on rm-candidates.)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#870450: ITP: deepin-screenshot -- Advanced screen shoting tool

[Weng Mo]

Package: wnpp
Severity: wishlist
Owner: Mo Weng 

* Package name: deepin-screenshot
  Version : 4.0.8+git20170725
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://www.deepin.org/
* License : GPL-3+
  Programming Lang: C++
  Description : Advanced screen shoting tool

Deepin Screenshot is a sophisticated screenshot software developed by deepin 
technology team. It’s characterized with smart window identification, shortcuts 
supporting, image editing, delay screenshot, social sharing, smart saving, 
image resolution adjusting and other functions.

I intend to co-maintain this package inside pkg-deepin team.

Bug#869723: Please upgrade to a new version

[Simon Quigley]

> Other than the version string, the patch is literally a one-line change.
> 
>>  - Murmur’s -limits command will now print output as it runs, instead of
>> at exit. (98cd156f0c26be2bacc22d8c64db9c349f16a213)
> 
> ... and this is the one-line change. ;-) Nothing OpenSSL related.
> 
> I'll leave this bug open and close it when I upgrade the mumble source
> package to 1.2.19 which I should be able to do soon. (Hopefully within
> the next couple of days.) I would have done this before the freeze for
> Debian Stretch, but upstream 1.2.19 was released after the freeze and I
> deemed the one-line change not important enough for a release freeze
> exception.

Fair. Thanks!

-- 
Simon Quigley
tsimo...@ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4

Bug#866510: Bug #866510 mate-system-monitor

[D]

Please add these comments to this bug report:

The text which displays the download speed is correct, but the speed scale to 
the left of the graph shows only two places of the value. For example, if the 
speed is between 200 and 400 Kbytes per second, the labels should be 200 and 
400 Kbytes per second. Instead, the labels appear as 00 and 00 Kbytes per 
second.

Doug L

Bug#870449: ITP: deepin-screen-recorder -- Default screen recorder application for Deepin desktop evironment

[Yanhao Mo]

Package: wnpp
Severity: wishlist
Owner: Yanhao Mo 

 * Package name: deepin-screen-recorder
   Version : 2.4
   Upstream Authro : Deepin Technology Co., Ltd.
 * URL : https://www.deepin.org/
 * License : GPLv3
   Programming Lang: C++
   Description : Default screen recorder appliction for Deepin
   desktop evironment.

Deepin Screen Recorder is a screen recorder tool,
it supports to save the recorded screens as gif or mp4 format.
It can select the recorded window automatically or manually by selecting the 
area.
Users just need to start and stop the recording process,
and the file will auto save to the desktop.

I intend to co-maintain this package inside pkg-deepin.


signature.asc
Description: PGP signature

Bug#870448: hw-detect - stop using modprobe -l

[Vincent McIntyre]

Package: hw-detect
Version: 1.124
Severity: normal
Tags: patch

I keep seeing this in installer logs, back to jessie.

Aug  2 01:52:11 main-menu[193]: (process:224): modprobe: invalid option -- 'l'


I rated this normal rather than minor because the way it is working
now the is_available() function always returns 1 (failure)

My suggestion is to use modinfo instead.
This will return multiline output inside the quotes but
a couple of tests suggests that is ok.
It does fail with some modules (nvidia), not sure if we care.

diff --git a/hw-detect.sh b/hw-detect.sh
index 7977814..d8196c1 100755
--- a/hw-detect.sh
+++ b/hw-detect.sh
@@ -43,7 +43,7 @@ is_not_loaded() {
 }
 
 is_available () {
-   [ "$(modprobe -l $1)" ] || return 1
+   [ "$(modinfo $1)" ] || return 1
 }
 
 # Module as first parameter, description of device the second.

Kind regards
Vince

Bug#870447: ITP: deepin-system-monitor -- a more user-friendly system monitor.

[Yanhao Mo]

Package: wnpp
Severity: wishlist
Owner: Yanhao Mo 

 * Package name: deepin-system-monitor
   Version : 1.0.2
   Upstream Author : Deepin Technology Co., Ltd.
 * URL : https://www.deepin.org/
 * License : GPLv3
   Programming Lang: C++
   Description : a more user-friendly system monitor

Deepin System Monitor is developed by Deepin Technology official Team,
which aims to provide a simple and practical tool for monitoring usage of CPU,
memory and network, as well as management of system and application
process including viewing, searching and killing.

I intend to co-maintain this package inside pkg-deepin team.


signature.asc
Description: PGP signature

Bug#870446: ITP: deepin-terminal -- Default terminal emulation application for Deepin desktop environment

[Yanhao Mo]

Package: wnpp
Severity: wishlist
Owner: Yanhao Mo 

  Version : 2.5.2
  Upstream Author : Deepin Technology Co., Ltd.
* URL : http://www.deepin.org/
* License : GPLv3
  Programming Lang: Vala
  Description : Default terminal emulation application for Deepin.

Deepin Terminal is a terminal emulator with simple interface,
rich and powerful functions created by Deepin Technology.
You can instantly start and close Deepin Terminal smoothly like normal file 
window,
allowing you to input commands with facility and no distractions.

I intend to co-maintain this package inside pkg-deepin team.


signature.asc
Description: PGP signature

Bug#870398: sks: recursive make intermittently breaks parallel builds

[Daniel Kahn Gillmor]

Control: tags 870398 + upstream
Control: retitle 870398 recursive make intermittently breaks parallel builds
Control: forwarded 870398 
https://bitbucket.org/skskeyserver/sks-keyserver/issues/51/recursive-make-breaks-parallelism

Stating the dependency between bdbwrap.cmi and bdb/bdb.cmi wasn't too
bad -- i just had to "overstate" the dependency by making it directly
depend on bdb/bdb.cma (see upstream pull request [0]).

However, there is still a problem with recursive make and descent into
bdb/, which i've documented at the forwarded link, above, which is also
evident in the i386 build of 1.1.6-7 [1] (i think 1.1.6-8 is likely to still
suffer from it, but we just got lucky on the rebuild).

As i wrote upstream:

> what's happening here is that the sub-make processes get invoked at the
> same time, don't know about each other, and try to build the exact same
> thing at the same time. One of the compilation steps complains about the
> other compilation clobbering a file out from under it.
> 
> One way to fix this would be to move all the dependency and build
> information entirely into a single makefile.  Another way would be to
> depend on an external ocaml bdb library, rather than shipping our own.

Stéphane, is there any prospect of packaging libbdb-ocaml separately for
debian?

or, i could just force the build of bdb/bdb.cma first in
sks:debian/rules, which should avoid the problem for the moment (though
it does feel a bit fiddly).

Any thoughts or preferences?

  --dkg

[0] 
https://bitbucket.org/skskeyserver/sks-keyserver/pull-requests/57/document-the-explicit-dependency-of/diff
[1] 
https://buildd.debian.org/status/fetch.php?pkg=sks=i386=1.1.6-7=1501622473=0


signature.asc
Description: PGP signature

Bug#870445: libglvnd: FTBFS on non-Linux: u_execmem_free undefined

[Aaron M. Ucko]

Source: libglvnd
Version: 0.2.999+git20170201-4
Severity: important
Tags: upstream
Justification: fails to build from source

Builds of libglvnd for kFreeBSD and the Hurd (admittedly not release
architectures) have been failing:

  
./build/src/GLdispatch/vnd-glapi/../../../../src/GLdispatch/vnd-glapi/stub.c:110:
 undefined reference to `u_execmem_free'

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#869724: ifupdown: coldplug of renamed interfaces renames but doesn't bring up

[Adam Borowski]

On Thu, Jul 27, 2017 at 05:39:57PM +0200, Guus Sliepen wrote:
> On Tue, Jul 25, 2017 at 11:42:01PM +0200, Adam Borowski wrote:
> 
> > rename mac/00:e0:4c:11:7f:4e/=wl0
> > allow-hotplug wl0
> > iface wl0 inet static
> > yaddayadda
> 
> I see you're using wpasupplicant. Could it be that that one is having a
> problem? Maybe it depends on something that is not available yet when
> the hotplug interface is brought up.

Possibly.  I see nothing in /var/log/daemon.log where wpa_supplicant usually
logs to, not even:
Aug  2 03:21:51 umbar wpa_supplicant[6816]: Successfully initialized 
wpa_supplicant
which it says when hotplugged.
 
> ifquery --state wl0 should say "wl0=wl0" when ifupdown things the
> interface is up, and it should say nothing if it thinks it is down. What
> does it say after a cold boot?

wl0=wl0

> Also, can you try commenting the wpa- options out, rebooting, and
> checking the output?

Same.

> > The interface gets renamed but stays down, wpa-supplicant is not started,
> > etc.  Note that the IP address _gets_ assigned, though:
> 
> That really means ifup was running up to and including configuring
> addresses. wpa-supplicant is started from both if-pre-up.d and if-up.d,
> so I think the error happens in the post-up phase. Is there anything in
> the logs that could tell you what is going on?

Nothing in logs that would appear interesting, but, on serial console (tty1
scrolls out as Manuel Schölling applied his wonderful persistent scrollback
patch only to vgacon for now) there's:

[] Starting the hotplug events dispatcher: systemd-udevdstarting version 234
[1G[ ok [?25h.
[] Synthesizing the initial hotplug events...[1G[ ok [?25hdone.
[] Waiting for /dev to be fully populated...[9.888986] nouveau 
:01:00.0: NVIDIA GF114 (0ce000a1
)
[9.932611] usbcore: registered new interface driver usbserial
[9.940499] usbcore: registered new interface driver usbserial_generic
[9.949140] usbserial: USB Serial support registered for generic
[9.962199] usbcore: registered new interface driver pl2303
[9.969745] usbserial: USB Serial support registered for pl2303
[9.977652] pl2303 6-3:1.0: pl2303 converter detected
[9.984821] usbcore: registered new interface driver cp210x
[9.992457] usbserial: USB Serial support registered for cp210x
[   10.000419] cp210x 3-1:1.0: cp210x converter detected
[   10.006270] usb 6-3: pl2303 converter now attached to ttyUSB0
[   10.006302] pl2303 4-1:1.0: pl2303 converter detected
[   10.027321] usb 4-1: pl2303 converter now attached to ttyUSB2
[   10.031235] usb 3-1: cp210x converter now attached to ttyUSB1
[   10.058025] nouveau :01:00.0: bios: version 70.24.2e.00.02
[   10.086077] EDAC amd64: Node 0: DRAM ECC disabled.
[   10.091422] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
[   10.091422]  Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
[   10.091422]  (Note that use of the override may cause unknown side effects.)
[   10.188478] EDAC amd64: Node 0: DRAM ECC disabled.
[   10.191468] usb 1-5: Vendor: Realtek
[   10.191471] usb 1-5: Product: 802.11n NIC
[   10.191473] usb 1-5: Serial: 
[   10.191475] usb 1-5: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes):

[   10.191572] usb 1-5: RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, 
GPS=0, HI PA=0
[   10.191574] usb 1-5: RTL8192EU MAC: 00:e0:4c:11:7f:4e
[   10.191576] usb 1-5: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
[   10.193470] usb 1-5: Firmware revision 19.0 (signature 0x92e1)
[   10.198836] do the RAM reset

[   11.373767] usbcore: registered new interface driver rtl8xxxu
[   11.417507] rtl8xxxu 1-5:1.0 wl0: renamed from wlan0
[   11.512204] [TTM] Zone  kernel: Available graphics memory: 4087048 kiB
[   11.519015] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[   11.525790] [TTM] Initializing pool allocator
[   11.530413] [TTM] Initializing DMA pool allocator
[   11.535351] nouveau :01:00.0: DRM: VRAM: 1024 MiB
[   11.540617] nouveau :01:00.0: DRM: GART: 1048576 MiB
[   11.546179] nouveau :01:00.0: DRM: TMDS table version 2.0
[   11.552145] nouveau :01:00.0: DRM: DCB version 4.0
[   11.554111] IPv6: ADDRCONF(NETDEV_UP): wl0: link is not ready

[] Cleaning up temporary files...[1G[ ok [?25h.
[] Setting kernel variables...[1G[ ok [?25hdone.
[] Configuring network interfaces...[   18.600624] r8169 :02:06.0 eth0: 
link down
[   18.600650] r8169 :02:06.0 eth0: link down
[   18.609635] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
invoke-rc.d: could not determine current runlevel
[   18.681691] br0: port 1(eth0) entered blocking state
[   18.686776] br0: port 1(eth0) entered disabled state
[   18.691927] device eth0 entered promiscuous mode
[   18.701007] IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready

Waiting for br0 to get ready (MAXWAIT is 32 seconds).
Waiting for DAD... [   21.732402] r8169 :02:06.0 eth0: link up

Bug#870443: ITP: cjson -- Ultralightweight JSON parser in ANSI C

[Yanhao Mo]

Package: wnpp
Severity: wishlist
Onwer: Yanhao Mo 

 * Package name: cjson
   Version : 1.5.7
   Upstream Author : Dave Gamble
 * URL : https://github.com/DaveGamble/cJSON
 * License : MIT
   Programming Lang: C
   Description : Ultralightweight JSON parser in ANSI C.

cJSON aims to be the dumbest possible parser that you can
get your job done with. It's a single file of C, and a single
header file.

As a library, cJSON exists to take away as much legwork as it can,
but not get in your way.

I intend to co-maintain this package inside collab-maint team.


signature.asc
Description: PGP signature

Bug#870444: libglvnd: FTBFS on arm64: no _glapi_tls_Current@Base

[Aaron M. Ucko]

Source: libglvnd
Version: 0.2.999+git20170201-4
Severity: important
Tags: upstream
Justification: fails to build from source

The arm64 build of libglvnd failed:

  dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libglvnd0/DEBIAN/symbols doesn't match 
completely debian/libglvnd0.symbols
  --- debian/libglvnd0.symbols (libglvnd0_0.2.999+git20170201-4_arm64)
  +++ dpkg-gensymbols4xEoPS 2017-08-01 17:19:46.984994738 +
  @@ -16,4 +16,4 @@
__glDispatchUnregisterStubCallbacks@Base 0
_glapi_Current@Base 0
_glapi_get_current@Base 0
  - _glapi_tls_Current@Base 0
  +#MISSING: 0.2.999+git20170201-4# _glapi_tls_Current@Base 0

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#485776: debian-policy: Adding graphical flowcharts for maintainer scripts invocation would help understand the process

[Russ Allbery]

Sean Whitton  writes:
> On Tue, Aug 01, 2017 at 04:55:33PM +0100, Ian Jackson wrote:

>> We should surely import the diagrams as-is.

> Russ -- you were the one that suggested generating them.  What do you
> think about importing them as-is now?

My only concern about importing them as-is is that dia is kind of tedious
to use and we'd need to be sure to update them for further changes.
(Documenting triggers will require changing those diagrams, for instance.)
They felt like they might be more maintainable in something like dot files
(for Graphviz).

That said, I don't think that concern should stop us from importing them.
Having them is clearly better than not having them.

-- 
Russ Allbery (r...@debian.org)   

Bug#824839: librrd-simple-perl: FTBFS on armhf and arm64: t/23graph.t failures

[Russ Allbery]

intrigeri  writes:

> You did the initial upload of librrd-simple-perl to Debian back in 2013,
> so I'm seeking your opinion wrt. removing it from sid as part of the
> pkg-perl ongoing effort towards removing the most hopeless of our
> RC-buggy packages.

> Summary:

>  * This package was not shipped in Stretch due to this bug.

>  * On https://rt.cpan.org/Public/Bug/Display.html?id=78785 you've
>attached a patch that fixed the problem on x86_64, but sadly it
>doesn't fix it on armhf and arm64.

>  * This is a leaf package and popcon is fairly low:
>Inst = 43, Vote = 5.

> Are you interested in working further on this problem?

> Would you mind if we removed this package from sid?

Yeah, go for it.  I was using it for a specific project, and I think I
ended up abandoning that project anyway (and I'm no longer working for the
employer who had that problem).  If someone runs into a need for it, they
can always circle back and look at the package again.  It seemed pretty
seriously unmaintained.

-- 
Russ Allbery (r...@debian.org)   

Bug#868213: libmate-menu2:amd64: The Provides and Breaks in this package prevents the crossgrading of Mate from i386 to amd64

[Mike Gabriel]

Hi Jose,

On  Do 13 Jul 2017 09:03:28 CEST, Jose M Calhariz wrote:


Package: libmate-menu2
Version: 1.16.0-2
Severity: normal

I have been doing experiments on Crossgrading of Mate and Xorg from
i386 to amd64.  The crossgrading following the instructions in
http://blog.calhariz.com/post/2017/07/12/Crossgrading-a-minimal-install-of-Debian-9
that are an adaptation from the Debian Wiki
https://wiki.debian.org/CrossGrading

The crossgrade fails with the message:
dpkg: dependency problems prevent configuration of libmate-menu2:amd64:
 libmate-menu2:i386 (1.16.0-2) breaks libmatemenu and is installed.
   libmate-menu2:amd64 (1.16.0-2) provides libmatemenu.

The way to exit from this situation is:
dpkg --install --force-breaks  
/var/cache/apt/archives/libmate-menu2_1.16.0-2_amd64.deb


Kind regards
Jose M Calhariz


My proposal for a fix for the above is actually dropping the  
stone-age-old Provides: fields.


See:
https://anonscm.debian.org/cgit/pkg-mate/mate-menus.git/commit/?id=cb23c4740ba7a44736998493b3edb8674b65f401

Do you agree that this could be a possible solution?

Thanks+Greets,
Mike

PS: Thanks for blogging about your cross-grading effort. Those posts  
are relevant here for me with a local project I run based on Debian.

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpIQeeWwsTaw.pgp
Description: Digitale PGP-Signatur

Bug#759553: suggested patch

[Steve McIntyre]

Control: tag -1 +pending

On Wed, Aug 02, 2017 at 10:26:12AM +1000, Vincent McIntyre wrote:
>Tags: patch
>Thanks
>
>Can this be fixed please? I wasted an hour tracking this down
>while trying to resolve another issue.
>
>
>--- lib/auto-lvm.sh.org 2017-08-02 10:24:35.773321165 +1000
>+++ lib/auto-lvm.sh 2017-08-02 10:24:49.709392154 +1000
>@@ -302,7 +302,7 @@
>defvgname="$RET"
> 
># Check that the volume group name is not in use
>-   if ! vg_get_info "$defvgname" && ! stat "/dev/$defvgname"; then
>+   if ! vg_get_info "$defvgname" && [ ! -e "/dev/$defvgname" ]; 
>then
>break
>fi
>noninteractive="bail_out vg_exists"

Cool, thanks for the patch. I've just pushed the fix into git now.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"You can't barbecue lettuce!" -- Ellie Crane

Bug#870442: upower lazy about critical-action

[Brian Ristuccia]

Package: upower
Version: 0.99.4-4+b1
Severity: critical
Justification: causes serious data loss

   * When the charge level is below PercentageAction or TimeAction as
applicable, upower fails to be sufficiently aggressive about hibernating the
system.
   * When hibernation fails, the system can shut down abruptly, 
resulting in

loss of all unsaved data.
   * On some systems, running down the battery completely erases firmware
confirguration information, rendering the system unbootable.

A few examples of cases where it fails:

   * On my Acer UX32VD, upower will hybrid suspend the system on low 
battery.
When the battery reaches a critical level during suspend, the system 
wakes up
and then runs until the battery is completely dead. This can happen even 
with

the lid closed while the system is in a bag or briefcase, which can cause
elevated temperatures. The BIOS configuration including UEFI boot options is
lost.
   * Plugging in a charger briefly and then unplugging it may forestall
suspending, then the system will then run until the battery is 
completely dead.
   * Waking a hybrid suspended system without first connecting a 
charger can

cause it to run until the battery is completely dead. This problem is easily
triggered if the user is actively typing at the time of suspend.
   * If a system is woken from hibernation with a critically low battery,
upower does not try to re-hibernate it.
   * There is no facility to block resume on a critically low battery 
early in
the boot process, thus a resume image can be "wasted" by consuming it 
with no

hope of continued execution.

Here's the behavior I expect:

   * upower should aggressively try the critical action if the battery has
reached the critical action level and no charger is connected
   * upower should run the critical action if a charger is disconnected for
more than a few seconds while the battery is still below the critical action
level
   * If the system wakes up from hybrid suspend (or fails to hybrid 
suspend)

with a critical battery and no charger connected, it should be immediately
hibernated
   * If the system wakes up from hibernation with a critical battery and no
charger connected, it should be immediately re-hibernated
   * Early in the initramfs, upower should check the battery status and 
block

bootup if the battery is critical and no charger is connected




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

Kernel: Linux 4.11.0-0.bpo.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 upower depends on:
ii  dbus   1.10.18-1
ii  libc6  2.24-11+deb9u1
ii  libglib2.0-0   2.50.3-2
ii  libgudev-1.0-0 230-3
ii  libimobiledevice6  1.2.0+dfsg-3.1
ii  libplist3  1.12+git+1+e37ca00-0.3
ii  libupower-glib30.99.4-4+b1
ii  libusb-1.0-0   2:1.0.21-1
ii  udev   232-25+deb9u1

Versions of packages upower recommends:
ii  policykit-1  0.105-18

upower suggests no packages.

-- Configuration Files:
/etc/UPower/UPower.conf changed [not included]

-- no debconf information

Bug#870441: RM: wysihtml -- RoQA; RC buggy; effectively orphaned

[Sean Whitton]

Package: ftp.debian.org
Severity: normal

Last maintainer upload was 2007.

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#419510: Upgrading severity of this bug

[Sean Whitton]

control: severity -1 serious

Hello,

Someone at DebCamp pointed out that this bug is actually a security
issue: this is a network library, and should definitely not be a
convenience copy of the code, and indeed, not a ten-year-old version.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#857256: /usr/bin/nvim: Neovim says it is not an optimized build

[James McCoy]

Version: 0.2.0-1

On Thu, Mar 09, 2017 at 10:41:07AM +0100, Ulrik wrote:
> :CheckHealth in neovim has the following output for the performance
> section, so it claims to not be optimized.
> 
> 
> ## Performance
>   - INFO: Build type: None
>   - WARNING: Non-optimized build-type. Nvim will be slower.
> - SUGGESTIONS:
>   - Install a different Nvim package, or rebuild with 
> `CMAKE_BUILD_TYPE=RelWithDebInfo`.
>   - See https://github.com/neovim/neovim/wiki/FAQ

This was fixed with the 0.2.0-1 upload as part of reworking how the
buildsystem is invoked.

neovim (0.2.0-1) experimental; urgency=medium

  …
  * Rewrite debian/rules to invoke cmake directly, instead of through
top-level Makefile.
  …

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#759553: suggested patch

[Vincent McIntyre]

Tags: patch
Thanks


Can this be fixed please? I wasted an hour tracking this down
while trying to resolve another issue.


--- lib/auto-lvm.sh.org 2017-08-02 10:24:35.773321165 +1000
+++ lib/auto-lvm.sh 2017-08-02 10:24:49.709392154 +1000
@@ -302,7 +302,7 @@
defvgname="$RET"
 
# Check that the volume group name is not in use
-   if ! vg_get_info "$defvgname" && ! stat "/dev/$defvgname"; then
+   if ! vg_get_info "$defvgname" && [ ! -e "/dev/$defvgname" ]; 
then
break
fi
noninteractive="bail_out vg_exists"

Kind regards
Vince

Bug#868818: RM: fedmsg -- RoQA; unmaintained, RC-buggy

[Chris Lamb]

Hi,

> RM: fedmsg -- RoQA; unmaintained, RC-buggy

Hm, that would break these build-depends:

  datanommer.commands
  datanommer.consumer
  datanommer.models
  fedmsg-meta-debian
  fedmsg-meta-fedora-infrastructure


Regards,

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

Bug#856614: dask.distributed: please make the build reproducible

[Diane Trout]

version: 1.18.0+ds.1-1
tags: pending

Hi,

The code you marked as being not reproducible was altered in 1.18.0 in
a way that I think removes the non-determinism.

Diane

Bug#870318: Acknowledgement (mate-polkit: MATE polkit built against GTK 3 displays a corrupted icon.)

[Omar Jair Purata Funes]

Patch can be applied "successfully", though Debuild throws some deprecated
flags issues
 g-ir-scanner: warning: Option --strip-prefix has been deprecated; which
results in:
make[3]: *** [PolkitGtkMate-1.0.gir] Error 1

2017-07-31 18:09 GMT-05:00 Debian Bug Tracking System :

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 870318:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870318.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   omarpura...@gmail.com
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  MATE Packaging Team 
>
> If you wish to submit further information on this problem, please
> send it to 870...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 870318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870318
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#856614: dask.distributed: please make the build reproducible

[Chris Lamb]

Hi Diane,

> The code you marked as being not reproducible was altered in 1.18.0 in
> a way that I think removes the non-determinism.

Ah, great; feel free to close this bug when it lands naturally :)


Best wishes,

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

Bug#870440: libc++abi-dev: typo in Breaks

[Andreas Beckmann]

Package: libc++abi-dev
Version: 3.9.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Package: libc++abi-dev
Version: 3.9.1-2
Replaces: libc++-dev (<< 3.9.0-3)
Breaks:   lic++-dev (<< 3.9.0-3)
   ^^

(This triggers Replaces-without-Breaks bugs in piuparts).


Andreas

Bug#870435: libkpmcore5: removal of libkpmcore5 makes files disappear from libkpmcore4

[Andreas Beckmann]

Followup-For: Bug #870435
Control: affects -1 + libkpmcore-dev

Similar problems exist in libkpmcore-dev which Replaces, but not Breaks
libkpmcore4-dev.


Andreas

Bug#758124: Documenting the Testsuite field in the Policy.

[Sean Whitton]

Hello Guillem,

On Wed, Aug 02, 2017 at 12:54:15AM +0200, Guillem Jover wrote:
> Except for the last dpkg which should probably be dpkg-source, I do
> like this version better.
> 
> Also perhaps worth mentioning that dpkg-source will remove the value
> if there is no debian/tests/control file (and emit a warning).

Sorry, I didn't see your message before I applied the older patch that
was seconded.  In the interests of getting Testsuite: documented, and
since the amendments are addendums to the description, rather than
changes, I think it would be best not to revert the change.

Could you prepare a patch for the versoin you like that applies cleanly
against the current git HEAD,[1] and seek seconds for it, please?  If
policy is released before you can do that, we can just clone the bug or
similar.

[1]  https://anonscm.debian.org/git/dbnpolicy/policy.git

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#865308: khronos-api is not Multi-Arch compatible

[Jens Reyer]

On 08/01/2017 11:30 PM, Jens Reyer wrote:
> Maintainer fields aren't mentioned explicitly in policy 5.11, while
> large parts of Debian take a very liberal stance at NMUs nowadays.

s/policy/debian reference/

Anyway, what I meant is afaic there is no rule about it.

Bug#798476: debian-policy: don't require Uploaders

[Jonas Smedegaard]

> The problem is that the information in Uploaders is no more likely to 
> be up-to-date than the team homepage/policy/docs.

I disagree: team homepage/policy/docs can go unmaintained for long, 
whereas every upload triggers a lintian warning unless the uploader is 
listed as such (and unless explicitly circumvented by flagged the upload 
as an NMU or an upload by a not-regularly-uploading team member).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#870439: refresh Texinfo version

[積丹尼 Dan Jacobson]

Package: gv
Version: 1:3.7.4-1+b1
X-Debbugs-CC: bug...@gnu.org, bug-texi...@gnu.org, Eli Zaretskii 


> "EZ" == Eli Zaretskii  writes:
>> From: 積丹尼 Dan Jacobson 
>> Cc: bug-texi...@gnu.org
>> Date: Wed, 26 Jul 2017 08:06:37 +0800
>> 
>> All I know is if I do
>> (info "(gv) Top")^X^E
>> i RET
>> I end up on
>> (info "(gv) GNU General Public License")
>> here on Debian,
>> gv:
>> Installed: 1:3.7.4-1+b1
>> emacs25:
>> Installed: 25.2+1-2

EZ> That's because gv.info was produced with makeinfo 4.8, which had a
EZ> bug: it would produce an Index entry even if the manual had no
EZ> indices.  There's this snippet near the end of gv.info in the gv
EZ> distribution:

EZ>   ^@^H[index^@^H]
EZ>   * Menu:

EZ> It shouldn't be there.  When I produce the GV manual using the latest
EZ> makeinfo 6.4, this part is not generated.

EZ> IOW, you should report this bug to the GV maintainers: they should
EZ> refresh their Texinfo version.

Bug#846970: debian-policy: Proposal for a Build-Indep-Architecture: control file field

[Colin Watson]

On Tue, Aug 01, 2017 at 07:47:47PM +0300, Adrian Bunk wrote:
> 1. Debian does not currently have non-amd64 binary-all autobuilders
> 
> Stating that binary-all packages in the archive are always being 
> built on amd64 would actually document the current status quo,
> assuming source-only uploads.
> 
> AFAIR pixfrogger and pixbros that I converted from binary-all to
> an explicit list of all 32bit architectures were the last two
> binary-all packages in main that could not be built on amd64.
> 
> These were pretty rare cases of requiring a 32bit-only package,
> and such a rare hack is better than mandating that Debian must
> add binary-all autobuilders for every architecture.

This is an essentially artificial argument that depends on the current
(IMO unnecessarily complicated) way in which Debian happens to implement
autobuilding of Architecture: all binaries.  If they were just builds
that happened on the normal autobuilders with a slightly different
configuration, which would be perfectly possible, then nobody would need
to worry about the effort of adding them for every architecture; any
autobuilder would be able to build Architecture: all packages if it
needed to do so.

To me, as one of the maintainers of Ubuntu's autobuilding
infrastructure, this is a sufficiently obviously simpler approach that
I'm quite puzzled as to why the Debian buildd maintainers chose to
implement it the way they did; I did talk to Andreas Barth about it at
the time that he was doing the work, but I had the feeling neither of us
was quite understanding the other.

I can see the argument for not documenting this field in policy until
the autobuilding infrastructure is actually able to cope with it
(depending on how heavily one weights the downstream arguments), but I
do think that the capability would fall quite naturally out of a
better-designed infrastructure.  I don't agree that your "explicitly
list all 32-bit architectures" hack is better than having the improved
infrastructure, even though it was probably necessary at the time.

> 2. We were not able to build all binaries in a release
> 
> For aboot and palo we are shipping binaries in jessie that cannot be 
> rebuilt in jessie since the build architecture is not part of jessie.
> 
> Cross-compilers are available on amd64, and this is how palo and 
> openhackware were fixed for stretch.

This has certainly been possible in some cases, but I still think it's
more simply done at the builder level.  And for the "build architecture
not part of release" case, is it really worth shipping boot loaders for
architectures where we don't ship the rest of the architecture?  The
rare case of systems building images for older releases could be handled
by just installing binaries from older releases.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#806544: libical-parser-sax-perl: FTBFS: t/01parse.t failure

[intrigeri]

Jonas Smedegaard:
> Quoting intrigeri (2017-08-01 16:38:06)
>> Jonas, what do you think?

> Please request removal - also of the reverse dependency.

Done: #870437

Bug#758124: Documenting the Testsuite field in the Policy.

[Guillem Jover]

Hi!

On Wed, 2014-08-20 at 09:44:45 -0300, Antonio Terceiro wrote:
> There are cases when you want to add it explicitly, e.g. when someone
> comes up with a new possible value for it that is not automatically
> added yet.
> 
> Testsuite: mynewthing
> 
> or even
> 
> Testsuite: autopkgtest, mynewthing
> 
> So maybe we could review the text like this:
> 
> Testsuite
> 
> 
>   Simple field containing a comma-separated list of values allowing
>   test execution environments to discover packages which provide
>   tests.  Currently, the only defined value is autopkgtest.
> 
> 
> 
>   dpkg-sourcefrom dpkg-dev version
>   1.17.11. will automatically add this field to Debian source
>   control files with the value autopkgtest if a
>   debian/tests/control file is present in the source
>   package. This field may also be used in source package control files
>   if needed in other situations, for example to declare other test suite
>   handlers that are not yet automatically detected by dpkg.
> 

Except for the last dpkg which should probably be dpkg-source, I do
like this version better.

Also perhaps worth mentioning that dpkg-source will remove the value
if there is no debian/tests/control file (and emit a warning).

I've also noticed that dsc(5) specifies this field as space-separated
in contradiction to the current implementations, which I'll be fixing
for dpkg 1.19.0.

Thanks,
Guillem

Bug#870438: RM: gcc-5-doc -- RoQA; obsolete

[Adrian Bunk]

Package: ftp.debian.org
Severity: normal

gcc-5-doc is obsolete:
- gcc-6-doc exists
- gcc-5 was already not in stretch

This removal has been ACK'ed by Guo Yixuan.

Bug#870437: ftp.debian.org: RM: libical-parser-sax-perl -- ROM: RC-buggy and inactive upstream

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

we (pkg-perl team) would like to remove this RC-buggy package and its
only reverse dependency (libical-parser-html-perl) from the archive.

Reference: https://bugs.debian.org/806544

Cheers,
-- 
intrigeri

Bug#870435: libkpmcore5: removal of libkpmcore5 makes files disappear from libkpmcore4

[Andreas Beckmann]

Package: libkpmcore5
Version: 3.1.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install libkpmcore4
  # (1)
  apt-get install libkpmcore5
  apt-get remove libkpmcore5
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/lib/x86_64-linux-gnu/qt5/plugins/libpmdummybackendplugin.so
  /usr/lib/x86_64-linux-gnu/qt5/plugins/libpmlibpartedbackendplugin.so
  /usr/share/kservices5/pmdummybackendplugin.desktop
  /usr/share/kservices5/pmlibpartedbackendplugin.desktop
  /usr/share/kservicetypes5/pmcorebackendplugin.desktop

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
https://www.debian.org/doc/debian-policy/footnotes.html#f53

The libkpmcore5 package has the following relationships with libkpmcore4:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libkpmcore3, libkpmcore4

>From the attached log (scroll to the bottom...):

3m54.1s ERROR: FAIL: After purging files have disappeared:
  /usr/lib/x86_64-linux-gnu/qt5/plugins/libpmdummybackendplugin.so   owned 
by: libkpmcore5
  /usr/lib/x86_64-linux-gnu/qt5/plugins/libpmlibpartedbackendplugin.so   owned 
by: libkpmcore5
  /usr/share/kservices5/pmdummybackendplugin.desktop owned by: libkpmcore5
  /usr/share/kservices5/pmlibpartedbackendplugin.desktop owned by: 
libkpmcore5
  /usr/share/kservicetypes5/pmcorebackendplugin.desktop  owned by: libkpmcore5

3m54.1s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/libkpmcore4.listnot owned

(note that ownership was recorded after libkpmcore5 claimes these files)


cheers,

Andreas


libkpmcore4=3.0.2-2_libkpmcore5=3.1.2-1.log.gz
Description: application/gzip

Bug#822430: debian-policy: Please update 8.1.1 to use the "ldconfig" trigger instead

[David Bremner]

On Sun, Apr 24, 2016 at 01:14:49PM +0200, Niels Thykier wrote:
> 
> """
> Any package installing shared libraries in one of the default library
> directories of the dynamic linker (which are currently /usr/lib and
> /lib) or a directory that is listed in /etc/ld.so.conf[60] must use
> ldconfig to update the shared library system.
> 
> Any such package must have an "activate-noawait ldconfig" line in
> their "triggers" control file.
> """
> (replacing the entire section).
> 
> Alternative wordings welcome; I am not entirely certain the one above
> is all that well.

seconded, with the suggestion of adding "(i.e. DEBIAN/triggers)" before the 
final '.'

But feel free to not take the suggestion also.




signature.asc
Description: PGP signature

Bug#870436: RM: morituri/experimental -- RoQA; obsolete, already removed from unstable

[Adrian Bunk]

Package: ftp.debian.org
Severity: normal

morituri was already removed from unstable in #817838

Jonas ACK'ed removing it also from experimental.

Bug#826619: pluma: Pluma - external tools missing

[Mike Gabriel]

Control: close -1

On  Di 07 Jun 2016 08:48:10 CEST, Gene Benson wrote:


Package: pluma
Version: 1.14.0-1
Severity: normal


Now really closing this bug.

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpBZgLJIUm07.pgp
Description: Digitale PGP-Signatur

Bug#824046: libtkx-perl: FTBFS: Tcl error 'Foo at /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking scalar result call

[intrigeri]

intrigeri:
> that's a leaf package, with 2 votes on popcon,

And now: 1.

> that made it into one
> single stable release ⇒ unless I missed a compelling reason to keep
> it, I would simply get the package remove from sid.

There's a pull request opened since February
(https://github.com/gisle/tkx/pull/2) that looks like it is about this
very issue; upstream didn't comment yet, just like they have not
commented on the RT bug report yet.

So we could certainly review that pull request and apply it in Debian,
but to me it essentially means we're becoming the new upstream
maintainers, and then we will have to keep this module on life-support
ourselves: the last upstream release was in 2010, and there was
1 single upstream commit (in 2013) since then
(https://github.com/gisle/tkx/commits/master).

I'd rather not do that and thus I'm still in favour of removing this
package from Debian.

Thoughts?

Bug#850157: Please deprecate all ad-hoc patch systems

[Sean Whitton]

On Thu, Jan 05, 2017 at 03:22:44PM +1100, Stuart Prescott wrote:
> [ various comments on Ian's proposal ]

Ian, do you have an updated proposal in response to Stuart's points?

> * Deprecating patch systems should also deprecate the 'patch' target
> in debian/rules from §4.9.

Thanks for noting this.

> * There are still other useful roles for d/README.source documented
> within policy and in associated documents; the python modules team
> refer to README.source as the place to document that a package is not
> using their standardised tool (git-dpm) and why, for instance.

Agreed, but we probably don't need to list all those roles in policy.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#870377: gcc-5-doc: FTBFS with perl 5.26: Unescaped left brace in regex is illegal

[Guo Yixuan]

On Tue, Aug 1, 2017 at 11:24 AM, Adrian Bunk  wrote:
>
> On Tue, Aug 01, 2017 at 03:59:12PM +0200, Andreas Beckmann wrote:
> > Source: gcc-5-doc
> > Version: 5.3.0-2
> > Severity: serious
> > Tags: sid buster
> > Justification: fails to build from source
> >
> > [...]
> > (cd gcc/doc && perl ../../contrib/texi2pod.pl -Dfngccint=gccint-5
-DBUGURL=http://bugs.debian.org/) < gcc/doc/invoke.texi > gcc.pod
> > Unescaped left brace in regex is illegal here in regex; marked by <--
HERE in m/^\@strong{ <-- HERE (.*)}$/ at ../../contrib/texi2pod.pl line 319.
> > debian/Makefile:198: recipe for target 'gcc.pod' failed
> > make[2]: *** [gcc.pod] Error 255
> > make[2]: Leaving directory '/build/gcc-5-doc-5.3.0'
> > debian/rules:56: recipe for target 'override_dh_auto_build' failed
> > make[1]: *** [override_dh_auto_build] Error 2
> > [...]
>
> I am surprised that gcc-5-doc is in stable and still in unstable even
> though gcc-5 is not in stable.
>
> Any objections to filing an RM bug for removing it from unstable?
>
> > Andreas
>
> cu
> Adrian

No problem. Please go ahead.

Yixuan
>
> --
>
>"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




--
GUO Yixuan

Bug#870433: [debian-mysql] Bug#870433: mysql-server: crash during upgrade to mariadb

[Robie Basak]

reassign 870433 mariadb-server-10.1 10.1.23-9+deb9u1
thanks


signature.asc
Description: PGP signature

Bug#822430: debian-policy: Please update 8.1.1 to use the "ldconfig" trigger instead

[Sean Whitton]

Hello Niels,

On Sun, Apr 24, 2016 at 01:14:49PM +0200, Niels Thykier wrote:
> Possible wording could be:
> 
> """
> Any package installing shared libraries in one of the default library
> directories of the dynamic linker (which are currently /usr/lib and
> /lib) or a directory that is listed in /etc/ld.so.conf[60] must use
> ldconfig to update the shared library system.
> 
> Any such package must have an "activate-noawait ldconfig" line in
> their "triggers" control file.
> """
> (replacing the entire section).
> 
> Alternative wordings welcome; I am not entirely certain the one above
> is all that well.

I think this wording is fine.  Seconded.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#870434: mesa: Break build dependency cycle with libva

[Daniel Schepler]

Source: mesa
Version: 17.1.5-1
Severity: wishlist

Currently, the mesa and libva source packages both Build-Depend on
each other.  It would be nice if mesa could provide a bootstrapping
build profile to break this cycle.

Hopefully, this would just be a matter of disabling the --enable-va
configure flag, and dropping the mesa-va-drivers package for the
stage1 build profile - provided that doesn't change the binary
contents of the other packages.
-- 
Daniel Schepler

Bug#870433: mysql-server: crash during upgrade to mariadb

[Jan Christoph Uhde]

Package: mysql-server
Version: 5.5.+default
Severity: important

Dear Maintainer,


the post install step fails with:

```
Setting up mariadb-server-10.1 (10.1.23-9+deb9u1) ...
/var/lib/dpkg/info/mariadb-server-10.1.postinst: line 17:  8957 Done
echo "$password_column_fix_query"
  8958 Aborted | $MYSQL_BOOTSTRAP 2>&1
  8959   | $ERR_LOGGER
dpkg: error processing package mariadb-server-10.1 (--configure):
 subprocess installed post-installation script returned error exit status 134
dpkg: dependency problems prevent configuration of default-mysql-server:
 default-mysql-server depends on mariadb-server-10.1; however:
  Package mariadb-server-10.1 is not configured yet.

dpkg: error processing package default-mysql-server (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on default-mysql-server; however:
  Package default-mysql-server is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 mariadb-server-10.1
 default-mysql-server
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

Probably caused by:

```
» /usr/bin/mysql_install_db --skip-auth-anonymous-user 
--auth-root-authentication-method=socket --rpm --cross-bootstrap --user=mysql 
--disable-log-bin
2017-08-02  0:20:17 139707596689984 [Note] /usr/sbin/mysqld (mysqld 
10.1.23-MariaDB-9+deb9u1) starting as process 8381 ...
Aborted

Installation of system tables failed!  Examine the logs in
/var/lib/mysql for more information.

The problem could be conflicting information in an external
my.cnf files. You can ignore these by doing:

shell> /usr/scripts/scripts/mysql_install_db --defaults-file=~/.my.cnf

You can also try to start the mysqld daemon with:

shell> /usr/sbin/mysqld --skip-grant --general-log &

and use the command line tool /usr/bin/mysql
to connect to the mysql database and look at the grant tables:

shell> /usr/bin/mysql -u root mysql
mysql> show tables;

Try 'mysqld --help' if you have problems with paths.  Using
--general-log gives you a log in /var/lib/mysql that may be helpful.

The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
MariaDB is hosted on launchpad; You can find the latest source and
email lists at http://launchpad.net/maria

Please check all of the above before submitting a bug report
at http://mariadb.org/jira
```

The following error can be found in the logs:

```
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Using mutexes to ref count 
buffer pool pages
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: The InnoDB memory heap is 
disabled
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Mutexes and rw_locks use GCC 
atomic builtins
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: GCC builtin 
__atomic_thread_fence() is used for memory barrier
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Compressed tables use zlib 
1.2.8
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Using Linux native AIO
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Using generic crc32 
instructions
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Initializing buffer pool, 
size = 128.0M
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Completed initialization of 
buffer pool
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Highest supported file 
format is Barracuda.
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Starting crash recovery from 
checkpoint LSN=625800204
2017-08-02  0:12:02 139668228993600 [Note] InnoDB: Restoring possible 
half-written data pages from the do
ublewrite buffer...
2017-08-02  0:12:03 139668228993600 [Note] InnoDB: 128 rollback segment(s) are 
active.
2017-08-02  0:12:03 139668228993600 [Note] InnoDB: Waiting for purge to start
2017-08-02 00:12:03 7f06e87fa700  InnoDB: Assertion failure in thread 
139667647211264 in file trx0purge.cc line 692
InnoDB: Failing assertion: purge_sys->iter.trx_no <= 
purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
170802  0:12:03 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will 

Bug#826619: pluma: Pluma - external tools missing

[Mike Gabriel]

Control: fixed -1 1.18.2-1
Control: close

Hi,

On  Di 07 Jun 2016 08:48:10 CEST, Gene Benson wrote:


Package: pluma
Version: 1.14.0-1
Severity: normal

Dear Maintainer,

After the latest update to Pluma 1.14.0-1 in testing external tools are not
included/missing.



This bug will be resolved with the upcoming upload of pluma 1.18.2-1.  
Unfortunately, I forgot to close this bug in the new pluma package's  
changelog.


So doing it manually now here...

Thanks,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpY09idtqGHM.pgp
Description: Digitale PGP-Signatur

Bug#645828: your search.cpan.org/metacpan.org commit / Bug#645828: Fold libdatetime-astro-sunrise-perl into libdatetime-event-sunrise-perl

[intrigeri]

intrigeri:
> I'll request the removal right away.

#870431

Bug#870432: debian-l10n-albanian mailing list creation

[Silva Arapi]

Package: lists.debian.org
Severity: wishlist

This is a request for a new mailing list

*Name*: debian-l10n-albanian

*Rationale:* I want this list to be created because me and other people
from a local community in Tirana called Open Labs, want to volnteer and
help with the translation of Debian related content into Albanian. A
mailing list can be a very useful mean of  communication, not only for us
but also for other people who might want to get involved.

* Short description*: Albanian / Shqip localization

*Long description:* "Discussing Albanian localization issues, mainly
translating Debian docs and programs to Albanian.

*Category:* i18n

S*ubscription Policy: *open

*Post Policy:* open to list subscribers

*Web Archive:* yes

Bug#485776: debian-policy: Adding graphical flowcharts for maintainer scripts invocation would help understand the process

[Hideki Yamane]

Hi,

On Tue, 1 Aug 2017 11:23:28 -0400
Sean Whitton  wrote:
> We are hoping to migrate Policy to rST built by Sphinx.  Maybe there is
> a flowchart tool that integrates particularly well with Sphinx.  CCing
> Hideki in case he knows.

 Maybe python-sphinxcontrib.blockdiag is the one.

$ apt show python-sphinxcontrib.blockdiag
Package: python-sphinxcontrib.blockdiag
Version: 1.5.5-1
(snip)
Homepage: https://github.com/blockdiag/sphinxcontrib-blockdiag
Download-Size: 7,700 B
APT-Sources: http://debian-mirror.sakura.ne.jp/debian sid/main amd64 Packages
Description: Sphinx "blockdiag" extension
 This package contains the blockdiag Sphinx extension. This extension enable
 you to insert block diagrams in your Sphinx document. This renders block
 diagrams by using python-blockdiag.


-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane

Bug#870431: ftp.debian.org: RM: libdatetime-astro-sunrise-perl -- ROM: obsolete developer snapshot, maintained alternative is in the archive

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

as reported to us by upstream and a couple users, this Perl module:

1. "was just a proof of concept and which had an active life of just
   4 days before becoming obsolete";
2. is affected by many bugs that were fixed after it was renamed (and
   the new versions are available in Debian, with their new name,
   since at least Wheezy).

So we (pkg-perl) would like to remove it from the archive.

References:

 * https://bugs.debian.org/645828
 * 
https://bugs.launchpad.net/ubuntu/+source/libdatetime-astro-sunrise-perl/+bug/1654056

Cheers,
-- 
intrigeri

Bug#645828: your search.cpan.org/metacpan.org commit / Bug#645828: Fold libdatetime-astro-sunrise-perl into libdatetime-event-sunrise-perl

[intrigeri]

Hi,

at least I could call a method on a DateTime::Set object returned by
DateTime::Event::Sunrise->sunrise. I don't think it's worth it's worth
my time to check any further if the incompatibility of
DateTime::Event::Sunrise with some version of DateTime::Set is still
a thing 10 years later, especially given I could find no description
of what the actual problem is more precise than "not compatible".

Current popon: Inst = 56, Vote = 9.

Given what the current upstream maintainer explains on the Launchpad
bug report gregor pointed to (i.e. we're shipping "a module which was
just a proof of concept and which had an active life of just 4 days
before becoming obsolete. And this module is buggy."), I agree with
gregor that we should remove this package from the archive.

*If* the DateTime::Event::Sunrise issue is still a thing, then that's
a bug to be reported elsewhere. And if someone really wants to use
DateTime::Astro::Sunrise instead, then IMO they should step up and
maintain it upstream before we re-introduce it into the archive: it's
not pkg-perl's mission to become the de facto upstream maintainer for
obsolete developer releases from 14 years ago.

I'll request the removal right away.

Cheers,
-- 
intrigeri

Bug#758124: Seconded, and non-normative updates

[Sean Whitton]

control: tag -1 +pending

On Tue, Aug 01, 2017 at 11:18:56PM +0200, Bill Allombert wrote:
> Please always quote what you are seconding. This avoid confusion.

Thanks for the tip, Bill.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#851988: nrpe-ng: Please implement the ssl_verify_server=0 option in check_nrpe_ng

[Chris Boot]

Control: tags -1 pending

On 20/01/17 10:43, John Lines wrote:
> Dear Maintainer,
> 
> nrpe_ng is particularly useful for people migrating from jessie to
> stretch, as it is available in jessie-backports, however if they have
> a large number of internal hosts to monitor, and not all of those
> hosts use puppet (or similar) then the ability to move from
> nagios-nrpe-server (which is stretch does not provide SSL) to
> nrpe-ng would be made simpler by a functioning ssl_verify_server=0
> option.

Hi John,

Apologies this didn't make it in time for the stretch release where it
would have been particularly useful. I have, however, now implemented
this as part of a bit of a rewrite of the check_nrpe_ng client code.

Hope this helps.

https://github.com/bootc/nrpe-ng/commit/347c7d20f83dd63f59fa6ea78a6e7852c12fe13b

Regards,
Chris

-- 
Chris Boot
Tiger Computing Ltd
"Linux for Business"

Tel: 01600 483 484
Web: http://www.tiger-computing.co.uk
Follow us on Facebook: http://www.facebook.com/TigerComputing

Registered in England. Company number: 3389961
Registered address: Wyastone Business Park,
 Wyastone Leys, Monmouth, NP25 3SR

Bug#870430: linux-image-4.9.0-3-marvell: Couldn't find DTB in /usr/lib/linux-image-4.9.0-3-marvell or /etc/flash-kernel/dtbs

[noone never]

Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: important
Dear Maintainer,

When I dist-upgrade my Sheevaplug from jessie to stretch, I get this error:
Couldn't find DTB  in /usr/lib/linux-image-4.9.0-3-marvell or 
/etc/flash-kernel/dtbs
The file /usr/lib/linux-image-4.9.0-3-marvell does exist in the filesystem.
 
Truncated log:
apt-get dist-upgrade
...
4 not fully installed or removed.
...
Setting up initramfs-tools (0.130) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-4.9.0-3-marvell (4.9.30-2+deb9u2) ...
/etc/kernel-img.conf:4: W: ignoring unknown parameter relative_links
/etc/kernel-img.conf:6: W: ignoring unknown parameter do_bootfloppy
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.9.0-3-marvell
/usr/share/flash-kernel/functions: line 155: warning: command substitution: 
ignored null byte in input
I: The initramfs will attempt to resume from /dev/sda3
I: (UUID=6fcd0aea-6301-4c47-a3fd-9f5eb2c1f8b5)
I: Set the RESUME variable to override this.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
/usr/share/flash-kernel/functions: line 155: warning: command substitution: 
ignored null byte in input
Using DTB: kirkwood-sheevaplug.dtb
Couldn't find DTB  in /usr/lib/linux-image-4.9.0-3-marvell or 
/etc/flash-kernel/dtbs
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.9.0-3-marvell (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-marvell:
 linux-image-marvell depends on linux-image-4.9.0-3-marvell; however:
  Package linux-image-4.9.0-3-marvell is not configured yet.

dpkg: error processing package linux-image-marvell (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-kirkwood:
 linux-image-kirkwood depends on linux-image-marvell; however:
  Package linux-image-marvell is not configured yet.
dpkg: error processing package linux-image-kirkwood (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-3-marvell
/usr/share/flash-kernel/functions: line 155: warning: command substitution: 
ignored null byte in input
I: The initramfs will attempt to resume from /dev/sda3
I: (UUID=6fcd0aea-6301-4c47-a3fd-9f5eb2c1f8b5)
I: Set the RESUME variable to override this.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
/usr/share/flash-kernel/functions: line 155: warning: command substitution: 
ignored null byte in input
Using DTB: kirkwood-sheevaplug.dtb
Couldn't find DTB  in /usr/lib/linux-image-4.9.0-3-marvell or 
/etc/flash-kernel/dtbs
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-4.9.0-3-marvell
 linux-image-marvell
 linux-image-kirkwood
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
 
 
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
Hardware: Marvell Kirkwood (Flattened Device Tree)
Revision: 
Device Tree model: Globalscale Technologies SheevaPlug
** PCI devices:
** USB devices:
Bus 001 Device 002: ID 1a4a:1670 Silicon Image 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (600, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 3.16.0-4-kirkwood
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages linux-image-4.9.0-3-marvell depends on:
ih  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5
Versions of packages linux-image-4.9.0-3-marvell recommends:
ii  firmware-linux-free  3.4
ii  u-boot-tools 2016.11+dfsg1-4
Versions of packages linux-image-4.9.0-3-marvell suggests:
pn  debian-kernel-handbook  
pn  linux-doc-4.9   
Versions of packages linux-image-4.9.0-3-marvell is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  

Bug#869966: stretch-pu: package gosa-plugin-mailaddress/0.99.5-2+deb9u1

[Mike Gabriel]

Hi Adam,

On  So 30 Jul 2017 23:49:13 CEST, Adam D. Barratt wrote:


Control: tags -1 + confirmed

On Fri, 2017-07-28 at 10:59 +0200, Mike Gabriel wrote:
Vincent Danjean spotted a flaw in gosa-plugin-mailaddress,  
recently, that relates to the

renaming of class constructor names as required with PHP 7.

The attached .debdiff fixes this issue for Debian stretch. Please  
accept the .debdiff as

a stretch-pu upload candidate.


+gosa-plugin-mailaddress (0.99.5-2+deb9u1) stretch-proposed-updates;  
urgency=medium


Ack. Package adapted this this.


The preferred changelog distribution is simply "stretch".

Please go ahead.


Uploaded just now.

Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpNp22JwDJKt.pgp
Description: Digitale PGP-Signatur

Bug#865308: khronos-api is not Multi-Arch compatible

[Jens Reyer]

Hi Mike

On 07/31/2017 05:11 AM, Michael Gilbert wrote:
> On Fri, Jul 21, 2017 at 3:03 PM, Jens Reyer wrote:
>> I just uploaded 0~svn33340-0.1 to delayed/10, debdiff attached.
>>
>> Changelog:
>>
>> khronos-api (0~svn33340-0.1) unstable; urgency=medium
>>
>>   * Non-maintainer upload.
>>   * New (and final in svn) upstream revision 33340.
>>   * Refresh timestamps.patch.
>>   * Make package Multi-Arch: foreign (closes: #865308).
>> Thanks to Hugh McMaster
>>   * Minor improvement to the package description (closes: #865307).
>>   * Bump standards version to 4.0.0, no changes needed.
>>   * Fix file exclusion in tarball generation.
> 
> Hi Jens,
> 
> This isn't really a great version, but ok it will land later today.
> It would be far better to update to upstream git, which is now in sync
> with the latest opengl 4.5 spec.

For the reasoning to do this intermediate version see my follow-up bug
#869233.  (btw, I'm quite busy atm, but luckily upstream Wine had a
patch for this just today, so they will do the initial testing.)


> By the way, NMUs are not supposed to touch maintainer fields like the
> standards version, but it's not a big deal.

I'm not sure about your intention here.

My goal is keeping the build-dependencies of Wine (especially
unicode-data and khronos-api) in fine shape.  Since I know that you
don't have much time I offered to add me as co-maintainer, and started
to work on the package in kind of an extension of pkg-wine.

The spirit of this upload was to fix uncritical things, while I opened
#869233 before doing eventually controversial things.  Not checking and
bumping the standards version would have felt wrong to me.

Maintainer fields aren't mentioned explicitly in policy 5.11, while
large parts of Debian take a very liberal stance at NMUs nowadays.  So
I'm really not sure about your intention here, and how/if to progress
with khronos-api: should I only work on khronos-api if there's a rc bug
and no sign of activity from your side?  Or how far can I go in helping
you here and do you want a specific workflow, e.g. bugs for every change
or a git repo?

So I'll postpone this until further notice from you.  I'd really
appreciate an answer to #869233.

Greets
jre

Bug#870145: ITP: localepurge

[Miguel Figueiredo]

I will try to update the package.

BR,

Miguel

Bug#870429: timidity: defaults to too-bad-to-live freepats

[Adam Borowski]

Package: timidity
Version: 2.13.2-40.5
Severity: normal

Hi!
The default sound font timidity pulls in and configures by default,
freepats, is of abysmal quality and so incomplete I can't recall the last
real-world .mid file I've seen that doesn't lack at least one instrument.

In the past, freepats used to be the only free sound font.  This is long
untrue, as we have:

 34MB   freepats
149MB   fluid-soundfont-gm
  3.3MB fluid-soundfont-gs
  5.4MB timgm6mb-soundfont

I'm personally using the last, timgm6mb-soundfont, and it works without a
hitch.

Thus, could you please ship a configuration that works out of the box?


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.13.0-rc3-debug-00051-g286e6722ee26 (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 timidity depends on:
ii  libasound21.1.3-5
ii  libaudio2 1.9.4-5+b1
ii  libc6 2.24-13
ii  libesd0   0.2.41-11+b2
ii  libflac8  1.3.2-1
ii  libice6   2:1.0.9-2
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-5
ii  libncurses5   6.0+20170715-2
ii  libogg0   1.3.2-1+b1
ii  libpng16-16   1.6.30-2
ii  libsm62:1.2.2-1+b3
ii  libtinfo5 6.0+20170715-2
ii  libvorbis0a   1.3.5-4
ii  libvorbisenc2 1.3.5-4
ii  libx11-6  2:1.6.4-3
ii  libxaw7   2:1.0.13-1+b2
ii  libxext6  2:1.3.3-1+b2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  lsb-base  9.20161125
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages timidity recommends:
pn  freepats 
pn  timidity-daemon  

Versions of packages timidity suggests:
pn  fluid-soundfont-gm  
pn  fluid-soundfont-gs  
pn  pmidi   

-- Configuration Files:
/etc/timidity/timidity.cfg changed:
source /etc/timidity/timgm6mb.cfg


-- no debconf information

Bug#869070: apt-listbugs does not honor Acquire::http::TimeOut

[Francesco Poli]

Control: tags -1 - moreinfo
Control: tags -1 + help


On Tue, 1 Aug 2017 10:34:00 +0200 Vincent Lefevre wrote:

> On 2017-08-01 10:24:13 +0200, Vincent Lefevre wrote:
> > This solves the timeout issue, but actually the bug is worse than
> > I thought. After setting
> > 
> > @drv.options["protocol.http.connect_timeout"] = 10
> > @drv.options["protocol.http.send_timeout"] = 10
> > @drv.options["protocol.http.receive_timeout"] = 10
> > 
> > I get:
> > 
> > Retrieving bug reports... 0% Fail
> > Error retrieving bug reports from the server with the following error 
> > message:
> > E: execution expired
> > It could be because your network is down, or because of broken proxy 
> > servers, or the BTS server itself is down. Check network configuration and 
> > try again
> > Retry downloading bug information? [Y/n] 
> > 
> > i.e. it doesn't fallback to the IPv4 address, contrary to what
> > other tools do!
> 
> Well, without the above change, I get the usual 2-minute timeout
> per IP address, and the fallback to the first IP address that works
> (here, IPv4). I assume that this is because the timeout occurs at
> the socket level instead of the protocol level, thus not handled
> by the same code.

Then the situation is less easy than I was hoping...

My huge ignorance about http support in Ruby is quite an impediment
here: I will have to study some aspects and/or seek help from more
knowledgeable people.
Please bear with me: the feature you are requesting could require more
time than we thought.   :-(


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpfWhb7HFzN4.pgp
Description: PGP signature

Bug#870428: libverto1: Upstream has moved

[Robbie Harwood]

Package: libverto1
Version: 0.2.4-2.1
Severity: normal

Dear Maintainer,

Since Fedorahosted isn't around anymore, we've moved the libverto upstream to
https://github.com/latchset/libverto .

I also notice that the Debian package is 0.2.4 while we have released 0.2.6
upstream.  I am happy to help with maintaining this package if it would be
helpful to you.

Thanks,
--Robbie

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

Kernel: Linux 4.12.0-trunk-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: sysvinit (via /sbin/init)

Versions of packages libverto1 depends on:
ii  libc62.24-12
ii  libverto-glib1   0.2.4-2.1
ii  libverto-libev1  0.2.4-2.1

libverto1 recommends no packages.

libverto1 suggests no packages.

-- no debconf information

Bug#758124: Seconded, and non-normative updates

[Bill Allombert]

On Tue, Aug 01, 2017 at 04:23:05PM -0400, Sean Whitton wrote:
> Hello,
> 
> I second Charles' patch.

Please always quote what you are seconding. This avoid confusion.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#859867: [buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

[Michael Stapelberg]

Alright! Patch attached and provided inline, for your convenience:

>From b29b1faf6bafb4b6e51b4e99d0febc81abbb543c Mon Sep 17 00:00:00 2001
From: Michael Stapelberg 
Date: Tue, 1 Aug 2017 23:13:36 +0200
Subject: [PATCH] add sbuild-debian-developer-setup package

---
 bin/Makefile.am  |  1 +
 bin/sbuild-debian-developer-setup| 49

 debian/control   | 16 +
 debian/sbuild-debian-developer-setup.install |  1 +
 4 files changed, 67 insertions(+)
 create mode 100755 bin/sbuild-debian-developer-setup
 create mode 100644 debian/sbuild-debian-developer-setup.install

diff --git a/bin/Makefile.am b/bin/Makefile.am
index 138fc0b3..0fcbda09 100644
--- a/bin/Makefile.am
+++ b/bin/Makefile.am
@@ -28,6 +28,7 @@ bin_SCRIPTS = \
  sbuild-abort \
  sbuild-apt \
  sbuild-checkpackages \
+ sbuild-debian-developer-setup   \
  sbuild-update \
  sbuild-upgrade \
  sbuild-distupgrade \
diff --git a/bin/sbuild-debian-developer-setup
b/bin/sbuild-debian-developer-setup
new file mode 100755
index ..82341d28
--- /dev/null
+++ b/bin/sbuild-debian-developer-setup
@@ -0,0 +1,49 @@
+#!/usr/bin/perl
+#
+# Set up sbuild so that packages for Debian unstable can be built and
+# maintenance is done automatically via a daily update cronjob.
+# Copyright © 2017 Michael Stapelberg .
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+# General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see
+# .
+#
+###
+
+use strict;
+use warnings;
+use autodie qw(:all);
+use v5.10;
+
+if (!defined($ENV{SUDO_USER})) {
+die "Please run sudo $0";
+}
+
+system("adduser", "--quiet", "--", $ENV{SUDO_USER}, "sbuild");
+
+chomp(my $arch = `dpkg --print-architecture`);
+
+system("sbuild-createchroot",
+   "--command-prefix=eatmydata",
+   "--include=eatmydata",
+   "--alias=UNRELEASED",
+   "--alias=sid",
+   "unstable",
+   "/srv/chroot/unstable-$arch-sbuild",
+   "http://localhost:3142/deb.debian.org/debian;);
+
+open(my $fh, ">", "/etc/cron.d/sbuild-debian-developer-setup-update-all");
+say $fh q|@daily root /usr/share/doc/sbuild/examples/sbuild-update-all|;
+close($fh);
+
+say "Now run `newgrp sbuild', or log out and log in again.";
diff --git a/debian/control b/debian/control
index 7249e630..7b4bd21b 100644
--- a/debian/control
+++ b/debian/control
@@ -75,6 +75,22 @@ Description: Tool for building Debian binary packages
from Debian sources
  build-essential packages, plus those in the package build
  dependencies.

+Package: sbuild-debian-developer-setup
+Architecture: all
+Depends: sbuild,
+ apt-cacher-ng,
+ lintian,
+ ${misc:Depends},
+ ${perl:Depends},
+ ${shlibs:Depends}
+Description: Convenience script to set up an sbuild environment for Debian
Developers
+ Run "sudo sbuild-debian-developer-setup" to add the current user to the
sbuild
+ group, create an schroot for building packages for Debian unstable, and
create
+ a cronjob which updates said schroot daily.
+ .
+ This script assumes you are on an un-metered internet connection (daily
schroot
+ updates might be costly otherwise).
+
 Package: buildd
 Architecture: all
 Depends: adduser,
diff --git a/debian/sbuild-debian-developer-setup.install
b/debian/sbuild-debian-developer-setup.install
new file mode 100644
index ..406b3af9
--- /dev/null
+++ b/debian/sbuild-debian-developer-setup.install
@@ -0,0 +1 @@
+usr/bin/sbuild-debian-developer-setup
-- 
2.13.2


On Tue, Aug 1, 2017 at 11:05 AM, Johannes Schauer  wrote:

> Quoting Michael Stapelberg (2017-08-01 11:04:16)
> > That works for me :).
> >
> > How shall we proceed? Should I prepare a patch against the sbuild
> package?
>
> Yes please!
>
> Put the patch into this bug and then we can talk about it. :)
>



-- 
Best regards,
Michael
From b29b1faf6bafb4b6e51b4e99d0febc81abbb543c Mon Sep 17 00:00:00 2001
From: Michael Stapelberg 
Date: Tue, 1 Aug 2017 23:13:36 +0200
Subject: [PATCH] add sbuild-debian-developer-setup package

---
 bin/Makefile.am  |  1 +
 bin/sbuild-debian-developer-setup| 49 
 debian/control   | 16 +
 debian/sbuild-debian-developer-setup.install |  1 +
 4 files changed, 67 

Bug#827770: wine-development: FTBFS in Ubuntu

[Jens Reyer]

On 07/26/2017 11:05 AM, Gianfranco Costamagna wrote:
> control: reopen -1
> control: tags -1 patch
> 
>> No, they get to deal with the problems they create for themselves.
> 
> while this is true in general, in this particular case this is a problem in 
> Debian too, when different versions of
> the same libraries might coexist in Debian too.
> 
> Fortunately the new approach patch seems sane and applicable directly in 
> Debian too
> 
> diff -Nru wine-development-2.13/debian/scripts/sonames2elf 
> wine-development-2.13/debian/scripts/sonames2elf
> --- wine-development-2.13/debian/scripts/sonames2elf2017-07-22 
> 17:17:47.0 +0200
> +++ wine-development-2.13/debian/scripts/sonames2elf2017-07-23 
> 00:25:08.0 +0200
> @@ -34,7 +34,10 @@
>  fi
>  tmpdir=$(mktemp -d -t sonames2elf.XX)
>  cd "$tmpdir"
> -printf 'INPUT(%s)\n' "$@" > libeverything.so
> +# Use the unversioned solink because the soname might be not found.
> +# solink always points to the default soname, which is what wine uses.
> +SOLINKS="$(echo $@ | sed "s|\([[:alnum:]]*\.so\)[\.[0-9]*]*|\1|g")"
> +printf 'INPUT(%s)\n' "$SOLINKS" > libeverything.so
>  gcc -shared -Wl,--no-as-needed -L. -leverything -o elf
>  cat elf
>  rm -rf "$tmpdir"
> 
> what do you think about?

Having written that patch, I totally agree and suggest to add it.

Bug#785480: Expanding interest in bcg729

[Jaap Keuter]

Hi,

Recent developments in Wireshark have seen this library being used in RTP stream
decoding. It would be appreciated by many users of Wireshark on Debian (and
derivatives) when this would be available for the Debian build of Wireshark.

Thanks,
Jaap

Bug#870427: lxinput: no way to adjust mouse wheel scroll speed

[Mark Hedges]

Package: lxinput
Version: 0.3.5-1
Severity: wishlist

LXDE menu > Preferences > Keyboard and Mouse

Cannot adjust mouse wheel scroll speed.

It's pretty slow.  Not unuseable, but slow.  It would be nice.

Thanks.

Mark



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=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 lxinput depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libx11-6 2:1.6.4-3

lxinput recommends no packages.

Versions of packages lxinput suggests:
ii  lxsession  0.5.3-2

-- no debconf information

Bug#870426: cython: Break build dependency cycle with python-numpy

[Daniel Schepler]

Source: cython
Version: 0.25.2-2
Severity: wishlist

Currently, src:cython and src:python-numpy both have Build-Depends on
each other which makes it difficult to bootstrap those packages.  It
would be nice if one or the other could provide a build profile to
break this cycle.

The cython source package successfully builds if I drop the build
dependencies on python-numpy, python3-numpy, and gdb and then build
with DEB_BUILD_OPTIONS=nocheck.  However, I don't really know enough
about the package to tell whether the resulting binary packages are
unchanged.  If so, then it should be enough just to update
debian/control with something like:

Build-Depends: debhelper (>= 7.0.50~), dpkg-dev (>= 1.16.1~),
python-all-dev (>= 2.6.6-3~), python-all-dbg, help2man (>= 1.37.1~),
python-sphinx, python-numpy , python3-all-dev,
python3-all-dbg, python3-numpy , gdb 

Otherwise, the results might still be useful for bootstrapping; but
then you would need to have it produce renamed packages like
cython-stage1, and then update other source packages involved in
cycles to be able to build using that.
-- 
Daniel Schepler

Bug#758124: Seconded

[David Bremner]

On Tue, Aug 01, 2017 at 04:23:05PM -0400, Sean Whitton wrote:
> Hello,
> 
> I second Charles' patch.
> 
> I'll note that as a policy delegate I'll make the following
> purely informative changes to the patch once committed:
> 
> - don't qualify with dpkg version number since it is older than the
>   version in oldstable
> 
> - move the text out of  tags since we're trying to reduce the
>   number of footnotes in Policy.
> 
> -- 
> Sean Whitton

Seconded

David Bremner


signature.asc
Description: PGP signature

Bug#806544: libical-parser-sax-perl: FTBFS: t/01parse.t failure

[Jonas Smedegaard]

Quoting intrigeri (2017-08-01 16:38:06)
> Hi Jonas,
> 
> Niko Tyni (28 Nov 2015):
> > Package: libical-parser-sax-perl
> > Version: 1.09-3
> > Severity: serious
> > Tags: sid
> > Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=109258
> 
> > This package fails to build on current sid/amd64.
> 
> For the record:
> 
>  * I've just reproduced this issue on current sid/amd64.
>  * I have proposed a year ago [1] to remove this package.
>  * It was not shipped in Stretch due to this bug report.
>  * This package has one single reverse-dependency
>(libical-parser-html-perl) that itself is a leaf package.
> 
> [1] https://lists.debian.org/debian-perl/2016/06/msg00038.html
> 
> > [rt.cpan.org #109258] blames DateTime-Event-Recurrence-0.18
> > and DateTime-Set-0.3600. The above timeline indeed matches
> > libdatetime-event-recurrence-perl_0.18-1.
> 
> Since then upstream did not reply.
> 
> With all this in mind, I'm very much tempted to go ahead and request
> the removal of this package + its reverse-dependency from sid, unless
> someone is interested enough in this package to work on a fix (that
> might be in DateTime-Event-Recurrence or elsewhere).
> 
> Jonas, what do you think?

Please request removal - also of the reverse dependency.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#869680: u-boot-tools: fw_setenv fails with MTD erase error

[Vagrant Cascadian]

Control: tags 869680 moreinfo

On 2017-07-25, John Forecast wrote:
> /etc/fw_env.config was not present so I copied
> /usr/share/doc/u-boot-tools/examples/linkstation_pro_live.config to
> /etc/fw_env.config. This allowed me to see the current environment variables
> with fw_printenv but any attempt to modify an environment variable with
> fw_setenv generated the error:
>
> MTD erase error on /dev/mtd2: Invalid argument
> Error: can't write fw_env to flash
>
> /etc/fw_env.config contained a single entry:
>
> /dev/mtd2 0x3F000 0x1000 0x1000

It looks like the linkstation mini currently has the same config...


> This was similar to the entry I had seen in Jessie except that there was only
> a single device for all 3 regions. I changed the offset to 0x0:
>
> /dev/mtd2 0x0 0x1000 0x1000

I don't have this device, so it's a bit hard to verify on my end. It may
be possible that mainline u-boot and vendor-supplied u-boot require
different settings, in which case I'd like to at least document both
settings, if someone can confirm what the various values were and in
which cases they apply, that would be helpful.

The Debian packages do not currently build the "lsxhl" target, which
appears to be the appropriate mainline target for this board, but in
mainline u-boot, include/configs/lsxhl.h has:

  #define CONFIG_ENV_SIZE 0x1 /* 64k */
  #define CONFIG_ENV_OFFSET   0x7 /* env starts here */


I guess I can add both, leaving both commented, but I'd like to know in
what contexts which values are appropriate, so that we can include
useful comments.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#870334: pkg-perl-autopkgtest: revisiting smoke prove --recurse

[gregor herrmann]

On Tue, 01 Aug 2017 19:58:55 +0300, Niko Tyni wrote:

> Hm. I agree the goal is to get the same list of tests that are run at
> build time. 

I don't agree 100% I think.
From what I've seen so far when looking at a dozen of the failures we
have:
- same tests in autopkgtest as during build, which fail because of
  paths or missing files; so just the usual stuff but it appears only
  now for t/**/*.t;
- more tests in autopkgtest than during build but perfectly
  reasonable tests where it looks more like an issue that they are
  not run during build (and the typical easy-to-fix-failures);
- and then the group where something weird is in t/ which happens to
  look like a test but is a data file or a (misplaced and not
  environment-variable-protected) author test etc.
  Which is somewhat a case for #870252

> Alternatively, if we're running Makefile.PL anyway (I'm ignoring M::B
> for the moment), this might all be solved if we could just force run
> 'make test' without actually building first. The tests would get run
> with blib/lib etc. in @INC but if those were empty the installed files
> would presumably get used anyway. Unfortunately make doesn't seem to be
> too helpful with this...

Hm, we could also "make" the distribution and rm blib/ before "make
test". Doesn't feel very clean though ...
 
> One more wild idea I had is to patch the build machinery (probably EU::MM
> itself) to record the list of tests it runs in a file. We could then
> install that file in the binary package during the build, and look
> there in the autopkgtest phase. This does feel somewhat intrusive,
> just mentioning it for completeness :)

We had similar ideas as well :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#824839: librrd-simple-perl: FTBFS on armhf and arm64: t/23graph.t failures

[intrigeri]

Hi Russ!

You did the initial upload of librrd-simple-perl to Debian back in
2013, so I'm seeking your opinion wrt. removing it from sid as part of
the pkg-perl ongoing effort towards removing the most hopeless of our
RC-buggy packages.

Summary:

 * This package was not shipped in Stretch due to this bug.

 * On https://rt.cpan.org/Public/Bug/Display.html?id=78785 you've
   attached a patch that fixed the problem on x86_64, but sadly it
   doesn't fix it on armhf and arm64.

 * This is a leaf package and popcon is fairly low:
   Inst = 43, Vote = 5.

Are you interested in working further on this problem?

Would you mind if we removed this package from sid?

Cheers,
-- 
intrigeri

Bug#797289: libxml-easyobj-perl: FTBFS: Can't locate object method "getXMLDecl" via package "XML::DOM::Element"

[intrigeri]

Niko Tyni:
> There's been no reaction on the upstream bug, and the last upstream
> release was in 2002. There are no reverse dependencies. I suggest
> removal unless somebody objects?

Requested: https://bugs.debian.org/870424

Bug#870409: webkit2gtk: FTBFS on hppa - WebKitEnumTypes.h:27:0: error: unterminated #ifndef

[John David Anglin]

On 2017-08-01, at 3:11 PM, Alberto Garcia wrote:

> On Tue, Aug 01, 2017 at 08:52:54PM +0200, Alberto Garcia wrote:
> 
>> What I don't get is what that has to do with the missing #endif in
>> the WebKitEnumTypes.h file.
> 
> I saw the problem, there's a non-ascii character in WebKitWebContext.h
> and glib-mkenums fails if the locale is POSIX:

Good catch!

--
John David Anglin   dave.ang...@bell.net

Bug#836004: python-gflags: please make the build reproducible

[Chris Lamb]

tags 836004 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/python-modules/packages/python-gflags/commit/?id=c4259f521483460aa1d37ba066ceb104e352febf


Regards,

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

Bug#806544: libical-parser-sax-perl: FTBFS: t/01parse.t failure

[intrigeri]

Hi Jonas,

Niko Tyni (28 Nov 2015):
> Package: libical-parser-sax-perl
> Version: 1.09-3
> Severity: serious
> Tags: sid
> Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=109258

> This package fails to build on current sid/amd64.

For the record:

 * I've just reproduced this issue on current sid/amd64.
 * I have proposed a year ago [1] to remove this package.
 * It was not shipped in Stretch due to this bug report.
 * This package has one single reverse-dependency
   (libical-parser-html-perl) that itself is a leaf package.

[1] https://lists.debian.org/debian-perl/2016/06/msg00038.html

> [rt.cpan.org #109258] blames DateTime-Event-Recurrence-0.18
> and DateTime-Set-0.3600. The above timeline indeed matches
> libdatetime-event-recurrence-perl_0.18-1.

Since then upstream did not reply.

With all this in mind, I'm very much tempted to go ahead and request
the removal of this package + its reverse-dependency from sid, unless
someone is interested enough in this package to work on a fix (that
might be in DateTime-Event-Recurrence or elsewhere).

Jonas, what do you think?

Cheers,
-- 
intrigeri

Bug#870398: sks: non-deterministically FTBFS with "Error: Unbound module Bdb"

[Stéphane Glondu]

On 01/08/2017 20:15, Stéphane Glondu wrote:
>> Take a look at the buildd results for 1.1.6-5 and 1.1.6-6:
>>
>> https://buildd.debian.org/status/logs.php?pkg=sks=1.1.6-5=sid
>> https://buildd.debian.org/status/logs.php?pkg=sks=1.1.6-6=sid
>>
>> in 1.1.6-5, mips, mipsel, and sh4 all fail with:
>>
>> -
>> File "bdbwrap.mli", line 4, characters 13-22:
>> Error: Unbound module Bdb
>> Makefile:360: recipe for target 'bdbwrap.cmi' failed
>> make[2]: *** [bdbwrap.cmi] Error 2
>> make[2]: *** Waiting for unfinished jobs
>> -
>>
>> (but armel and i386 build OK)
>>
>> While with 1.1.6-6, we see the same failures on armel and i386 (but not on 
>> mips!)
>>
>> There should have been no change with the ocaml Bdb bindings between
>> these different builds.
>>
>> I suspect something weird is happening with ocaml, but i'm not sure
>> what steps to take for debugging, so i'm flagging this as "help" -- if
>> the OCaml maintainers have any suggestions, i'm all ears.
> 
> It looks like the build process is not parallel-safe. Try running dh
> with --no-parallel.

Indeed, bdbwrap.cmi depends on bdb/bdb.cmi, but this dependency cannot
be inferred given the way the build system is designed. I would suggest
to just disable parallel build.

Cheers,

-- 
Stéphane

Bug#778419: fedmsg: please make the build reproducible

[Chris Lamb]

tags 778419 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/python-modules/packages/fedmsg/commit/?id=a6bac54783fabe56b6b95bef33c85aa789db4989

Not uploading due to other bugs.


Regards,

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

Bug#758124: Seconded, and non-normative updates

[Sean Whitton]

Hello,

I second Charles' patch.

I'll note that as a policy delegate I'll make the following
purely informative changes to the patch once committed:

- don't qualify with dpkg version number since it is older than the
  version in oldstable

- move the text out of  tags since we're trying to reduce the
  number of footnotes in Policy.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#870424: RM: libxml-easyobj-perl -- ROM; FTBFS, inactive upstream

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

this package is RC-buggy (FTBFS) and upstream doesn't seem to be
interested in fixing it, so we (pkg-perl) would like to remove it.

References:
https://bugs.debian.org/797289
https://rt.cpan.org/Public/Bug/Display.html?id=108867
https://lists.debian.org/debian-perl/2016/06/msg00038.html

Cheers,
-- 
intrigeri

Bug#868255: openjdk-9: Please build with --with-debug-level=slowdebug on Zero-only architectures

[John Paul Adrian Glaubitz]

On 08/01/2017 10:03 PM, John Paul Adrian Glaubitz wrote:
> This patch fixes the build for me. Could you get it merged upstream?

Hmm, wait a second. I just had the JVM lock up. Will do a clean build
to re-test.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#868255: openjdk-9: Please build with --with-debug-level=slowdebug on Zero-only architectures

[John Paul Adrian Glaubitz]

Hi Andrew!

On 08/01/2017 02:57 PM, Andrew Haley wrote:
> The second one is more subtle.  Zero is so called because it uses zero
> assembly language, but this is not quite true: there is a tiny bit of
> assembly language, and it is wrong.  Here is the PPC32 definition of
> atomic_copy64.  It uses a floating-point register to copy a 64-bit
> doubleword atomically:
> 
>   // Atomically copy 64 bits of data
>   static void atomic_copy64(volatile void *src, volatile void *dst) {
> #if defined(PPC32) && !defined(__NO_FPRS__)
> double tmp;
> asm volatile ("lfd  %0, 0(%1)\n"
>   "stfd %0, 0(%2)\n"
>   : "=f"(tmp)
>   : "b"(src), "b"(dst));
> 
> The eagle-eyed among you might have noticed the bug: this asm has no
> memory effect.  It has no memory inputs, no memory outputs, and no
> memory clobber.  So, as far as GCC is concerned atomic_copy64 does not
> touch memory at all, and there is no need to store the source operand
> into memory.  For all GCC knows, the asm might just be doing some
> arithmetic on the pointers.  We need a better definition of
> atomic_copy64, and this is mine:
> 
>   // Atomically copy 64 bits of data
> static void atomic_copy64(volatile void *src, volatile void *dst) {
> #if defined(PPC32) && !defined(__NO_FPRS__)
> double tmp;
> asm volatile ("lfd  %0, %2\n"
>   "stfd %0, %1\n"
>   : "="(tmp), "=Q"(*(volatile double*)dst)
>   : "Q"(*(volatile double*)src));
> 
> Note that we dereference src and dst and pass the actual memory
> operands to the asm, not just pointers to them.
This patch fixes the build for me. Could you get it merged upstream?

I assume it will go into the jdk10 branch because jdk9 isn't taking
any particular fixes at the moment. Am I correct?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#485776: debian-policy: Adding graphical flowcharts for maintainer scripts invocation would help understand the process

[Sean Whitton]

On Tue, Aug 01, 2017 at 04:55:33PM +0100, Ian Jackson wrote:
> We should surely import the diagrams as-is.

Russ -- you were the one that suggested generating them.  What do you
think about importing them as-is now?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#870422: libgnome2-gconf-perl: Remove libgnome2-gconf-perl during the Buster cycle

[intrigeri]

Package: libgnome2-gconf-perl
Severity: normal
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
Control: blocked -1 by 870418
Control: blocked -1 by 870413

Yet another bug about removing pkg-perl packages that depend on
obsolete GNOME 2 technologies.

Bug#870423: libgnome2-wnck-perl: Remove libgnome2-wnck-perl during the Buster cycle

[intrigeri]

Package: libgnome2-wnck-perl
Severity: normal
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
Control: blocked -1 by 870417
Control: blocked -1 by 870418

Yet another tracking bug about removing pkg-perl packages that depend on
obsolete GNOME 2 technologies.

Bug#870421: libgnome2-canvas-perl: Remove libgnome2-canvas-perl during the Buster cycle

[intrigeri]

Package: libgnome2-canvas-perl
Severity: normal
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal

Yet another blocking bug about removing pkg-perl packages that depend on
obsolete GNOME 2 technologies.

Bug#842706: solr-jetty: packaged version is ancient

[Emmanuel Bourg]

Le 1/08/2017 à 04:48, Simon Ruggier a écrit :
> I made an attempt to package a newer version of Solr last December, but
> it got bogged down by a combination of missing dependencies and problems
> related to Maven that I wasn't able to troubleshoot with my limited Java
> packaging experience.

Hi Simon,

What Maven and dependencies issues did you get? I might be able to help.

Emmanuel Bourg

Bug#870420: tumbler is not built from source

[Helmut Grohne]

Source: tumbler
Version: 0.1.32-1
User: helm...@debian.org
Usertags: rebootstrap

Hi,

I tried reporting a cross build bug against tumbler with a patch, but I
noticed that my patch was ineffective, because tumbler is not built from
source. Updating acinclude.m4 does not affect the build, because it
doesn't autoreconf. For doing autoreconf one needs an additional build
dependency on gtk-doc-tools. Then autoreconf succeeds, but the configure
fails, because XDT_I18N is not interpolated. I gave up here.

Please make it possible to build configure from source. Preferably
rebuild it as part of the package build.

Thanks

Helmut

Bug#868395: libgnome2-perl: Please drop the (build-)dependency against gnome-vfs

[intrigeri]

Hi,

I've now filed blocking bugs for all the bits that prevent us
(pkg-perl) from removing libgnome2-perl + libgnome2-vfs-perl, and in
turn prevent pkg-gnome from removing gnome-vfs.

For the record I'm now going to look into removing *all*
libgnome2-*perl packages, ideally during the Buster cycle: at first
glance most of them are depending on other GNOME technologies that
have been obsoleted a while ago too, and that are not maintained
upstream anymore. I don't feel comfortable shipping such stuff to
our users.

I'll track this effort with
usertags and "blocked by" relationships:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=gnome2-removal=pkg-perl-maintainers%40lists.alioth.debian.org

Cheers,
-- 
intrigeri

Bug#870204: RFS: openfst/1.6.3-1 -- weighted finite-state transducers library

[Jakub Wilk]

* Giulio Paci , 2017-07-31, 00:19:

Dear Jakub,

I am looking for a sponsor for my package "openfst".


Don't count on me. Sorry!

--
Jakub Wilk

Bug#869241: python-libnacl FTBFS: Illegal instruction

[Adrian Bunk]

Control: reassign -1 python-libnacl 1.5.2-1
Control: retitle -1 python-libnacl test unconditionally uses aes instruction

On Tue, Aug 01, 2017 at 06:23:19PM +0200, Andreas Beckmann wrote:
> Followup-For: Bug #869241
> Control: reassign -1 libsodium18 1.0.12-1
> Control: affects -1 + src:python-libnacl
> Control: retitle -1 'libsodium18: unconditionally uses aes instructions'
> 
> Anything beyond the default instruction set may only be used after
> runtime cpu feature detection, and there must be a fallback in case
> the cpu does not support some extension.
>...

libsodium does provide runtime feture detection through 
crypto_aead_aes256gcm_is_available(), the bug is that
python-nacl does not use it when calling this code in
a unit test.

> Andreas

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#859844: vmtk: diff for NMU version 1.3+dfsg-2.2

[Adrian Bunk]

Control: tags 859844 + patch
Control: tags 859844 + pending

[Replace XX with correct value] Dear maintainer,

I've prepared an NMU for vmtk (versioned as 1.3+dfsg-2.2) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

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

diff -Nru vmtk-1.3+dfsg/debian/changelog vmtk-1.3+dfsg/debian/changelog
--- vmtk-1.3+dfsg/debian/changelog	2017-01-18 23:36:18.0 +0200
+++ vmtk-1.3+dfsg/debian/changelog	2017-08-01 19:06:28.0 +0300
@@ -1,3 +1,10 @@
+vmtk (1.3+dfsg-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS by using OpenSSL 1.1. (Closes: #859844)
+
+ -- Adrian Bunk   Tue, 01 Aug 2017 19:06:28 +0300
+
 vmtk (1.3+dfsg-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru vmtk-1.3+dfsg/debian/control vmtk-1.3+dfsg/debian/control
--- vmtk-1.3+dfsg/debian/control	2017-01-18 23:36:13.0 +0200
+++ vmtk-1.3+dfsg/debian/control	2017-08-01 19:06:20.0 +0300
@@ -19,7 +19,7 @@
libexpat1-dev,
uuid-dev,
libvtkgdcm2-dev,
-   libssl1.0-dev | libssl-dev (<< 1.1.0~),
+   libssl-dev,
libvtk6-qt-dev,
libvtk6-java,
libfftw3-dev

Bug#870419: valgrind: --xml-socket is broken

[Orgad Shaneh]

Package: valgrind
Version: 1:3.13.0-1
Severity: important
Tags: patch upstream

Dear Maintainer,

I filed a bug upstream: https://bugs.kde.org/show_bug.cgi?id=382998

The easiest way to reproduce is:

$ nc -l -p 2 &
[1] 2811
$ valgrind --xml-socket=127.0.0.1:2 --xml=yes true 
valgrind: Bad option: --xml=yes, but no XML destination specified
valgrind: --xml=yes has been specified, but there is no XML output
valgrind: destination.  You must specify an XML output destination
valgrind: using --xml-fd, --xml-file or --xml-socket.
valgrind: Use --help for more information or consult the user manual.
[1]+  Donenc -l -p 2

valgrind does connect to the socket, but closes it immediately (netcat quits 
after valgrind is executed).

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

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

Versions of packages valgrind depends on:
ii  libc6  2.24-13
ii  libc6-dbg  2.24-13

Versions of packages valgrind recommends:
ii  gdb   7.12-6
pn  valgrind-dbg  

Versions of packages valgrind suggests:
pn  alleyoop  
ii  kcachegrind   4:16.08.3-1
pn  valgrind-mpi  
ii  valkyrie  2.0.0-1+b1

-- no debconf information

Patch follows.

>From f1d5f6cc6a76170812f656dfc913baa80e92fd33 Mon Sep 17 00:00:00 2001
From: Orgad Shaneh 
Date: Tue, 1 Aug 2017 22:19:55 +0300
Subject: [PATCH] Fix parsing of --xml-socket argument

The socket was assigned to log_fd due to copy-paste error.
Then valgrind complained that --xml=yes is enabled, but no
file, fd or socket is given.

https://bugs.kde.org/show_bug.cgi?id=382998
---
 coregrind/m_libcprint.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/coregrind/m_libcprint.c b/coregrind/m_libcprint.c
index d66c67d..f6ba202 100644
--- a/coregrind/m_libcprint.c
+++ b/coregrind/m_libcprint.c
@@ -526,7 +526,7 @@ void VG_(init_log_xml_sinks)(VgLogTo log_to, VgLogTo xml_to,
  break;
 
   case VgLogTo_Socket:
- log_fd = prepare_sink_socket(VG_(clo_xml_fname_unexpanded),
+ xml_fd = prepare_sink_socket(VG_(clo_xml_fname_unexpanded),
   _(xml_output_sink), True);
  break;
}
-- 
2.13.3
>From f1d5f6cc6a76170812f656dfc913baa80e92fd33 Mon Sep 17 00:00:00 2001
From: Orgad Shaneh 
Date: Tue, 1 Aug 2017 22:19:55 +0300
Subject: [PATCH] Fix parsing of --xml-socket argument

The socket was assigned to log_fd due to copy-paste error.
Then valgrind complained that --xml=yes is enabled, but no
file, fd or socket is given.

https://bugs.kde.org/show_bug.cgi?id=382998
---
 coregrind/m_libcprint.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/coregrind/m_libcprint.c b/coregrind/m_libcprint.c
index d66c67d..f6ba202 100644
--- a/coregrind/m_libcprint.c
+++ b/coregrind/m_libcprint.c
@@ -526,7 +526,7 @@ void VG_(init_log_xml_sinks)(VgLogTo log_to, VgLogTo xml_to,
  break;
 
   case VgLogTo_Socket:
- log_fd = prepare_sink_socket(VG_(clo_xml_fname_unexpanded),
+ xml_fd = prepare_sink_socket(VG_(clo_xml_fname_unexpanded),
   _(xml_output_sink), True);
  break;
}
-- 
2.13.3

Bug#870418: shutter: Depends on obsolete libgnome2-vfs-perl that will go away during the Buster cycle

[intrigeri]

Package: shutter
Severity: important
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
X-Debbugs-Cc: ChangZhuo Chen (陳昌倬) , Dominique Dumont 


Hi,

as said on July 20
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868398#15),
this package is one of the very few blockers that currently prevent us
from removing the obsolete libgnome2-perl and libgnome2-vfs-perl from
the archive.

Can I proceed and request the removal of this package from
the archive? Or has someone a plan to remove this dependency during
the Buster cycle?

I'm explicitly adding the people who've worked on this package this
most recently into the loop as they might have a plan or opinions.

Context: ideally I would like to sort this out during DebCamp, so
a quick answer would be appreciated. But of course I understand if you
can't react this fast :)

Cheers,
-- 
intrigeri

Bug#870417: perlpanel: Depends on obsolete libgnome2-vfs-perl that will go away during the Buster cycle

[intrigeri]

Package: perlpanel
Severity: important
X-Debbugs-Cc: Adrian Bunk 

Hi QA,

this package is one of the very few blockers that currently prevent us
from removing the obsolete libgnome2-*perl from the archive.

The version in the archive is a CVS (!) snapshot from 2005 and popcon
is fairly low (inst:74, vote: 14). It's been orphaned back in March
and is now maintained by the Debian QA group. Adrian (Cc'ed) uploaded
it in June.

Can I proceed and request the removal of perlpanel from the archive,
or is anyone interested to remove this obsolete dependency during the
Buster cycle?

Context: ideally I would like to sort this out during DebCamp, so
a quick answer would be appreciated. But of course I understand if you
can't react this fast :)

For background information, see #868398.

Cheers,
-- 
intrigeri