Bug#901553: [apt-transport-s3] missing changelog for URL format change

[Tim Sattarov]

Package: apt-transport-s3
Version: 1.3.0-1
Severity: normal

--- Please enter the report below this line. ---
I see the issue about URL schema change 
https://github.com/BashtonLtd/apt-transport-s3/issues/33
But I do not see this major change reflected anywhere in the package 
changelogs: not in
changelog.Debian.gz or changelog.gz
Since this is breaking change, I'd also include it in the NEWS.Debian.gz as 
well.

Thank you

--- System information. ---
Architecture:
Kernel: Linux 4.16.0-2-amd64

Debian Release: buster/sid
800 testing mirror.csclub.uwaterloo.ca
800 testing cloudfront.debian.net
500 stretch download.docker.com
500 stable repository.spotify.com
500 stable repo.skype.com
500 stable packages.microsoft.com
500 stable dl.google.com
500 stable artifacts.elastic.co
500 sid linux.dropbox.com
500 jessie packagecloud.io
500 binary pkg.jenkins.io
100 unstable cloudfront.debian.net
100 experimental cloudfront.debian.net

--- Package information. ---
Depends (Version) | Installed
===-+-===
python | 2.7.15-3
apt | 1.6.1
python-configobj | 5.0.6-2


Package's Recommends field is empty.

Package's Suggests field is empty.

-- 
Tim, the beardless keeper of keys and grounds @ AgileBits Inc.
~~~
1Password remembers all your passwords for you. It keeps your digital life 
secure and always available, safe behind the one password that only you know.
Create your 1Password account today at https://1password.com




signature.asc
Description: OpenPGP digital signature

Bug#901552: ruby-bunny: autopkgtest times out

[Paul Gevers]

Source: ruby-bunny
Version: 2.6.1-2
Severity: normal
User: debian...@lists.debian.org
Usertags: regression timeout

Since version 2.6.1-2, the autopkgtests¹ are timing out (~ 3 hours)
while previous runs tested in less than 1 minute. Could you please
investigate how to get rid of the timeout?

I will blacklist ruby-bunny on ci.debian.net for now, but will
reactivate it when this bug is closed and the test doesn't time out anymore.

Don't hesitate to ask for help for the Debian CI team² if you need help
solving this issue.

Paul

¹ https://ci.debian.net/packages/r/ruby-bunny
² #debci on oftc or debian...@lists.debian.org

https://ci.debian.net/data/autopkgtest/unstable/amd64/r/ruby-bunny/442501/log.gz

autopkgtest [07:26:22]: test command1: [---

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5
  │
└──┘

Invalid gemspec in [bunny.gemspec]: No such file or directory - git
GEM_PATH= ruby2.5 -e gem\ \"bunny\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake
  │
└──┘

mv lib .gem2deb.lib
RUBYLIB=. GEM_PATH= ruby2.5 -S rake -f debian/ruby-tests.rake

WARNING: THE FOLLOWING TESTS ARE BEING SKIPPED:
spec/higher_level_api/integration/connection_recovery_spec.rb
spec/higher_level_api/integration/connection_stop_spec.rb
spec/higher_level_api/integration/consistent_hash_exchange_spec.rb
spec/higher_level_api/integration/tls_connection_spec.rb
spec/stress/channel_close_stress_spec.rb
spec/stress/long_running_consumer_spec.rb
spec/stress/connection_open_close_spec.rb
spec/stress/concurrent_publishers_stress_spec.rb
spec/stress/concurrent_consumers_stress_spec.rb
spec/stress/channel_open_stress_with_single_threaded_connection_spec.rb
spec/stress/channel_open_stress_spec.rb

ERROR: distribution port 25672 in use by rabbit@localhost
Waiting for 'bunny@ruby-bunny-1528701948'
pid is 4334
autopkgtest [10:13:03]: ERROR: timed out on command "su -s /bin/bash
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.4w33gp7j/downtmp/build.KvC/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.4w33gp7j/downtmp/command1-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.4w33gp7j/downtmp/command1-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.4w33gp7j/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.4w33gp7j/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; touch
/tmp/autopkgtest-lxc.4w33gp7j/downtmp/command1-stdout
/tmp/autopkgtest-lxc.4w33gp7j/downtmp/command1-stderr; bash -ec
'gem2deb-test-runner --autopkgtest --check-dependencies 2>&1' 2> >(tee
-a /tmp/autopkgtest-lxc.4w33gp7j/downtmp/command1-stderr >&2) > >(tee -a
/tmp/autopkgtest-lxc.4w33gp7j/downtmp/command1-stdout);" (kind: test)
autopkgtest [10:13:03]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Bug#901551: unblock: libgcrypt20/1.8.3-1

[Andreas Metzler]

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

Please unblock package libgcrypt20, this is a upstream bugfix/security
release of the stable branch, fixing CVE-2018-0495.
https://www.nccgroup.trust/us/our-research/technical-advisory-return-of-the-hidden-number-problem/

unblock libgcrypt20/1.8.3-1

thanks, cu Andreas


1.8.2-2_to_1.8.3-1.diff.xz
Description: application/xz


signature.asc
Description: PGP signature

Bug#851558: autopkgtest: define Restrictions for tests that aren't suitable for gating CI

[Simon McVittie]

On Sun, 22 Jan 2017 at 18:07:49 +, Simon McVittie wrote:
> Suppose I want to
> test that some tool (ostree or tar or whatever) can back up and restore
> xattrs. I can't test that unless I have some scratch area that lets the
> current user set xattrs.
...
> Or, imagine I want to test a non-http network protocol, perhaps testing
> whether my XMPP client can connect to an XMPP server. As we discussed
> on #851556, we would expect this to work on ci.debian.net, but not on
> Ubuntu's equivalent. I could probe for this with ": | nc xmpp.debian.net 5222"
> or something.
> 
> With Automake, I would be able to exit 77 to get the test recorded as
> having been skipped, but with current autopkgtest I would have to exit 0.
> 
> This would hopefully affect autopkgtest's exit status the same way as if
> the test had been skipped due to "Restrictions: something-you-dont-support" -
> so if one or more tests exit 77, autopkgtest would exit 2.

I've implemented this at

since an implementation is probably easier to comment on than an idea.
It's really orthogonal to what I first asked for in #851558.

smcv

Bug#851558: autopkgtest: define Restrictions for tests that aren't suitable for gating CI

[Simon McVittie]

Control: forwarded -1 
https://salsa.debian.org/ci-team/autopkgtest/merge_requests/19

On Mon, 16 Jan 2017 at 12:34:50 +0100, Martin Pitt wrote:
> Simon McVittie [2017-01-16  9:06 +]:
> > Specifically, if a maintainer is unable to fix a particular unreliable
> > or broken test, or the non-RC bug that it exposes, I think it's still
> > correct for that test to continue to run on CI infrastructure, with
> > its result logged but the usual side-effects of that result ignored.

I've implemented this (provisionally named "flaky", but other names are
available for bikeshedding).

If the flaky test passes, it is recorded as PASS as usual, and
autopkgtest's exit status is the same as if a normal test had passed.
If it fails, it is recorded as FLAKY, and autopkgtest's exit status is
the same as if it had been skipped due to Restrictions: isolation-machine
or similar.

smcv

Bug#901550: linux-image-4.16.0-2-amd64: Audio stops playing from speaker in ~3 mins

[Alice Vixie]

Package: src:linux
Version: 4.16.12-1
Severity: important

Dear Maintainer,

When I want to play an audio from any source (Chromium, VLC, ...) over built-in
speakers in my laptop Lenovo X201, it stops playing in 2-3 minutes. I don't
observe the same effect when playing audio over a bluetooth speaker or even
analog jack phones.

No, the problem isn't caused by audio being redirected to some other BT device
as you'd think.

This situation started some month ago.

The situation remains that way for another ~5 minutes, I guess something gets
restarted then?



-- Package-specific info:
** Version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.16.0-2-amd64 
root=UUID=1c7ddf77-579b-4cea-a10f-b1ce8794bcf6 ro quiet

** Not tainted

** Kernel log:
[   14.308071] audit: type=1400 audit(1528986742.760:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-soffice//gpg" 
pid=445 comm="apparmor_parser"
[   14.335963] audit: type=1400 audit(1528986742.788:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/mysqld-akonadi" 
pid=481 comm="apparmor_parser"
[   14.335967] audit: type=1400 audit(1528986742.788:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" pid=481 comm="apparmor_parser"
[   14.433403] Adding 8177660k swap on /dev/sda5.  Priority:-2 extents:1 
across:8177660k FS
[   14.497738] Bluetooth: Core ver 2.22
[   14.497760] NET: Registered protocol family 31
[   14.497761] Bluetooth: HCI device and connection manager initialized
[   14.497767] Bluetooth: HCI socket layer initialized
[   14.497769] Bluetooth: L2CAP socket layer initialized
[   14.497775] Bluetooth: SCO socket layer initialized
[   14.876826] usbcore: registered new interface driver btusb
[   15.336117] usbcore: registered new interface driver usbserial_generic
[   15.336127] usbserial: USB Serial support registered for generic
[   15.391030] media: Linux media interface: v0.10
[   15.396270] usbcore: registered new interface driver qcserial
[   15.396281] usbserial: USB Serial support registered for Qualcomm USB modem
[   15.396314] qcserial 2-1.4:1.1: Qualcomm USB modem converter detected
[   15.396411] usb 2-1.4: Qualcomm USB modem converter now attached to ttyUSB0
[   15.486567] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
[   15.555726] Linux video capture interface: v2.00
[   16.192182] intel ips :00:1f.6: i915 driver attached, reenabling gpu 
turbo
[   16.669086] uvcvideo: Found UVC 1.00 device Integrated Camera (17ef:4816)
[   16.670785] uvcvideo 1-1.6:1.0: Entity type for entity Extension 3 was not 
initialized!
[   16.670787] uvcvideo 1-1.6:1.0: Entity type for entity Processing 2 was not 
initialized!
[   16.670788] uvcvideo 1-1.6:1.0: Entity type for entity Camera 1 was not 
initialized!
[   16.670860] input: Integrated Camera: Integrated C as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input16
[   16.670930] usbcore: registered new interface driver uvcvideo
[   16.670931] USB Video Class driver (1.1.1)
[   19.884825] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   19.884826] Bluetooth: BNEP filters: protocol multicast
[   19.884831] Bluetooth: BNEP socket layer initialized
[   20.890632] rfkill: input handler disabled
[   23.079491] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[   23.300396] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[   23.324665] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   23.331189] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1
[   23.568680] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1
[   23.652150] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   23.676442] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1
[   23.912566] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1
[   23.994760] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   24.231386] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   27.206126] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1
[   27.440336] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1
[   27.526539] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   30.612322] wlp2s0: authenticate with d4:ca:6d:de:97:5f
[   30.612340] wlp2s0: capabilities/regulatory prevented using AP HT/VHT 
configuration, downgraded
[   30.647952] wlp2s0: send auth to d4:ca:6d:de:97:5f (try 1/3)
[   30.649934] wlp2s0: authenticated
[   30.656036] wlp2s0: associate with d4:ca:6d:de:97:5f (try 1/3)
[   30.658926] wlp2s0: RX AssocResp from d4:ca:6d:de:97:5f (capab=0x431 
status=0 aid=3)
[   30.662665] wlp2s0: associated
[   30.767558] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[   32.477534] fuse init (API version 7.26)
[   45.526548] Bluetooth: RFCOMM TTY layer initialized
[   45.526562] Bluetooth: RFCOMM socket layer initialized
[   45.526569] Bluetooth: RFCOMM 

Bug#901549: matrix-synapse: unauthorised users can hijack rooms when there is no m.room.power_levels event in force

[Andrej Shadura]

Source: matrix-synapse
Version: 0.31.1+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/matrix-org/synapse/pull/3397

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

- From https://matrix.org/blog/2018/06/14/security-update-synapse-0-31-2/:

> …we are releasing a security update of Synapse (0.31.2) today which
> changes the rules used to authenticate power_level events, such that
> we fail-safe rather than fail-deadly if the existing auth mechanisms
> fail. In practice this means changing the default power level required
> to set state to be 50 rather than 0 if there is no power_levels event
> present, thus meaning that only the room creator can set the initial
> power_levels event.

See also https://github.com/matrix-org/matrix-doc/issues/1304
(Proposal to simplify the auth rules of m.room.power_level events.)

-BEGIN PGP SIGNATURE-

iQFIBAEBCAAyFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlsinAYUHGFuZHJld3No
QGRlYmlhbi5vcmcACgkQXkCM2RzYOdKFbQf8CmUFQ7Cnf1gq15BzZ7DW5wdHFSF2
mtCHGSGQQksyjuSw+Lz3Unqil3YRI9Z8hvPM/oCadFH19JxSBPRhW2a90WjZ67V4
8Vcn2l1VC4mLd98Ms38v1j7TiU2Qa3gfadk6+YIXq51D5OC8LXRKozoVHH0XJ0yG
3iV8LodPqL2D5wcDuQry8uZ4tEH3lhQbzqIjZKKeJp2WhFZBCuAU98DYjL7plqph
36Ce41+0z4zJXYi8DQ55MPOskOqYCOHFUZxTBw8umhwfK32xD9ao+Qfv27Poh0YT
M6EgZjkKqBBBVZc8NzvuEmHSHMcjI1FdlpZFHhy0DhYmkpPwJ3RHyW+k7g==
=5wg3
-END PGP SIGNATURE-

Bug#888767: jessie-pu: package debian-security-support/2018.01.29~deb8u1

[Guido Günther]

Hi,
On Fri, Jun 08, 2018 at 10:18:18PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2018-01-29 at 17:45 +0100, Guido Günther wrote:
> > This update brings debian-security-support in line with unstable.
> > Most
> > notably in oldstable this affects swftools since security support for
> > it is
> > now limited and chromium which doesn't receive any further security
> > updates.
> > 
> 
> Please go ahead.

Uploaded. Thanks!
 -- Guido

> 
> Regards,
> 
> Adam
> 

Bug#901535: cb2bib FTCBFS: does not pass cross flags to qmake

[Filippo Rusconi]

Greetings,

On Thu, Jun 14, 2018 at 04:35:02PM +0200, Helmut Grohne wrote:

Source: cb2bib
Version: 1.9.7-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

cb2bib fails to cross build from source, because it does not pass cross
flags to qmake. The easiest way of doing so is letting dh_auto_configure
do it. That makes cb2bib cross buildable. Please consider applying the
attached patch.


Thanks for the patch. 


Could you please enlighten me on the presence of the lonely


+override_dh_auto_install:


patch line, please?

Thank you,

Filippo

--
⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
⣾⠁⢠⠒⠀⣿⡁   Scientist at CNRS
⢿⡄⠘⠷⠚⠋⠀   Debian Developer
⠈⠳⣄  http://msxpertsuite.org
 http://www.debian.org

Bug#901548: diffoscope: Add lz4 comparator

[Xavier Briand]

Source: diffoscope
Version: 95
Severity: wishlist

Add lz4 comparator.
-- 


Xavier Briand
Senior Web Application Developer| ExperiencePoint


20 Duncan Street, Suite 200, Toronto, ON, M5H 3G8
(416) 369-9888 x259

Connect with me: LinkedIn  |
Twitter  | Blog


..


*ExperiencePoint is an Edison Award winning company.*


0001-Add-lz4-comparator.patch
Description: Binary data

Bug#901547: seabios: Source tarball ships compiled binaries

[Vivia Nikolaidou]

Package: seabios
Version: 1.11.1-1
Severity: serious
Justification: Policy 2.1.2

Dear Maintainer,

I just noticed that the source tarball of seabios includes some compiled
binaries:

$ ls src/fw/*.hex
src/fw/acpi-dsdt.hex  src/fw/ssdt-misc.hex  src/fw/ssdt-pcihp.hex  src/fw/ssdt-
proc.hex

In debian/rules, these files are moved away and rebuilt:

# move out shipped .hex files and rebuild them
mkdir -p build/src/fw
for f in ${FW_FILES}; do [ -f $$f.sav -o ! -f $$f ] || mv $$f $$f.sav;
done
rm -f ${FW_FILES}
make OUT=build/ ${FW_FILES}
touch $@

They should not be shipped at all, they should just be built when packaging.



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

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

-- no debconf information

Bug#901546: transition: libcdio

[Matthias Klose]

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

libcdio 2.0 in experimental changes the API slightly again.  All packages build, 
except for


 - vcdimager (new upstream required, in experimental)
 - libdevice-cdio-perl (new upstream required, prepared)
 - fuse-umfuse-iso9660 (patch available)

Bug#901470: apparmor-utils: aa-logprof prints a lot of garbage with "Error: Unknown line found in file"

[Vincas Dargis]

On 6/14/18 12:16 PM, intrigeri wrote:

At first glance this looks like:

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

Can you please confirm that MR fixes this problem for you?
If it does I'll import it into debian/patches.



Yes, it fixed.

Bug#901545: siggen: ignores config files

[Jacek Sobczak]

Package: siggen
Version: 2.3.10-7+b1
Severity: normal

Dear Maintainer,

The siggen set of programs ignore (do not read?) config files
/etc/siggen.conf, $HOME/.siggen.conf, ./.siggen.conf.

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

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

Versions of packages siggen depends on:
ii  libc62.27-3
ii  libncurses6  6.1+20180210-4
ii  libtinfo66.1+20180210-4
ii  oss-compat   7

siggen recommends no packages.

siggen suggests no packages.

-- no debconf information

Bug#901544: Make libwx-perl build reproducible

[Brüns]

Package: libwx-perl
Version: 1:0.9932-4

libwx-perl build is still not reproducible.


Exported names are randomly vanishing/reappearing due to unstable build order, 
i.e. in /usr/lib//perl5/5.26/Wx/Wx_Exp.pm 

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/libwx-perl.html
https://tests.reproducible-builds.org/debian/rb-pkg/stretch/i386/diffoscope-results/libwx-perl.html

Upstream BR: https://rt.cpan.org/Public/Bug/Display.html?id=120657


The openSUSE version builds reproducibly for over a year. Please pick up the 
patches from:
https://build.opensuse.org/package/show/devel:languages:perl/perl-Wx

Bug#900936: some info on this bug

[Valentin Blot]

I filled a bug upstream because the source of the problem is that the
agent is started while geoclue is not running.

see https://gitlab.freedesktop.org/geoclue/geoclue/issues/68

Bug#901543: aeolus FTCBFS: upstream Makefile hard codes build architecture compiler g++

[Helmut Grohne]

Source: aeolus
Version: 0.9.5-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

aeolus fails to cross build from source, because the upstream Makefile
hard codes the build architecture compiler g++. After making it
substitutable, aeolus cross builds successfully. Please consider
applying the attached patch.

Helmut
--- aeolus-0.9.5.orig/source/Makefile
+++ aeolus-0.9.5/source/Makefile
@@ -34,7 +34,7 @@
 aeolus:	LDLIBS += -lzita-alsa-pcmi -lclthreads -ljack -lasound -lpthread -ldl -lrt
 aeolus: LDFLAGS += -L$(PREFIX)/$(LIBDIR)
 aeolus:	$(AEOLUS_O)
-	g++ $(LDFLAGS) -o $@ $(AEOLUS_O) $(LDLIBS)
+	$(CXX) $(LDFLAGS) -o $@ $(AEOLUS_O) $(LDLIBS)
 
 addsynth.o:	CPPFLAGS += -fpic -D_REENTRANT
 $(AEOLUS_O):
@@ -48,7 +48,7 @@
 aeolus_x11.so:	LDLIBS += -lclthreads -lclxclient -lpthread -lXft -lX11
 aeolus_x11.so:	LDFLAGS += -shared -L$(PREFIX)/$(LIBDIR) -L/usr/X11R6/$(LIBDIR)
 aeolus_x11.so: $(XIFACE_O) $(LIBCLX)
-	g++ $(LDFLAGS) -o $@ $(XIFACE_O) $(LDLIBS)
+	$(CXX) $(LDFLAGS) -o $@ $(XIFACE_O) $(LDLIBS)
 
 $(XIFACE_O):
 -include $(XIFACE_O:%.o=%.d)
@@ -60,7 +60,7 @@
 aeolus_txt.so:	LDLIBS += -lclthreads -lpthread -lreadline
 aeolus_txt.so:	LDFLAGS += -shared -L$(PREFIX)/$(LIBDIR)
 aeolus_txt.so: $(TIFACE_O)
-	g++ $(LDFLAGS) -o $@ $(TIFACE_O) $(LDLIBS)
+	$(CXX) $(LDFLAGS) -o $@ $(TIFACE_O) $(LDLIBS)
 
 $(TIFACE_O):
 -include $(TIFACE_O:%.o=%.d)

Bug#901390: RFP: python-orderedmultidict -- an ordered multivalue dictionary that retains method parity with Python's dict.

[Inaki Malerba]

Edwads,

Thanks for your review.

The package was already accepted but I'll fix that now.
I packaged this as a dependency for furl, also form Gruns, which has
also the same license. I'll fix it there too.

Thanks !

Saludos.

On 14/06/18 04:43, Edward Betts wrote:
> I'd also like to see this package in Debian.
>
> Inaki Malerba  wrote:
>> License: Public Domain
> Just to be a little more specific python-orderedmultidict uses the Unlicense.
>
> The license says the software is released into the public domain.
>
> See https://github.com/gruns/orderedmultidict/blob/master/LICENSE.md
>
> And https://unlicense.org/

-- 
- ina




signature.asc
Description: OpenPGP digital signature

Bug#901526: python-django: FTBFS: FAIL: test_invalid (migrations.test_loader.PycLoaderTests)

[Chris Lamb]

Chris Lamb wrote:

> We are likely deleting or otherwise refreshing the .pyc file. :)

Curiously, I can reproduce in stretch, buster and sid in upstream's
git repo...


Regards,

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

Bug#901542: sreview: FTBFS: unable to load addon sysuser

[Niko Tyni]

Source: sreview
Version: 0.3.1-1
Severity: serious

This package fails to build in a clean sid/amd64 chroot.

>From the build log:

  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with apache2,sysuser
  dh: unable to load addon sysuser: Can't locate 
Debian/Debhelper/Sequence/sysuser.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::sysuser module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 11) line 
1.
  BEGIN failed--compilation aborted at (eval 11) line 1.
  
  make: *** [debian/rules:4: clean] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2
 
-- 
Niko Tyni   nt...@debian.org

Bug#901541: more MIME types in xpdf.desktop

[Maxim Nikulin]

Package: xpdf
Version: 3.04-7
Severity: wishlist

Currently xpdf.desktop file contains just one MIME type in the 
application description


MimeType=application/pdf;

Xpdf supports several types of compressed files so I suggest to add them 
to the xpdf.desktop file


MimeType=application/pdf;application/x-pdf;application/x-gzpdf;application/x-bzpdf;application/x-xzpdf;

Some documentation .pdf files are gzipped and additional MIME types will 
remove an obstacle in opening such files using xpdf from GUI. Actually 
the wrapper may be modified for one more type, namely 
application/x-lzpdf using the lzcat utility.


Originally I faced a problem in Ubuntu-16.04, I could not select xpdf at 
all from firefox dialog. It uses gtk application chooser now that lacks 
ability to select particular executable as file type handler or just 
specify the path to the desired application. Unexpected side effect of 
attempt to be user-friendly. It is pleasant surprise to see fix with 
"%f" in Exec field in Debian upstream package. Extended list of MIME 
types may be next step to desktop integration that can not be ignored now.

Bug#901540: vnlog: FTBFS: test failures

[Niko Tyni]

Source: vnlog
Version: 1.9-1
Severity: serious

This package failed to build on many architectures where previous versions
have built.

  https://buildd.debian.org/status/package.php?p=vnlog

From the i386 build log:

Test failed. Expected success, but got failure.
Ran 'perl /<>/test/../vnl-sort -k a data1 data2'.
STDERR: 'All input legends must match! Instead files 'data1' and 'data2' have 
keys 'a b e' and 'a b' respectively at /<>/lib/Vnlog/Util.pm line 
234.
Vnlog::Util::ensure_all_legends_equivalent(ARRAY(0x58855cfc)) called at 
/<>/test/../vnl-sort line 131
' at /<>/test/TestHelpers.pm line 95.
TestHelpers::check("# a b\x{a}1 1.69\x{a}20 0.09\x{a}3 0.49\x{a}4 
2.89\x{a}5 -10\x{a}5 7.29\x{a}6 -8\x{a}7 -6\x{a}8 -"..., "-k", "a", "\$data1", 
"\$data2") called at test/test_vnl-sort.pl line 82
[...]
11 tests failed!
Makefile:79: recipe for target 'test/test_vnl-sort.pl.RUN' failed
make[1]: *** [test/test_vnl-sort.pl.RUN] Error 1
make[1]: *** Waiting for unfinished jobs
All tests passed!
All tests passed!
make[1]: Leaving directory '/<>'
dh_auto_test: make -j4 test returned exit code 2
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

-- 
Niko Tyni   nt...@debian.org

Bug#901539: gnushogi swallows errors from make (policy 4.6)

[Helmut Grohne]

Source: gnushogi
Version: 1.4.2-3
Severity: serious
Justification: policy 4.6
Tags: upstream

If you run

grep '^\s*-' Makefile.in

you'll find a number of crucial make rules that ignore errors. In
particular the main build and install targets are among them. Thus
gnushogi continues building in the presence of errors and risks
misbuilds. Such behaviour is prohibited by policy section 4.6.

Helmut

Bug#901538: RFS: fqterm/0.9.9-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

  Dear mentors and Chinese team folks,

  I am looking for a sponsor for my package "fqterm"

 * Package name: fqterm
   Version : 0.9.9-1
   Upstream Author : Iru Cai 
 * URL : https://github.com/mytbk/fqterm
 * License : GPL-2+ with OpenSSL exception
   Section : x11

  It builds those binary packages:

fqterm - BBS client written in Qt

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

  https://mentors.debian.net/package/fqterm


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

dget -x 
https://mentors.debian.net/debian/pool/main/f/fqterm/fqterm_0.9.9-1.dsc


Git packaging repository:

https://salsa.debian.org/chinese-team/fqterm

  Changes since the last upload:

 fqterm (0.9.9-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/control: Revert maintainer address to chinese-developers@lists.a.d.o.
   * d/patches: Backport upstream trunk commit till 2018-06-08.
 - Fix FTBFS with prospective Qt 5.11.


  Regards,
   Boyuan Yang

Bug#901537: ooniprobe: FTBFS: ERROR: test_send_packet_with_answer (ooni.tests.test_txscapy.TestTxScapy)

[Andreas Beckmann]

Source: ooniprobe
Version: 2.3.0-1
Severity: serious
Justification: fails to build from source

Hi,

ooniprobe recently started to FTBFS in a minimal current sid pbuilder
environment:

==
ERROR: test_send_packet_with_answer (ooni.tests.test_txscapy.TestTxScapy)
test_send_packet_with_answer
--
TimeoutError:  (test_send_packet_with_answer) still 
running at 120.0 secs

--
Ran 156 tests in 171.430s

FAILED (errors=1, skipped=25)


Andreas


ooniprobe_2.3.0-1.log.gz
Description: application/gzip

Bug#901528: please package new version 2.0.0 to build with libcdio 2.0

[gregor herrmann]

Control: tag -1 + pending

On Thu, 14 Jun 2018 16:09:01 +0200, Matthias Klose wrote:

> please package new version 2.0.0 to build with libcdio 2.0.

Already done in git, this is just a bit of a chicken/egg problem:
2.0.0 needs libcdio-dev >= 1.1; unstable has 1.0.0, only experimental
has 2.0.0.
So we can either upload to experimental or wait for libcdio-dev 2.0.0
to go into unstable. -- I guess the latter makes more sense, so maybe
just shout when you migrate libcdio-dev and we follow with
libdevice-cdio-perl?

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 VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Kurt Ostbahn: I mecht' so gern land'n


signature.asc
Description: Digital Signature

Bug#901536: gkrellweather FTCBFS: upstream Makefile hard codes build architecture pkg-config

[Helmut Grohne]

Source: gkrellweather
Version: 2.0.8-2.1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

gkrellweather fails to cross build from source, because the upstream
Makefile hard codes the build architecture pkg-config. After making it
substitutable, gkrellweather cross builds successfully. Please consider
applying the attached patch.

Helmut
--- gkrellweather-2.0.8.orig/Makefile
+++ gkrellweather-2.0.8/Makefile
@@ -1,7 +1,8 @@
 PKGNAME = gkrellweather
 VERSION = 2.0.8
-CFLAGS += -O2 -std=gnu99 -Wall -fPIC `pkg-config gtk+-2.0 --cflags`
-LIBS = `pkg-config gtk+-2.0 --libs`
+PKG_CONFIG ?= pkg-config
+CFLAGS += -O2 -std=gnu99 -Wall -fPIC `$(PKG_CONFIG) gtk+-2.0 --cflags`
+LIBS = `$(PKG_CONFIG) gtk+-2.0 --libs`
 LDFLAGS += -shared
 PREFIX = /usr/local
 

Bug#858819: availability new package version in stable

[Kraus, Sebastian]

Dear Adrian Bunk,



thanks for your corrections.

Do you plan to push the new package version

also to Debian stable (stretch)? There only the

buggy package version 2.10.0-1 is available.



Regards

Sebastian



Sebastian Kraus
Team IT am Institut für Chemie
Gebäude C, Straße des 17. Juni 115, Raum C7

Technische Universität Berlin
Fakultät II
Institut für Chemie
Sekretariat C3
Straße des 17. Juni 135
10623 Berlin

Email: sebastian.kr...@tu-berlin.de

Bug#732796: Please remove the link from open to openvt

[Vitezslav Crhonek]

On 05/28/2018 10:05 PM, Andreas Henriksson wrote:
> Hello Vitezslav Crhonek,
> 
> Gürkan Myczko sent the below forwarded message to fedora devel list
> in May 2017, but it seems there was no followup so I'm trying
> sending it directly to you as you seem to be the one who has
> been actively committing to the kbd package in fedora.
> 
> In summary, some people would like to se "open" command be used
> for a different purpose than the current decades old compatibility
> link. Personally I think if/when the link is removed we should make
> sure it's not reused for anything for multiple releases/years to avoid
> confusion about it pointing to different things in different
> things in different distros.
> 
> What do you think? Is it doable to drop it in Fedora?
> 
> I'd be willing to drop it in Debian which should trickle down to
> all derived .deb based distros. Hopefully if you change Fedora
> the rest of the .rpm world will follow suite. This should make
> the change pretty universal I think and avoid deviating between
> different distros.
> 
> Regards,
> Andreas Henriksson
> 
> 
> 
> - Forwarded message from Gürkan Myczko  -
> 
> Date: Wed, 17 May 2017 14:00:52 +0200
> From: Gürkan Myczko 
> To: de...@lists.fedoraproject.org
> Cc: 732...@bugs.debian.org
> Subject: Please remove the link from open to openvt
> User-Agent: Roundcube Webmail/1.2.5
> 
> Hello,
> 
> First, I have no relation to Fedora, but I write here because of this bug in
> Debian:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732796
> 
> Would you guys at Fedora feel like it's time to get rid of the symlink
> /bin/open to make space for
> xdg-open (for fdo fans) or gopen/openapp (for macOS, GNUstep fans).
> 
> The name change was like 16 years ago. And I wasn't able to find anything
> still using /bin/open.
> 
> Thanks,
> Myczko
> 
> 
> - End forwarded message -
> 


Hello Andreas,

Sorry for late response.

I have no objections against dropping it and I'm willing to do it
in Fedora Rawhide.

Best regards,
Vita

-- 
Vitezslav Crhonek
Software Engineer
Red Hat



signature.asc
Description: OpenPGP digital signature

Bug#901535: cb2bib FTCBFS: does not pass cross flags to qmake

[Helmut Grohne]

Source: cb2bib
Version: 1.9.7-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

cb2bib fails to cross build from source, because it does not pass cross
flags to qmake. The easiest way of doing so is letting dh_auto_configure
do it. That makes cb2bib cross buildable. Please consider applying the
attached patch.

Helmut
diff --minimal -Nru cb2bib-1.9.7/debian/changelog cb2bib-1.9.7/debian/changelog
--- cb2bib-1.9.7/debian/changelog   2018-01-25 17:38:13.0 +0100
+++ cb2bib-1.9.7/debian/changelog   2018-06-14 16:26:40.0 +0200
@@ -1,3 +1,10 @@
+cb2bib (1.9.7-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 14 Jun 2018 16:26:40 +0200
+
 cb2bib (1.9.7-2) unstable; urgency=low
 
   * Fix broken symbolic man page link. Although the bug report suggested an
diff --minimal -Nru cb2bib-1.9.7/debian/rules cb2bib-1.9.7/debian/rules
--- cb2bib-1.9.7/debian/rules   2017-12-04 14:48:16.0 +0100
+++ cb2bib-1.9.7/debian/rules   2018-06-14 16:26:40.0 +0200
@@ -2,26 +2,22 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DH_VERBOSE=1
+export QT_SELECT=qt5
 
 BUILDDIR=$(CURDIR)/debian/build
 
 %:
-   dh $@ --parallel
+   dh $@ --parallel --buildsystem=qmake --builddirectory=$(BUILDDIR)
 
 override_dh_auto_configure:
mkdir -p $(BUILDDIR) && \
cp -rpf c2bscripts  c2btools  cb2bib.pro  cb2bib.rc data src 
testPDFImport xpdf $(BUILDDIR) && \
-   cd $(BUILDDIR) && \
-   qtchooser -run-tool=qmake -qt=5 ../../
+   dh_auto_configure
 
 debian/cb2bib.xpm: src/icons/cb2bib.png
convert src/icons/cb2bib.png -resize 32x32 debian/cb2bib.xpm
 
 override_dh_auto_build: debian/cb2bib.xpm
-   $(MAKE) -C $(BUILDDIR)
-
-override_dh_clean:
-   dh_clean
-   -rm -rf $(BUILDDIR)
-
+   dh_auto_build
 
+override_dh_auto_install:

Bug#901534: mp4h statically links libpcre

[Helmut Grohne]

Package: mp4h
Version: 1.3.1-16
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

mp4h statically links libpcre. That's a pretty bad idea. pcre has a
history of security issues and having to rebuild mp4h for security is
not a nice property. It also raises the question whether mp4h should
have a Built-Using Header. Half of the Installed-Size is contributed by
libpcre. Finally using the build architecture libpcre in a host
architecture application breaks cross compilation.

Quite simply, I propose linking mp4h dynamically to solve all of these
issues. Please consider applying the attached patch.

Helmut
diff --minimal -Nru mp4h-1.3.1/debian/changelog mp4h-1.3.1/debian/changelog
--- mp4h-1.3.1/debian/changelog 2016-08-13 00:17:10.0 +0200
+++ mp4h-1.3.1/debian/changelog 2018-06-14 13:50:26.0 +0200
@@ -1,3 +1,10 @@
+mp4h (1.3.1-16.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Link libpcre dynamically. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 14 Jun 2018 13:50:26 +0200
+
 mp4h (1.3.1-16) unstable; urgency=medium
 
   * Finetune regular expression for replacing  output in HTML
diff --minimal -Nru mp4h-1.3.1/debian/patches/use-system-pcre.diff 
mp4h-1.3.1/debian/patches/use-system-pcre.diff
--- mp4h-1.3.1/debian/patches/use-system-pcre.diff  2016-08-12 
23:48:06.0 +0200
+++ mp4h-1.3.1/debian/patches/use-system-pcre.diff  2018-06-14 
13:50:15.0 +0200
@@ -37,19 +37,15 @@
  mp4h_LDFLAGS = -export-dynamic
  endif
 -mp4h_LDADD   = -lm $(top_builddir)/lib/libmp4h.a 
$(top_builddir)/pcre/libpcre.a @LIBINTL@ $(MODULE_LDADD)
-+mp4h_LDADD   = -lm $(top_builddir)/lib/libmp4h.a 
@DEB_BUILD_MULTIARCH@/libpcre.a @LIBINTL@ $(MODULE_LDADD)
++mp4h_LDADD   = -lm $(top_builddir)/lib/libmp4h.a -lpcre @LIBINTL@ 
$(MODULE_LDADD)
  
  include_HEADERS = mp4h.h
  noinst_HEADERS  = builtin.h
 Index: mp4h/configure.ac
 ===
 --- mp4h.orig/configure.ac 2013-09-25 01:46:25.984808776 +0200
 +++ mp4h/configure.ac  2013-09-25 01:46:26.008809186 +0200
-@@ -140,10 +140,10 @@
- dnl  This line is needed for Debian builds
- AC_SUBST(CFLAGS)
- AC_SUBST([INTLINCL], [])
-+AC_SUBST([DEB_BUILD_MULTIARCH], [/usr/lib/`dpkg-architecture 
-qDEB_BUILD_MULTIARCH`])
+@@ -143,7 +143,6 @@
  
  AC_CONFIG_FILES([
 Makefile

Bug#901497: Hard system hangs after upgrade from 18.0.5-1 to 18.1.1-1

[Tehnic]

Hi all,

last information for now:

When starting the session with "GNOME on Xorg" the effect disappears.

Maybe the bug should be assigned to xwayland?

Regards. Robert

-- 
Tehnic 

Bug#901497: Hard system hangs after upgrade from 18.0.5-1 to 18.1.1-1

[Tehnic]

Hi all,

here some more informations. maybe it helps:

1) Purging flashplayer doesnt solve the problem

2) You still can login by network when graphic hangs

3) Xwayland process uses 100% CPU

4) Connecting to this process with strace shows only a lot of:

writev(16, [], 0)   = 0

regulary interrupted by:

--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
rt_sigreturn({mask=[]}) = 0

5) A restart/stop of gdm (systemctl restart/stop gdm) doesnt help,
you have to do a hard kill (kill -9) of the Xwayland process.

Regards. Robert

-- 
Tehnic 

Bug#901533: mesa: please build

[Laurent Bonnaud]

Source: mesa
Severity: wishlist


Dear Maintainer,

the Mesa source package contains this file:

  ./mesa-18.1.1/src/intel/tools/intel_sanitize_gpu.c

but it is not built during the Debian binary packages creation.  Could you 
please build it?

It would be very helpful to debug Mesa issues, such as:

  https://bugs.freedesktop.org/show_bug.cgi?id=106859


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

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

-- 
Laurent.

Bug#901531: ITP: node-p-try - Starts a promise chain

[Rushi Bhadane]

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

* Package name: node-p-try
  Version : 1.0.0
  Upstream Author :  Sindre Sorhus  (
sindresorhus.com)
* URL :  https://github.com/sindresorhus/p-try#readme
* License : Expat
  Programming Lang: JavaScript
  Description: ITP: node-p-try - Starts a promise chain

Bug#901530: fix build failure with libcdio-2.0

[Matthias Klose]

Package: src:fuse-umfuse-iso9660
Version: 0.3-1.2
Tags: patch

fix build failure with libcdio-2.0 (experimental)

http://launchpadlibrarian.net/374504428/fuse-umfuse-iso9660_0.3-1.2build1_0.3-1.2ubuntu1.diff.gz

Bug#901529: cups: SystemGroup options cannot work with account/group NSS providers if don't enumerate groups

[Marco Gaiarin]

Package: cups
Version: 1.7.5-11+deb8u2
Severity: normal

Dear Maintainer,

I've found that setting 'SystemGroup' opton in cups-files.conf does not work
if the NSS provider does not enumerate group (eg, 'getent group '
does not return the list of users).

Some examples:

a) using winbind nss providers. My user is correctly in 'printops' group:

root@vdmsv1:~# id gaio
uid=1(gaio) gid=10513(domain users) gruppi=10513(domain 
users),11001(sir),10999(unixadm),10998(printops),5001(BUILTIN\users),5000(BUILTIN\administrators)

but if i check 'printops' groups there's no 'gaio' users:

root@vdmsv1:~# getent group printops
printops:x:10998:

and this is normal, Samba team suggest to disable users and group
enumeration for performance reasons.


b) using pam_groups (eg /etc/security/group.conf) to assign some local
 groups to users:

gaio@vdmsv1:~$ id
uid=1(gaio) gid=10513(domain users) gruppi=10513(domain 
users),4(adm),20(dialout),24(cdrom),25(floppy),46(plugdev),5000(BUILTIN\administrators),5001(BUILTIN\users),10998(printops),10999(unixadm),11001(sir)

but still no group enumeration:

gaio@vdmsv1:~$ getent group lpadmin
lpadmin:x:119:

and this is again normal, pam_groups add group membership dynamically on
logon (pam auth context).


In both way, eg, trying to use 'printops' group or 'lpadmin' group as
SystemGroup does not work, eg i can login to CUPS web interface with user
gaio, but without '@SYSTEM' privileges.

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

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

Versions of packages cups depends on:
ii  cups-client1.7.5-11+deb8u2
ii  cups-common1.7.5-11+deb8u2
ii  cups-core-drivers  1.7.5-11+deb8u2
ii  cups-daemon1.7.5-11+deb8u2
ii  cups-filters   1.0.61-5+deb8u3
ii  cups-ppdc  1.7.5-11+deb8u2
ii  cups-server-common 1.7.5-11+deb8u2
ii  debconf [debconf-2.0]  1.5.56+deb8u1
ii  ghostscript9.06~dfsg-2+deb8u6
ii  libavahi-client3   0.6.31-5
ii  libavahi-common3   0.6.31-5
ii  libc-bin   2.19-18+deb8u10
ii  libc6  2.19-18+deb8u10
ii  libcups2   1.7.5-11+deb8u2
ii  libcupscgi11.7.5-11+deb8u2
ii  libcupsimage2  1.7.5-11+deb8u2
ii  libcupsmime1   1.7.5-11+deb8u2
ii  libcupsppdc1   1.7.5-11+deb8u2
ii  libgcc11:4.9.2-10+deb8u1
ii  libstdc++6 4.9.2-10+deb8u1
ii  libusb-1.0-0   2:1.0.19-1
ii  lsb-base   4.1+Debian13+nmu1
ii  poppler-utils  0.26.5-2+deb8u4
ii  procps 2:3.3.9-9+deb8u1

Versions of packages cups recommends:
ii  avahi-daemon 0.6.31-5
ii  colord   1.2.1-1+b2
ii  cups-filters [ghostscript-cups]  1.0.61-5+deb8u3
ii  printer-driver-gutenprint5.2.10-3

Versions of packages cups suggests:
pn  cups-bsd   
pn  cups-pdf   
pn  foomatic-db-compressed-ppds | foomatic-db  
ii  hplip  3.14.6-1+deb8u1
ii  printer-driver-hpcups  3.14.6-1+deb8u1
ii  smbclient  2:4.5.12+dfsg-2+deb9u2~bpo8+1
ii  udev   215-17+deb8u7

-- debconf information:
* cupsys/backend: lpd, socket, usb, snmp, dnssd
* cupsys/raw-print: true

Bug#901528: please package new version 2.0.0 to build with libcdio 2.0

[Matthias Klose]

Package: libdevice-cdio-perl
Version: 0.4.0-3
Tags: patch

please package new version 2.0.0 to build with libcdio 2.0. Example packaging is 
available at https://launchpad.net/ubuntu/+source/libdevice-cdio-perl/2.0.0-0ubuntu1

Bug#901526: python-django: FTBFS: FAIL: test_invalid (migrations.test_loader.PycLoaderTests)

[Chris Lamb]

Hi Andreas,

> […]

This is the test in question:

def test_invalid(self):
"""
MigrationLoader reraises ImportErrors caused by "bad magic number" pyc
files with a more helpful message.
"""
with 
self.temporary_migration_module(module='migrations.test_migrations_bad_pyc'):
msg = (
r"Couldn't import '\w+.migrations.0001_initial' as it appears "
"to be a stale .pyc file."
)
with self.assertRaisesRegex(ImportError, msg):
MigrationLoader(connection)

We are likely deleting or otherwise refreshing the .pyc file. :)


Regards,

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

Bug#901527: disable more network related tests

[Matthias Klose]

Package: src:tellico
Version: 3.1.2-2
Tags: patch

Apparently there are more network related tests, I had to disable these for the 
Launchpad builds.


diff -Nru tellico-3.1.2/debian/changelog tellico-3.1.2/debian/changelog
--- tellico-3.1.2/debian/changelog	2018-05-26 10:54:12.0 +
+++ tellico-3.1.2/debian/changelog	2018-06-14 13:16:55.0 +
@@ -1,3 +1,9 @@
+tellico (3.1.2-2ubuntu2) cosmic; urgency=medium
+
+  * Disable more network related tests.
+
+ -- Matthias Klose   Thu, 14 Jun 2018 15:16:55 +0200
+
 tellico (3.1.2-2) unstable; urgency=medium
 
   * Try to fix the unit tests:
diff -Nru tellico-3.1.2/debian/patches/tests-no-network.diff tellico-3.1.2/debian/patches/tests-no-network.diff
--- tellico-3.1.2/debian/patches/tests-no-network.diff	2018-05-26 08:10:24.0 +
+++ tellico-3.1.2/debian/patches/tests-no-network.diff	2018-06-14 13:16:55.0 +
@@ -5,6 +5,8 @@
 Last-Updated: 2018-05-26
 Forwarded: not-needed
 
+Index: b/src/tests/tellicoreadtest.cpp
+===
 --- a/src/tests/tellicoreadtest.cpp
 +++ b/src/tests/tellicoreadtest.cpp
 @@ -258,6 +258,7 @@ void TellicoReadTest::testLocalImage() {
@@ -25,3 +27,60 @@
  }
  
  void TellicoReadTest::testXMLHandler() {
+Index: b/src/tests/imagejobtest.cpp
+===
+--- a/src/tests/imagejobtest.cpp
 b/src/tests/imagejobtest.cpp
+@@ -191,6 +191,7 @@ void ImageJobTest::testImageLink() {
+   QCOMPARE(img.linkOnly(), true);
+ }
+ 
++#if 0
+ void ImageJobTest::testNetworkImage() {
+   if(!networkIsAvailable()) {
+ QSKIP("This test requires network access", SkipSingle);
+@@ -262,6 +263,7 @@ void ImageJobTest::testNetworkImageInval
+   const Tellico::Data::Image& img = job->image();
+   QVERIFY(img.isNull());
+ }
++#endif
+ 
+ void ImageJobTest::testFactoryRequestLocal() {
+   QVERIFY(m_imageId.isEmpty());
+@@ -310,6 +312,7 @@ void ImageJobTest::testFactoryRequestLoc
+   QVERIFY(!Tellico::ImageFactory::self()->hasImageInfo(m_imageId));
+ }
+ 
++#if 0
+ void ImageJobTest::testFactoryRequestNetwork() {
+   if(!networkIsAvailable()) {
+ QSKIP("This test requires network access", SkipSingle);
+@@ -338,6 +341,7 @@ void ImageJobTest::testFactoryRequestNet
+   QCOMPARE(img.format(), QByteArray("png"));
+   QCOMPARE(img.linkOnly(), false);
+ }
++#endif
+ 
+ void ImageJobTest::testFactoryRequestNetworkLinkOnly() {
+   if(!networkIsAvailable()) {
+Index: b/src/tests/imagejobtest.h
+===
+--- a/src/tests/imagejobtest.h
 b/src/tests/imagejobtest.h
+@@ -44,12 +44,16 @@ private Q_SLOTS:
+   void testImageLoad();
+   void testImageLoadWithId();
+   void testImageLink();
++#if 0
+   void testNetworkImage();
+   void testNetworkImageLink();
+   void testNetworkImageInvalid();
++#endif
+   void testFactoryRequestLocal();
+   void testFactoryRequestLocalInvalid();
++#if 0
+   void testFactoryRequestNetwork();
++#endif
+   void testFactoryRequestNetworkLinkOnly();
+ 
+ Q_SIGNALS:

Bug#901526: python-django: FTBFS: FAIL: test_invalid (migrations.test_loader.PycLoaderTests)

[Chris Lamb]

Hi Andreas,

> python-django/experimental FTBFS with a test failure on both i386 and
> amd64:
> 
> ==
> FAIL: test_invalid (migrations.test_loader.PycLoaderTests)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/unittest/case.py", line 59, in 
> testPartExecutor
> yield
>   File "/usr/lib/python3.6/unittest/case.py", line 605, in run
> testMethod()
>   File "/build/python-django-2.1~alpha1/tests/migrations/
> test_loader.py", line 530, in test_invalid
> MigrationLoader(connection)
>   File "/usr/lib/python3.6/unittest/case.py", line 203, in __exit__
> self._raiseFailure("{} not raised".format(exc_name))
>   File "/usr/lib/python3.6/unittest/case.py", line 135, in _raiseFailure
> raise self.test_case.failureException(msg)
> AssertionError: ImportError not raised

Cool, same thing in the r-b setup:

  
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/python-django.html


Regards,

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

Bug#901525: TAG: isc-kea -- Next-gen DHCP server

[Jason Guy]

Package: wnpp
Severity: important

The current version of the isc-kea package in the debian repo is 1.1. ISC
is about to release version 1.4. The user community has been requesting the
Debian packages get updated, with the current version of Kea 1.3 pushed to
stable, and provide beta version 1.4 in testing.

I have been trying to contact the maintainer for over a year, with minimal
success getting a response. In one reply, he mentioned back in December he
is very busy. I have offered my help many times and I actually went ahead
and packaged Kea 1.3, and sent him the patches. He gladly took the patches,
and updated the git repo, but unfortunately he never pushed the package to
the Sid repo for users to test. Furthermore, I have some bug fixes, which I
have sent him and have not seen them merged on the git repo.

Adam has not replied to me in over 6 months, and it seems he has no
interest actively maintaining this package. I will be more than happy to
take over the maintenance or become a co-maintainer of this package.

Currently it looks like there is an error with the build system accessing
the git repo, which needs fixed. Most of the bugs should be fixed with
latest patches I have.


Thanks,
Jason Guy

Bug#901524: tracker.debian.org: removed packages improvements: add snapshot.d.o link, update bugs links

[Paul Wise]

Package: tracker.debian.org
Severity: wishlist
Tags: newcomer

On the pages for removed packages, in the panel saying the package has
been removed it would be nice to add a link to the snapshot.debian.org
page for the source package.

In addition, the bugs link for removed packages should link to both
archived and unarchived bugs instead of just unarchived bugs.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#901502: ITP: twig-extensions -- Twig Extensions

[Joost van Baal-Ilić]

Hi Felipe,

On Thu, Jun 14, 2018 at 09:11:46AM -0400, Felipe Sateler wrote:
> On Thu, 14 Jun 2018 10:27:40 +0200 Joost van =?utf-8?Q?Baal-Ili=C4=87?= <
> joos...@debian.org> wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Joost van Baal-Ilić 
> >
> > * Package name: twig-extensions
> >   Version : 1.3.0
> >   Upstream Author : Fabien Potencier
> > * URL : https://github.com/twigphp/Twig-extensions
> > * License : MIT/X
> >   Programming Lang: PHP
> >   Description : Twig Extensions
> >
> >  The Twig Extensions is a library that provides several useful extensions
> >  for Twig that do not belong to the core.  It currently ships Text, i18n,
> >  Intl, Array and Date Extensions.
> >
> >  Symphony's Twig is a flexible, fast, and secure template engine for PHP.
> 
> I have made an attempt at packaging this at [1] (it's needed by phpmyadmin
> too). However, I've lacked time to properly test and request review by more
> experienced PHP people. Please feel free to use my attempt as a starting
> point if it is useful.
> 
> [1] https://salsa.debian.org/phpmyadmin-team/twig-extensions

Thanks, this is very likely helpful indeed.  Note that other previous work is
available from
https://github.com/eduvpn/eduvpn-debian/tree/master/Twig-extensions too...

Bye,

Joost

Bug#901523: sbt-template-resolver: FTBFS with openjdk-10

[Andreas Beckmann]

Source: sbt-template-resolver
Version: 0.1-1
Severity: serious
Justification: fails to build from source

Hi,

sbt-template-resolver FTBFS with openjdk-10 as the default jdk:

[...]
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/sbt-template-resolver-0.1'
mkdir -p /build/sbt-template-resolver-0.1/debian/sbt_home/.ivy2/cache
cp -fr /build/sbt-template-resolver-0.1/bootstrapdeps/* 
/build/sbt-template-resolver-0.1/debian/sbt_home/.ivy2/cache/
mkdir /build/sbt-template-resolver-0.1/debian/sbt_home/.sbt
echo "[repositories]" > 
/build/sbt-template-resolver-0.1/debian/sbt_home/.sbt/repositories
echo "local" >> 
/build/sbt-template-resolver-0.1/debian/sbt_home/.sbt/repositories
cp -frv /build/sbt-template-resolver-0.1/bootstrapdeps-sources/. 
/build/sbt-template-resolver-0.1/debian/sbt_home/.ivy2/cache/
'/build/sbt-template-resolver-0.1/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs'
 -> 
'/build/sbt-template-resolver-0.1/debian/sbt_home/.ivy2/cache/./org.scala-sbt/compiler-interface/srcs'
'/build/sbt-template-resolver-0.1/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs/compiler-interface-0.13.12-sources.jar'
 -> '/build/sbt-template-resolver-0.1/debian/sbt_home/.ivy2/cache/./org.scala-
sbt/compiler-interface/srcs/compiler-interface-0.13.12-sources.jar'
/build/sbt-template-resolver-0.1/bootstrapsbt/bin/sbt -verbose -debug -sbt-dir 
/build/sbt-template-resolver-0.1/debian/sbt_home/.sbt -ivy 
/build/sbt-template-resolver-0.1/debian/sbt_home/.ivy2 'set offline := true
' -Dsbt.override.build.repos=true packageBin make-pom
[residual] arg = '-sbt-dir'
[residual] arg = '/build/sbt-template-resolver-0.1/debian/sbt_home/.sbt'
[addJava] arg = 
'-Dsbt.ivy.home=/build/sbt-template-resolver-0.1/debian/sbt_home/.ivy2'
[residual] arg = 'set offline := true'
[addJava] arg = '-Dsbt.override.build.repos=true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[addJava] arg = 
'-Dsbt.global.base=/build/sbt-template-resolver-0.1/debian/sbt_home/.sbt'
[residual] arg = 'set offline := true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[process_args] java_version = '10.0.1'
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/sbt-template-resolver-0.1/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/sbt-template-resolver-0.1/debian/sbt_home/.sbt
-jar
/build/sbt-template-resolver-0.1/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/53ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/25ms)
[ERROR] Failed to construct terminal; falling back to unsupported
java.lang.NumberFormatException: For input string: "0x100"
at 
java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.base/java.lang.Integer.parseInt(Integer.java:652)
at java.base/java.lang.Integer.valueOf(Integer.java:983)
at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:233)
at jline.UnixTerminal.(UnixTerminal.java:64)
at jline.UnixTerminal.(UnixTerminal.java:49)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at java.base/java.lang.Class.newInstance(Class.java:560)
at jline.TerminalFactory.getFlavor(TerminalFactory.java:209)
at jline.TerminalFactory.create(TerminalFactory.java:100)
at jline.TerminalFactory.get(TerminalFactory.java:184)
at jline.TerminalFactory.get(TerminalFactory.java:190)
at sbt.ConsoleLogger$.ansiSupported(ConsoleLogger.scala:123)
at sbt.ConsoleLogger$.(ConsoleLogger.scala:117)
at sbt.ConsoleLogger$.(ConsoleLogger.scala)
at sbt.GlobalLogging$.initial(GlobalLogging.scala:43)
at sbt.StandardMain$.initialGlobalLogging(Main.scala:61)
at sbt.StandardMain$.initialState(Main.scala:70)
at sbt.xMain.run(Main.scala:29)
at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109)
at xsbt.boot.Launch$.withContextLoader(Launch.scala:128)
at xsbt.boot.Launch$.run(Launch.scala:109)
at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:35)
at xsbt.boot.Launch$.launch(Launch.scala:117)
at 

Bug#772571: powertop still maintained?

[ghostbar]

Hi Tomas!

I’ll work on this on the weekend/monday. Sorry for this, I lost it in my todo 
list 5 years ago ¯_(ツ)_/¯

On Wed, Jun 6, 2018 at 02:04, Tomas Pospisek  wrote:

> Hello, today I got hit by the same problem as reported in #772571. The report 
> is from 2014 and the reply from Jose Luis mentions that "ACK, working on a 
> patch for it.". Now it seems to me that the patch for this problem would be 
> trivial (replacing /usr/sbin/hciconfig with /bin/hciconfig in the 
> sourcecode). However this has not happened during the past three and a half 
> years. So my question is: is powertop still maintained? (In case it was not: 
> wouldn't it be good to orphan it, so maybe somebody can take care of it?) 
> Thanks, *t

Bug#901522: scala-pickling: FTBFS with openjdk-10

[Andreas Beckmann]

Source: scala-pickling
Version: 0.10.1-1
Severity: serious
Justification: fails to build from source

Hi,

scala-pickling FTBFS with openjdk-10 as the default jdk:

[...]
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/scala-pickling-0.10.1'
mkdir -p /build/scala-pickling-0.10.1/debian/sbt_home/.ivy2/cache
cp -fr /build/scala-pickling-0.10.1/bootstrapdeps/* 
/build/scala-pickling-0.10.1/debian/sbt_home/.ivy2/cache/
mkdir /build/scala-pickling-0.10.1/debian/sbt_home/.sbt
echo "[repositories]" > 
/build/scala-pickling-0.10.1/debian/sbt_home/.sbt/repositories
echo "local" >> /build/scala-pickling-0.10.1/debian/sbt_home/.sbt/repositories
cp -frv /build/scala-pickling-0.10.1/bootstrapdeps-sources/. 
/build/scala-pickling-0.10.1/debian/sbt_home/.ivy2/cache/
'/build/scala-pickling-0.10.1/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs'
 -> 
'/build/scala-pickling-0.10.1/debian/sbt_home/.ivy2/cache/./org.scala-sbt/compiler-interface/srcs'
'/build/scala-pickling-0.10.1/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs/compiler-interface-0.13.12-sources.jar'
 -> 
'/build/scala-pickling-0.10.1/debian/sbt_home/.ivy2/cache/./org.scala-sbt/comp
iler-interface/srcs/compiler-interface-0.13.12-sources.jar'
/build/scala-pickling-0.10.1/bootstrapsbt/bin/sbt -verbose -debug -sbt-dir 
/build/scala-pickling-0.10.1/debian/sbt_home/.sbt -ivy 
/build/scala-pickling-0.10.1/debian/sbt_home/.ivy2 'set offline := true' 
-Dsbt.over
ride.build.repos=true packageBin make-pom
[residual] arg = '-sbt-dir'
[residual] arg = '/build/scala-pickling-0.10.1/debian/sbt_home/.sbt'
[addJava] arg = 
'-Dsbt.ivy.home=/build/scala-pickling-0.10.1/debian/sbt_home/.ivy2'
[residual] arg = 'set offline := true'
[addJava] arg = '-Dsbt.override.build.repos=true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[addJava] arg = 
'-Dsbt.global.base=/build/scala-pickling-0.10.1/debian/sbt_home/.sbt'
[residual] arg = 'set offline := true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[process_args] java_version = '10.0.1'
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/scala-pickling-0.10.1/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/scala-pickling-0.10.1/debian/sbt_home/.sbt
-jar
/build/scala-pickling-0.10.1/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/59ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/26ms)
[ERROR] Failed to construct terminal; falling back to unsupported
java.lang.NumberFormatException: For input string: "0x100"
at 
java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.base/java.lang.Integer.parseInt(Integer.java:652)
at java.base/java.lang.Integer.valueOf(Integer.java:983)
at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:233)
at jline.UnixTerminal.(UnixTerminal.java:64)
at jline.UnixTerminal.(UnixTerminal.java:49)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at java.base/java.lang.Class.newInstance(Class.java:560)
at jline.TerminalFactory.getFlavor(TerminalFactory.java:209)
at jline.TerminalFactory.create(TerminalFactory.java:100)
at jline.TerminalFactory.get(TerminalFactory.java:184)
at jline.TerminalFactory.get(TerminalFactory.java:190)
at sbt.ConsoleLogger$.ansiSupported(ConsoleLogger.scala:123)
at sbt.ConsoleLogger$.(ConsoleLogger.scala:117)
at sbt.ConsoleLogger$.(ConsoleLogger.scala)
at sbt.GlobalLogging$.initial(GlobalLogging.scala:43)
at sbt.StandardMain$.initialGlobalLogging(Main.scala:61)
at sbt.StandardMain$.initialState(Main.scala:70)
at sbt.xMain.run(Main.scala:29)
at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109)
at xsbt.boot.Launch$.withContextLoader(Launch.scala:128)
at xsbt.boot.Launch$.run(Launch.scala:109)
at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:35)
at xsbt.boot.Launch$.launch(Launch.scala:117)
at xsbt.boot.Launch$.apply(Launch.scala:18)
at xsbt.boot.Boot$.runImpl(Boot.scala:41)
at 

Bug#901497: Hard system hangs after upgrade from 18.0.5-1 to 18.1.1-1

[Tehnic]

The firefox versions:

firefox  60.0.2-1 amd64
firefox-esr  52.8.1esr-2  amd64

Flashplayer is installed but set to "Ask to Activate". Unfortunately i still 
need sometimes...

flashplayer-mozilla 3:30.0.0.113-dmo2 amd64

Regards, Robert

-- 
Tehnic 

Bug#901502: ITP: twig-extensions -- Twig Extensions

[Felipe Sateler]

Hi,

On Thu, 14 Jun 2018 10:27:40 +0200 Joost van =?utf-8?Q?Baal-Ili=C4=87?= <
joos...@debian.org> wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Joost van Baal-Ilić 
>
> * Package name: twig-extensions
>   Version : 1.3.0
>   Upstream Author : Fabien Potencier
> * URL : https://github.com/twigphp/Twig-extensions
> * License : MIT/X
>   Programming Lang: PHP
>   Description : Twig Extensions
>
>  The Twig Extensions is a library that provides several useful extensions
for
>  Twig that do not belong to the core.  It currently ships Text, i18n,
Intl,
>  Array and Date Extensions.
>
>  Symphony's Twig is a flexible, fast, and secure template engine for PHP.

I have made an attempt at packaging this at [1] (it's needed by phpmyadmin
too). However, I've lacked time to properly test and request review by more
experienced PHP people. Please feel free to use my attempt as a starting
point if it is useful.


[1] https://salsa.debian.org/phpmyadmin-team/twig-extensions

Bug#901495: redis: multiple security issues in Lua scripting

[Chris Lamb]

Chris Lamb wrote:

> > redis: multiple security issues in Lua scripting
> 
> This has now been assigned CVE-2018-11219 & CVE-2018-11218.

Security team, oermission to upload the attached to
stretch-security?

  redis (3:3.2.6-3+deb9u1) stretch-security; urgency=high

* CVE-2018-11218, CVE-2018-11219: Backport patches to fix multiple heap
  corruption and integer overflow vulnerabilities. (Closes: #901495)

   -- Chris Lamb   Thu, 14 Jun 2018 15:08:27 +0200


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/changelog b/debian/changelog
index c66f34fb..1c449909 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+redis (3:3.2.6-3+deb9u1) stretch-security; urgency=high
+
+  * CVE-2018-11218, CVE-2018-11219: Backport patches to fix multiple heap
+corruption and integer overflow vulnerabilities. (Closes: #901495)
+
+ -- Chris Lamb   Thu, 14 Jun 2018 15:08:27 +0200
+
 redis (3:3.2.6-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/patches/0009-Security-fix-redis-cli-buffer-overflow.patch 
b/debian/patches/0009-Security-fix-redis-cli-buffer-overflow.patch
new file mode 100644
index ..0ba4ccd7
--- /dev/null
+++ b/debian/patches/0009-Security-fix-redis-cli-buffer-overflow.patch
@@ -0,0 +1,53 @@
+From: antirez 
+Date: Mon, 11 Jun 2018 12:08:42 +0200
+Subject: Security: fix redis-cli buffer overflow.
+
+Thanks to Fakhri Zulkifli for reporting it.
+
+The fix switched to dynamic allocation, copying the final prompt in the
+static buffer only at the end.
+---
+ src/redis-cli.c | 27 ---
+ 1 file changed, 16 insertions(+), 11 deletions(-)
+
+diff --git a/src/redis-cli.c b/src/redis-cli.c
+index 9043915..f5e26d9 100644
+--- a/src/redis-cli.c
 b/src/redis-cli.c
+@@ -151,20 +151,25 @@ static long long mstime(void) {
+ }
+ 
+ static void cliRefreshPrompt(void) {
+-int len;
+-
+ if (config.eval_ldb) return;
+-if (config.hostsocket != NULL)
+-len = snprintf(config.prompt,sizeof(config.prompt),"redis %s",
+-   config.hostsocket);
+-else
+-len = anetFormatAddr(config.prompt, sizeof(config.prompt),
+-   config.hostip, config.hostport);
++
++sds prompt = sdsempty();
++if (config.hostsocket != NULL) {
++prompt = sdscatfmt(prompt,"redis %s",config.hostsocket);
++} else {
++char addr[256];
++anetFormatAddr(addr, sizeof(addr), config.hostip, config.hostport);
++prompt = sdscatlen(prompt,addr,strlen(addr));
++}
++
+ /* Add [dbnum] if needed */
+ if (config.dbnum != 0)
+-len += snprintf(config.prompt+len,sizeof(config.prompt)-len,"[%d]",
+-config.dbnum);
+-snprintf(config.prompt+len,sizeof(config.prompt)-len,"> ");
++prompt = sdscatfmt(prompt,"[%i]",config.dbnum);
++
++/* Copy the prompt in the static buffer. */
++prompt = sdscatlen(prompt,"> ",2);
++snprintf(config.prompt,sizeof(config.prompt),"%s",prompt);
++sdsfree(prompt);
+ }
+ 
+ /* Return the name of the dotfile for the specified 'dotfilename'.
diff --git 
a/debian/patches/0010-Security-fix-Lua-struct-package-offset-handling.patch 
b/debian/patches/0010-Security-fix-Lua-struct-package-offset-handling.patch
new file mode 100644
index ..8cbc89ce
--- /dev/null
+++ b/debian/patches/0010-Security-fix-Lua-struct-package-offset-handling.patch
@@ -0,0 +1,40 @@
+From: antirez 
+Date: Tue, 15 May 2018 13:13:49 +0200
+Subject: Security: fix Lua struct package offset handling.
+
+After the first fix to the struct package I found another similar
+problem, which is fixed by this patch. It could be reproduced easily by
+running the following script:
+
+return struct.unpack('f', "x",-3)
+
+The above will access bytes before the 'data' pointer.
+---
+ deps/lua/src/lua_struct.c | 8 ++--
+ 1 file changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/deps/lua/src/lua_struct.c b/deps/lua/src/lua_struct.c
+index a602bb4..e263f8e 100644
+--- a/deps/lua/src/lua_struct.c
 b/deps/lua/src/lua_struct.c
+@@ -295,14 +295,18 @@ static int b_unpack (lua_State *L) {
+   const char *fmt = luaL_checkstring(L, 1);
+   size_t ld;
+   const char *data = luaL_checklstring(L, 2, );
+-  size_t pos = luaL_optinteger(L, 3, 1) - 1;
++  size_t pos = luaL_optinteger(L, 3, 1);
++  luaL_argcheck(L, pos > 0, 3, "offset must be 1 or greater");
++  pos--; /* Lua indexes are 1-based, but here we want 0-based for C
++  * pointer math. */
+   defaultoptions();
+   lua_settop(L, 2);
+   while (*fmt) {
+ int opt = *fmt++;
+ size_t size = optsize(L, opt, );
+ pos += gettoalign(pos, , opt, size);
+-luaL_argcheck(L, pos+size <= ld, 2, "data string too short");
++luaL_argcheck(L, size <= ld && pos <= ld - size,
++   2, "data string too short");
+ luaL_checkstack(L, 1, "too many results");
+ switch 

Bug#901521: cinnamon-control-center: fails to clean after build: attempts to distclean in panels/common twice

[Andreas Beckmann]

Source: cinnamon-control-center
Version: 3.8.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

cinnamon-control-center fails to clean after a successful build. It
attempts to perform a distclean in panels/common twice, but then the
Makefile is already gone:

[...]
Making distclean in panels
make[2]: Entering directory '/build/cinnamon-control-center-3.8.0/panels'
Making distclean in common
make[3]: Entering directory '/build/cinnamon-control-center-3.8.0/panels/common'
rm -rf .libs _libs
test -z "liblanguage.la" || rm -f liblanguage.la
rm -f *.o
 rm -f list-languages
rm -f *.lo
rm -f *.tab.c
test -z "" || rm -f 
test . = "." || test -z "" || rm -f 
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -f ./so_locations
rm -rf ./.deps
rm -f Makefile
make[3]: Leaving directory '/build/cinnamon-control-center-3.8.0/panels/common'
Making distclean in common
make[3]: Entering directory '/build/cinnamon-control-center-3.8.0/panels/common'
make[3]: *** No rule to make target 'distclean'.  Stop.
make[3]: Leaving directory '/build/cinnamon-control-center-3.8.0/panels/common'
Makefile:443: recipe for target 'distclean-recursive' failed
make[2]: *** [distclean-recursive] Error 1
make[2]: Leaving directory '/build/cinnamon-control-center-3.8.0/panels'
Makefile:501: recipe for target 'distclean-recursive' failed
make[1]: *** [distclean-recursive] Error 1
make[1]: Leaving directory '/build/cinnamon-control-center-3.8.0'
dh_auto_clean: make -j4 distclean returned exit code 2
debian/rules:11: recipe for target 'clean' failed
make: *** [clean] Error 2


This can be triggered by attempting to build the package twice in a row.


Andreas


cinnamon-control-center_3.8.0-1_twice.log.gz
Description: application/gzip

Bug#901520: scopt: FTBFS with openjdk-10

[Andreas Beckmann]

Source: scopt
Version: 3.5.0-1
Severity: serious
Justification: fails to build from source

Hi,

scopt FTBFS with openjdk-10 as the default jdk:

[...]
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/scopt-3.5.0'
git init
Initialized empty Git repository in /build/scopt-3.5.0/.git/
mkdir -p /build/scopt-3.5.0/debian/sbt_home/.ivy2/cache
cp -fr /build/scopt-3.5.0/bootstrapdeps/* 
/build/scopt-3.5.0/debian/sbt_home/.ivy2/cache/
mkdir /build/scopt-3.5.0/debian/sbt_home/.sbt
echo "[repositories]" > /build/scopt-3.5.0/debian/sbt_home/.sbt/repositories
echo "local" >> /build/scopt-3.5.0/debian/sbt_home/.sbt/repositories
cp -frv /build/scopt-3.5.0/bootstrapdeps-sources/. 
/build/scopt-3.5.0/debian/sbt_home/.ivy2/cache/
'/build/scopt-3.5.0/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs'
 -> 
'/build/scopt-3.5.0/debian/sbt_home/.ivy2/cache/./org.scala-sbt/compiler-interface/srcs'
'/build/scopt-3.5.0/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs/compiler-interface-0.13.12-sources.jar'
 -> 
'/build/scopt-3.5.0/debian/sbt_home/.ivy2/cache/./org.scala-sbt/compiler-interface/srcs/
compiler-interface-0.13.12-sources.jar'
/build/scopt-3.5.0/bootstrapsbt/bin/sbt -verbose -debug -sbt-dir 
/build/scopt-3.5.0/debian/sbt_home/.sbt -ivy 
/build/scopt-3.5.0/debian/sbt_home/.ivy2 'set offline := true' 
-Dsbt.override.build.repos=true packageB
in make-pom
[residual] arg = '-sbt-dir'
[residual] arg = '/build/scopt-3.5.0/debian/sbt_home/.sbt'
[addJava] arg = '-Dsbt.ivy.home=/build/scopt-3.5.0/debian/sbt_home/.ivy2'
[residual] arg = 'set offline := true'
[addJava] arg = '-Dsbt.override.build.repos=true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[addJava] arg = '-Dsbt.global.base=/build/scopt-3.5.0/debian/sbt_home/.sbt'
[residual] arg = 'set offline := true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[process_args] java_version = '10.0.1'
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/scopt-3.5.0/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/scopt-3.5.0/debian/sbt_home/.sbt
-jar
/build/scopt-3.5.0/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/60ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/26ms)
[ERROR] Failed to construct terminal; falling back to unsupported
java.lang.NumberFormatException: For input string: "0x100"
at 
java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.base/java.lang.Integer.parseInt(Integer.java:652)
at java.base/java.lang.Integer.valueOf(Integer.java:983)
at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:233)
at jline.UnixTerminal.(UnixTerminal.java:64)
at jline.UnixTerminal.(UnixTerminal.java:49)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at java.base/java.lang.Class.newInstance(Class.java:560)
at jline.TerminalFactory.getFlavor(TerminalFactory.java:209)
at jline.TerminalFactory.create(TerminalFactory.java:100)
at jline.TerminalFactory.get(TerminalFactory.java:184)
at jline.TerminalFactory.get(TerminalFactory.java:190)
at sbt.ConsoleLogger$.ansiSupported(ConsoleLogger.scala:123)
at sbt.ConsoleLogger$.(ConsoleLogger.scala:117)
at sbt.ConsoleLogger$.(ConsoleLogger.scala)
at sbt.GlobalLogging$.initial(GlobalLogging.scala:43)
at sbt.StandardMain$.initialGlobalLogging(Main.scala:61)
at sbt.StandardMain$.initialState(Main.scala:70)
at sbt.xMain.run(Main.scala:29)
at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109)
at xsbt.boot.Launch$.withContextLoader(Launch.scala:128)
at xsbt.boot.Launch$.run(Launch.scala:109)
at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:35)
at xsbt.boot.Launch$.launch(Launch.scala:117)
at xsbt.boot.Launch$.apply(Launch.scala:18)
at xsbt.boot.Boot$.runImpl(Boot.scala:41)
at xsbt.boot.Boot$.main(Boot.scala:17)
at xsbt.boot.Boot.main(Boot.scala)

error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 

Bug#901519: gdcm: FTBFS: xsltApplySequenceConstructor: A potential infinite template recursion was detected.

[Andreas Beckmann]

Source: gdcm
Version: 2.8.6-2exp1python3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gdcm/experimental FTBFS in an up-to-date minimal sid+experimental
pbuilder environment, in both amd64 and i386:

[323/644] cd /build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen && 
/usr/bin/cmake -E copy /build/gdcm-2.8.6/Utilities/doxygen/man/gdcmdump.xml 
/build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen/gdcmdum
p.xml && /usr/bin/xsltproc --param man.output.quietly 1 --nonet 
/build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen/gdcmdump.xml
FAILED: Utilities/doxygen/gdcmdump.1 
cd /build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen && /usr/bin/cmake 
-E copy /build/gdcm-2.8.6/Utilities/doxygen/man/gdcmdump.xml 
/build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen/gdcmdump.xml && /
usr/bin/xsltproc --param man.output.quietly 1 --nonet 
/build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen/gdcmdump.xml
runtime error: file 
file:/usr/share/xml/docbook/stylesheet/docbook-xsl-ns/lib/lib.xsl line 62 
element variable
xsltApplySequenceConstructor: A potential infinite template recursion was 
detected.
You can adjust xsltMaxDepth (--maxdepth) in order to raise the maximum number 
of nested template calls and variables/params (currently set to 3000).
Templates:
#0 name string.subst 
#1 name string.subst 
#2 name string.subst 
#3 name string.subst 
#4 name string.subst 
#5 name string.subst 
#6 name string.subst 
#7 name string.subst 
#8 name string.subst 
#9 name string.subst 
#10 name string.subst 
#11 name string.subst 
#12 name string.subst 
#13 name string.subst 
#14 name string.subst 
Variables:
#0
replacement 
target 
string 
#1
target 
string 
#2
string 
#3
replacement 
target 
string 
#4
target 
string 
#5
string 
#6
replacement 
target 
string 
#7
target 
string 
#8
string 
#9
replacement 
target 
string 
#10
target 
string 
#11
string 
#12
replacement 
target 
string 
#13
target 
string 
#14
string 
no result for 
/build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen/gdcmdump.xml
[324/644] cd /build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen && 
/usr/bin/cmake -E copy /build/gdcm-2.8.6/Utilities/doxygen/man/gdcmgendir.xml 
/build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen/gdcmgendir.xml && 
/usr/bin/xsltproc --param man.output.quietly 1 --nonet 
/build/gdcm-2.8.6/obj-x86_64-linux-gnu/Utilities/doxygen/gdcmgendir.xml
[325/644] /usr/bin/c++  
-DvtkDomainsChemistry_AUTOINIT="1(vtkDomainsChemistryOpenGL2)" 
-DvtkFiltersCore_AUTOINIT="1(vtkFiltersParallelDIY2)" 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL2)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL2)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLICOpenGL2_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingOpenGL2_AUTOINIT="1(vtkRenderingGL2PSOpenGL2)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL2)" -Dvtkgdcm_EXPORTS 
-I/usr/include/vtk-7.1 -I/usr/include/freetype2 -I/usr/include/x86_64-linux-gnu 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python3.6m 
-I/usr/include/hdf5/openmpi -I/usr/include/jsoncpp -I/usr/include/libxml2 
-I/usr/include/tcl -ISource/Common -I../Source/Common 
-I../Source/DataStructureAndEncodingDefinition 
-I../Source/MediaStorageAndFileFormat -I../Source/DataDictionary 
-I../Utilities/VTK -I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux -g -O2 
-fdebug-prefix-map=/build/gdcm-2.8.6=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC -MD -MT 
Utilities/VTK/CMakeFiles/vtkgdcm.dir/vtkGDCMThreadedImageReader2.cxx.o -MF 
Utilities/VTK/CMakeFiles/vtkgdcm.dir/vtkGDCMThreadedImageReader2.cxx.o.d -o 
Utilities/VTK/CMakeFiles/vtkgdcm.dir/vtkGDCMThreadedImageReader2.cxx.o -c 
../Utilities/VTK/vtkGDCMThreadedImageReader2.cxx
[326/644] /usr/bin/c++  
-DvtkDomainsChemistry_AUTOINIT="1(vtkDomainsChemistryOpenGL2)" 
-DvtkFiltersCore_AUTOINIT="1(vtkFiltersParallelDIY2)" 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL2)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL2)"
 

Bug#901518: protobuf: FTBFS with openjdk-10: error: package sun.misc does not exist

[Andreas Beckmann]

Source: protobuf
Version: 3.6.0.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

protobuf/experimental FTBFS with openjdk-10 as default jdk. I didn't
test the version in sid.

   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/build/protobuf-3.6.0.1'
dh_auto_build --indep
make -j4
make[2]: Entering directory '/build/protobuf-3.6.0.1'
make  all-recursive
make[3]: Entering directory '/build/protobuf-3.6.0.1'
Making all in .
make[4]: Entering directory '/build/protobuf-3.6.0.1'
make[4]: Leaving directory '/build/protobuf-3.6.0.1'
Making all in src
make[4]: Entering directory '/build/protobuf-3.6.0.1/src'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/build/protobuf-3.6.0.1/src'
make[3]: Leaving directory '/build/protobuf-3.6.0.1'
make[2]: Leaving directory '/build/protobuf-3.6.0.1'
# Java build.
ant -f debian/java-build.xml jar
Buildfile: /build/protobuf-3.6.0.1/debian/java-build.xml

generate:
[mkdir] Created dir: 
/build/protobuf-3.6.0.1/java/core/target/generated-sources
 [echo] src

compile:
[mkdir] Created dir: /build/protobuf-3.6.0.1/java/core/target/classes
[javac] Using javac -source 1.5 is no longer supported, switching to 7
[javac] Using javac -target 1.5 is no longer supported, switching to 7
[javac] Release attribute not specified, defaulting to the value of the 
target attribute (7)
[javac] Compiling 79 source files to 
/build/protobuf-3.6.0.1/java/core/target/classes
[javac] Ignoring source, target and bootclasspath as release has been set
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:45:
 error: package sun.misc does not exist
[javac]   private static final sun.misc.Unsafe UNSAFE = getUnsafe();
[javac]^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:292:
 error: package sun.misc does not exist
[javac]   static sun.misc.Unsafe getUnsafe() {
[javac]  ^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:432:
 error: package sun.misc does not exist
[javac] sun.misc.Unsafe unsafe;
[javac] ^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:434:
 error: package sun.misc does not exist
[javac] MemoryAccessor(sun.misc.Unsafe unsafe) {
[javac]^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:511:
 error: package sun.misc does not exist
[javac] JvmMemoryAccessor(sun.misc.Unsafe unsafe) {
[javac]   ^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:293:
 error: package sun.misc does not exist
[javac] sun.misc.Unsafe unsafe = null;
[javac] ^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:297:
 error: package sun.misc does not exist
[javac]   new PrivilegedExceptionAction() {
[javac] ^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:299:
 error: package sun.misc does not exist
[javac] public sun.misc.Unsafe run() throws Exception {
[javac]^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:300:
 error: package sun.misc does not exist
[javac]   Class k = sun.misc.Unsafe.class;
[javac] ^
[javac] 
/build/protobuf-3.6.0.1/java/core/src/main/java/com/google/protobuf/UnsafeUtil.java:300:
 error: package sun.misc does not exist
[javac]   Class k = sun.misc.Unsafe.class;
[javac]  ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 10 errors

BUILD FAILED
/build/protobuf-3.6.0.1/debian/java-build.xml:27: Compile failed; see the 
compiler error output for details.

Total time: 5 seconds
make[1]: *** [debian/rules:69: override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/build/protobuf-3.6.0.1'
make: *** [debian/rules:18: build] Error 2


Andreas


protobuf_3.6.0.1-1.log.gz
Description: application/gzip

Bug#901517: ITP: opa-fm -- Intel Omni-Path Fabric Management Software

[Roland Fehrenbacher]

Package: wnpp
Severity: wishlist

Homepage: https://github.com/intel/opa-fm
License: BSD-3-clause

The Intel(R) Omni-Path Fabric Management Software contains Intel Omni-Path
fabric management applications. This includes: the Subnet Manager,
Baseboard Manager, Performance Manager, Fabric Executive, and some fabric
management tools.

Cheers,

Roland

---
http://www.q-leap.com / http://qlustar.com
  --- HPC / Storage / Cloud Linux Cluster OS ---

Bug#901516: sbt-serialization: FTBFS with openjdk-10: NumberFormatException: For input string: "0x100"

[Andreas Beckmann]

Package: sbt-serialization
Version: 0.1.2-1
Severity: serious
Justification: fails to build from source

sbt-serialization FTBFS with openjdk-10 as default jdk:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/sbt-serialization-0.1.2'
git init
Initialized empty Git repository in /build/sbt-serialization-0.1.2/.git/
mkdir -p /build/sbt-serialization-0.1.2/debian/sbt_home/.ivy2/cache
cp -fr /build/sbt-serialization-0.1.2/bootstrapdeps/* 
/build/sbt-serialization-0.1.2/debian/sbt_home/.ivy2/cache/
mkdir /build/sbt-serialization-0.1.2/debian/sbt_home/.sbt
echo "[repositories]" > 
/build/sbt-serialization-0.1.2/debian/sbt_home/.sbt/repositories
echo "local" >> /build/sbt-serialization-0.1.2/debian/sbt_home/.sbt/repositories
cp -frv /build/sbt-serialization-0.1.2/bootstrapdeps-sources/. 
/build/sbt-serialization-0.1.2/debian/sbt_home/.ivy2/cache/
'/build/sbt-serialization-0.1.2/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs'
 -> 
'/build/sbt-serialization-0.1.2/debian/sbt_home/.ivy2/cache/./org.scala-sbt/compiler-interface/srcs'
'/build/sbt-serialization-0.1.2/bootstrapdeps-sources/./org.scala-sbt/compiler-interface/srcs/compiler-interface-0.13.12-sources.jar'
 -> '/build/sbt-serialization-0.1.2/debian/sbt_home/.ivy2/cache/./org.scala-sbt/
compiler-interface/srcs/compiler-interface-0.13.12-sources.jar'
/build/sbt-serialization-0.1.2/bootstrapsbt/bin/sbt -verbose -debug -sbt-dir 
/build/sbt-serialization-0.1.2/debian/sbt_home/.sbt -ivy 
/build/sbt-serialization-0.1.2/debian/sbt_home/.ivy2 'set offline := true' -Dsb
t.override.build.repos=true packageBin make-pom
[residual] arg = '-sbt-dir'
[residual] arg = '/build/sbt-serialization-0.1.2/debian/sbt_home/.sbt'
[addJava] arg = 
'-Dsbt.ivy.home=/build/sbt-serialization-0.1.2/debian/sbt_home/.ivy2'
[residual] arg = 'set offline := true'
[addJava] arg = '-Dsbt.override.build.repos=true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[addJava] arg = 
'-Dsbt.global.base=/build/sbt-serialization-0.1.2/debian/sbt_home/.sbt'
[residual] arg = 'set offline := true'
[residual] arg = 'packageBin'
[residual] arg = 'make-pom'
[process_args] java_version = '10.0.1'
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/sbt-serialization-0.1.2/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/sbt-serialization-0.1.2/debian/sbt_home/.sbt
-jar
/build/sbt-serialization-0.1.2/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/56ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/24ms)
[ERROR] Failed to construct terminal; falling back to unsupported
java.lang.NumberFormatException: For input string: "0x100"
at 
java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.base/java.lang.Integer.parseInt(Integer.java:652)
at java.base/java.lang.Integer.valueOf(Integer.java:983)
at jline.internal.InfoCmp.parseInfoCmp(InfoCmp.java:59)
at jline.UnixTerminal.parseInfoCmp(UnixTerminal.java:233)
at jline.UnixTerminal.(UnixTerminal.java:64)
at jline.UnixTerminal.(UnixTerminal.java:49)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at java.base/java.lang.Class.newInstance(Class.java:560)
at jline.TerminalFactory.getFlavor(TerminalFactory.java:209)
at jline.TerminalFactory.create(TerminalFactory.java:100)
at jline.TerminalFactory.get(TerminalFactory.java:184)
at jline.TerminalFactory.get(TerminalFactory.java:190)
at sbt.ConsoleLogger$.ansiSupported(ConsoleLogger.scala:123)
at sbt.ConsoleLogger$.(ConsoleLogger.scala:117)
at sbt.ConsoleLogger$.(ConsoleLogger.scala)
at sbt.GlobalLogging$.initial(GlobalLogging.scala:43)
at sbt.StandardMain$.initialGlobalLogging(Main.scala:61)
at sbt.StandardMain$.initialState(Main.scala:70)
at sbt.xMain.run(Main.scala:29)
at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109)
at xsbt.boot.Launch$.withContextLoader(Launch.scala:128)
at xsbt.boot.Launch$.run(Launch.scala:109)
at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:35)
at xsbt.boot.Launch$.launch(Launch.scala:117)
at 

Bug#901030: some context

[Ian Jackson]

Antonio Terceiro writes ("Bug#901030: some context"):
> the problem here is that by definition, some types of testbed don't
> allow you to test some packages.

Right, but in principle these testbeds could.  All that is needed is
to install binfmt-misc in the host.  I am suggesting that this should
be fixed by having the container virt server packages depend on
binfmt-misc.

> in this specific case, there is just no
> way you can reliably test a feature that depends on a kernel feature in
> a container.

As a general rule, what you say is clearly not true.  "Being able to
run amd64 binaries" is a kernel feature which is generally available
in amd64 containers :-).  And many more sophisticated kernel features
are containerisable (in the sense that they can be used in the
container, even if the host doesn't want to know about it, and even if
they require root).

But, our whole dependency scheme does not really handle kernel
features.  binfmt-misc is a helper for accessing a kernel feature -
one which is available in containers but not configurable separately
from the host.


Stepping back a bit: if we don't wnat to make adt-virt-lxc depend on
binfmt-misc, we could do something more sophisticated:

Define two new DEP-8 test fieldc:
  Virt-Server-Capability-Depends
  Virt-Server-Capability-Conflicts

These are in Depends field syntax but the referred-to names are not
packages but capabilities from the virt server protocol.

We provide both, so that test authors have the choice between
(i) using Depends, and experiencing unnecessary test skips;
(ii) using Conflicts, and expericing spurious test failures.

We also define new conventional capability syntaxes:
bug-*
bug-debianN
for use in Virt-Server-Capability-Conflicts.  (-Conflicts should
usually be used rather than -Depends, because other virt servers
who do not have the bug should not be required to advertise it.)

We only need to teach autopkgtest about the field names, and then the
affected packages can conspire as follows.

  Package: something-needing-binfmt
  Virt-Server-Capability-Conflicts: bug-debian901030

And then adt-virt-lxc can advertise a `capability' bug-debian901030.
Indeed, if we want to get clever, adt-virt-lxc can do so if:
  * binfmt-misc is not installed on the host
and
  * the kernel has not been fixed to support per-container binfmt handling

Also, virt servers should gain a runtime option for the administrator
to have them advertise capabilities.  That way it is not necessary to
update the software when a new bug is discovered: the admin can update
the config.


What do people think ?

Ian.

-- 
Ian JacksonThese opinions are my own.

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

Bug#901514: ITP: opa-ff -- Tools to manage an Omni-Path Architecture fabric.

[Roland Fehrenbacher]

Package: wnpp
Severity: wishlist

Homepage: https://github.com/intel/opa-ff
License: BSD-3-clause

The package contains basic tools and libraries for the management of an
Intel(R) Omni-Path Architecture fabric.
 
Cheers,

Roland

---
http://www.q-leap.com / http://qlustar.com
  --- HPC / Storage / Cloud Linux Cluster OS ---

Bug#901515: RM: relion [arm64 armel armhf mips mips64el mipsel ppc64el s390x alpha hppa hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k powerpc powerpcspe ppc64 riscv64 sh4 sparc64 x32] -- ROM; R

[Andreas Tille]

Package: ftp.debian.org
Severity: normal

Hi,

as it was discussed in bug #897239 relion should be restricted to
architectures amd64 and i386.  Please remove the other architectures.

Thanks for your work as ftpmaster

 Andreas.

Bug#901497: Hard system hangs after upgrade from 18.0.5-1 to 18.1.1-1

[Stuart Young]

Which specific versions of Firefox are you using?

Are you using FlashPlayer with Firefox at all, and if so, which version?

On Thu, 14 Jun 2018 at 20:24, Tehnic  wrote:

> Exactly the same problem here with this URL:
>
> https://www.golem.de/news/spionagevorwurf-eu-parlament-will-kaspersky-l
> oswerden-1806-134949.html
> 
>
> I can reproduce the effect with Firefox and Firefox ESR. Chromium is
> not affected by this.
>
> I not downgraded until now so if you need more information please
> contact me.
>
> Regards, Robert
>
> --
> Tehnic 
>
>

-- 
Stuart Young (aka Cefiar)

Bug#901495: redis: multiple security issues in Lua scripting

[Chris Lamb]

Hi,

> redis: multiple security issues in Lua scripting

This has now been assigned CVE-2018-11219 & CVE-2018-11218.


Regards,

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

Bug#863919: Fixed in https://salsa.debian.org/science-team/sympow/merge_requests/1

[Julian Rüth]

I don't pretend to understand sympow's malloc/free logic, but the
changes in my merge request fix this specific issue for me.

https://salsa.debian.org/science-team/sympow/merge_requests/1

Bug#901512: python3: Python doesn't register with the debian alternatives system

[Piotr Ożarowski]

Control: tags -1 +wontfix
Control: severity -1 wishlist

/usr/bin/python points to default Python 2.X version and we support python2.7 
only
right now. The only change planned for 2.X is to remove 2.7 from list of
supported 2.X versions.

Python 3 is a completely different language from our POV so
/usr/bin/python will never point to python3. When 2.7 will be removed
from supported versions - /usr/bin/python will disappear.

Bug#901513: slurm-client: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/sacctmgr, /usr/share/man/man1/sacctmgr.1.gz

[Andreas Beckmann]

Package: slurm-client
Version: 14.03.9-5+deb8u1
Severity: serious
Tags: jessie
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package slurm-client.
  Unpacking slurm-client (from .../slurm-client_14.03.9-5+deb8u1_amd64.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/slurm-client_14.03.9-5+deb8u1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/sacctmgr.1.gz', which is also in 
package slurm-llnl-slurmdbd 2.3.4-2+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/slurm-client_14.03.9-5+deb8u1_amd64.deb

The conflicting files are:

  usr/bin/sacctmgr
  usr/share/man/man1/sacctmgr.1.gz

This should be fixable by adding
  Breaks+Replaces: slurm-llnl-slurmdbd (<< 14.03.9-5)
(The existing B+R: slurmdbd (<< 14.03.9-5) is probably incorrect and was
intended to do this, but better keep it in place ...)

Please note that the window for the final jessie point release closes
this weekend ...


cheers,

Andreas


slurm-llnl-slurmdbd=2.3.4-2+b1_slurm-client=14.03.9-5+deb8u1.log.gz
Description: application/gzip

Bug#859130: diff -ur gitrepo/ origtar/ && collab

[Geert Stappers]

On Tue, Jun 12, 2018 at 04:55:48PM +0200, Albert van der Horst wrote:
> 
> Even so, if a Debian developer thinks the ciforth compiler
> factory is a valuable addition *to a debian distribution*, (s)he is
> free to fork ciforth and get it accepted.

I prefer collaboration over forking.

>  [ ... ]
> Remember how this started?

It started as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859130#5
  "Source code in git getting packaged for Debian"
For me it still is.


I'm aware that am in no position to demand something,
but I do take the liberity to express what I want and don't want.

Wanted:

Upon having a directory with a subdirectory containing the git repo
and another subdir containing the orig tarball should
 git -ur --exclude=.git  git_repo_dir/  orig_tarball_dir/
report _no differences_

Not wanted:

* Binary files like .tar.gz inside a git repo
* Commits on binaries like 
https://github.com/albertvanderhorst/ciforth/commit/2db78aee03e75564e67209075f5ba1cfa14ee944
 

>  [ ... ]
> 
> I welcome a new sponsor!
 
There was no old sponsor, there is no current sponsor.

There is a wannabe sponsor
who is doing reviews on what is uploaded
to https://mentors.debian.net/package/lina


Groeten
Geert Stappers
DD
-- 
Leven en laten leven


signature.asc
Description: Digital signature

Bug#901512: python3: Python doesn't register with the debian alternatives system

[sungazer]

Package: python3
Version: 3.5.3-1
Severity: important

Dear Maintainer,

Shouldn't python be registering with the debian alternatives system, so that 
update-alternatives allows things like /usr/bin/python to symlink to the 
desired version when multiple python versions are installed?

Currently, with 2.7 and 3.5 installed, I have to do it all by hand if I want to 
make python3 the default, and this feels undebian and like I might be missing 
important things because /usr/bin also contains stuff like python-config and 
python3m which I guess might need symlinking too and I don't know if there are 
libs anywhere that need similar treatment, or stuff in other packages that 
assumes python will always be python version 2 and might break so an official 
supported way of changing python version via update-alternatives would be 
really good.

Thanks!

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

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

Versions of packages python3 depends on:
ii  dh-python  2.20170125
ii  libpython3-stdlib  3.5.3-1
ii  python3-minimal3.5.3-1
ii  python3.5  3.5.3-1

python3 recommends no packages.

Versions of packages python3 suggests:
pn  python3-doc   
pn  python3-tk
pn  python3-venv  

-- no debconf information

Bug#787816: Replace FHS 2.3 by FHS 3.0 in the Policy.

[Simon McVittie]

On Fri, 05 Jun 2015 at 20:43:10 +0900, Charles Plessy wrote:
> Le Thu, Jun 04, 2015 at 07:09:00PM -0700, Russ Allbery a écrit :
> > I have not looked at this at all, but this list should be aware that it
> > exists.
> 
> > The LSB workgroup is happy to announce the release of FHS 3.0.
> ... 
> > Release notes can be found here:
> > 
> > https://wiki.linuxfoundation.org/en/FHSReleaseNotes30

Unfortunately those release notes have vanished, but a copy can be found at:
https://web.archive.org/web/20160624022300/wiki.linuxfoundation.org/en/FHSReleaseNotes30

I've prepared patches for this, which are available here:
https://salsa.debian.org/smcv/policy/merge_requests/1/diffs

I've attached them here, except for the patch that replaces the bundled
copy of FHS v2.3 with a bundled copy of FHS v3.0, which is inconveniently
large. I think patch 0002 is the only normative one?

The only thing I found that would make Debian non-compliant is the
fact that the /usr/bin/mh/ directory used to be allowed, but is not
allowed any more. For the moment I think this should be documented as a
departure from FHS v3.0, and if anyone cares enough about removing that
exception, it should be discussed with the maintainers of nmh (which ships
/usr/bin/mh/) and mailutils-mh (which is technically non-Policy-compliant,
although does comply with the spirit of the policy) on a separate bug.

I got my copy of the FHS source code from
http://refspecs.linuxfoundation.org/FHS_3.0/ (which contains source and
compiled copies), not from
http://bzr.linuxfoundation.org/loggerhead/lsb/devel/fhs-spec/changes
(which I only found later), and I didn't include the bundled copy of
docbook-xsl or the outdated FHS in draft.sgml. I used a directory
instead of a tarball, for better transparency.

> By the way, I wonder if the debian-policy package is the best place for
> shipping a copy of the FHS.

Probably not, but let's not delay its adoption by another 3 years while
we paint that particular bike shed :-)

smcv
>From 8867b0b88d311739fd360f1f6dc945406c39ed54 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 14 Jun 2018 11:43:04 +0100
Subject: [PATCH 2/3] Update to FHS v3.0

Notable changes that this causes:

* A GNU-style /usr/libexec is now allowed.

Notable non-changes:

* /usr/games, /usr/share/games and /usr/lib/games were optional in
  FHS 2.3, and are still optional. It is up to us whether we want
  to keep using those directories.

Drop our special exception for /run, and replace it with a requirement
that the pairs (/run, /var/run) and (/run/lock, /var/lock) are made
equivalent via symlinks or bind mounts. The FHS does not mandate this
(although I think it should) and some misguided distributions make
/run and /var/run non-equivalent, but they have always been equivalent
on Debian.

Drop our special exception for /sys, which is now standardized in the
FHS.

Add a special exception for /usr/bin/mh/ for now, restoring the FHS
2.3 situation (dropping this might be a good idea, but should be
disussed with the nmh and mailutils-mh maintainers if desired).

Signed-off-by: Simon McVittie 
Closes: #787816
---
 policy/ch-opersys.rst | 29 ++---
 1 file changed, 10 insertions(+), 19 deletions(-)

diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst
index 7d85c00..b18e2c2 100644
--- a/policy/ch-opersys.rst
+++ b/policy/ch-opersys.rst
@@ -12,7 +12,7 @@ File System Structure
 ~
 
 The location of all files and directories must comply with the
-Filesystem Hierarchy Standard (FHS), version 2.3, with the exceptions
+Filesystem Hierarchy Standard (FHS), version 3.0, with the exceptions
 noted below, and except where doing so would violate other terms of
 Debian Policy. The following exceptions to the FHS apply:
 
@@ -76,25 +76,20 @@ Debian Policy. The following exceptions to the FHS apply:
 ``/etc``, or at least are symlinked there, is relaxed to a
 recommendation.
 
-8.  The additional directory ``/run`` in the root file system is
-allowed. ``/run`` replaces ``/var/run``, and the subdirectory
-``/run/lock`` replaces ``/var/lock``, with the ``/var`` directories
-replaced by symlinks for backwards compatibility. ``/run`` and
-``/run/lock`` must follow all of the requirements in the FHS for
-``/var/run`` and ``/var/lock``, respectively, such as file naming
-conventions, file format requirements, or the requirement that files
-be cleared during the boot process. Files and directories residing
-in ``/run`` should be stored on a temporary file system.
+8.  The ``/var/run`` and ``/var/lock`` directories are required to be
+made equivalent to ``/run`` and ``/run/lock`` respectively, for
+example using symbolic links or bind-mounts.
 
-9.  The ``/sys`` directory in the root filesystem is additionally
-allowed.  [#]_
+9.  The ``/var/www`` directory is additionally allowed.
 
-10. The ``/var/www`` directory is additionally allowed.
-
-11. The requirement for 

Bug#567033: Decide if we should continue recommending /usr/games

[Simon McVittie]

Control: unmerge 567033

On Fri, 11 Aug 2017 at 07:07:49 -0700, Sean Whitton wrote:
> The latest version of the FHS does not have /usr/games, so merging this
> with the bug about updating our FHS version.

Removing the games directories was considered in

and , but there
was no consensus. The FHS 3.0 as published by the Linux Foundation says
essentially the same things games as FHS 2.3:

> [/usr/]games  Games and educational binaries (optional)
> ...
> [/usr/share/]gamesStatic data files for /usr/games (optional)
> ...
> Similarly, a /usr/lib/games hierarchy may be used in addition to the
> /usr/share/games hierarchy if the distributor wishes to place some game
> data there.

(/usr/local/games is technically also mandatory, although I'm sure
that's an oversight and it was meant to be optional...)

Debian can choose to put games in the /.../games directories, or in the
standard directories /usr/bin, /usr/share etc., or any mixture of our
choice, orthogonal to whether/when we move to FHS 3.0.

smcv

Bug#901501: RFP: powerline-gitstatus -- Powerline Git segment

[Daniel Baumann]

close 901501
thanks

Jerome already uploaded a package based on mine, waiting currently in
NEW (900661), hence closing this RFP.

Regards,
Daniel

Bug#901497: Hard system hangs after upgrade from 18.0.5-1 to 18.1.1-1

[Tehnic]

Exactly the same problem here with this URL:

https://www.golem.de/news/spionagevorwurf-eu-parlament-will-kaspersky-l
oswerden-1806-134949.html

I can reproduce the effect with Firefox and Firefox ESR. Chromium is
not affected by this.

I not downgraded until now so if you need more information please
contact me.

Regards, Robert

-- 
Tehnic 

Bug#880920: Document Rules-Requires-Root field

[Paul Gevers]

I want to second this text, but have some questions.

> diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
> index 0771346..3519d99 100644
> --- a/policy/ch-controlfields.rst
> +++ b/policy/ch-controlfields.rst

> @@ -1020,6 +1022,118 @@ This field is automatically added to Debian source 
> control files
>  field may also be used in source package control files
>  (``debian/control``) if needed in other situations.
>
> +.. _s-f-Rules-Requires-Root:
> +
> +``Rules-Requires-Root``
> +~~~
> +
> +Simple field that defines if the source package requires access to
> +root (or fakeroot) during selected targets in the :ref:`Main building
> +script: debian/rules `.
> +
> +The field can consist of exactly one of the following three items:
> +
> + - ``no``: Declares that neither root nor fakeroot is required.
> +   Package builders (e.g. dpkg-buildpackage) may choose to invoke any
> +   target in ``debian/rules`` with an unprivileged user.
> +
> + - ``binary-targets`` (default): Declares that the package will need
> +   the root (or fakeroot) when either of the ``binary``,
> +   ``binary-arch`` or ``binary-indep`` targets are called.  This is
> +   how every tool behaved before this field was defined.
> +
> + - A space separated list of keywords described below.  These must
> +   always contain a forward slash, which sets them apart from the
> +   other values.  When this list is provided, the builder must provide

^^ plural here, makes sense.

> +   a `gain root command` (as defined in :ref:`debian/rules and
> +   Rules-Requires-Root `) *or* pretend that
> +   the value was set to ``binary-targets``, and both the builder and
> +   the package's ``debian/rules`` script must downgrade accordingly
> +   (see below).
> +
> +If the package builder supports the ``Rules-Requires-Root`` field and
> +want to enable the feature, then it must set the environment variable
> +``DEB_RULES_REQUIRES_ROOT`` when invoking the package building script
> +``debian/rules``.  The value of ``DEB_RULES_REQUIRES_ROOT`` should be
> +one of:
> +
> + * The value of ``Rules-Requires-Root`` if the builder can support

  ^ singular here. I find this ambiguous. I think you mean
to treat the list of values above as one variable by calling it singular
here, a suggested by the remark about space below.

> +   that value.  The builder may trim unnecessary whitespace used to
> +   format the field for readability.
> +
> + * The value ``binary-targets`` if it cannot support the value of
> +   ``Rules-Requires-Root``.
> +
> +A compliant builder may also leave ``DEB_RULES_REQUIRES_ROOT`` unset
> +or set it to ``binary-targets`` if it has been requested to test
> +whether the package it builds correctly implements the fall-back for
> +legacy builders.
> +
> +Remarks
> +^^^
> +
> +All packages and builders must support ``binary-targets`` as this was
> +the historical behaviour prior to the introduction of this field.
> +
> +Any tool (partiularly older versions of them) may be unaware of this
> +field and behave like the field was set to ``binary-targets``.  The
> +package build must gracefully cope with this and produce a
> +semantically equivalent result.
> +
> +This field intentionally does not enable a package to request a true
> +root over fakeroot.

Apparently some details in the implementation are unclear to me, as I
don't get this statement if the example at the end includes a sudo
example. Isn't that a true root or is that not what you mean? Is only
$(su root) a real root (and why wouldn't that work)?

> +
> +Definition of the keywords
> +^^
> +
> +The keywords have the format ``/``, where:
> +
> + *  must consist entirely of printable ASCII characters
> +   except for any whitespace and the forward slash (``/``).  It must
> +   consist of at least 2 characters.
> +
> + * ``/`` (between  and ) is a single ASCII
> +   forward slash.
> +
> + *  must consist entirely of printable ASCII characters
> +   except for any whitespace.  It must consist of at least 2
> +   characters.
> +
> +These keywords define where the package build script ``debian/rules``,
> +or the tools called by that script, will need access to root or
> +fakeroot.
> +
> +In addition to the keywords defined in the next section, each tool or
> +package may define keywords within a namespace named after that tool
> +or package.  The package or tool is considered to own that namespace.
> +
> +A tool may use the `gain root command` to do something under

  ^^^ a?
   ^ should this be linked to the
*section describing it? It drops out of thin air here.

> +(fake)root if and only if the tool defines an appropriate keyword in
> +its namespace, and the package lists that keyword in
> +``Rules-Requires-Root``.
> +
> +All tools must ignore keywords under namespaces they do not know or
> +own.  A tool may emit a warning, or abort with 

Bug#901511: RM: openmolar -- ROM; discontinued upstream

[Dmitry Smirnov]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-med-packag...@lists.alioth.debian.org, n...@openmolar.com

Openmolar is one of a kind software without (free) alternatives but regretfully
it was discontinued upstream:

 http://openmolar.com/news/2017/01/18/id25/

Please remove "openmolar" from "unstable".

-- 
Best wishes,
 Dmitry Smirnov.

---

Good luck happens when preparedness meets opportunity.


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

Bug#901510: RFS: ddupdate/0.6.1-2 (Upstream bugs #11, #12, #13)

[Alec Leamas]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "ddupdate"

 * Package name: ddupdate
   Version : 0.6.1-2
   Upstream Author : Alec Leamas
 * URL : https://github.com/leamas/ddupdate
 * License : MIT
   Section : net

It builds those binary packages:

ddupdate   - Tool updating DNS data for dynamic IP addresses

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

  https://mentors.debian.net/package/ddupdate

Alternatively, one can download the package with dget using:

dget -x
https://mentors.debian.net/debian/pool/main/d/ddupdate/ddupdate_0.6.1-2.dsc

More information about ddupdate can be obtained from github homepage.

Changes since the last upload (merging 0.6.1-1 and 0.6.2-1)
  * Fix packaging glitches: standards-version, whitespace
  * Add missing debian/upstream/metadata.
  * New upstream maintenance release

Upstream bugs fixed by upstream release: #11, #12, #13 at
   https://github.com/leamas/ddupdate/issues?q=is%3Aissue+is%3Aclosed


Regards,
   Alec

Bug#901509: RFP: libhandy -- GTK+ widgets for mobile phones

[Guido Günther]

Package: wnpp
Severity: wishlist

* Package name: libhandy
  Version : 0.0.1
  Upstream Author : Guido Günther 
Adrien Plazas 
* URL : https://source.puri.sm/Librem5/libhandy
* License : LGPL
  Programming Lang: C
  Description : GTK+ widgets for mobile phones

Set of widgets to ease developing GTK+/GNOME applications for mobile
phones and other devices with small screens.

Basic packaging is already there. We mostly need to switch from 1.0
native to 3.0 quilt. I might pick that up if nobody else grabs it
beforehand.

Bug#901470: apparmor-utils: aa-logprof prints a lot of garbage with "Error: Unknown line found in file"

[intrigeri]

Control: tag -1 + upstream
Control: tag -1 + fixed-upstream
Control: forwarded -1 https://gitlab.com/apparmor/apparmor/merge_requests/110

Hi Vincas,

Vincas Dargis:
> This is what I get with `aa-logprof` after installing 2.13 from
> experimental (no reboot yet):

At first glance this looks like:

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

Can you please confirm that MR fixes this problem for you?
If it does I'll import it into debian/patches.

Bug#833692: pinot: links GPLv2+ code with OpenSSL

[Jonas Smedegaard]

Quoting Olly Betts (2018-06-14 04:29:27)
> On Thu, Jun 14, 2018 at 12:45:38AM +0200, Jonas Smedegaard wrote:
>> I still like pinot and believe there is a use for it in Debian as 
>> alternative to extract and tracker.  But evidently it keeps falling 
>> too low on my priority list :-(
>> 
>> Please do adopt it.  Or co-maintain it with me, if you prefer that.
>
> Sounds good.  I've made a start on preparing an upload.
>
> It looks like the packaging was on collab-maint which has now gone - 
> do you have a checkout of it handy?  Not vital, but preserving the 
> history seems useful if it's easy to do.

https://salsa.debian.org/debian/pinot


Thanks a lot for co-maintaining!  Please do tell if you have any 
questions or disagree with how some stuff was done in the past - or 
simply change things and inform me, if you prefer (we are in it together 
- equally!).


 - 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#901508: rinse: centos-7/post-install.sh dosent use $http_proxy

[Reiner Schulz]

Package: rinse
Version: 3.2
Severity: normal
Tags: upstream

Dear Maintainer,

   * What led up to the situation?
  building centos7 basefile for FAI

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
  root@debian9:/var/rinse# http_proxy=http:/// 
   /usr/sbin/rinse --directory  /var/rinse/ --distribution centos-7 
--arch amd64 --cache 0  --verbose

   * What was the outcome of this action?
Bootstrapping yum
Loaded plugins: fastestmirror, keys, protectbase
Determining fastest mirrors
Could not retrieve mirrorlist
http://mirrorlist.centos.org/?release=7=x86_64=os=stock
error was
12: Timeout on
http://mirrorlist.centos.org/?release=7=x86_64=os=stock:
(28, 'Connection timed out after 30001 milliseconds')
  cleaning up...


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages rinse depends on:
ii  cpio   2.11+dfsg-6
ii  libterm-size-perl  0.207-1+b4
ii  libwww-perl6.15-1
ii  perl   5.24.1-3+deb9u2
ii  rpm4.12.0.2+dfsg1-2
ii  rpm2cpio   4.12.0.2+dfsg1-2
ii  wget   1.18-5+deb9u1

rinse recommends no packages.

rinse suggests no packages.

-- Configuration Files:
/etc/rinse/centos-7.packages changed [not included]

-- no debconf information

Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.

[Ian Campbell]

On Wed, 2018-06-13 at 12:25 -0700, Geoff Levand wrote:
> On 06/09/2018 05:15 AM, Ian Campbell wrote:
> 
> > I think this is probably something for the arch (or perhaps
> > platform)
> > code to deal with. See for example all the various platform quirks
> > in
> > arch/x86/kernel/acpi/boot.c, which fixup various wrongness and/or
> > disable features.
> 
> I followed your advice and created a fix in the arm64 acpi init
> code of arch/arm64/kernel/acpi.c.  Here's the submission:
> 
>   https://marc.info/?l=linux-acpi=152891415600796=2
>   https://www.spinics.net/lists/linux-acpi/msg82887.html

Thanks!

Bug#901507: lintian: warn if debhelper, dh-* are in B-D-Arch or B-D-Indep but not Build-Depends

[Simon McVittie]

Package: lintian
Version: 2.5.90
Severity: wishlist

Packages that use debhelper normally invoke it in their clean target,
which according to Policy §7.7 can only rely on having the Build-Depends
available. If a source package only provides Architecture: all binaries,
maintainers are often tempted to put debhelper in Build-Depends-Indep,
but that would make `sbuild --dist=unstable --source --no-arch-any .`
(normally a way to build a clean, canonical source package) fail.
Similarly, if a source package has no Architecture: all binaries,
maintainers might be tempted to put debhelper in Build-Depends-Arch,
but that will cause the same command to fail.

I think it would be useful for lintian to issue a
warning in this case, similar to the experimental
libmodule-build-perl-needs-to-be-in-build-depends and
libmodule-build-tiny-perl-needs-to-be-in-build-depends tags.

The same is true for packages that provide debhelper sequences.
`apt-file search /usr/share/perl5/Debian/Debhelper/Sequence` tells me
there are more packages providing debhelper sequences than I had expected,
so it might be best if this warning is issued for packages that are
normally only useful as a source of debhelper addons, such as dh-*,
pkg-kde-tools and pkg-php-tools, but maybe not (for example)
bash-completion, cme or gem2deb.

Maybe debhelper-needs-to-be-in-build-depends for debhelper itself and
debhelper-addon-needs-to-be-in-build-depends for build systems and
sequences?

debhelper-like frameworks like cdbs have the same issue. cdbs is
probably the only one common enough to justify its own tag.

Regards,
smcv

Bug#886291: pycryptodome naming

[Petter Reinholdtsen]

[Andres Salomon]
> I modified the package to provide/conflict with python-crypto, and that
> seems to work.  I didn't test upgrade paths, though.

Would it be better to introduce a extra set of Crypto compatible packages?
It would allow those packages using the current namespace to keep working
without changes, and allow them to use the "compat" packages if they
want to.

I just uploaded python-httpsig with the following patch to get it to work
with Cryptodome, and it was not too intrusive:

Index: python-httpsig/httpsig/sign.py
===
--- python-httpsig.orig/httpsig/sign.py 2018-06-14 08:37:32.408021349 +
+++ python-httpsig/httpsig/sign.py  2018-06-14 08:37:32.408021349 +
@@ -1,9 +1,9 @@
 import base64
 import six
 
-from Crypto.Hash import HMAC
-from Crypto.PublicKey import RSA
-from Crypto.Signature import PKCS1_v1_5
+from Cryptodome.Hash import HMAC
+from Cryptodome.PublicKey import RSA
+from Cryptodome.Signature import PKCS1_v1_5
 
 from .utils import *
 
Index: python-httpsig/httpsig/utils.py
===
--- python-httpsig.orig/httpsig/utils.py2018-06-14 08:37:32.408021349 
+
+++ python-httpsig/httpsig/utils.py 2018-06-14 08:37:32.408021349 +
@@ -11,7 +11,7 @@
 # Python 2
 from urllib2 import parse_http_list
 
-from Crypto.Hash import SHA, SHA256, SHA512
+from Cryptodome.Hash import SHA, SHA256, SHA512
 
 ALGORITHMS = frozenset([
 'rsa-sha1',
Index: python-httpsig/setup.py
===
--- python-httpsig.orig/setup.py2018-06-14 08:37:44.912143622 +
+++ python-httpsig/setup.py 2018-06-14 08:42:15.662330444 +
@@ -37,6 +37,6 @@
 zip_safe=True,
 #use_scm_version=True,
 setup_requires=['setuptools_scm'],
-install_requires=['pycryptodome>=3.4.7', 'six'],
+install_requires=['pycryptodomex>=3.4.7', 'six'],
 test_suite="httpsig.tests",
 )

Bug#901486: python/python3: no package currently in testing/unstable/experimental ships the python policy

[Julian Gilbey]

On Thu, Jun 14, 2018 at 12:14:58AM +0200, Matthias Klose wrote:
> > Hiya,
> > 
> > I just upgraded my testing machine to python 2.7.15-3, which says in
> > its changelog:
> >* Remove the Debian Python policy, now found in the python3 package.
> > 
> > Unfortunately that is not the case: the python3 package does not ship
> > this file (at least not as of version 3.6.5-3 or experimental version
> > 3.6.5-5).  Probably an oversight.
> 
> yes, will be fixed with the next upload.


Thanks Matthias!

   Julian

Bug#901506: RFP: port-for -- local TCP ports managment

[Daniel Baumann]

Package: wnpp
Severity: wishlist

Hi,

it would be nice if someone would maintain port-for in
Debian. I made a ready-to-be-uploaded package available here:

  https://salsa.debian.org/daniel-guest/port-for

It is used as a dependency by sphinx-autobuild, which is available at:

  https://salsa.debian.org/daniel-guest/sphinx-autobuild

Regards,
Daniel

Bug#897217: debian-policy: Vcs-Hg should support -b too

[Andrej Shadura]

On Mon, 30 Apr 2018 09:55:03 +0200 Samuel Thibault
 wrote:
> Hello,
> 
> In 5.6.26, one can read about Vcs-:
> 
> "In the case of Git, the value consists of a URL, optionally followed by
> the word -b the name of a branch in the indicated repository, following
> the syntax of the git clone command".
> 
> It would be useful to have the same for Hg, for instance:
> 
> "In the case of Git and Hg, the value consists of a URL, optionally
> followed by the word -b the name of a branch in the indicated
> repository, following the syntax of the git clone and hg clone
> commands".

Actually, with hg there’s not much need for this since the native hg URL
format supports specifying the branch to check out in a URL fragment:
https://server.org/path/to/repo#branch.

-- 
Cheers,
  Andrej

Bug#901505: RFP: sphinx-autobuild -- Automatically rebuild Sphinx documentation

[Daniel Baumann]

Package: wnpp
Severity: wishlist

Hi,

it would be nice if someone would maintain sphinx-autobuild in
Debian. I made a ready-to-be-uploaded package available here:

  https://salsa.debian.org/daniel-guest/sphinx-autobuild

It requires one new depends, port-for, which is available at:

  https://salsa.debian.org/daniel-guest/port-for

Regards,
Daniel

Bug#901504: generated bindings incompatible with octave 4.4

[Sébastien Villemot]

Package: swig3.0
Version: 3.0.12-1
Severity: important
Tags: upstream
Control: block 901155 by -1
Control: affects -1 plplot
X-Debbugs-Cc: debian-oct...@lists.debian.org

Dear Maintainer,

Octave 4.4 has been uploaded to unstable, and swig needs to be updated in order
to generate compatible bindings.

The most urgent issue is to fix plplot, which now FTBFS, and is blocking the
Octave 4.4 transition:

 
https://buildd.debian.org/status/fetch.php?pkg=plplot=amd64=5.13.0%2Bdfsg-7%2Bb1=1528654000=0

Upstream has already a series of commits for Octave 4.4, see:

 git log 
ee17f8d04f40bfc25ecaf146a6ebe667eabcffb6..a2ab3d7b20feec5f46100d98712dd92cf4f9bc52

If you don't have the time to backport these, I can do the work (possibly
limiting myself to the commit(s) needed to fix plplot) and then NMU. Please
advise.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#901503: golang-golang-x-crypto-dev: Please update the package to >= 0.0~git20180530.5ba7f63

[Benjamin Drung]

Package: golang-golang-x-crypto-dev
Version: 1:0.0~git20180513.94e3fad-2
Severity: normal

Hi,

Please update the package to >= 0.0~git20180530.5ba7f63, because gokey
need the ed25519.Seed() function that was introduced in following
commit:

commit 5ba7f63082460102a45837dbd1827e10f9479ac0
Author: David Benjamin 
Date:   Wed May 30 11:49:09 2018 -0400

ed25519: actually be compatible with RFC 8032

See ITP bug #900881 and https://github.com/cloudflare/gokey/issues/10

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg, Christoph Steffens

Bug#866872: Bug#900882: susv4: fails to install: ERROR 404: Not Found.

[Simon McVittie]

Control: tags -1 + patch

On Wed, 06 Jun 2018 at 12:29:54 +0200, Jakub Wilk wrote:
> --2018-06-06 10:24:50--  
> http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4tc2.tar.bz2
...
> 2018-06-06 10:24:52 ERROR 404: Not Found.

I've prepared a patch to update this package to susv4-2018, aka
POSIX.1-2017, and fixed some minor issues I noticed while doing that
update. Please see attached.

I've also imported the history of the sus package from snapshot.debian.org
into a git repository at . If you
find that useful, please copy that repository somewhere appropriate (I
would suggest https://salsa.debian.org/debian) or ask me to move it. My
proposed changes are available on the proposed/susv4-2018 branch in the
same repository.

On Sun, 02 Jul 2017 at 13:13:49 +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package left unowned files on
> the system after purge, which is a violation of policy 6.8 (or 10.8)
...
>   /usr/share/doc/susv4/susv4tc2/   not owned
>   /usr/share/doc/susv4/susv4tc2/Figures/   not owned

This is because the postrm wasn't updated when the rest of the package
was updated from TC1 to TC2, so it is still trying to delete
/usr/share/doc/susv4/susv4tc1. It's fixed in the attached patches.

smcv
>From 57d7d008fd4761213ab6364e8380107a12bd66e1 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 14 Jun 2018 09:04:27 +0100
Subject: [PATCH 1/4] Update susv4 to POSIX.1-2017 (SUSv4, 2018 edition)

- This fixes installability of the package since SUSv4 TC2 is no
  longer available for download (Closes: #900882)
- Delete the correct directory in postrm (Closes: #866872)
- Update doc-base metadata
- Update Lintian overrides
---
 debian/changelog   | 12 
 debian/control |  7 ---
 debian/susv4.doc-base  |  8 
 debian/susv4.lintian-overrides |  4 ++--
 debian/susv4.postinst  |  8 
 debian/susv4.prerm |  2 +-
 6 files changed, 27 insertions(+), 14 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index f58df3b..013d3c2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+sus (7.20161013+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update susv4 to POSIX.1-2017 (SUSv4, 2018 edition)
+- This fixes installability of the package since SUSv4 TC2 is no
+  longer available for download (Closes: #900882)
+- Delete the correct directory in postrm (Closes: #866872)
+- Update doc-base metadata
+- Update Lintian overrides
+
+ -- Simon McVittie   Thu, 14 Jun 2018 08:20:34 +0100
+
 sus (7.20161013) unstable; urgency=medium
 
   * New upstream release: contains SUSv4 TC2; update checksum
diff --git a/debian/control b/debian/control
index d810a5d..4cd1f96 100644
--- a/debian/control
+++ b/debian/control
@@ -27,9 +27,10 @@ Description: Fetch and install SUSv3
 Package: susv4
 Architecture: all
 Depends: wget, bzip2, ${misc:Depends}
-Description: Fetch and install SUSv4 (POSIX.1-2008)
+Description: Fetch and install SUSv4 (POSIX.1-2017)
  The Single Unix Specifications are not permitted to be generally
  redistributed, so this is an installer that fetches them and installs
  them in a Debian appropriate way.  This installer will fetch and
- install POSIX:2008 (also known as Single Unix Specification v4) with
- POSIX:2013 Technical Corrigendum 1 and POSIX:2016 Technical Corrigendum 2.
+ install POSIX.1-2017 (variously also known as IEEE Std 1003.1-2017,
+ The Open Group Base Specifications Issue 7, 2018 Edition, or
+ Single Unix Specification v4, 2018 edition).
diff --git a/debian/susv4.doc-base b/debian/susv4.doc-base
index 2a4b809..c039ce9 100644
--- a/debian/susv4.doc-base
+++ b/debian/susv4.doc-base
@@ -1,9 +1,9 @@
 Document: susv4
-Title: Single Unix Specification Version 4
+Title: Single Unix Specification Version 4, 2018 edition
 Author: The Open Group
-Abstract: This is the POSIX:2008 standard with POSIX:2013 corrigendum 1
+Abstract: The POSIX.1-2017 standard for Unix-like operating systems.
 Section: Debian
 
 Format: HTML
-Index: /usr/share/doc/susv4/susv4tc1/index.html
-Files: /usr/share/doc/susv4/susv4tc1/*.html
+Index: /usr/share/doc/susv4/susv4-2018/index.html
+Files: /usr/share/doc/susv4/susv4-2018/*.html
diff --git a/debian/susv4.lintian-overrides b/debian/susv4.lintian-overrides
index 8e90836..1eda5d8 100644
--- a/debian/susv4.lintian-overrides
+++ b/debian/susv4.lintian-overrides
@@ -1,3 +1,3 @@
 susv4: postinst-has-useless-call-to-install-docs
-susv4: doc-base-file-references-missing-file susv4:8 /usr/share/doc/susv4/susv4tc1/index.html
-susv4: doc-base-file-references-missing-file susv4:9 /usr/share/doc/susv4/susv4tc1/*.html
+susv4: doc-base-file-references-missing-file susv4:8 /usr/share/doc/susv4/susv4-2018/index.html
+susv4: doc-base-file-references-missing-file susv4:9 /usr/share/doc/susv4/susv4-2018/*.html
diff --git a/debian/susv4.postinst 

Bug#897330: apt-cudf/aspcud: fails to resolve anything on this system

[Julian Andres Klode]

Control: retitle -1 apt-cudf/aspcud: fails to resolve anything on this system
Control: reassign -1 apt-cudf,aspcud

On Sat, May 19, 2018 at 11:01:38AM +0200, Paul Gevers wrote:
> On Tue, 1 May 2018 12:54:30 +0100 Julian Andres Klode 
> wrote:
> > aspcud is unable to find a proper solution to installing petname:amd64 on a 
> > system
> > that already has petname:amd64 installed. Instead, it goes on removing a 
> > ton of
> > amd64 packages and crossgrades part of the system to i386 (e.g., 
> > base-files).
> 
> This works for me on a buster system:
> paul@testavoira ~ $ sudo apt --simulate --solver aspcud -o
> APT::Solver::Strict-Pinning=false -o
> APT::Solver::aspcud::Preferences='-removed,-changed,-new,+count(solution,APT-Pin:=/995/)'
> -o Debug::pkgProblemResolver=true install emacs:amd64

That's a completely different thing. The point is that for the given system in 
the EDSP
dump, aspcud fails to resolve _anything_. There is a bug in aspcud or apt-cudf. 
For example,
emacs with your preferences:

The following packages have unmet dependencies: 


   
 liborc-0.4-dev : Depends: liborc-0.4-dev-bin:any (= 1:0.4.28-2)
 libwayland-egl1-mesa : Conflicts: libwayland-egl1  


   
Conflicts: libwayland-egl1:i386 but 1.15.0-2 is to be 
installed   

 
 pkgconf:i386 : Breaks: pkg-config (>= 0.29-1)
Breaks: pkg-config:i386 (>= 0.29-1)  


it's completely useless atm.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#901502: ITP: twig-extensions -- Twig Extensions

[Joost van Baal-Ilić]

Package: wnpp
Severity: wishlist
Owner: Joost van Baal-Ilić 

* Package name: twig-extensions
  Version : 1.3.0
  Upstream Author : Fabien Potencier
* URL : https://github.com/twigphp/Twig-extensions
* License : MIT/X
  Programming Lang: PHP
  Description : Twig Extensions

 The Twig Extensions is a library that provides several useful extensions for
 Twig that do not belong to the core.  It currently ships Text, i18n, Intl,
 Array and Date Extensions.

 Symphony's Twig is a flexible, fast, and secure template engine for PHP.

vpn-lib-common ( https://github.com/eduvpn/vpn-lib-common ) and
vpn-user-portalhttps://github.com/eduvpn/vpn-user-portal ) depend upon
twig-extensions ( http://twig-extensions.readthedocs.io/ ).  The
vpn-lib-common, vpn-user-portal and twig-extensions packages are part of the
Let's Connect! VPN software suite.  See https://bugs.debian.org/901499 for
another ITP for Let's Connect!/eduVPN (
https://github.com/eduvpn/eduvpn-debian).

I'll request to package this software in the PHP PEAR and Composer group at
https://salsa.debian.org/php-team/pear .

Bye,

Joost

Bug#831459: jessie-pu: package virtualbox-guest-additions-iso

[Gianfranco Costamagna]

On Wed, 13 Jun 2018 20:52:32 +0100 "Adam D. Barratt"  
wrote:
> Control: tags -1 + confirmed
> 
> On Thu, 2016-09-29 at 17:45 +0100, Adam D. Barratt wrote:
> > On 2016-09-29 14:37, Gianfranco Costamagna wrote:
> > > control: tags -1 -moreinfo
> > > > (I'm not removing moreinfo tag)
> > > 
> > > removing it now.
> > 
> > fwiw the mail you're replying to does not appear to have made it to 
> > debian-release.
> > 
> 
> If you're still interested in getting this updated in jessie before it
> becomes LTS, please go ahead, bearing in mind the time constraints.
> 

on my way

G.
> Regards,
> 
> Adam
> 
> 

Bug#901390: RFP: python-orderedmultidict -- an ordered multivalue dictionary that retains method parity with Python's dict.

[Edward Betts]

I'd also like to see this package in Debian.

Inaki Malerba  wrote:
> License: Public Domain

Just to be a little more specific python-orderedmultidict uses the Unlicense.

The license says the software is released into the public domain.

See https://github.com/gruns/orderedmultidict/blob/master/LICENSE.md

And https://unlicense.org/
-- 
Edward.

Bug#901501: RFP: powerline-gitstatus -- Powerline Git segment

[Daniel Baumann]

Package: wnpp
Severity: wishlist

Hi,

it would be nice if someone would maintain powerline-gitstatus in
Debian. I made a ready-to-be-uploaded package available here:

  https://salsa.debian.org/daniel-guest/powerline-gitstatus

Regards,
Daniel

Bug#901498: [pkg-gnupg-maint] Bug#901498: FTBFS on stretch, needs newer libgpg-error

[Werner Koch]

On Thu, 14 Jun 2018 09:14, daniel.baum...@progress-linux.org said:

> when locally backporting gnupg2, I noticed that 2.2.8-1 now FTBFS on
> stretch due to old libgpg-error. Would you mind bumping build-depends

Please apply the attached patch to GnuPG 2.2.8 as suggested by
https://dev.gnupg.org/T4012


Salam-Shalom,

   Werner

-- 
#  Please read:  Daniel Ellsberg - The Doomsday Machine  #
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
From 18274db32b5dea7fe8db67043a787578c975de4d Mon Sep 17 00:00:00 2001
From: Werner Koch 
Date: Fri, 8 Jun 2018 22:01:10 +0200
Subject: [PATCH GnuPG] gpg: Allow building with older libgpg-error.

* g10/mainproc.c (proc_encrypted): Use constant from logging.h
--

Because the log levels are enums I had to change there names in
libgpg-error to avoid clashes.  Master uses the new names but 2.2
needs to stick to the old names.

Fixes-commit: 825909e9cd5f344ece6c0b0ea3a9475df1d643de
Signed-off-by: Werner Koch 
---
 g10/mainproc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/g10/mainproc.c b/g10/mainproc.c
index 72b0dd828..f5cc4532a 100644
--- a/g10/mainproc.c
+++ b/g10/mainproc.c
@@ -683,7 +683,7 @@ proc_encrypted (CTX c, PACKET *pkt)
* are rare in practice we print a hint on how to decrypt
* such messages.  */
   log_string
-(GPGRT_LOGLVL_INFO,
+(GPGRT_LOG_INFO,
  _("Hint: If this message was created before the year 2003 it is\n"
"likely that this message is legitimate.  This is because back\n"
"then integrity protection was not widely used.\n"));
-- 
2.11.0



pgpjcNzLcqdEE.pgp
Description: PGP signature

Bug#837458: jessie-pu: package mactelnet/0.4.0-1

[Gianfranco Costamagna]

Hello Adam,

On Wed, 13 Jun 2018 21:22:50 +0100 "Adam D. Barratt"  
wrote:
> Control: tags -1 -moreinfo
> 
> On Thu, 2017-01-05 at 20:06 +, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Sun, 2016-09-11 at 19:55 +0200, haakon.nessj...@gmail.com wrote:
> > 
> > > Request for uploading to stable, as there is posted a CVE for a bug
> > > in mactelnet-client.
> > > This update is a backport of the fix that is done upstream, that
> > > fixes only the mentioned bug.
> > > 
> > > Mor information here: https://security-tracker.debian.org/tracker/C
> > > VE-2016-7115
> > > and here: https://bugs.debian.org/836320
> > 
> > +mactelnet (0.4.0-2) stable; urgency=low
> > 
> > The version should be 0.4.0-1+deb8u1. With that change, please go
> > ahead.
> > 
> 
> And the distribution should be "jessie". If this is still of interest,
> please upload *soon*.
> 


done!

G.

> Regards,
> 
> Adam
> 
> 

Bug#888095: [debian-mysql] Bug#888095:

[Andy Li]

Hi Otto,

On Fri, May 11, 2018 at 9:53 AM, Andy Li  wrote:

>
>
>> > On 10/05/18 20:24, Otto Kekäläinen wrote:
>> >> MariaDB 10.3 needs to be finalized and imported into Debian. After
>> >> that all the mess that are a fallout of a misfortunate upload of
>> >> mariadb-10.2 to Debian unstable will start to become resolved.
>>
>
> What do you mean by finalized? Are we waiting upstream for something?
> If it will still take an unknown number of months to stabilize, using
> an epoch as suggested by Emilio seems to be a good immediate solution.
>

I'm sure you have been busy, but this issue has been there unfixed for
several months.
I would appreciate if you can spend a few minutes to answer our questions.
If you lack the time to maintain the package, would you let the Debian
MySQL Maintainers team temporally handle it?

Best regards,
Andy

Bug#804396: if IPv6 configuration fails, then IPv4 is not configured

[Harald Dunkel]

> > If /etc/network/interfaces defines 2 protocols for one interface,
> > then a tiny problem for one protocol can affect both.
>
> This is by design. Recent versions of ifupdown will even exit with an
> error code if there is an error while configuring any part of an
> interface.

Then we have a design problem. IMHO its reasonable to distinguish between
configuring network interfaces (bridges, wlan, etc.), and configuring
network protocols on these interfaces, e.g. assigning IPv4 or IPv6 addresses.

Surely you cannot configure a protocol, if the network interface confi-
guration failed. But I don't see any reason to stop configuring protocols
just because the protocol that was chosen first by chance shows a problem.


Regards
Harri

Bug#901500: tracker.debian.org: does not remove the versions panel when the package has been removed entirely

[Raphaël Hertzog]

Package: tracker.debian.org
Severity: normal
Tags: newcomer

If you look at https://tracker.debian.org/pkg/jenkins it looks like that
jenkins is still in unstable with version 1.565.3-6 but in fact it has
been removed everywhere (the "package is gone" panel is a proof).

So the code updating the "versions" panel is not pruning the last entry
correctly when the package has been entirely removed from all known
repositories.

The relevant code is in distro_tracker/core/retrieve_data.py in the
UpdateVersionInformation object.

The execute function should really have some logic to drop the PackageData
entries for packages that have no associated source_package_versions.

Cheers,

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

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

Bug#864615: please update version of posix standard for scripts (section 10.4)

[Simon McVittie]

On Sat, 14 Oct 2017 at 15:28:04 -0700, Sean Whitton wrote:
> On Sat, Oct 14 2017, Adam D. Barratt wrote:
> > The 2016 edition is Technical Corrigendum 2. I'm not sure that it's
> > conventional to use versioning such as 4.2 in such cases, however. I'd
> > expect it to be referred to as SUSv4, SUSv4TC2, or SUSv4 2016 edition;
> > the latter seems to be more common.

http://pubs.opengroup.org/onlinepubs/9699919799/ has now been replaced
(see #900882, for which I'm preparing a patch) with POSIX.1-2017, which
is variously labelled as:

* POSIX.1-2017
* IEEE Std 1003.1-2017
* The Open Group Technical Standard Base Specifications, Issue 7
* The Open Group Base Specifications Issue 7, 2018 Edition

and no longer has visible "Single Unix Specification" branding at all.
However, the downloadable tarballs at
http://pubs.opengroup.org/onlinepubs/9699919799/download/
have basename susv4-2018. According to Wikipedia it "incorporates Singles
UNIX Specification TC1 and TC2, and is technically identical to the
2016 edition."

I'd suggest replacing SUSv3 with POSIX.1-2017 or SUSv4 2018 edition
instead, or perhaps replacing SUSv3 with POSIX and clarifying that we
use POSIX to refer to the latest version of the POSIX.1 standard.

smcv

Bug#901499: ITP: php-yubitwee - YubiKey OTP Validator library

[Joost van Baal-Ilić]

Package: wnpp
Severity: wishlist
Owner: Joost van Baal-Ilić 

* Package name: php-yubitwee
  Version : 1.1.3
  Upstream Author : François Kooman 
* URL : https://git.tuxed.net/fkooman/php-yubitwee/about/
* License : MIT/X
  Programming Lang: PHP
  Description : YubiKey OTP Validator library

 A very simple, secure YubiKey OTP Validator with pluggable HTTP client.

vpn-server-api ( https://github.com/eduvpn/vpn-server-api ) depends upon
php-yubitwee.  (At one point in time vpn-server-api will migrate from using
php-yubitwee to U2F.  It is not yet known _when_ that will happen.)  The
vpn-server-api and php-yubitwee packages are part of the Let's Connect! VPN
software suite, being developed by SURFnet, the Dutch National Research and
Education Network.  Packaging php-yubitwee in Debian is the first step towards
integrating the Let's Connect! stack in Debian.  Currently, the suite consists
of 15 source packages, see https://github.com/eduvpn/eduvpn-debian .

Refer to https://letsconnect-vpn.org and https://eduvpn.org/ for more
information.

I'll request to package this software in the PHP PEAR and Composer group at
https://salsa.debian.org/php-team/pear .

Bye,

Joost


signature.asc
Description: Digital signature

Bug#901446: inkscape: Bug fix latex rendering

[Mattia Rizzolo]

On Wed, Jun 13, 2018 at 02:58:49PM +0200, Marc-Olivier Buob wrote:
> This bug is related to #880650.
> With the current version of inkscape, when using Extensions > Rendering > 
> Latex... the latex rendering does not work.

Which is, once again, #897407

> This bug can be fixed by modifying: 
> /usr/share/inkscape/extensions/eqtexsvg.py the following line (l.143)
> 
>  os.system('cd "%s" %s pstoedit -f plot-svg -dt -ssp "%s" "%s" > "%s" 
> 2> "%s"' \
> 
> ... by:
> 
>  os.system('cd "%s" %s pstoedit -f plot-svg -dt -rdb -ssp "%s" "%s" > 
> "%s" 2> "%s"' \
> 
> See man pstoedit for further details, option -rdb.

Quoting from the pstoedit's manpage (note that it's an option available
only in the buster+ package):
|[-rdb]
|
|Since version 3.10 pstoedit uses the -dDELAYBIND option when calling
|Ghostscript. But in version 9.22 of GhostScript, that option is not
|supported anymore because of security reasons. As a fallback, that
|version provides the REALLYDELAYBIND option and pstoedit can use this if
|you supply the -rdb option. Use this with caution as it might open
|security risks, e.g. a PostScript file injecting some malicious code
|into PostScript standard operators. However, not using this option can
|cause some of the PostScript drawings operations to be not seen by
|pstoedit, hence causing missing artefacts in the output. Later versions
|of Ghostscript will probably support -dDELAYBIND again. But also in that
|case the security risk remains. So be careful with what files you
|process with pstoedit and Ghostscript.

tbh, I'd prefer Ghostscript to be updated, as in #897407

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature