Bug#823655: mutt-patched: IMAP folders displayed in the wrong location with sidebar

2016-05-06 Thread Carbonated Beverage
Package: mutt-patched
Version: 1.6.0-1
Severity: important

   * What led up to the situation?

 Using the attached example .muttrc (sanitized) reproduces the problem.
 Opening the example.org mailbox will display the list of subscribed
 folders below the last mailbox in the sidebar, instead of example.org.

 The IMAP server used on the remote end is:
 ii  dovecot-imapd 1:2.2.13-12~deb8u1  amd64

 Marked important due to:

 Given there are several folders with the same name in my various accounts,
 this can lead to a confusion related to which account mails came in for,
 or lead to mail for urgent accounts being missed.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 Tried tweaking the various sidebar options, ran into other already
 reported bugs (823454, 823142).  Tweaking the order of the accounts in
 the "mailboxes" line appears to make the folders appear in different
 locations, sometimes in the correct location for a few accounts, but not
 others.

   * What was the outcome of this action?

 No difference.

   * What outcome did you expect instead?

 Didn't expect a difference, as those options are unrelated, just tried
 them to be thorough.

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

Kernel: Linux 4.5.3+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mutt-patched depends on:
ii  libassuan02.4.2-3
ii  libc6 2.22-7
ii  libcomerr21.43~WIP.2016.03.15-2
ii  libgnutls30   3.4.11-4
ii  libgpg-error0 1.22-1
ii  libgpgme111.6.0-3
ii  libgssapi-krb5-2  1.13.2+dfsg-5
ii  libidn11  1.32-3
ii  libk5crypto3  1.13.2+dfsg-5
ii  libkrb5-3 1.13.2+dfsg-5
ii  libncursesw5  6.0+20160319-1
ii  libsasl2-22.1.26.dfsg1-15
ii  libtinfo5 6.0+20160319-1
ii  libtokyocabinet9  1.4.48-10
ii  mutt  1.6.0-1

mutt-patched recommends no packages.

mutt-patched suggests no packages.

-- no debconf information
#bind index \Cn next-unread
#bind index \Cg pipe egrep '^Subject: '
#set index_format = "%6l %s"

set postponed = ~/postponed
set folder=~/Maildir
set mbox=~/Maildir
set mbox_type=Maildir
set spoolfile=~/Maildir
#set trash=~/Maildir/trash
fcc-hook $ +sent

set mail_check=60
set timeout=180
set imap_check_subscribed=yes

#
# == Global -- unchanged across all accounts by default
#

set abort_nosubject = no
set abort_unmodified = no
set askbcc = yes
set askcc = yes
set auto_tag = yes
set confirmappend = no
set confirmcreate = no
set copy = yes
set delete_untag = no
set dsn_notify = never
set edit_headers = yes
set editor = /usr/bin/vi
set fcc_attach = yes
set forward_quote = yes
set header = yes
set hidden_host = yes
set implicit_autoview = no
set mark_old = no
set move = no
set pager = "/usr/bin/less -X"
set prompt_after = no
set sendmail = "/usr/sbin/sendmail -oem -oi"
set strict_threads = yes
set tmpdir = ~/.tmp
set use_from = yes
set user_agent = no

#
# == Sidebar
#

set sidebar_width=52
set sidebar_visible=yes
set sidebar_delim='|'
#set sidebar_indentstr="  "
#set sidebar_shortpath=yes
#set sidebar_format="%B %* %N"
#set sidebar_folderindent=yes

#set sidebar_sort=yes
#set sidebar_delim_chars = /

# Mailboxes listed in sidebar
mailboxes "~/Maildir" imaps://us...@imap.gmail.com imaps://us...@imap.gmail.com 
imaps://example.org imaps://us...@imap.gmail.com 
imaps://us...@example.com@imap.gmail.com

# Sidebar navitation
bind index \CP sidebar-prev
bind index \CN sidebar-next
bind index \CO sidebar-open
bind index \CB sidebar-scroll-up
bind index \CF sidebar-scroll-down

#
# == SSL
#

set ssl_use_sslv3 = no
set ssl_use_tlsv1 = yes
set ssl_use_tlsv1_1 = yes
set ssl_use_tlsv1_2 = yes
set ssl_force_tls = yes

# == PGP
# Legacy format stuff.  Don't enable unless absolutely needed.
folder-hook . 'set pgp_auto_decode = no'
folder-hook . 'set pgp_autoinline = no'
# Sort by addx -- trust will be managed externally
folder-hook . 'set pgp_sort_keys = address'

#
# == IMAP stuff
#
# NOTE
# Password chars that need to be escaped: $\;`"#
# Password char that can't be escaped and has to be avoided: '

# -- Local system

# Always have account hooks for these!
account-hook . 'unset imap_user'
account-hook . 'unset imap_pass'
account-hook . 'unset smtp_pass'
account-hook . 'unset smtp_authenticators'
account-hook . 'unset ssl_client_cert'

# PGP -- This changes per-account (with a folder hook)
folder-hook . 'unset pgp_sign_as'

folder-hook . 'set from = "foo "'
folder-hook . 'set smtp_url=smtp://localhost:587'

folder-hook . 'set folder=~/Maildir'
folder-hook . 'set postponed=~/Maildir/postponed'
folder-hook . 'set 

Bug#823654: mutt-patched: sidebar mailbox name truncated too early

2016-05-06 Thread ramune
Package: mutt-patched
Version: 1.6.0-1
Severity: normal

 Since the upgrade from 1.5.24-1 to 1.6.0-1, the mailbox name shown
 in the sidebar has the uri://user@ prepended to the name.  Given the
 hard-coded 31-character limit, it's not possible to differentiate
 some of the accounts I have, in particular, those that have usernames
 of the format:

 first.l...@example.com

 The full URIs are of the form:

 imaps://first.l...@example.com@mail.internal.mycompany.test
 imaps://first.l...@example.com@mail-external.mycompany.test

 Both get truncated to:

 imaps://first.l...@example.com@

 As a workaround, I tried:
  
 set sidebar_shortpath=yes
 mailboxes imaps://first.l...@example.com@mail.internal.mycompany.test 
imaps://first.l...@example.com@mail-external.mycompany.test

 Leads to the mailbox names in the sidebar being an empty string,

 If an explicit folder name is used, that folder name is shown, but that
 makes it impossible to differentiate imaps://u...@example.com/INBOX and
 imaps://u...@example.org/INBOX from each other.

 Using the attached patch solved it for me, after setting the sidebar
 width to a larger value.

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

Kernel: Linux 4.5.3+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mutt-patched depends on:
ii  libassuan02.4.2-3
ii  libc6 2.22-7
ii  libcomerr21.43~WIP.2016.03.15-2
ii  libgnutls30   3.4.11-4
ii  libgpg-error0 1.22-1
ii  libgpgme111.6.0-3
ii  libgssapi-krb5-2  1.13.2+dfsg-5
ii  libidn11  1.32-3
ii  libk5crypto3  1.13.2+dfsg-5
ii  libkrb5-3 1.13.2+dfsg-5
ii  libncursesw5  6.0+20160319-1
ii  libsasl2-22.1.26.dfsg1-15
ii  libtinfo5 6.0+20160319-1
ii  libtokyocabinet9  1.4.48-10
ii  mutt  1.6.0-1

mutt-patched recommends no packages.

mutt-patched suggests no packages.

-- no debconf information
diff -urN mutt-1.6.0/debian/patches/series ../mutt-1.6.0/debian/patches/series
--- mutt-1.6.0/debian/patches/series2016-04-24 05:31:09.0 -0700
+++ ../mutt-1.6.0/debian/patches/series 2016-05-06 21:25:11.378323933 -0700
@@ -31,3 +31,4 @@
 mutt-patched/sidebar-newonly.patch
 mutt-patched/sidebar-compose.patch
 #mutt-patched/nntp.patch
+wider.patch
diff -urN mutt-1.6.0/debian/patches/wider.patch 
../mutt-1.6.0/debian/patches/wider.patch
--- mutt-1.6.0/debian/patches/wider.patch   1969-12-31 16:00:00.0 
-0800
+++ ../mutt-1.6.0/debian/patches/wider.patch2016-05-06 21:26:32.149856594 
-0700
@@ -0,0 +1,11 @@
+--- a/sidebar.c2016-05-06 21:21:17.436578616 -0700
 b/sidebar.c2016-05-06 21:21:33.690710298 -0700
+@@ -158,7 +158,7 @@
+ sbe.new = new;
+ sbe.flagged = flagged;
+ sbe.size = size;
+-strncpy(sbe.box, box, 31);
++strncpy(sbe.box, box, SHORT_STRING - 1);
+ 
+ safe_realloc(, SBvisual + 2);
+ entry[SBvisual + 1] = '\0';


Bug#823653: graxxia: FTBFS: Could not resolve org.codehaus.groovy:groovy:2.3.11.

2016-05-06 Thread Chris Lamb
Source: graxxia
Version: 1.0~20150714-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

graxxia fails to build from source in unstable/amd64:

  [..]

  Adding debian:certSIGN_ROOT_CA.pem
  Adding debian:ePKI_Root_Certification_Authority.pem
  Adding debian:thawte_Primary_Root_CA.pem
  Adding debian:thawte_Primary_Root_CA_-_G2.pem
  Adding debian:thawte_Primary_Root_CA_-_G3.pem
  done.
  done.
  Setting up openjdk-8-jre-headless:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to 
provide /usr/bin/rmid (rmid) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java to 
provide /usr/bin/java (java) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/keytool 
to provide /usr/bin/keytool (keytool) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/jjs to 
provide /usr/bin/jjs (jjs) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/pack200 
to provide /usr/bin/pack200 (pack200) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmiregistry to provide 
/usr/bin/rmiregistry (rmiregistry) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/unpack200 to provide 
/usr/bin/unpack200 (unpack200) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/orbd to 
provide /usr/bin/orbd (orbd) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/servertool to provide 
/usr/bin/servertool (servertool) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/tnameserv to provide 
/usr/bin/tnameserv (tnameserv) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jexec to 
provide /usr/bin/jexec (jexec) in auto mode
  Setting up default-jre-headless (2:1.8-57) ...
  Setting up openjdk-8-jre:amd64 (8u91-b14-2) ...
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
/usr/bin/policytool (policytool) in auto mode
  Setting up default-jre (2:1.8-57) ...
  Setting up openjdk-8-jdk-headless:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jsadebugd to 
provide /usr/bin/jsadebugd (jsadebugd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/native2ascii 
to provide /usr/bin/native2ascii (native2ascii) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript 
to provide /usr/bin/jrunscript (jrunscript) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to 
provide /usr/bin/jhat (jhat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to 
provide /usr/bin/javap (javap) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to 
provide /usr/bin/jar (jar) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to 
provide /usr/bin/xjc (xjc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen to 
provide /usr/bin/schemagen (schemagen) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to 
provide /usr/bin/jps (jps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck to 
provide /usr/bin/extcheck (extcheck) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to 
provide /usr/bin/jmap (jmap) in auto mode
  

Bug#823652: cargo: FTBFS: cargo.rs:88:15: 88:29 error: Cannot declare a non-inline module inside a block unless it has a path attribute

2016-05-06 Thread Chris Lamb
Source: cargo
Version: 0.8.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

cargo fails to build from source in unstable/amd64:

  [..]

  cargo:git2:url:uuid:rand:advapi32-sys:  PROFILE="release" 
TARGET="x86_64-unknown-linux-gnu" 
CARGO_MANIFEST_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2"
 
OUT_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/"
 CARGO_PKG_VERSION_MAJOR="0" CARGO_PKG_VERSION="0.1.2" 
CARGO_PKG_VERSION_PATCH="2" HOST="x86_64-unknown-linux-gnu" 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11" DEBUG="0" OPT_LEVEL="0" 
CARGO_PKG_VERSION_MINOR="1" NUM_JOBS="1" CARGO_PKG_VERSION_PRE="" rustc 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2/build.rs
 --crate-name build_script_advapi32_sys --crate-type bin -C 
extra-filename=-0_1_2 --out-dir 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ 
--emit=dep-info,link --target x86_64-unknown-linux-gnu -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps//lib 
--extern 
winapi_build=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi_build-0_1_1.rlib
 --extern 
winapi=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi-0_2_5.rlib
  cargo:git2:url:uuid:rand:advapi32-sys: cd 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2
 &&  PROFILE="release" TARGET="x86_64-unknown-linux-gnu" 
CARGO_MANIFEST_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2"
 
OUT_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/"
 CARGO_PKG_VERSION_MAJOR="0" CARGO_PKG_VERSION="0.1.2" 
CARGO_PKG_VERSION_PATCH="2" HOST="x86_64-unknown-linux-gnu" 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11" DEBUG="0" OPT_LEVEL="0" 
CARGO_PKG_VERSION_MINOR="1" NUM_JOBS="1" CARGO_PKG_VERSION_PRE="" 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/build_script_advapi32_sys-0_1_2
  cargo:git2:url:uuid:rand:advapi32-sys:  PROFILE="release" 
TARGET="x86_64-unknown-linux-gnu" 
CARGO_MANIFEST_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2"
 
OUT_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/"
 CARGO_PKG_VERSION_MAJOR="0" CARGO_PKG_VERSION="0.1.2" 
CARGO_PKG_VERSION_PATCH="2" HOST="x86_64-unknown-linux-gnu" 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11" DEBUG="0" OPT_LEVEL="0" 
CARGO_PKG_VERSION_MINOR="1" NUM_JOBS="1" CARGO_PKG_VERSION_PRE="" rustc 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2/src/lib.rs
 --crate-name advapi32 --crate-type lib -C extra-filename=-0_1_2 --out-dir 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ 
--emit=dep-info,link --target x86_64-unknown-linux-gnu -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps//lib 
--extern 
winapi_build=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi_build-0_1_1.rlib
 --extern 
winapi=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi-0_2_5.rlib
  
  cargo:git2:url:uuid:rand: Building rand-0.3.13 (needed by: uuid-0.1.18)
  cargo:git2:url:uuid:rand:  PROFILE="release" 
TARGET="x86_64-unknown-linux-gnu" 
CARGO_MANIFEST_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/rand-0.3.13"
 
OUT_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/"
 CARGO_PKG_VERSION_MAJOR="0" CARGO_PKG_VERSION="0.3.13" 
CARGO_PKG_VERSION_PATCH="13" HOST="x86_64-unknown-linux-gnu" 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11" DEBUG="0" OPT_LEVEL="0" 
CARGO_PKG_VERSION_MINOR="3" NUM_JOBS="1" CARGO_PKG_VERSION_PRE="" rustc 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/rand-0.3.13/src/lib.rs
 --crate-name rand --crate-type lib -C extra-filename=-0_3_13 --out-dir 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ 
--emit=dep-info,link --target x86_64-unknown-linux-gnu -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps//lib 
--extern 
advapi32_sys=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libadvapi32_sys-0_1_2.rlib
 --extern 
winapi=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi-0_2_5.rlib
 --extern 
libc=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/liblibc-0_2_4.rlib
  
  cargo:git2:url:uuid:rustc-serialize: Building 

Bug#823599: task-polish-desktop: Please add firefox-l10n-pl to package recommendations

2016-05-06 Thread Christian PERRIER
Quoting Christian PERRIER (bubu...@debian.org):

> Isn't this a more general issue with iceweasel|firefox in desktop
> tasks ?
> 
> To Mozilla package maintainers, since the change from iceweasel to
> firefox, isn't there something we should change in tasksel tasks?
> 
> (please keep all addresses CC'ed when answering, except /me as I'm
> subscribed to tasksel bugs)
> 

OK...#823605, which I didn't originally noticed;..:-)




-- 




signature.asc
Description: PGP signature


Bug#823599: task-polish-desktop: Please add firefox-l10n-pl to package recommendations

2016-05-06 Thread Christian PERRIER
Quoting Gsc (gscs...@gmail.com):
> Package: task-polish-desktop
> Version: 3.34
> Severity: wishlist
> Tags: l10n
> 
> Dear Maintainer,
> 
> task-polish-desktop recommends iceweasel-l10n-pl, which depends on
> firefox-esr-l10n-pl. So if one wanted to install non-esr firefox (and
> firefox-l10n-pl), while installing also task-polish-desktop, he may end up
> having both firefox and firefox-esr installed.
> 
> Is it possible to modify task-polish-desktop dependencies so that it will
> recommend either firefox-l10n-pl or firefox-esr-l10n-pl?


Isn't this a more general issue with iceweasel|firefox in desktop
tasks ?

To Mozilla package maintainers, since the change from iceweasel to
firefox, isn't there something we should change in tasksel tasks?

(please keep all addresses CC'ed when answering, except /me as I'm
subscribed to tasksel bugs)



signature.asc
Description: PGP signature


Bug#821484: Bumping severity of PHP 7.0 transition bugs to serious

2016-05-06 Thread Sunil Mohan Adapa
On 05/07/2016 02:05 AM, James Valleroy wrote:
> tags 821484 patch
> thanks
> 
> The attached patch will simply switch from PHP 5 to PHP 7.0.
> 

The patch looks correct but insufficient.  Here are my notes:

- ownCloud depends on php5 but is being removed.

- tt-rss seems to work okay with php7.  Faced some weird issues during
installation, probably unrelated.

- Shaarli is still dependent on php5 modules but seems to work with php7.

- Roundcube seems to have problem with php7 but upstream supports php7
in 1.2beta (unreleased and not yet available in Debian).

- Php7 module is not enabled in freedombox-setup for people upgrading
from an earlier version.

I have applied the patch and marked that it closes the bug.  However, we
need to address the issue of enabling php7 module for upgrading users.
I propose that we add 'a2enmod php7.0' to post-install.  What do you think?

-- 
Sunil



signature.asc
Description: OpenPGP digital signature


Bug#819328: avrdude: arduino pro mini reset problem

2016-05-06 Thread Milan Kupcevic
Control: severity -1 wishlist


Hi Michal,


On 03/28/2016 12:44 PM, Michal Suchanek wrote:

[...]

> 
> I fixed the reset problem with pro mini by inverting the DTR handling in
> arduino.c
> 

[...]

> Ideally an extra argument would be added to switch which method is tried
> first.


This looks like a new feature. Please file a bug report at:

http://savannah.nongnu.org/bugs/?func=additem=avrdude

and work with the upstream on the issue.


Milan




signature.asc
Description: OpenPGP digital signature


Bug#815668: Upstream report

2016-05-06 Thread Tim Richardson
I  have reported this here, or at least I think it's the same bug:

https://bugzilla.gnome.org/show_bug.cgi?id=765830

-- 
Tim Richardson


Bug#810401: avrdude: please switch to libusb 1.0

2016-05-06 Thread Milan Kupcevic
Control: forwarded -1 https://savannah.nongnu.org/bugs/?43338
Control: block 810366 by -1


On 01/08/2016 01:35 PM, Aurelien Jarno wrote:

[...]

> 
> If avrdude supports the new libusb 1.0 library, please consider
> switching the build-depends from libusb-dev to libusb-1.0-0-dev. If not
> please inform upstream that porting the software to the new API is
> recommended.
> 


So far the upstream relies on "0.1 API compatibility wrapper".[0] The
libusb 0.1 API "is required by AVRDUDE in order to work with USB".[1]

Milan


[0] https://savannah.nongnu.org/bugs/?func=detailitem_id=41854#comment7
[1] https://savannah.nongnu.org/bugs/?func=detailitem_id=43338#comment1





signature.asc
Description: OpenPGP digital signature


Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

2016-05-06 Thread Robert Lange
You are correct. I have Python 3.4 installed. Rebuilding on a system with 
Python 3.5 worked as expected. Apparently if the X-Python-Version is not 
satisfied, the build gives no fatal errors and appears to work, while not 
actually building the package properly. But that's a bug for the build system, 
not this package.

On 2016-05-06 21:08, Axel Beckert wrote:
> Control: tag -1 + unreproducible moreinfo
>
> Hi Robert,
>
> Robert Lange wrote:
>> Package: sshuttle
>> Version: 0.78.0-1~bpo8+1
>> Severity: grave
> […]
>> I tried to make a backport of sshuttle for jessie using stretch
>> sources.
> This seems to be an issue with your backporting. Because the package
> builds fine on Debian Sid.
>
> Maybe this line from debian/control needs to be changed for
> backporting, too:
>
>   X-Python3-Version: >= 3.5
>
>   Regards, Axel



Bug#823608: nginx-common: Move nginx.vim to a separate package?

2016-05-06 Thread Michael Lustfield
A separate package just for a single file seems a little bit overkill, but
I do understand. You may not want /etc/nginx but want to edit the configs.
I do this frequently and just skip the benefits of nginx.vim.

This should stay open for discussion for a while, but I'm in support of
this change.


Bug#823380: Blank screen after successful login

2016-05-06 Thread Louis-Philippe Véronneau
This is a duplicate of #811551.

Sorry for the noise.

--
pollo

On Wed, 4 May 2016 02:15:04 -0400
=?UTF-8?Q?Louis-Philippe_V=c3=a9ronneau?=  wrote:
> Package: gdm3
> Version: 3.18.0-2
> 
> For a few weeks now when I log in successfully with gdm3, I get a grey
> screen with nothing on it.
> 
> Pressing the "enter" button gives me the "show password" drop list.
> 
> The only way to get out of this is by pressing the "Escape" button.
> 
> I doubt this is due to a change in gdm3 since it has not been updated
> recently on testing.
> 
> I was able to reproduce this bug on at least 3 different computers, all
> running NVIDIA proprietary drivers.
> 
> I'm not sure what infos you need to debug this, but please ask!
> 
> --
> pollo
> 
> 



signature.asc
Description: OpenPGP digital signature


Bug#822667: uploaded to mentors.debian.net

2016-05-06 Thread 郭溢譞
Package: wnpp
Followup-For: Bug #822667
Owner: "Guo Yixuan (郭溢譞)" 

Hello,

The packages was just uploaded to mentors.debian.net.
(sponsorship-requests: #823650)

Regards,
Yixuan



Bug#823043: zsh FTBFS since yodl 3.08.00-1 in the same way that c++-annotations FTBFSed with 3.07.00-1 (was: Re: Bug#823043 closed by f.b.brok...@rug.nl (Frank B. Brokken) (Bug#823043: fixed in yodl 3

2016-05-06 Thread Frank B. Brokken
Dear Axel Beckert, you wrote:

> Hi Frank,

Hi Axel,

You wrote:

> I'm not 100% sure what's going on, but it seems to me that while
> c++-annotations indeed FTBFS with 3.07.00-1 and builds fine again with
> 3.08.00-1 (verified it :-), it's the opposite way round with zsh:
> 
> It builds fine with yodl 3.07.00-1, but FTBFS with 3.08.00-1 as
> follows:
> 
> ...Zsh Yodl-to-man converter
> Including file Zsh/zftpsys.yo
> yodl -k -L -o ../../Doc/zshzle.1 -I../../Doc:. -w zman.yo version.yo
> ../../Doc/zshzle.yo
> Zsh Yodl-to-man converter
> Including file Zsh/zle.yo
> yodl -k -L -o ../../Doc/zshall.1 -I../../Doc -DZSHALL -w zman.yo version.yo 
> zsh.yo
> `ZSHALL' (symbol) multiply defined
> `ZSHALL' (symbol) multiply defined
> `ZSHALL' (symbol) multiply defined
> Error(s) in command line arguments. Terminating
> ...

Thanks for reporting this bug: I just downloaded the zsh source package and
can reproduce the error. I'll have a look at what's going, and report back to
you once I know more.

Cheers,

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA


signature.asc
Description: PGP signature


Bug#823651: pbuilder: fails to make temp file - breaks

2016-05-06 Thread Norbert Preining
Package: pbuilder
Version: 0.224
Severity: grave
Justification: renders package unusable

Dear all,

the recent changes in /tmp handling seem to have made
cowbuilder/pbuilder unable to build any package:

$ cowbuilder --build foobar.dsc
...
 This package was created automatically by pbuilder to satisfy the
  build-dependencies of the package being currently built.
Depends: 
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
dpkg-deb: error: failed to make temporary file (control member): No such file 
or directory
E: pbuilder-satisfydepends failed.

I am not sure where the fix should be, though.

Thanks

Norbert

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

Kernel: Linux 4.6.0-rc6+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pbuilder depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  debootstrap1.0.81
ii  dpkg-dev   1.18.6
ii  wget   1.17.1-2

Versions of packages pbuilder recommends:
ii  devscripts  2.16.4
ii  fakeroot1.20.2-1
ii  iproute24.3.0-1+b1
ii  net-tools   1.60+git20150829.73cef8a-2
ii  sudo1.8.15-1.1

Versions of packages pbuilder suggests:
ii  cowdancer   0.79
ii  gdebi-core  0.9.5.7

-- debconf information:
  pbuilder/mirrorsite: http://ftp.jaist.ac.jp/debian/
  pbuilder/rewrite: false
  pbuilder/nomirror:



Bug#823650: RFS: gcc-6-doc/6.1.0-1 [ITP]

2016-05-06 Thread 郭溢譞
Package: sponsorship-requests
Severity: wishlist
Control: block 822667 by -1

Dear mentors,

I'm looking for a sponsor for my package gcc-6-doc. (ITP: #822667)

* Package name: gcc-6-doc
  Version : 6.1.0-1
  Upstream Author : FSF
* URL : http://gcc.gnu.org/
* License : GFDL-1.3+, with invariant sections
  Programming Lang: Texinfo
  Description : documentation for the GNU compilers (gcc, gobjc, g++)

This package contains manual pages and documentation in info, html,
and pdf format, for the GNU compilers.

This documentation is licensed under the terms of the GNU Free
Documentation License, and contains invariant sections, so it can't be
part of Debian main.

(See gcc-5-doc as an example.)

  It builds those binary packages:

 cpp-6-doc  - documentation for the GNU C preprocessor (cpp)
 gcc-6-doc  - documentation for the GNU compilers (gcc, gobjc, g++)
 gccgo-6-doc - documentation for the GNU Go compiler (gccgo)
 gcj-6-doc  - documentation for the GNU Java tools (gcj, gij)
 gfortran-6-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-6-doc - documentation for the GNU Ada Compiler (gnat)

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

  https://mentors.debian.net/package/gcc-6-doc


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

dget -x 
https://mentors.debian.net/debian/pool/non-free/g/gcc-6-doc/gcc-6-doc_6.1.0-1.dsc


Thanks,
Yixuan



Bug#823649: libjs-mediaelement: Reflected XSS vulnerability

2016-05-06 Thread Craig Small
Package: libjs-mediaelement
Version: 2.15.1+dfsg-1
Severity: important
Tags: security upstream

I saw this regarding the wordpress 4.5.2 release[1]. MediaElement.js is
vulnerable to a reflected XSS attack. The wordpress patch is at [2]
but I cannot exactly find what has changed but I think it is the
url has the time added to randomize it more. [3]

1: https://wordpress.org/news/2016/05/wordpress-4-5-2/
2: https://core.trac.wordpress.org/changeset/37370
3: 
https://github.com/johndyer/mediaelement/commit/34834eef8ac830b9145df169ec22016a4350f06e

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

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

libjs-mediaelement depends on no packages.

Versions of packages libjs-mediaelement recommends:
ii  libjs-jquery  1.11.3+dfsg-4

libjs-mediaelement suggests no packages.

-- no debconf information



Bug#823648: monobristol : new version upstream (was: "pkg-multimedia-maintain...@lists.alioth.debian.org")

2016-05-06 Thread trebmuh

Please retitle to : "monobristol : new version upstream", my bad.

Copying the multimedia team this time.



Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

2016-05-06 Thread lumin
Hi,

I've split the caffe-cpu package and the caffe-cuda package,
and I'd like to first handle the cpu version, leaving the CUDA
version pending at debian/science/caffe-contrib.
The updated cpu version has been uploaded to mentors:

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

This update involves fix on multiarch, removal of caffe-cuda,
and removal of libproto.a .

However I found that hardening-no-fortify-functions is still
unsolved, and the upstream CMakeFiles.txt seems not to be
the trouble maker, as it contains this line
```
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fPIC -Wall")
```
and I really see the -D_FORTIFY_SOURCE=2 option added in the
verbose gcc command line.

On Tue, 2016-05-03 at 08:03 +, Gianfranco Costamagna wrote:
> Hi,
> 
> >set(CFLAGS ...) which should be replaced by set(CFLAGS $(CFLAGS) ...)
> >
> >An upstream classic unfortunately.
> 
> 
> as upstream I did this once, and the side effect was something weird.
> 
> when you run multiple times cmake .. the cflags gets appended multiple times, 
> so you might
> end up in a really weird CMakeCache.txt and with really long build lines.
> 
> I'm not sure which way is the best one, but cmake should provide something 
> different from CFLAGS.
> 
> e.g.
> CMAKE_C_FLAGS
> CMAKE_C_FLAGS_RELEASE
> CMAKE_C_FLAGS_DEBUG
> CMAKE_EXE_LINKER_FLAGS
> CMAKE_MODULE_LINKER_FLAGS
> 
> and so on.
> that way they will be appended to current CFLAGS without having to override 
> them manually.
> 
> (thanks again for your nice reviews!)
> 
> g.



Bug#823648: pkg-multimedia-maintain...@lists.alioth.debian.org

2016-05-06 Thread trebmuh

Package: monobristol
Version: 0.60.3-2.1

Dear maintainer,
just to inform you that a new (minor) version has been released upstream 
:

https://sourceforge.net/projects/monobristol/files/monobristol/monobristol-0.60.3.2/

Copying the multimedia team here.

HTH
Olivier



Bug#636518: monobristol: Moog Voyager Blue Ice, Prophet-52, Pro-1, YAMAHA DX cannot be called from monoBristol

2016-05-06 Thread trebmuh

Dear maintainers,

I'm just adding a +1 on this one. I did rebuild (using pbuilder) 
monobristol with the patch mentionned above (on a debian Jessie), and 
that's wonderful to hear those 4 synth/piano sounding !


Just adding my voice here trying to get some interest.

I'm copying the multi mediateam as well since they could have some 
interest in providing this new build.


Cheers,
Olivier



Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

2016-05-06 Thread Axel Beckert
Control: tag -1 + unreproducible moreinfo

Hi Robert,

Robert Lange wrote:
> Package: sshuttle
> Version: 0.78.0-1~bpo8+1
> Severity: grave
[…]
> I tried to make a backport of sshuttle for jessie using stretch
> sources.

This seems to be an issue with your backporting. Because the package
builds fine on Debian Sid.

Maybe this line from debian/control needs to be changed for
backporting, too:

  X-Python3-Version: >= 3.5

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



Bug#822635: udev rules for USB device access effective at boot, but not on hotplug

2016-05-06 Thread Martin Pitt
Control: tag -1 moreinfo

Hello Josh,

Josh Triplett [2016-04-25 13:48 -0700]:
> ~$ cat /etc/udev/rules.d/99-local-gnubby.rules
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0200", 
> TAG+="uaccess"
>
> If I boot with the device attached, this seems to take effect:
>
> However, if I unplug and replug the device, this rule no longer seems to take
> effect:

The uaccess tag is evaluated in /lib/udev/rules.d/73-seat-late.rules,
thus 99-* is too late. Can you please move it to e. g.
70-gnubby.rules? I'm fairly sure it will work then, but I'll keep the
bug open until you confirm, just in case.

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)



Bug#823530: systemd 228 reduced maximum number of tasks in a cgroup to 512 by default

2016-05-06 Thread Martin Pitt
Hello all,

Sebastian Schmidt [2016-05-05 20:14 +0200]:
> Whilst debugging why Chrome would regularly fail to create new
> threads[1] and zsh couldn’t fork I noticed that:
> - - All affected processes run in the /system.slice/xdm.service cgroup
> - - “systemctl status xdm.service” says “Tasks: 476 (limit: 512)”

Antonio Terceiro [2016-05-06 15:45 -0300]:
> I am seeing some inconsistency in this. On my laptop, I don't see any
> limits being applied, even though I am on a fully up to date unstable
> (tried both with my main account from a terminal emulator in GNOME, and
> from a console login with a freshly created user account):
> 
> $ ulimit -u 22988

Note that these are two different things:

  * TasksMax is enforced via the pids cgroups, and only applies to
.service units started by systemd. It should not apply to user
sessions (i. e. .scopes) started through libpam-systemd, but
as Sebastian is not using them all subprocesses of xdm.service
inherit xdm's limit.

 * ulimit -u is the classic ulimit which is unrelated to TaskMax=
   (instead, it is LimitNPROC= if you want to set it in a unit).
   systemd does not have/impose a default setting for ulimits, this
   usually comes through /etc/security/limits.conf and is being
   applied to PAM sessions only, not to .services.

> I do appreciate the idea of systemd imposing sane limits on tasks, but
> this will cause A LOT of breakage in all sorts of places, and we need
> figure out a plan forward. Will every package need to start declaring
> higher limits explicitly?

Since we released Ubuntu 16.04 LTS with this I've also gotten reports
about this. E. g. MySQL and RabbitMQ easily break the TasksMax=512
limit even under moderate load.  (https://launchpad.net/bugs/1578080
is one example) Note that this actually limits threads, not just full
processes.

So in retrospect, having a default limit there was not such a good
idea after all: 512 is way too much for most "simple" services, and
it's way too little for others such as the ones mentioned above. There
is also no particular rationale about "512", so even if we'd bump it
to 1024 we'd just make the limit even less useful while still breaking
software.

So I think we should disable the default limit. It is both much safer
and also much more effective in terms of guarding against berserk
programs/bugs/unintended fork bombs etc. to set limits in units
individually. Once someone looks at one, this is then a great time to
also flip on the other resource and privilege limitations that systemd
offers, such as CapabilityBoundingSet=, SecureBits=, PrivateDevices=,
PrivateNetwork=, ProtectSystem=, ProtectHome=, etc.

So I'm proposing to change the default to "infinity". We could do this
with a /lib/systemd/system.conf.d/no-task-max.conf, but this would be
confusing to someone looking at /etc/systemd/system.conf, so a patch
might be preferable (i. e. reverting upstream commit 9ded9cd). I'll
also raise this upstream (once I have internet again), perhaps we can
even change the default there.

Opinions?

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: PGP signature


Bug#788667: lintian: suggest adding DEP-8 tests when an automake installcheck-local target is detected

2016-05-06 Thread Martin Pitt
Hello,

Paul Wise [2016-04-10 17:13 +0800]:
> > Assuming this is just a trivial "run target", wouldn't it be even better
> > if autopkgtests added support for this directly like it did with
> > pkg-perl tests (i.e. adding a "Testsuite: autopkgtest-automake" or so)?
> 
> I don't know enough about DEP-8 to answer this. Thoughts Martin?
> 
> I also note that autodep8 exists and may be the place to put this?

In principle autodep8 could grow an automatic test for this, such as

  Test-Command: make installcheck-local
  Restrictions: needs-build, needs-root, isolation-container, breaks-testbed

However, this has some caveats:

 * You always have to build the package as part of the test to even be
   able to run "make installcheck-local". Depending on the package,
   this can range anywhere from "trivial" over "nuisance" to
   "prohibitively expensive".

 * There is no way to predict whether the test can be run as user,
   thus this could only default to running as root.

 * There is no way to predict what kind of features the test expects
   from the testbed, i. e. whether it is safe to run in a schroot,
   or won't work in a container, thus again you can only assume the
   worst and restrict this to "isolation-machine" (i. e. QEMU or bare
   metal). However, it would then not actually run on our Debian
   infrastructure, thus we'd rather default to isolation-container,
   and accept a few failures.

 * For the same reason we have to assume the worst and declare it to
   break the testbed, so that we don't run this e. g. via the ssh
   runner on a non-throwaway machine.

 * It's not a given that the package's binaries are sufficient to run
   the test, so it could fail on missing test dependencies.

Thus, while possible, this would have the maximum inefficiency.  Doing
this on a per-package basis means knowing what the installcheck will
actually do and then the restrictions can become much softer and also
the test dependencies can be adjusted.

This of course should also get tried for the packages which have
installcheck-local to see what else breaks, before we enable this in
production.

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: PGP signature


Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

2016-05-06 Thread Robert Lange
Package: sshuttle
Version: 0.78.0-1~bpo8+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I tried to make a backport of sshuttle for jessie using stretch sources. I did
the usual package build steps:

apt-get source sshuttle
cd sshuttle-0.78.0/
dch --bpo
sudo apt-get build-dep sshuttle
debuild -sa -uc -us

The package built without any fatal errors and produced a deb. The following is
the build output:

(jessie-amd64-sbuild)rlange@iset:~/debsrc/sshuttle/sshuttle-0.78.0$ debuild -sa
-uc -us
 dpkg-buildpackage -rfakeroot -D -us -uc -sa
dpkg-buildpackage: source package sshuttle
dpkg-buildpackage: source version 0.78.0-1~bpo8+1
dpkg-buildpackage: source distribution jessie-backports
dpkg-buildpackage: source changed by Robert Lange 
 dpkg-source --before-build sshuttle-0.78.0
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
   debian/rules override_dh_clean
make[1]: Entering directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
dh_clean
rm -rf tmp
rm -rf docs/.build docs/_build
make[1]: Leaving directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
 dpkg-source -b sshuttle-0.78.0
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building sshuttle using existing
./sshuttle_0.78.0.orig.tar.gz
dpkg-source: info: building sshuttle in sshuttle_0.78.0-1~bpo8+1.debian.tar.xz
dpkg-source: info: building sshuttle in sshuttle_0.78.0-1~bpo8+1.dsc
 debian/rules build
dh build --with python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   debian/rules override_dh_auto_build
make[1]: Entering directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
dh_auto_build
PYTHONPATH=. sphinx-build -b html -d docs/.build/.doctrees -N docs
docs/.build/html
Making output directory...
Running Sphinx v1.2.3
loading pickled environment... failed: [Errno 2] No such file or directory:
'/home/rlange/debsrc/sshuttle/sshuttle-0.78.0/docs/.build/.doctrees/environment.pickle'
building [html]: targets for 13 source files that are out of date
updating environment: 13 added, 0 changed, 0 removed
reading sources... [  7%] changes
reading sources... [ 15%] how-it-works
reading sources... [ 23%] index
reading sources... [ 30%] installation
reading sources... [ 38%] manpage
reading sources... [ 46%] overview
reading sources... [ 53%] platform
reading sources... [ 61%] requirements
reading sources... [ 69%] support
reading sources... [ 76%] tproxy
reading sources... [ 84%] trivia
reading sources... [ 92%] usage
reading sources... [100%] windows

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [  7%] changes
writing output... [ 15%] how-it-works
writing output... [ 23%] index
writing output... [ 30%] installation
writing output... [ 38%] manpage
writing output... [ 46%] overview
writing output... [ 53%] platform
writing output... [ 61%] requirements
writing output... [ 69%] support
writing output... [ 76%] tproxy
writing output... [ 84%] trivia
writing output... [ 92%] usage
writing output... [100%] windows

writing additional files... genindex search
copying static files... WARNING: html_static_path entry
'/home/rlange/debsrc/sshuttle/sshuttle-0.78.0/docs/_static' does not exist
done
copying extra files... done
dumping search index... done
dumping object inventory... done
build succeeded, 1 warning.
PYTHONPATH=. sphinx-build -b man -d docs/.build/.doctrees -N docs
docs/.build/man
Making output directory...
Running Sphinx v1.2.3
loading pickled environment... done
building [man]: all manpages
updating environment: 0 added, 0 changed, 0 removed
looking for now-outdated files... none found
writing... sshuttle.1 { }
build succeeded.
make[1]: Leaving directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
PYTHONPATH=. \
dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest"
make[1]: Leaving directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
 fakeroot debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
   dh_testroot -O--buildsystem=pybuild
   dh_prep -O--buildsystem=pybuild
dh_installdirs -O--buildsystem=pybuild
   dh_auto_install -O--buildsystem=pybuild
   dh_install -O--buildsystem=pybuild
   dh_installdocs -O--buildsystem=pybuild
   dh_sphinxdoc -O--buildsystem=pybuild
   dh_installchangelogs -O--buildsystem=pybuild
   dh_installman -O--buildsystem=pybuild
   dh_python3 -O--buildsystem=pybuild
   dh_perl -O--buildsystem=pybuild
   dh_link -O--buildsystem=pybuild
   dh_compress -O--buildsystem=pybuild
   dh_fixperms -O--buildsystem=pybuild
   dh_installdeb -O--buildsystem=pybuild
   dh_gencontrol 

Bug#823465: dpkg: Won't run at all on i586 Pentium MMX due to illegal instruction

2016-05-06 Thread Pierre Ynard
Yes, I run unstable in production. My stuff isn't business-critical.
But I can say the same thing about this making it impossible to run
unstable. That's not the idea I'd like to have about Debian. If I wanted
a distro where unstable is broken and unusable, I would have installed
 long ago.

I don't care too much that the change is "silent", since I'm here and
know now. That's nice to document the next release, but I was asking for
an answer to my problem now. What do I do with my i586 system running
unstable of last week? Drop it into a tub of water, just like i586
support is getting dropped? That's going to cause way more downtime than
simply running unstable in production.

My "complaint" against unstable is valid. Typical Debian bugs don't
(or at least shouldn't) wait for the stable release to get fixed. I
don't see why you retitled this copy of the bug, since it described the
situation accurately. i586 users running unstable are getting their
system broken, with no obvious way to handle it. Maybe I'm the only such
user and you don't care, then at least have the decency to wontfix me.

Please tell me, what do I do with it??

-- 
Pierre Ynard
"Une âme dans un corps, c'est comme un dessin sur une feuille de papier."



Bug#823646: firmware-crystalhd contains an unnecessary, obsolete non-free firmware file

2016-05-06 Thread Daniel Lenski
Package: firmware-crystalhd
Version: 0.0~git20120110.fdd2f19-1

The firmware file /lib/firmware/bcmFilePlayFw.bin which is included
with this package is NEVER USED by any extant version of
libcrystalhd3, with any version of the Broadcom CrystalHD hardware.
This file can be removed.

This firmware file was REPLACED by bcm70012fw.bin in a very early
version of libcrystalhd3:

  
http://git.linuxtv.org/jarod/crystalhd.git/commit/?id=14640128497e8e6d8d01d7fc85c4eef043d428c2

This is far older than the snapshot on which the Debian libcrystalhd3
package is based:

  http://git.linuxtv.org/jarod/crystalhd.git/commit/?id=fdd2f19

As far as I can tell, even the earliest Debian packages for
libcrystalhd3 did not rely on this obsolete firmware file.



Bug#786611: Info received (Patch, new maintainer request)

2016-05-06 Thread Julia Longtin
When testing this patch, i found that i had forgotten an earlier patch,
from a different source. Attached.

Julia Longtin
diff -ur iscsitarget/kernel/conn.c iscsitarget.patched/kernel/conn.c
--- iscsitarget/kernel/conn.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/conn.c	2015-05-05 18:01:40.0 +
@@ -127,7 +127,7 @@
 
 	dprintk(D_GENERIC, "%llu\n", (unsigned long long) session->sid);
 
-	conn->sock = SOCKET_I(conn->file->f_dentry->d_inode);
+	conn->sock = SOCKET_I(conn->file->f_path.dentry->d_inode);
 	conn->sock->sk->sk_user_data = conn;
 
 	write_lock_bh(>sock->sk->sk_callback_lock);
diff -ur iscsitarget/kernel/file-io.c iscsitarget.patched/kernel/file-io.c
--- iscsitarget/kernel/file-io.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/file-io.c	2015-05-05 18:03:10.0 +
@@ -69,7 +69,7 @@
 static int fileio_sync(struct iet_volume *lu, struct tio *tio)
 {
 	struct fileio_data *p = lu->private;
-	struct inode *inode = p->filp->f_dentry->d_inode;
+	struct inode *inode = p->filp->f_path.dentry->d_inode;
 	struct address_space *mapping = inode->i_mapping;
 	loff_t ppos, count;
 	int res;
@@ -213,7 +213,7 @@
 		eprintk("%d\n", err);
 		goto out;
 	}
-	inode = p->filp->f_dentry->d_inode;
+	inode = p->filp->f_path.dentry->d_inode;
 
 	if (S_ISREG(inode->i_mode))
 		;
diff -ur iscsitarget/kernel/iscsi.c iscsitarget.patched/kernel/iscsi.c
--- iscsitarget/kernel/iscsi.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/iscsi.c	2015-05-05 17:59:39.0 +
@@ -986,9 +986,6 @@
 		set_cmnd_lunit(req);
 
 	switch (req_hdr->scb[0]) {
-	case SERVICE_ACTION_IN:
-		if ((req_hdr->scb[1] & 0x1f) != 0x10)
-			goto error;
 	case INQUIRY:
 	case REPORT_LUNS:
 	case TEST_UNIT_READY:
diff -ur iscsitarget/kernel/target_disk.c iscsitarget.patched/kernel/target_disk.c
--- iscsitarget/kernel/target_disk.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/target_disk.c	2015-05-05 18:04:09.0 +
@@ -606,9 +606,6 @@
 	case REQUEST_SENSE:
 		send_data_rsp(cmnd, build_request_sense_response);
 		break;
-	case SERVICE_ACTION_IN:
-		send_data_rsp(cmnd, build_service_action_in_response);
-		break;
 	case READ_6:
 	case READ_10:
 	case READ_16:
diff -ur iscsitarget/kernel/volume.c iscsitarget.patched/kernel/volume.c
--- iscsitarget/kernel/volume.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/volume.c	2015-05-05 18:02:29.0 +
@@ -398,9 +398,6 @@
 		case READ_CAPACITY:
 			/* allowed commands when reserved */
 			break;
-		case SERVICE_ACTION_IN:
-			if ((scb[1] & 0x1F) == 0x10)
-break;
 			/* fall through */
 		default:
 			err = -EBUSY;
@@ -465,9 +462,6 @@
 		if (excl_access_ro && !registered)
 			err = -EBUSY;
 		break;
-	case SERVICE_ACTION_IN:
-		if ((scb[1] & 0x1F) == 0x10)
-			break;
 		/* fall through */
 	case RELEASE:
 	case RESERVE:


signature.asc
Description: Digital signature


Bug#823406: emacs24: freeze in sh mode with show-paren-mode

2016-05-06 Thread Vincent Lefevre
Control: tags -1 patch

I've attached the patch from

  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23445#23

which fixes this bug (it works for me).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
commit 1bab3cefc133e06aaf4a48efb1623d1b458ab212
Author: Tassilo Horn 
Date:   Mon Oct 26 08:01:18 2015 +0100

Fix infinite loop in sh-script's SMIE code

* lisp/progmodes/sh-script.el (sh-smie-sh-forward-token): Fix infinite
loop (bug#21747).

diff --git a/lisp/progmodes/sh-script.el b/lisp/progmodes/sh-script.el
index fbb4a90..baed27b 100644
--- a/lisp/progmodes/sh-script.el
+++ b/lisp/progmodes/sh-script.el
@@ -1920,10 +1920,11 @@ Does not preserve point."
 ;; Pretend the here-document is a "newline representing a
 ;; semi-colon", since the here-doc otherwise covers the newline(s).
 ";")
-(let ((semi (sh-smie--newline-semi-p)))
-  (forward-line 1)
-  (if (or semi (eobp)) ";"
-(sh-smie-sh-forward-token
+(unless (eobp)
+  (let ((semi (sh-smie--newline-semi-p)))
+(forward-line 1)
+(if (or semi (eobp)) ";"
+  (sh-smie-sh-forward-token)
 (forward-comment (point-max))
 (cond
  ((looking-at "\n") (forward-line 1) (sh-smie-sh-forward-token))


Bug#823645: glibc-doc-reference: should at least Suggest info-browser or info

2016-05-06 Thread Noel David Torres Taño
Package: glibc-doc-reference
Version: 2.19-1
Severity: normal

Dear Maintainer,

glibc-doc-reference contains libc manual in info format, among others. But 
installing it is useless since the info package itself is not triggered to be 
installed as well. This package should at least Suggest, probably Recommend the 
package 'info' or the virtual package 'info-browser'.

-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 1.0 (jessie)
Release:1.0
Codename:   jessie
Architecture: x86_64

Kernel: Linux 4.4.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- debconf information:
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line 
30.



Bug#786611: Patch, new maintainer request

2016-05-06 Thread Julia Longtin
Hello,

I would also like to maintain this package, since my infrastructure requires it 
working.

This would be my first package (so i would have to go through new maintainer), 
but i'm very familiar with openiscsi internals. gotta keep systems working...

Attached, you can find my patch for iscsitarget working with debian's 4.5 
kernel on arm7i.

Julia Longtin
diff --git a/Makefile b/Makefile
index 32efe5e..9a841b1 100644
--- a/Makefile
+++ b/Makefile
@@ -1 +1,2 @@
+subdir-ccflags-y = -Wall -Werror
 obj-m = kernel/
diff --git a/kernel/block-io.c b/kernel/block-io.c
index 00365b5..d7222c6 100644
--- a/kernel/block-io.c
+++ b/kernel/block-io.c
@@ -29,11 +29,13 @@ struct tio_work {
 	struct completion tio_complete;
 };
 
-static void blockio_bio_endio(struct bio *bio, int error)
+/* dropped error parameter in 4.3. */
+static void blockio_bio_endio(struct bio *bio)
 {
+	int error;
 	struct tio_work *tio_work = bio->bi_private;
 
-	error = test_bit(BIO_UPTODATE, >bi_flags) ? error : -EIO;
+	error = -(bio->bi_error);
 
 	if (error)
 		atomic_set(_work->error, error);
@@ -68,7 +70,7 @@ blockio_make_request(struct iet_volume *volume, struct tio *tio, int rw)
 
 	/* Calculate max_pages for bio_alloc (memory saver) */
 	if (bdev_q)
-		max_pages = bio_get_nr_vecs(bio_data->bdev);
+		max_pages = BIO_MAX_PAGES;
 
 	tio_work = kzalloc(sizeof (*tio_work), GFP_KERNEL);
 	if (!tio_work)
diff --git a/kernel/conn.c b/kernel/conn.c
index 3ae6881..01bdb6f 100644
--- a/kernel/conn.c
+++ b/kernel/conn.c
@@ -87,13 +87,14 @@ static void iet_state_change(struct sock *sk)
 	target->nthread_info.old_state_change(sk);
 }
 
-static void iet_data_ready(struct sock *sk, int len)
+/* dropped len is 3.15. */
+static void iet_data_ready(struct sock *sk)
 {
 	struct iscsi_conn *conn = sk->sk_user_data;
 	struct iscsi_target *target = conn->session->target;
 
 	nthread_wakeup(target);
-	target->nthread_info.old_data_ready(sk, len);
+	target->nthread_info.old_data_ready(sk);
 }
 
 /*
diff --git a/kernel/iscsi.c b/kernel/iscsi.c
index 7f20568..432d113 100644
--- a/kernel/iscsi.c
+++ b/kernel/iscsi.c
@@ -489,8 +489,8 @@ static void cmnd_skip_pdu(struct iscsi_cmnd *cmnd)
 	}
 	conn->read_iov[i].iov_base = addr;
 	conn->read_iov[i].iov_len = size;
-	conn->read_msg.msg_iov = conn->read_iov;
-	conn->read_msg.msg_iovlen = ++i;
+	conn->read_msg.msg_iter.iov = conn->read_iov;
+	conn->read_msg.msg_iter.nr_segs = ++i;
 }
 
 static void iscsi_cmnd_reject(struct iscsi_cmnd *req, int reason)
@@ -718,7 +718,7 @@ static int cmnd_recv_pdu(struct iscsi_conn *conn, struct tio *tio, u32 offset, u
 	idx = offset >> PAGE_CACHE_SHIFT;
 	offset &= ~PAGE_CACHE_MASK;
 
-	conn->read_msg.msg_iov = conn->read_iov;
+	conn->read_msg.msg_iter.iov = conn->read_iov;
 	conn->read_size = size = (size + 3) & -4;
 	conn->read_overflow = 0;
 
@@ -730,14 +730,14 @@ static int cmnd_recv_pdu(struct iscsi_conn *conn, struct tio *tio, u32 offset, u
 		conn->read_iov[i].iov_base =  addr + offset;
 		if (offset + size <= PAGE_CACHE_SIZE) {
 			conn->read_iov[i].iov_len = size;
-			conn->read_msg.msg_iovlen = ++i;
+			conn->read_msg.msg_iter.nr_segs = ++i;
 			break;
 		}
 		conn->read_iov[i].iov_len = PAGE_CACHE_SIZE - offset;
 		size -= conn->read_iov[i].iov_len;
 		offset = 0;
 		if (++i >= ISCSI_CONN_IOV_MAX) {
-			conn->read_msg.msg_iovlen = i;
+			conn->read_msg.msg_iter.nr_segs = i;
 			conn->read_overflow = size;
 			conn->read_size -= size;
 			break;
@@ -879,6 +879,7 @@ static void scsi_cmnd_exec(struct iscsi_cmnd *cmnd)
 	}
 }
 
+/* handle a nop-out packet. */
 static int nop_out_start(struct iscsi_conn *conn, struct iscsi_cmnd *cmnd)
 {
 	u32 size, tmp;
@@ -918,7 +919,7 @@ static int nop_out_start(struct iscsi_conn *conn, struct iscsi_cmnd *cmnd)
 
 	if ((size = cmnd->pdu.datasize)) {
 		size = (size + 3) & -4;
-		conn->read_msg.msg_iov = conn->read_iov;
+		conn->read_msg.msg_iter.iov = conn->read_iov;
 		if (cmnd->pdu.bhs.itt != cpu_to_be32(ISCSI_RESERVED_TAG)) {
 			struct tio *tio;
 			int pg_cnt = get_pgcnt(size);
@@ -946,7 +947,7 @@ static int nop_out_start(struct iscsi_conn *conn, struct iscsi_cmnd *cmnd)
 		}
 		assert(!size);
 		conn->read_overflow = size;
-		conn->read_msg.msg_iovlen = i;
+		conn->read_msg.msg_iter.nr_segs = i;
 	}
 
 out:
diff --git a/kernel/iscsi.h b/kernel/iscsi.h
index 3bc687e..657e96a 100644
--- a/kernel/iscsi.h
+++ b/kernel/iscsi.h
@@ -81,7 +81,8 @@ struct network_thread_info {
 	spinlock_t nthread_lock;
 
 	void (*old_state_change)(struct sock *);
-	void (*old_data_ready)(struct sock *, int);
+  /* changes in 3.15 */
+  void (*old_data_ready)(struct sock *);
 	void (*old_write_space)(struct sock *);
 };
 
diff --git a/kernel/iscsi_hdr.h b/kernel/iscsi_hdr.h
index ec119b7..02b6f6d 100644
--- a/kernel/iscsi_hdr.h
+++ b/kernel/iscsi_hdr.h
@@ -16,6 +16,7 @@
 #define __packed __attribute__ ((packed))
 #endif
 
+/* This structure is packed so that it matches rfc3720 when transmitted over tcp. */
 struct iscsi_hdr {
 	u8  opcode;			/* 0 */
 	u8  

Bug#823644: [patch] missing b-d on libjzlib-java

2016-05-06 Thread Matthias Klose

Package: src:jruby
Version: 1.7.22-2
Severity: serious
Tags: sid stretch patch

The package fails to build, libjzlib-java is needed as a *build* dependency as 
well.

patch at
http://launchpadlibrarian.net/258252483/jruby_1.7.22-2_1.7.22-2ubuntu1.diff.gz



Bug#823584: [PATCH] Correct top-level directory name in repackaged tarballs

2016-05-06 Thread Ben Finney
Jakub Wilk  writes:

> Once we fix #560287, we could perhaps say that the directory should be:
> --
>
> or something similar.

There isn't (to my knowledge) a defined concept of “repack suffix”.

But there is a defined concept of “Debian upstream version”; it is the
upstream version string (the version string minus the Debian release suffix)
specified in the Debian changelog entry.

I would think the correct, and expected, behaviour is to always unpack
to a directory named for the Debian upstream version.

Some examples:

* “foo (1.2.3.ds1-2)” heads the Debian changelog entry:

  * The Debian release suffix “-2” says this is the second Debian
release of the same upstream source.

  * The Debian upstream source is a re-packed tarball from upstream “foo
1.2.3”.

  * The Debian upstream version is “1.2.3.ds1”.

  * The Debian upstream source *does not match* the original, so “.orig”
is not appropriate in the directory name.

  * The Debian upstream source should unpack to ‘foo-1.2.3.ds1/’.

* “foo (1.2.3~xyz-2)” heads the Debian changelog entry:

  * The Debian release suffix “-2” says this is the second Debian
release of the same upstream source.

  * The Debian upstream source is upstream's (say) “foo 1.2.3.xyz”,
which is *prior* to a subsequent “1.2.3” by upstream's version
naming rules.

  * The Debian upstream version is “1.2.3~xyz”.

  * The Debian upstream source is identical to the original, so “.orig”
is appropriate in the directory name.

  * The Debian upstream source should unpack to ‘foo-1.2.3~xyz.orig/’.

* “foo (1.2.3-2)” heads the Debian changelog entry:

  * The Debian release suffix “-2” says this is the second Debian
release of the same upstream source.

  * The Debian upstream source is identical to upstream's “foo 1.2.3”.

  * The Debian upstream version is “1.2.3”.

  * The Debian upstream source is identical to the original, so “.orig”
is appropriate in the directory name.

  * The Debian upstream source should unpack to ‘foo-1.2.3.orig/’.

-- 
 \  “I don't want to live peacefully with difficult realities, and |
  `\ I see no virtue in savoring excuses for avoiding a search for |
_o__)real answers.” —Paul Z. Myers, 2009-09-12 |
Ben Finney 



Bug#792202: texlive-bin: Please make the CreationDate, ModDate and ID field deterministic

2016-05-06 Thread Alexis Bienvenüe
Hi.

Note that dvips honours SOURCE_DATE_EPOCH since
https://www.tug.org/svn/texlive/trunk/Build/source/texk/dvipsk/output.c?r1=32653=40885
so that suppress-dvips-creationdate.patch is not needed with TL2016.

Also, with SOURCE_DATE_EPOCH_TEX_PRIMITIVES=1,
remove-tex-output-timestamp.patch is not needed with TL2016: year,
month, day are the TeX primitives that can be set from SOURCE_DATE_EPOCH
if SOURCE_DATE_EPOCH_TEX_PRIMITIVES=1.
See https://www.tug.org/svn/texlive?view=revision=40889

Regards,
Alexis Bienvenüe.



Bug#823643: maxima-emacs must not depend on maxima and maxima-doc

2016-05-06 Thread Oleg Shalaev
Package: maxima-emacs
Version: 5.38.0-3
Severity: wishlist

I never use maxima-doc (prefer online help); I do not use maxima on my netbook.
However, sometimes I print maxima files on my netbook from emacs using M-x 
ps-print-buffer-with-faces
I suspect that maxima-emacs does not need neither maxima nor maxima-doc for its 
highlighting purposes. Moreover, some people (including myself) prefer to 
compile
maxima manually rather than using Debian package.
I find it unjustified that maxima-emacs depends on maxima and maxima-doc.
I suggest separating these three packages (like it was in good old times):
One should be able to use each of them without installing the other two.

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

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

Versions of packages maxima-emacs depends on:
ii  emacs24 [emacsen]24.5+1-6+b2
ii  emacsen-common   2.0.8
ii  maxima   5.38.0-3
ii  maxima-doc   5.38.0-3
ii  tex-common   6.05
ii  texlive-binaries [texlive-base-bin]  2015.20160222.37495-1
ii  texlive-latex-recommended2015.20160320-1

Versions of packages maxima-emacs recommends:
ii  ghostscript [postscript-viewer]   9.19~dfsg-1+b1
ii  mime-support  3.59
ii  zathura-pdf-poppler [pdf-viewer]  0.2.6-1
ii  zathura-ps [postscript-viewer]0.2.3-1

maxima-emacs suggests no packages.

-- debconf-show failed



Bug#817005: RFS: aseqjoy/0.0.1-1 [ITP]

2016-05-06 Thread Gianfranco Costamagna
Hi Adam,



>What's the problem?


none, you are right!
I read again your previous mail, and yes, there is no conflict assuming we use 
GPL2 only.

I would appreciate however a new tarball, because I don't like having to tell 
ftpmasters
where to look in the mail list for the license change.

Anyway, Fernando, please tell me when you want a new check :)

cheers,

G.



Bug#823642: [xserver-xorg-input-synaptics] Driver dosen't take setings from /etc/X11/xorg.conf.d

2016-05-06 Thread Yasen Atanasov
Package: xserver-xorg-input-synaptics
Version: 1.8.3-1+b1
Severity: normal

--- Please enter the report below this line. ---
Hello
After realising that synaptics driver is not loaded automaticaly
(#823636) I tried to load it forcfuli with synaptics.conf in
/etc/X11/xorg.conf.d (as I have tried to explain in #823607).

The result is that tapping and edge scroling is working but twofinger
scrolling is not working.

Cheers,
Yasen
--- System information. ---
Architecture: amd64
Kernel:   Linux 4.5.0-1-amd64

Debian Release: stretch/sid
  500 testing ftp.uni-sofia.bg
  500 stable-updates  ftp.uni-sofia.bg
  500 stable  security.debian.org
  500 stable  ftp.uni-sofia.bg
  500 stable  dl.google.com
  100 jessie-backports ftp.uni-sofia.bg

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.



-8<---8<---8<---8<---8<---8<---8<---8<---8<--
Please attach the file:
  /tmp/reportbug-ng-xserver-xorg-input-synaptics-xIv5fN.txt
to the mail. I'd do it myself if the output wasn't too long to handle.

  Thank you!
->8--->8--->8--->8--->8--->8--->8--->8--->8--
--- Output from package bug script ---
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

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

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

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 512 May  7 00:41 synaptics.conf

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

Kernel version (/proc/version):
---
Linux version 4.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 25869 May  7 00:46 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 6.721] 
X.Org X Server 1.18.3
Release Date: 2016-04-04
[ 6.721] X Protocol Version 11, Revision 0
[ 6.721] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 6.721] Current Operating System: Linux hp430g2 4.5.0-1-amd64 #1 SMP 
Debian 4.5.1-1 (2016-04-14) x86_64
[ 6.721] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-1-amd64 
root=UUID=4e40b4ea-b2e1-4f04-b4c5-8aad87e72e80 ro quiet
[ 6.721] Build Date: 05 April 2016  07:00:43AM
[ 6.721] xorg-server 2:1.18.3-1 (http://www.debian.org/support) 
[ 6.721] Current version of pixman: 0.33.6
[ 6.721]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 6.721] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 6.721] (==) Log file: "/var/log/Xorg.0.log", Time: Sat May  7 00:46:35 
2016
[ 6.722] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 6.722] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 6.724] (==) No Layout section.  Using the first Screen section.
[ 6.724] (==) No screen section available. Using defaults.
[ 6.724] (**) |-->Screen "Default Screen Section" (0)
[ 6.724] (**) |   |-->Monitor ""
[ 6.725] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 6.725] (==) Automatically adding devices
[ 6.725] (==) Automatically enabling devices
[ 6.725] (==) Automatically adding GPU devices
[ 6.725] (==) Max clients allowed: 256, resource mask: 0x1f
[ 6.727] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 6.727]Entry deleted from font path.
[ 6.729] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 6.729] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 6.729] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 6.729] (II) Loader magic: 0x559d67472dc0
[ 6.729] (II) Module ABI versions:
[ 6.729]X.Org ANSI C Emulation: 0.4
[ 6.729]X.Org Video Driver: 20.0
[ 6.729]X.Org XInput driver : 22.1
[ 6.729]X.Org Server Extension : 9.0
[ 6.729] (++) using VT number 7

[ 6.729] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[ 6.730] 

Bug#823629: reprepro: Please provide a way to compact references.db after some of its content has been freed

2016-05-06 Thread intrigeri
Hi,

intrig...@debian.org wrote (06 May 2016 19:57:00 GMT) :
> But would it be possible to have one extra operation, that one could
> run from time to time, and that compacts references.db [...]

I did a bit more research, and my understanding is that this problem
could be solved with a reprepro wrapper, called e.g. `reprepro
_reclaimdiskspace' that would:

 * be aware of reprepro's own locking, if any
 * call DB->compact() repeatedly, passing it the DB_FREE_SPACE flag
   and a low compact_fillpercent

If someone wants to draft this (perhaps allowing one to pass a custom
value for compact_fillpercent on the command-line), I'd be happy to
test it on a copy of my production data, and to report back how it
fares in practice :)

References:

   
https://docs.oracle.com/cd/E17076_02/html/programmer_reference/am_misc_diskspace.html
   https://docs.oracle.com/cd/E17076_02/html/api_reference/C/dbcompact.html

Cheers,
--
intrigeri



Bug#816272: [Pkg-clamav-devel] Bug#816272: clamav-freshclam: logrotate errors out with "gzip: stdin: file size changed while zipping"

2016-05-06 Thread Sebastian Andrzej Siewior
On 2016-05-05 14:31:31 [+0200], Christian Pernegger wrote:
> Hello!
Hi,

> So it seems to me like it has migrated to stable, and a while ago at that,
> or at least volatile / stable-updates. Or am I missing something?

No, this is correct. You reported the bug against 0.98.7+dfsg-0+deb8u1
and this version did not have the change. 

The question is now, what did you do to make the logrotate message go
away? Was it the upgrade to current stable or something else? If it was
the upgrade then yes, it is likely a duplicate of the other bug and can
be closed / merged.

> Cheers,
> C.

Sebastian



Bug#823641: RM: kdevelop-python/1.7.2-2

2016-05-06 Thread Lisandro Damián Nicanor Pérez Meyer
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi! With my team-maintainer hat on I would like to ask for kdevelop-python
removal from testing.

It currently can't be built with python3.5:

CMake Error at parser/CMakeLists.txt:19 (message):
  Python >= 3.4.3 and < 3.5 with --enable-shared is required to build this
  version of kdev-python

And this is currently an RC bug, #820186

As far as I understand the next version of it will be able to build
with a newer python-dev, so removing it now from testing seems the sanest
thing to do.

Thanks in advance, Lisandro.

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

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



Bug#823513: [Pkg-clamav-devel] Bug#823513: clamav-freshclam: freshclam fails to download daily.cvd and clamav do not start

2016-05-06 Thread Sebastian Andrzej Siewior
On 2016-05-06 15:10:39 [+0200], Simone Piccardi wrote:
> Yes, I tried.
> No, it's not a temporary or a network problem.
> The error messages/WARNING are the same I already reported.

The message regarding 0.90.0 is old and 0.90.2 is current is harmless.

> Anyway I reinstalled everything (using a VM snapshot) from the start two
> time, with the same result. This is the effect of:
> 
> root@jessie:~# systemctl stop clamav-freshclam.service
> root@jessie:~# freshclam -v
…
> Querying current.cvd.clamav.net
…
> Retrieving http://db.local.clamav.net/daily.cvd
> Ignoring mirror 195.154.7.176 (due to previous errors)
> Ignoring mirror 90.147.160.69 (due to previous errors)
> Ignoring mirror 195.154.7.176 (due to previous errors)
> Ignoring mirror 90.147.160.69 (due to previous errors)
> WARNING: Can't download daily.cvd from db.local.clamav.net

I assume that db.local.clamav.net points to db.it.clamav.net for you and
this in turn resolved to two hosts. Both are ignored due to previous
errors and therefore 

> Trying again in 5 secs...

freshclam does nothing.

> Giving up on database.clamav.net...

this is another hosts however it is an alias for db.local.clamav.net so
you get the same IPs in return. 

> Update failed. Your network may be down or none of the mirrors listed in
> /etc/clamav/freshclam.conf is working. Check
> http://www.clamav.net/doc/mirrors-faq.html for possible reasons.

To get rid of the "Ignoring mirror … due to previous errors" you need to
either wait or remove /var/lib/clamav/mirrors.dat - that is where it
information comes from.
Then you can try again and show what goes wrong.

> If I understand correctly the clamav FAQ the warning:
> 
> "WARNING: Your ClamAV installation is OUTDATED!"
> 
> means that current version of freshclam will always fail to download that
> file.

No, freshclam remains to work.
http://www.clamav.net/documents/official-mirror-faq CTRL-F is ou

> There is Local version: 0.99 and recommended 0.99.2, so until there is a way
> to relax that restriction, or accept a different minor version, or release
> an updated package, clamav-daemon will break.

This is just a warning. Freshclam is still working, so is clamav-daemon:
|# freshclam 
|ClamAV update process started at Fri May  6 23:41:31 2016
|WARNING: Your ClamAV installation is OUTDATED!
|WARNING: Local version: 0.99 Recommended version: 0.99.2
|DON'T PANIC! Read http://www.clamav.net/support/faq
|main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: 
amishhammer)
|WARNING: getfile: daily-21517.cdiff not found on remote server (IP: 
2620:121:0:23::67)
|WARNING: getpatch: Can't download daily-21517.cdiff from db.ipv6.clamav.net
|Downloading daily-21517.cdiff [100%]
|daily.cld updated (version: 21517, sigs: 98748, f-level: 63, builder: neo)
|bytecode.cld is up to date (version: 277, sigs: 47, f-level: 63, builder: neo)
|Database updated (4317585 signatures) from db.ipv6.clamav.net (IP: 
2001:41d0:2:9aba::1)
|Clamd successfully notified about the update.

As you see, it failed to download the file from 2620:121:0:23::67.

> Regards
> Simone

Sebastian



Bug#823071: python-pbr: diff for NMU version 1.8.0-4.1

2016-05-06 Thread Stefano Rivera
Control: tags 823071 + patch
Control: tags 823071 + pending

Dear maintainer,

I've prepared an NMU for python-pbr (versioned as 1.8.0-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru python-pbr-1.8.0/debian/changelog python-pbr-1.8.0/debian/changelog
--- python-pbr-1.8.0/debian/changelog	2015-10-24 01:36:49.0 +0200
+++ python-pbr-1.8.0/debian/changelog	2016-05-06 23:41:16.0 +0200
@@ -1,3 +1,10 @@
+python-pbr (1.8.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Depend on python{3,}-pkg-resources (Closes: #823071)
+
+ -- Stefano Rivera   Fri, 06 May 2016 23:41:16 +0200
+
 python-pbr (1.8.0-4) unstable; urgency=medium
 
   * override_dh_python3 to fix Py3 shebang.
diff -Nru python-pbr-1.8.0/debian/control python-pbr-1.8.0/debian/control
--- python-pbr-1.8.0/debian/control	2015-10-24 01:36:49.0 +0200
+++ python-pbr-1.8.0/debian/control	2016-05-06 23:39:46.0 +0200
@@ -45,7 +45,8 @@
 
 Package: python-pbr
 Architecture: all
-Depends: python-six (>= 1.9.0),
+Depends: python-pkg-resources,
+ python-six (>= 1.9.0),
  ${misc:Depends},
  ${python:Depends},
 Recommends: ${python:Recommends},
@@ -74,7 +75,8 @@
 
 Package: python3-pbr
 Architecture: all
-Depends: python3-six (>= 1.9.0),
+Depends: python3-pkg-resources,
+ python3-six (>= 1.9.0),
  ${misc:Depends},
  ${python3:Depends},
 Recommends: ${python3:Recommends},


Bug#823640: wordpress: Reflected XSS in PLupload and mediaelement

2016-05-06 Thread Craig Small
Package: wordpress
Version: 4.5.1
Severity: important
Tags: security upstream

Wordpress 4.2 to 4.5.1 has a XSS vulnerability in Plupload and
mediaelement.  I haven't yet done the analysis to see if we are
fully vulnerable (some mediaelement items are removed due to DFSG
problems) but most likely it is.

No CVE items as yet from what I can tell.

Given this problem was introduced in 4.2 then jessie and wheezy should
not be impacted. I'll have a look at them in case they no longer care
about such old versions.

They mention an imagemagick problem too, but sounds more about the
library. Cannot find a DSA about it though.

https://wordpress.org/news/2016/05/wordpress-4-5-2/


-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages wordpress depends on:
pn  apache2 | httpd 
ii  ca-certificates 20160104
ii  libjs-cropper   1.2.2-1
ii  libphp-phpmailer5.2.14+dfsg-2
ii  libphp-snoopy   2.0.0-1
ii  mysql-client5.6.28-1
ii  php55.6.19+dfsg-2
pn  php5-gd 
ii  php5-mysql  5.6.19+dfsg-2+b1
pn  wordpress-theme-twentyfourteen  

Versions of packages wordpress recommends:
pn  wordpress-l10n
pn  wordpress-theme-twentytwelve  

Versions of packages wordpress suggests:
ii  mysql-server  5.6.28-1



Bug#823639: Bump lshw version to B.02.18

2016-05-06 Thread Lee Trager
Package: lshw
Version: B.02.18

Upstream has released lshw-B.02.18 which contains a number of bug fixes. In
particular this release fixes two bugs

   1. The amount of RAM being displayed was the amount of RAM available to
   the user, not the amount of physical RAM
   2. On certain systems, such as Intel Atom, the amount of CPU cores was
   not being displayed.


Bug#823521: RFS: irstlm/6.00.05-1 -- IRST Language Modeling Toolkit

2016-05-06 Thread Gianfranco Costamagna
Hi Balint, so I presume you want to set yourself as owner of this bug, right?


thanks for your work!

Gianfranco


Il Venerdì 6 Maggio 2016 23:40, Balint Reczey  ha 
scritto:
Control: reopen -1

Luckily the upload got rejected, thus I did not interfere with the RFS
process.

Cheers,
Balint

On Fri, 6 May 2016 23:28:46 +0200 Balint Reczey 
wrote:
> Hi Giulio and All,
> 
> I'm sorry, but I have uploaded the package after a review but before
> I checked this RFS bug's progress. I have not received the follow-up
> emails.
> 
> The version uploaded is latest master at:
> http://anonscm.debian.org/cgit/collab-maint/irstlm.git
> 
> 56c3947 (HEAD, origin/master, master) Updated changelog.
> 
> I hope it won't cause too much inconvenience to import 6.00.05-2
> to Debian Science instead of this version.
> 
> Thanks,
> Balint



Bug#823521: RFS: irstlm/6.00.05-1 -- IRST Language Modeling Toolkit

2016-05-06 Thread Balint Reczey
Control: reopen -1

Luckily the upload got rejected, thus I did not interfere with the RFS
process.

Cheers,
Balint

On Fri, 6 May 2016 23:28:46 +0200 Balint Reczey 
wrote:
> Hi Giulio and All,
> 
> I'm sorry, but I have uploaded the package after a review but before
> I checked this RFS bug's progress. I have not received the follow-up
> emails.
> 
> The version uploaded is latest master at:
> http://anonscm.debian.org/cgit/collab-maint/irstlm.git
> 
> 56c3947 (HEAD, origin/master, master) Updated changelog.
> 
> I hope it won't cause too much inconvenience to import 6.00.05-2
> to Debian Science instead of this version.
> 
> Thanks,
> Balint



Bug#823638: mirrors: [ftp.debian.org] Hash Sum mismatch

2016-05-06 Thread Vincent Lefevre
Package: mirrors
Severity: normal

# apt update
[...]
Get:33 http://ftp.debian.org/debian unstable/main amd64 Contents (deb) [31.8 MB]
Err:33 http://ftp.debian.org/debian unstable/main amd64 Contents (deb) 
  Hash Sum mismatch
[...]
Get:40 http://ftp.debian.org/debian experimental/main amd64 Contents (deb) 
[3351 kB]
Err:40 http://ftp.debian.org/debian experimental/main amd64 Contents (deb) 
  Hash Sum mismatch
Fetched 35.5 MB in 1s (21.2 MB/s)  
Reading package lists... Done
E: Failed to fetch 
http://ftp.debian.org/debian/dists/unstable/main/Contents-amd64.gz  Hash Sum 
mismatch
E: Failed to fetch 
http://ftp.debian.org/debian/dists/experimental/main/Contents-amd64.gz  Hash 
Sum mismatch
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

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

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



Bug#823264: wine32-tools: Allow installation on amd64

2016-05-06 Thread Javier Serrano Polo
The gcc dependency should be
gcc | gcc-multilib:amd64 [i386]

dh_perl should support a ${perlany:Depends} substitution that outputs
perl:any instead of perl.


smime.p7s
Description: S/MIME cryptographic signature


Bug#823514: extra newline added to /etc/apt/listchanges.conf

2016-05-06 Thread Robert Luberda
積丹尼 Dan Jacobson writes:
> Package: apt-listchanges
> Version: 3.2
> Severity: wishlist
> 
> You added an extra newline to /etc/apt/listchanges.conf which causes the
> upgrade to pause to ask the administrator what to do.

It most probably happens only if the configuration file was modified by
hand; otherwise ucf will simply replace it with the new version without
prompting.

This is a side effect of using python's configparser module to write the
new version of configuration file (Another drawback is that it loses
comments. But in my opinion it is still better than previously, when
`dpkg-reconfigure apt-listchanges' forced the prompt if the
configuration file contained any setting not managed by debconf).

> 
> If you take it back off now it will only pause once again...

I can skip calling ucf when the files differ by whitespaces only (i.e.
when `diff -wB' returns no output).

Maybe a better way of fixing this would be to add some option to ucf
that would cause it to ignore differences in whitespaces while deciding
if files are different; Manoj, what do you think?

Regards,
robert



Bug#823637: firmware-nonfree: please add a firmware-nvidia-graphics package

2016-05-06 Thread Sven Joachim
Source: firmware-nonfree
Version: 20160110-1
Severity: wishlist

Starting with the Maxwell GM20x generation[1], NVidia graphics cards
require signed firmware for most operations, the Nouveau driver does not
provide acceleration without the firmware.

In February 2016, NVidia finally made the firmware available in the
linux-firmware git repository, and with Linux 4.6 and Mesa 11.2 (both
currently in experimental) users should be able to get acceptable
performance out of their expensive cards without having to resort to the
proprietary driver.


1. https://nouveau.freedesktop.org/wiki/CodeNames/#NV110



Bug#823636: [xserver-xorg] synaptics driver is not loaded

2016-05-06 Thread Yasen Atanasov
Package: xserver-xorg
Version: 1:7.7+15
Severity: normal

--- Please enter the report below this line. ---
Hello,
synclient -l
Couldn't find synaptics properties. No synaptics driver loaded?

The problem is that taping on touchpad and palm detection are not working.

Grretings,
Yasen

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.5.0-1-amd64

Debian Release: stretch/sid
  500 testing ftp.uni-sofia.bg
  500 stable-updates  ftp.uni-sofia.bg
  500 stable  security.debian.org
  500 stable  ftp.uni-sofia.bg
  500 stable  dl.google.com
  100 jessie-backports ftp.uni-sofia.bg

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.



-8<---8<---8<---8<---8<---8<---8<---8<---8<--
Please attach the file:
  /tmp/reportbug-ng-xserver-xorg-8tyyPo.txt
to the mail. I'd do it myself if the output wasn't too long to handle.

  Thank you!
->8--->8--->8--->8--->8--->8--->8--->8--->8--
--- Output from package bug script ---
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

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

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

Contents of /etc/X11/xorg.conf.d:
-
total 0

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

Kernel version (/proc/version):
---
Linux version 4.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 25203 May  7 00:04 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 6.590] 
X.Org X Server 1.18.3
Release Date: 2016-04-04
[ 6.590] X Protocol Version 11, Revision 0
[ 6.590] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 6.590] Current Operating System: Linux hp430g2 4.5.0-1-amd64 #1 SMP 
Debian 4.5.1-1 (2016-04-14) x86_64
[ 6.590] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-1-amd64 
root=UUID=4e40b4ea-b2e1-4f04-b4c5-8aad87e72e80 ro quiet
[ 6.590] Build Date: 05 April 2016  07:00:43AM
[ 6.590] xorg-server 2:1.18.3-1 (http://www.debian.org/support) 
[ 6.590] Current version of pixman: 0.33.6
[ 6.590]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 6.590] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 6.590] (==) Log file: "/var/log/Xorg.0.log", Time: Sat May  7 00:04:55 
2016
[ 6.595] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 6.596] (==) No Layout section.  Using the first Screen section.
[ 6.596] (==) No screen section available. Using defaults.
[ 6.596] (**) |-->Screen "Default Screen Section" (0)
[ 6.596] (**) |   |-->Monitor ""
[ 6.597] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 6.597] (==) Automatically adding devices
[ 6.597] (==) Automatically enabling devices
[ 6.597] (==) Automatically adding GPU devices
[ 6.597] (==) Max clients allowed: 256, resource mask: 0x1f
[ 6.599] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 6.599]Entry deleted from font path.
[ 6.601] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 6.601] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 6.601] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 6.601] (II) Loader magic: 0x559a40c8adc0
[ 6.601] (II) Module ABI versions:
[ 6.601]X.Org ANSI C Emulation: 0.4
[ 6.601]X.Org Video Driver: 20.0
[ 6.601]X.Org XInput driver : 22.1
[ 6.601]X.Org Server Extension : 9.0
[ 6.603] (++) using VT number 7

[ 6.603] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[ 6.604] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 6.605] (--) PCI:*(0:0:2:0) 8086:1616:103c:2246 rev 9, Mem @ 
0xc000/16777216, 0xb000/268435456, I/O @ 0x6000/64
[ 6.605] (II) LoadModule: "glx"
[ 6.607] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so

Bug#823634: umlet: conversion in batch mode hangs

2016-05-06 Thread Olivier Berger
Package: umlet
Version: 13.3-1
Severity: normal
Tags: upstream

Hi.

There is a problem with batch processing for converting files to other formats :
umlet -action=convert -format=png -filename=client-serveur.uxf 
-output=client-serveur.png
this hangs at the end.

Unsetting DISPLAY works around the issue.

Note that this is discussed upstream : https://github.com/umlet/umlet/issues/320

Hope this helps

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

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

Versions of packages umlet depends on:
ii  default-jdk [java6-sdk]2:1.8-57
ii  default-jre [java7-runtime]2:1.8-57
ii  jarwrapper 0.55
ii  libautocomplete-java   2.5.0-1
ii  libbatik-java  1.8-3
ii  libecj-java3.10.1-2
ii  libfop-java1:2.1-3
ii  libgnumail-java1.1.2-10
ii  libitext5-java 5.5.6-2
ii  libjavaparser-java 1.0.8-1
ii  libjlibeps-java0.1+2-2
ii  libjsyntaxpane-java0.9.6~r156-6
ii  liblog4j1.2-java   1.2.17-7
ii  librsyntaxtextarea-java2.5.0-1
ii  openjdk-8-jdk [java6-sdk]  8u91-b14-2
ii  openjdk-8-jre [java7-runtime]  8u91-b14-2

umlet recommends no packages.

umlet suggests no packages.

-- no debconf information



Bug#823635: umlet: Won't exit when opened with file argument

2016-05-06 Thread Olivier Berger
Package: umlet
Version: 13.3-1
Severity: normal

Dear Maintainer,

When loading a file with the -filename option, like : umlet 
-filename=client-serveur.uxf
the program starts and loads the file, but won't want to exit if closed, and 
displays :
Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException
at java.io.File.(File.java:277)
at com.baselet.control.config.Config.getOpenFileHome(Config.java:75)
at 
com.baselet.control.config.handler.ConfigHandler.saveConfig(ConfigHandler.java:182)
at com.baselet.control.Main.closeProgram(Main.java:474)
at 
com.baselet.gui.standalone.StandaloneGUI.closeWindow(StandaloneGUI.java:72)
at 
com.baselet.gui.standalone.SwingWindowListener.windowClosing(SwingWindowListener.java:19)
at 
java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:349)
at 
java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:349)
at java.awt.Window.processWindowEvent(Window.java:2058)
at javax.swing.JFrame.processWindowEvent(JFrame.java:305)
at java.awt.Window.processEvent(Window.java:2017)
at java.awt.Component.dispatchEventImpl(Component.java:4891)
at java.awt.Container.dispatchEventImpl(Container.java:2294)
at java.awt.Window.dispatchEventImpl(Window.java:2750)
at java.awt.Component.dispatchEvent(Component.java:4713)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.awt.EventQueue$4.run(EventQueue.java:729)
at java.security.AccessController.doPrivileged(Native Method)
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
at 
org.GNOME.Accessibility.AtkWrapper$5.dispatchEvent(AtkWrapper.java:697)
at 
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at 
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Hope this helps.

Best regards,

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

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

Versions of packages umlet depends on:
ii  default-jdk [java6-sdk]2:1.8-57
ii  default-jre [java7-runtime]2:1.8-57
ii  jarwrapper 0.55
ii  libautocomplete-java   2.5.0-1
ii  libbatik-java  1.8-3
ii  libecj-java3.10.1-2
ii  libfop-java1:2.1-3
ii  libgnumail-java1.1.2-10
ii  libitext5-java 5.5.6-2
ii  libjavaparser-java 1.0.8-1
ii  libjlibeps-java0.1+2-2
ii  libjsyntaxpane-java0.9.6~r156-6
ii  liblog4j1.2-java   1.2.17-7
ii  librsyntaxtextarea-java2.5.0-1
ii  openjdk-8-jdk [java6-sdk]  8u91-b14-2
ii  openjdk-8-jre [java7-runtime]  8u91-b14-2

umlet recommends no packages.

umlet suggests no packages.

-- no debconf information



Bug#823584: [PATCH] Correct top-level directory name in repackaged tarballs

2016-05-06 Thread Tormod Volden
On Fri, May 6, 2016 at 7:39 PM, Jakub Wilk wrote:
> * Tormod Volden, 2016-05-06, 11:21:
>>
>>
>> -packagename-upstream-version.orig
>> as the
>>
>> +packagename-upstream-version+dfsg
>> as the
>
>
> NACK. That would be misleading if the tarball was repacked for reason
> unrelated to DFSG.

So is it current practice, and policy, to use .orig? How misleading is that? :)

I thought it was a typo in the above text.

>
> Once we fix #560287, we could perhaps say that the directory should be:
>
> --

What is the repack-suffix?

>
> or something similar.
>
> Related bugs: #470960

Oh, reading that report: Exactly my point. And now 7 years and still
counting. So while waiting to decide which of the good solutions are
best, let's leave the worst and obvious wrong in place.

Tormod

PS. I didn't think about it initially, but I guess "NACK" means
"thanks for your patch and your interest in the developer reference,
but I don't think this is the best solution."

>
> --
> Jakub Wilk



Bug#823412: [PATCH] bsd-mailx : -b option is not working

2016-05-06 Thread Robert Luberda
reassign 823412 bsd-mailx
merge 823407 823412
thanks


Frederic Bonnard writes:
> Source: bsd-mailx
> Source-Version: 8.1.2-0.20160123cvs-2
> Tags: patch
> 
> --
> 
> A previous upstream commit allowed to "Use sendmail's '-t' flag when
> sendmail instead of specifying the list of recipients in argv." :
>
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/mail/send.c?rev=1.24=text/x-cvsweb-markup
>
> But a previous fix of Debian bug http://bugs.debian.org/75232 is based
on the fact
> that bcc recipients is given to sendmail command.

Many thanks for the analysis and finding the cause of the issue!

> I guess postfix, exim, etc .. will behave based on that sendmail option 
> compatibility's sake.

I've just found this link:
http://www.gossamer-threads.com/lists/exim/users/61977, and checked that
exim still works that way, i.e. does not strip Bcc unless the `-t'
option is given. On the other hand postfix seems to always remove the
Bcc header.


> 
> Also, I added that patch on top of all other instead of updating 
> 03-Base-fixes-2.patch

Thanks you a lot. I think I will go with updating the patch 03 anyway.

Regards,
robert



Bug#823394: sks: Exception raised when searching for specific key

2016-05-06 Thread Daniel Kahn Gillmor
[ adding the upstream sks-devel mailing list to this thread]

over on https://bugs.debian.org/823394, Joost wrote:

On Wed 2016-05-04 04:44:06 -0400, Joost van Baal-Ilić wrote:
> This query http://pgp.surfnet.nl/pks/lookup?search=satoshi=index gives
>
>  Error handling request
>  Error handling request. Exception raised.
>
> . It should of course either return "Search results for 'satoshi'" with a list
> of keys, or return "No results found  No results found: No keys found".  I
> suspect there _is_ a matching key; and I suspect sks in some way chokes on 
> that
> key.  Similar behaviour can be found at other sks keyservers (like e.g.
> pgp.mit.edu).
>
> FWIW, this bug looks a bit similar to https://bugs.debian.org/683328 .
>
> I can do _some_ debugging; but only on request and with some handholding.  I
> have no ocaml skills.

This is what's happening on the backend:

: 2016-05-06 16:38:58 Error handling request 
(GET,/pks/lookup?search=satoshi=index,[
: accept:*/*
: accept-encoding:identity
: connection:close
: host:localhost:11371
: user-agent:Wget/1.17.1 (linux-gnu)]): Invalid_argument("Too many responses")

it's not clear to me what the correct response should be for an sks
server in this case.  any ideas?  if a flood of matching User IDs make
it impossible to search for a user id, isn't that a DoS vector?

   --dkg


signature.asc
Description: PGP signature


Bug#823389: apt-listchanges: should add another newline character when a changelog entry does not end with a newline character

2016-05-06 Thread Robert Luberda
Source: apt-listchanges
Source-Version: 3.2


Vincent Lefevre writes:
> Severity: minor
> 
> apt-listchanges does not always put a blank line between changelog
> entries:
>

This was fixed in version 3.2, that is available in experimental.

(See
https://anonscm.debian.org/cgit/collab-maint/apt-listchanges.git/commit/?h=3.2=52e5db872ab44ef51eab8a504d1b29e7843a
: the _save_entry function first strips leading and trailing
whitespaces, and then adds '\n' at the end of entry).

Regards,
robert



Bug#821484: Bumping severity of PHP 7.0 transition bugs to serious

2016-05-06 Thread James Valleroy
tags 821484 patch
thanks

The attached patch will simply switch from PHP 5 to PHP 7.0.

--
James
From c31380d50e3f6fe55788d5302d324184273a6b6d Mon Sep 17 00:00:00 2001
From: James Valleroy 
Date: Fri, 6 May 2016 07:46:42 -0400
Subject: [PATCH] Switch to PHP 7.0.

---
 debian/control | 2 +-
 setup.d/90_apache2 | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 8fd813c..bc1b86d 100644
--- a/debian/control
+++ b/debian/control
@@ -47,7 +47,7 @@ Depends: ${misc:Depends}
  , iputils-ping
  , iw
  , libapache2-mod-gnutls
- , libapache2-mod-php5
+ , libapache2-mod-php
  , libnss-gw-name
  , libnss-mdns
  , libnss-myhostname
diff --git a/setup.d/90_apache2 b/setup.d/90_apache2
index dd132f2..30a79de 100755
--- a/setup.d/90_apache2
+++ b/setup.d/90_apache2
@@ -25,7 +25,7 @@ a2enmod headers
 
 # enable some critical modules to avoid restart while installing
 # Plinth applications.
-a2enmod php5
+a2enmod php7.0
 a2enmod cgi
 a2enmod authnz_ldap
 
-- 
2.8.1



signature.asc
Description: OpenPGP digital signature


Bug#823633: ffmpeg: please package and release minor ffmpeg 3.0.2 release

2016-05-06 Thread shirish शिरीष
Package: ffmpeg
Version: 7:3.0.1-3
Severity: wishlist

Dear Maintainer,

>From the upstream changelog :-

http://git.videolan.org/?p=ffmpeg.git;a=blob;f=Changelog;h=5cb30a0701c91b88e84904387f398507cdf88404;hb=ad559492dc75e7e6d74c48889eb6b90918a39126

version 3.0.2:
   6 - avcodec/ttaenc: Reallocate packet if its too small
   7 - configure: build fix for P5600 with mips code restructuring
   8 - mips: add support for R6
   9 - pgssubdec: fix subpicture output colorspace and range
  10 - avcodec/ac3dec: Reset SPX when switching from EAC3 to AC3
  11 - avfilter/vf_drawtext: Check return code of load_glyph()
  12 - avformat/mux: Check that deinit is set before calling it
  13 - avcodec/takdec: add code that got somehow lost in process of REing
  14 - avcodec/apedec: fix decoding of stereo files with one channel
full of silence
  15 - avcodec/avpacket: Fix off by 5 error
  16 - avcodec/h264: Fix for H.264 configuration parsing
  17 - avcodec/bmp_parser: Ensure remaining_size is not too small in
startcode packet crossing corner case
  18 - avcodec/pngdec: Fix alpha detection with skip_frame
  19 - Changelog: Make formating consistent
  20 - avfilter/src_movie: fix how we check for overflows with seek_point
  21 - avcodec/j2kenc: Add attribution to OpenJPEG project:

I did see that some commits were made for the same recently

http://lists.alioth.debian.org/pipermail/pkg-multimedia-commits/2016-May/thread.html

Look forward to see the new release in Debian.

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

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

Versions of packages ffmpeg depends on:
ii  libavcodec57 7:3.0.1-3
ii  libavdevice577:3.0.1-3
ii  libavfilter6 7:3.0.1-3
ii  libavformat577:3.0.1-3
ii  libavresample3   7:3.0.1-3
ii  libavutil55  7:3.0.1-3
ii  libc62.22-7
ii  libpostproc547:3.0.1-3
ii  libsdl1.2debian  1.2.15+dfsg1-4
ii  libswresample2   7:3.0.1-3
ii  libswscale4  7:3.0.1-3
ii  libvdpau11.1.1-3
ii  libx11-6 2:1.6.3-1

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
pn  ffmpeg-doc  

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8



Bug#823195: evince-common: Mouse Inverted Reversed Scrolling Does not Function

2016-05-06 Thread Jason Crain
On Fri, May 06, 2016 at 01:44:01PM -0400, Carl Nikolov wrote:
> In xfce the settings don't adapt to system wide setting

You are enabeling inverted scrolling through Xfce's Settings > Mouse and
Touchpad, the "Reverse Scroll Direction" option?

Is it only Evince that doesn't work, or do other GTK3 apps also not
work, such as gedit (Text Editor), Font Viewer, Gnome Terminal, etc?



Bug#823632: linux-libc-dev: architecture-dependent header in non-multiarch directory

2016-05-06 Thread Helmut Grohne
Package: linux-libc-dev
Severity: wishlist
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Hi Ben et al,

While looking into bootstrapping tilegx (#823167), I noticed that linux
installs some architecture dependent headers directly into /usr/include.
Exampes include:

/usr/include/arch/abi.h
/usr/include/arch/opcode.h

These should be moved to /usr/include/tilegx-linux-gnu. I am attaching
an architecture-generic patch. Please consider applying it.

Helmut
--- a/debian/rules.real
+++ b/debian/rules.real
@@ -341,6 +341,8 @@
 # Move include/asm to arch-specific directory
 	mkdir -p $(OUT_DIR)/include/$(DEB_HOST_MULTIARCH)
 	mv $(OUT_DIR)/include/asm $(OUT_DIR)/include/$(DEB_HOST_MULTIARCH)/
+	test -d $(OUT_DIR)/include/arch && \
+		mv $(OUT_DIR)/include/arch $(OUT_DIR)/include/$(DEB_HOST_MULTIARCH)/

 	+$(MAKE_SELF) install-base



Bug#823628: lintian: Please add autopkgtest-pkg-python to known test suites

2016-05-06 Thread Barry Warsaw
On May 06, 2016, at 10:05 PM, Axel Beckert wrote:

>Lintian in git already knows about this (for about a week :-), hence
>marking as pending.

Yay!  Thanks.


pgpUkehrL8JoF.pgp
Description: OpenPGP digital signature


Bug#823418: Info received (Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA)

2016-05-06 Thread Marc Haber
retitle #823418 add message to max_received_linelength DATA ACL
thanks


On Fri, May 06, 2016 at 11:13:51AM -0400, David Hill wrote:
> This solved this issue ... Now, why is this enforced ?  This is a new
> behavior and a lot of smtp servers are not enforcing this limitation like
> hotmail and some banks.

Having excessively long head lines is an RFC violation, and exim
doesn't want to send on messages that violate RFCs. While it cannot
split such header line, it is reasonable behavior not to accept those
messages in the first place.

We should, however, add a meaningful message to this ACL, retitling
the bug appropriately.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421



Bug#789352: faumachine: Homepage broken

2016-05-06 Thread Stefan Potyra
Hi Tobi,

thanks for reporting the issue, it's known by upstream.

For various reasons, it's not quite clear yet if

will be the new upstream addresss, but it's better than the current state.

I'll fix this with the next upstream release.

Thanks,
  Stefan.



Bug#823240: vlan: Does not work with interfaces named eno*

2016-05-06 Thread Ard van Breemen

Hi,

Michel Meyers schreef op 2016-05-02 17:39:

I recently ran into some VLAN issues on a new server and found that it
names all its interfaces eno1,  The following vlan scripts appear 
to

only take into account eth, bond and wlan interfaces:

 /etc/network/if-pre-up.d/vlan
 /etc/network/if-post-down.d/vlan

It would be nice if you could also make them handle eno interfaces.
Thanks for your work.


I would love to, but this happens:
http://anonscm.debian.org/cgit/collab-maint/vlan.git/commit/?id=3eed5b7482eb7952425b7455445df22419346047

It was working in 2010 in version 1.9-5 but it got "rejected".
As such, I am only a maintainer by name.

I have Cc: the guy that actually really does maintain the latest 
version.


Regards,

Ard van Breemen.



Bug#823628: lintian: Please add autopkgtest-pkg-python to known test suites

2016-05-06 Thread Axel Beckert
Control: tag -1 +pending

Hi Barry,

Barry Warsaw wrote:
> In Python packages, with autopkg8, you can now say this in your
> d/control file:
> 
> Testsuite: autopkgtest-pkg-python
> 
> but lintian doesn't know about this yet:
> 
> Now running lintian...
> W: pyparsing source: unknown-testsuite autopkgtest-pkg-python
> Finished running lintian.

Lintian in git already knows about this (for about a week :-), hence
marking as pending.

See 
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=8fdfa88f23bec650b9fa1a3055ec262662f08d37

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



Bug#823631: please add cross build support for tilegx

2016-05-06 Thread Helmut Grohne
Source: libgpg-error
Version: 1.21-3
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

Hi Daniel,

there is another architecture around the corner. tilegx is about to be
added to dpkg (#823167). As usual, libgpg-error needs an update for it.
Chris Metcalf was kind enough to run a native build and I am attaching
his lock-obj-pub header. Please add it to libgpg-error.

Helmut
## lock-obj-pub.tilegx-unknown-linux-gnu.h
## File created by gen-posix-lock-obj - DO NOT EDIT
## To be included by mkheader into gpg-error.h

typedef struct
{
  long _vers;
  union {
volatile char _priv[40];
long _x_align;
long *_xp_align;
  } u;
} gpgrt_lock_t;

#define GPGRT_LOCK_INITIALIZER {1,{{0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0}}}
##
## Local Variables:
## mode: c
## buffer-read-only: t
## End:
##


Bug#823630: please add cross build support for powerpcspe

2016-05-06 Thread Helmut Grohne
Source: libgpg-error
Version: 1.21-3
Tags: upstream
User: helm...@debian.org
Usertags: rebootstrap

Hi Daniel,

Even though the powerpcspe architecture is around for some time already,
libgpg-error never got around adding cross build support for it.
Fortunately, libgpg-error is built as a Debian port already, so you can
find the relevant header in one of its build logs:

https://buildd.debian.org/status/fetch.php?pkg=libgpg-error=powerpcspe=1.22-1=1461625154

Please add it to libgpg-error.

Helmut



Bug#823629: reprepro: Please provide a way to compact references.db after some of its content has been freed

2016-05-06 Thread intrigeri
Package: reprepro
Version: 4.16.0-1
Severity: wishlist
X-Debbugs-Cc: k...@debian.org

Hi,

for Tails we have a system that uses reprepro snapshots intensively
(basically, a large subset of the Debian archive is snapshot'ed four
times a day). And then, we use _removereferences (+ manually removing
the corresponding directory in dists/) to free the snapshots we don't
need anymore.

But despite the cleanup operation (_removereferences), it seems that
references.db keeps growing. As a result, some operations become very
slow unless there's enough memory available to keep that file in the
disk cache.

FYI, we're talking of a (currently) 5.4 GiB references.db here.

I'm sure that there must be a good reason (such as optimizing I/O) for
the current behavior, and that's fine with me. But would it be
possible to have one extra operation, that one could run from time to
time, and that compacts references.db so that it uses only the disk
space (and thus, the in-memory disk cache) that it needs?

And, just in case I find someone ready to implement it: any pointer to
where and how it could be done?

Cheers,
--
intrigeri



Bug#673193: apt-get: should remove foreign arch packages even if arch suffix is missing

2016-05-06 Thread Daniel Richard G.
The new wishlist item has been submitted: bug #823625.
-- 
Daniel Richard G. || sk...@iskunk.org
My ASCII-art .sig got a bad case of Times New Roman.



Bug#823628: lintian: Please add autopkgtest-pkg-python to known test suites

2016-05-06 Thread Barry Warsaw
Package: lintian
Version: 2.5.44
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

In Python packages, with autopkg8, you can now say this in your
d/control file:

Testsuite: autopkgtest-pkg-python

but lintian doesn't know about this yet:

Now running lintian...
W: pyparsing source: unknown-testsuite autopkgtest-pkg-python
Finished running lintian.

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

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

Versions of packages lintian depends on:
ii  binutils  2.26-8
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.25-2
ii  gettext   0.19.7-2
ii  hardening-includes2.8+nmu2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.29+b5
ii  libarchive-zip-perl   1.57-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-1+b1
ii  libdata-alias-perl1.20-1+b1
ii  libdpkg-perl  1.18.6
ii  libemail-valid-perl   1.198-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.413-1+b1
ii  libparse-debianchangelog-perl 1.2.0-8
ii  libperl5.22 [libdigest-sha-perl]  5.22.2-1
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.41-6+b1
ii  man-db2.7.5-1
ii  patchutils0.3.4-1
ii  perl  5.22.2-1
ii  t1utils   1.39-2
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages lintian recommends:
ii  dpkg 1.18.6
ii  libautodie-perl  2.29-2
ii  libperlio-gzip-perl  0.19-1+b1
ii  perl 5.22.2-1
ii  perl-modules-5.22 [libautodie-perl]  5.22.2-1

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.6
ii  libhtml-parser-perl3.72-1
ii  libtext-template-perl  1.46-1

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXLPYlAAoJEBJutWOnSwa/VwYP/0X+AAKxdoVBCThnsrRnViX6
iJQxQeFaL2pONTOHROVhUm+SfKlmKPePjSkmhSrHQDNTeDtfOy13Q7CE+xV5TXgq
YKhrrBqlte97QLNgQCX0gri7qcsvbqrglrIRI+rcYh7VDllGWUkkkVjAth0wqJqx
/+s+A1chMT6b1s5z1GKK+yVZVs8lj4quNObI4peSn3LCEtvEd4wOPYwJaO/ULrN9
a13r08PDN0R0icyz2kB0j9HF7OMXs9nXTWO1R961xJZUB9oUl+Y81+FyE4he/9LW
zQumW32j9v2G+B0BIPGZaF7agYuryQEUnj20MuhIYJoyybomzBMEmMofS0KGJ40j
iShDknUlA7Ol8c1+texZhT7gTwI948zirLy8puHCe6RXx9gq+Fean5mvl/lihkWV
/O7i8ufMQP4UctHJeNAOUUKtSaVQDc7FoKyKL4BtNWJILLQ733paniEuvRhfDAuu
aKsjf6ddAKzJDHS233MEI2Ui3z5hqxf6k3I8KRxR+CxROEOefjLs/UtRTKtldjOp
m7TixrPlfmpp2Pvc+AOapwRN+ChKXH+Nuo0ko6KGqZv1rFBw2uT4pTzAnjR6B0Zc
TEMgPHaFPliiGscBrxFxehJ5gaXSYnd99Dlw1bbNEmwBT3FlJBS8ClQtYV6xmx/6
VyTiC1NrSKarq2vgg9Yn
=T8TY
-END PGP SIGNATURE-



Bug#821874: RM faumachine -- RoQA, unmaintained, RC-Buggy, Depends on to be removed packages

2016-05-06 Thread Stefan Potyra
Hi,

as promised a short status update:

There have been quite some changes upstream-wise, but unfortunately it still
doesn't build with current gcc version found in unstable(see TLDR about the
reason).

Amd I've been once again accounted to do the upstream release...

So with my upstream hat on: I'd very much like to stay FAUmachine in the
archive, however with my DM hat, I think it's best to remove the binary
packages for now to not block anything.

Are you OK with this plan and/or do you have good advice for me?

Cheers,
  Stefan.
   

TLDR:
FAUmachine uses a forked version of qemu to build a just-in-time compiler. The
idea from Fabrice Bellard is brilliant: Code the emulation of assembly
instructions in C and let gcc produce binary code for it. Then use a script to
mange this binary code to be usable as input as basic blocks for the
jut-in-time-compiler.

Unfortunately, at this script is highly dependent on the produced assembly code
(e.g. just one return instruction per function) and this usually breaks with
every new gcc version :(.

This results in the current build breakage, and while this has been fixed for
the gcc version in stable, breakage occurs with the current gcc version in
unstable.



Bug#823627: Please detect embedded-javascript-library libjs-jquery-migrate-1

2016-05-06 Thread Jean-Michel Vourgère
Package: lintian
Version: 2.5.30+deb8u4
Severity: wishlist
Tags: patch

Hello

It would be nice if lintian could warn the maintainers about embedded
copies of jquery-migrate. The new package libjs-jquery-migrate-1 now
provides it.

Attached is a patch.

List of expected targets are described in #823416.

Thanks!
diff --git a/data/files/js-libraries b/data/files/js-libraries
index 62d9028..7cd250e 100644
--- a/data/files/js-libraries
+++ b/data/files/js-libraries
@@ -29,6 +29,7 @@ libjs-jquery-jush~~ (?i)/jquery\.jush$EXT
 libjs-jquery-livequery   ~~ (?i)/jquery\.livequery$EXT
 libjs-jquery-meiomask~~ (?i)/jquery\.meiomask$EXT
 libjs-jquery-metadata~~ (?i)/jquery\.metadata$EXT
+libjs-jquery-migrate-1   ~~ (?i)/jquery-migrate(?:-1[\d\.]*)(?:[\.-]min)$EXT
 libjs-jquery-mousewheel  ~~ (?i)/jquery\.mousewheel$EXT
 libjs-jquery-opacityrollover ~~ (?i)/jquery\.opacityrollover$EXT
 libjs-jquery-tablesorter ~~ (?i)/jquery\.tablesorter$EXT



Bug#823625: Interpret "apt-get install foo bar-" to prevent install of any arch-variants of "bar"

2016-05-06 Thread Daniel Richard G.
Package: apt
Version: 1.2.11
Severity: wishlist

This RFE was split off from bug #673193 by the maintainer's request.

When one specifies a command like

# apt-get install foo bar-

the intent is usually to install package "foo" while preventing package
"bar" from being pulled in as a dependency (assuming that "bar" is not
already installed, and is not a hard dependency of "foo").

With multi-arch support, however, this can currently lead to the
unexpected behavior where "bar"---equivalent to e.g. "bar:amd64" on an
amd64 system---is correctly declined for installation, but "bar:i386"
gets pulled in instead.

The original intent of the command is likely to have been "don't pull in
package 'bar' at all." This can be better expressed by specifying
"bar:*-", though this may have the undesired effect of additionally
removing pre-installed variants of "bar".

This request, then, is for "bar-" to prevent installation not just of
the native-arch variant of "bar", but all arch variants, to better align
with the usual intent behind that syntax.



Bug#822194: libdebug: diff for NMU version 0.5.1-1.1

2016-05-06 Thread Jakub Wilk

Control: tags 822194 + patch
Control: tags 822194 + pending

Dear maintainer,

I've prepared an NMU for libdebug (versioned as 0.5.1-1.1) and uploaded 
it to DELAYED/2. Please feel free to tell me if I should delay it 
longer.


--
Jakub Wilk
diffstat for libdebug-0.5.1 libdebug-0.5.1

 changelog |7 +++
 rules |2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)


No differences were encountered between the control files

diff -Nru libdebug-0.5.1/debian/changelog libdebug-0.5.1/debian/changelog
--- libdebug-0.5.1/debian/changelog	2016-04-21 22:35:40.0 +0200
+++ libdebug-0.5.1/debian/changelog	2016-05-06 21:04:09.0 +0200
@@ -1,3 +1,10 @@
+libdebug (0.5.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Disable parallel builds (closes: #822194).
+
+ -- Jakub Wilk   Fri, 06 May 2016 21:04:02 +0200
+
 libdebug (0.5.1-1) unstable; urgency=medium
 
   * Acknowledge Jakub Wilk's NMU; thanks!
diff -Nru libdebug-0.5.1/debian/rules libdebug-0.5.1/debian/rules
--- libdebug-0.5.1/debian/rules	2016-04-21 22:35:40.0 +0200
+++ libdebug-0.5.1/debian/rules	2016-05-06 21:03:59.0 +0200
@@ -31,4 +31,4 @@
 		libdir=/usr/lib/$(DEB_HOST_MULTIARCH) install
 
 %:
-	dh $@
+	dh $@ --no-parallel


Bug#812462: [Pkg-monitoring-maintainers] Bug#812462: ganglia: diff for NMU version 3.6.0-6.1

2016-05-06 Thread Daniel Pocock


On 06/05/16 20:53, Jean-Michel Nirgal Vourgère wrote:
> Control: tags 812462 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for ganglia (versioned as 3.6.0-6.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 


No need to delay it, you are welcome to upload it immediately as long as
you also commit your changes in the Git VCS

Regards,

Daniel



Bug#823624: devscripts: [uscan] please include tgz in @ARCHIVE_EXT@

2016-05-06 Thread Daniel Kahn Gillmor
Package: devscripts
Version: 2.16.4
Severity: normal
Tags: patch

Dear Maintainer,

some upstreams (like sks) ship their tarballs as foo-1.1.5.tgz

@ARCHIVE_EXT@ fails to locate this tarball.

The attached patch should address this concern.

--dkg

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
Not present

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev 1.18.4
ii  libc62.22-7
ii  perl 5.22.1-10
pn  python3:any  

Versions of packages devscripts recommends:
ii  apt 1.2.11
ii  at  3.1.18-2
ii  curl7.47.0-1
ii  dctrl-tools 2.24-2
ii  debian-keyring  2016.04.22
ii  dput-ng [dput]  1.10
ii  dupload 2.7.0
pn  equivs  
ii  fakeroot1.20.2-1
ii  file1:5.25-2
ii  gnupg   2.1.11-7+exp1
ii  libdistro-info-perl 0.14
ii  libencode-locale-perl   1.05-1
ii  liblwp-protocol-https-perl  6.06-2
pn  libsoap-lite-perl   
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  lintian 2.5.44
ii  man-db  2.7.5-1
ii  patch   2.7.5-1
ii  patchutils  0.3.4-1
ii  python3-debian  0.1.27
ii  python3-magic   1:5.25-2
ii  sensible-utils  0.0.9
ii  strace  4.10-3
ii  unzip   6.0-20
ii  wdiff   1.2.2-1+b1
ii  wget1.17.1-1+b1
ii  xz-utils5.1.1alpha+20120614-2.1

Versions of packages devscripts suggests:
ii  build-essential  11.7
pn  cvs-buildpackage 
ii  devscripts-el35.12
ii  diffoscope   52
pn  dose-extra   
pn  gnuplot  
ii  gpgv 2.1.11-7+exp1
pn  libauthen-sasl-perl  
pn  libfile-desktopentry-perl
ii  libnet-smtp-ssl-perl 1.03-1
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
ii  mailutils [mailx]1:2.99.99-1
ii  mozilla-devscripts   0.45.1
pn  mutt 
ii  openssh-client [ssh-client]  1:7.2p2-5
ii  s-nail [mailx]   14.8.8-1
ii  svn-buildpackage 0.8.5+nmu1
ii  w3m  0.5.3-27

-- debconf-show failed
>From 8039b887e7eb4ed03ce4f12cdee9f69fe89abaee Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Fri, 6 May 2016 15:14:11 -0400
Subject: [PATCH] include tgz in @ARCHIVE_EXT@

---
 scripts/uscan.pl | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/uscan.pl b/scripts/uscan.pl
index e105a68..dab1947 100755
--- a/scripts/uscan.pl
+++ b/scripts/uscan.pl
@@ -262,7 +262,7 @@ This is substituted by the legal upstream version regex (capturing).
 
 This is substituted by the typical archive file extension regex (non-capturing).
 
-  (?i)\.(?:tar\.xz|tar\.bz2|tar\.gz|zip)
+  (?i)\.(?:tar\.xz|tar\.bz2|tar\.gz|zip|tgz)
 
 =item B<@SIGNATURE_EXT@>
 
@@ -4159,7 +4159,7 @@ sub process_watchfile ()
 
 	# Handle @PACKAGE@ @ANY_VERSION@ @ARCHIVE_EXT@ substitutions
 	my $any_version = '[-_]?(\d[\-+\.:\~\da-zA-Z]*)';
-	my $archive_ext = '(?i)\.(?:tar\.xz|tar\.bz2|tar\.gz|zip)';
+	my $archive_ext = '(?i)\.(?:tar\.xz|tar\.bz2|tar\.gz|zip|tgz)';
 	my $signature_ext = $archive_ext . '\.(?:asc|pgp|gpg|sig)';
 	s/\@PACKAGE\@/$package/g;
 	s/\@ANY_VERSION\@/$any_version/g;
-- 
2.8.1



Bug#823616: fpga-icestorm-chipdb: please make the build reproducible (randomness)

2016-05-06 Thread Ruben Undheim
Hi Daniel,

Thanks a lot for figuring out why it wasn't reproducible. I wasn't sure where 
to start.

I will apply your patch.

Cheers!
Ruben

On Fri, May 06, 2016 at 05:08:10PM +, Daniel Shahaf wrote:
> Source: fpga-icestorm
> Version: 0~20160218gitf2b2549-1
> Severity: wishlist
> Tags: upstream patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: randomness
> 
> Dear Maintainer,
> 
> While working on the “reproducible builds” effort [1], we have noticed
> that fpga-icestorm-chipdb could not be built reproducibly: the order of
> ".pins" sections in chipdb-1k.txt and chipdb-8k.txt is random [2].
> 
> The attached patch ensures a stable section order in those two files.
> I believe with this patch, fpga-icestorm will be fully reproducible.
> 
> Best,
> 
> Daniel
> 
>  [1]: https://wiki.debian.org/ReproducibleBuilds
>  [2]: 
> https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/fpga-icestorm.html

> diff --git a/debian/patches/reproducible.patch 
> b/debian/patches/reproducible.patch
> new file mode 100644
> index 000..43779cb
> --- /dev/null
> +++ b/debian/patches/reproducible.patch
> @@ -0,0 +1,17 @@
> +Description: make the build reproducible
> +Author: Daniel Shahaf 
> +Bug-Debian: https://bugs.debian.org/-1
> +Last-Update: 2016-05-06
> +
> +--- fpga-icestorm-0~20160218gitf2b2549.orig/icebox/icebox_chipdb.py
>  fpga-icestorm-0~20160218gitf2b2549/icebox/icebox_chipdb.py
> +@@ -172,7 +172,7 @@ all_group_segments = ic.group_segments(a
> + print(".device %s %d %d %d" % (ic.device, ic.max_x+1, ic.max_y+1, 
> len(all_group_segments)))
> + print()
> + 
> +-for key in list(icebox.pinloc_db.keys()):
> ++for key in sorted(icebox.pinloc_db.keys()):
> + key_dev, key_package = key.split("-")
> + if key_dev == ic.device:
> + print(".pins %s" % (key_package))
> +
> diff --git a/debian/patches/series b/debian/patches/series
> index 0353649..e512c55 100644
> --- a/debian/patches/series
> +++ b/debian/patches/series
> @@ -3,3 +3,4 @@
>  03_cxxflags.patch
>  override-CXX.patch
>  fix_spelling_in_binaries.patch
> +reproducible.patch

> -- 
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers



Bug#814227: Pending fixes for bugs in the prometheus-node-exporter package

2016-05-06 Thread pkg-go-maintainers
tag 814227 + pending
thanks

Some bugs in the prometheus-node-exporter package are closed in
revision 717fa6634a4e0edbb757b8fe96e4b5c216f5f76c in branch
'debian/sid' by Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/prometheus-node-exporter.git/commit/?id=717fa66

Commit message:

New upstream release, which is really 0.12.0. The previous version was 
actually 0.12.0rc1, but I made a mistake, hence the weird version number for 
this release. Closes: #814227.



Bug#823264: wine32-tools: Allow installation on amd64 with 64-bit tools

2016-05-06 Thread Jens Reyer
control: retitle -1 wine32-tools: Allow installation on amd64

On 05/02/2016 08:56 PM, Javier Serrano Polo wrote:
> Package: wine32-tools
> Version: 1.8.1-2
> Severity: wishlist
> 
> This is somewhat related to https://bugs.debian.org/807926 .
> wine32-tools works with gcc-multilib and perl from amd64. Adding this
> type of dependency should work:
> 
> Depends: gcc | gcc-multilib:amd64 [amd64], perl | perl:amd64
> [amd64]

Thanks for the hint! Unfortunately there are some issues:

1.)
"[amd64]" seems to be related to the build host. Since wine32-tools is
built on i386 the expression simply is omitted.
Solution: simply omit.


2.)
*Theoretically* speaking: gcc-multilib is not multi-arch'ed [1]. For
"gcc-multilib:amd64" it would need to be "allowed", for omitting the
arch and just installing it from the host arch it would need to be
"foreign".

Quoting https://wiki.ubuntu.com/MultiarchSpec:
  Multi-Arch: no
  The package is not co-installable and it must not be used to satisfy
  the dependency of any package of another architecture than its own.

Other packages of the same source package have multi-arch fields, so I
assume there is a reason that this has none. But I have no real
knowledge about gcc in general and gcc-multilib in particular.

*In practice* it seems to work. Not sure if I'm wrong, or the tools
(tested with aptitude) permit things that they shouldn't.

[1]: See
https://tracker.debian.org/media/packages/g/gcc-defaults/control-1.161


3.)
The dependency on perl originates from "${perl:Depends}". If we just
added "| perl:amd64" this would break if the variable gets expanded to
several values. Just using "perl|perl:amd64" might be ok, but omitting
the variable sounds wrong to me.
At least perl is "Multi-Arch: allowed", so your suggestion works otherwise.


4.)
Finally, even if we got this working, co-installability of wine32-tools
and wine64-tools is not possible atm. They need to conflict with each
other, because they use the same binary names in /usr/lib/wine/. We had
wrappers in the past for winegcc32 and winegcc64 for co-installability,
but I'd like to avoid the mess of doing this again, especially since the
packaging changed since then, and we'd have to do this for every
executable in the -tools packages. Therefore retitling this bug to
reflect the part that needs to be solved first (not sure anyway what you
exactly meant with "64-bit tools").

Final sidenote: there's no gcc-multilib for arm64 (the other 64-bit
architecture with Wine).


Below patch applies to the wine32VERSION-tools section of d/control.in.
With this I could install wine32-development-tools on amd64. If we
replaced "${perl:Depends}" with "perl" we might try it (but again, see
point 2 and 3). Opinions?

diff --git a/debian/control.in b/debian/control.in
index c2b8296..03f81fb 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -171,8 +171,8 @@ Architecture: any-i386 any-powerpc armel armhf
 Section: libdevel
 Built-Using: ${built:Using}
 Depends:
- gcc,
- ${perl:Depends},
+ gcc | gcc-multilib:amd64,
+ ${perl:Depends} | perl:amd64,
  ${misc:Depends},
  ${shlibs:Depends},
  libwineVERSION-dev (= ${binary:Version}),


Greets
jre



Bug#823043: zsh FTBFS since yodl 3.08.00-1 in the same way that c++-annotations FTBFSed with 3.07.00-1 (was: Re: Bug#823043 closed by f.b.brok...@rug.nl (Frank B. Brokken) (Bug#823043: fixed in yodl 3

2016-05-06 Thread Axel Beckert
Control: reopen -1
Control: affects -1 src:zsh
Control: found -1 3.08.00-1

Hi Frank,

Debian Bug Tracking System wrote:
>  yodl (3.08.00-1) unstable; urgency=medium
>  .
>* New upstream release fixes a bug in handling multiple identical options.
>  (Closes: #823043).

Frank B. Brokken wrote:
> Thanks for your bug report. It looks like you encountered a real bug, and I'm
> still somewhat in the dark as to why it never has been observed
> before. Because of that (i.e., me satisfying my own curiosity) I'll need a bit
> more time to submit a fix, but at least I think I've located the cause of the
> problem. I'll probably have a fix ready by Monday or a bit earlier.
> 
> One minor thing: it's not an Annotations issue, but a bug in the Yodl
> package.

I'm not 100% sure what's going on, but it seems to me that while
c++-annotations indeed FTBFS with 3.07.00-1 and builds fine again with
3.08.00-1 (verified it :-), it's the opposite way round with zsh:

It builds fine with yodl 3.07.00-1, but FTBFS with 3.08.00-1 as
follows:

Zsh Yodl-to-man converter
Including file Zsh/zftpsys.yo
yodl -k -L -o ../../Doc/zshzle.1 -I../../Doc:. -w zman.yo version.yo
../../Doc/zshzle.yo
Zsh Yodl-to-man converter
Including file Zsh/zle.yo
yodl -k -L -o ../../Doc/zshall.1 -I../../Doc -DZSHALL -w zman.yo version.yo 
zsh.yo
`ZSHALL' (symbol) multiply defined
`ZSHALL' (symbol) multiply defined
`ZSHALL' (symbol) multiply defined
Error(s) in command line arguments. Terminating

Feel free to clone and close the original bug report if you think that
my issue is a different issue. (But it looks very similar to me.)

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



Bug#812462: ganglia: diff for NMU version 3.6.0-6.1

2016-05-06 Thread Jean-Michel Nirgal Vourgère
Control: tags 812462 + pending

Dear maintainer,

I've prepared an NMU for ganglia (versioned as 3.6.0-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru ganglia-3.6.0/debian/changelog ganglia-3.6.0/debian/changelog
--- ganglia-3.6.0/debian/changelog	2014-10-12 13:26:20.0 +0200
+++ ganglia-3.6.0/debian/changelog	2016-05-06 20:27:18.0 +0200
@@ -1,3 +1,10 @@
+ganglia (3.6.0-6.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Updated build-dependencies. Thanks Michael Tautschnig. (Closes: #812462)
+
+ -- Jean-Michel Vourgère   Fri, 06 May 2016 18:22:47 +
+
 ganglia (3.6.0-6) unstable; urgency=medium
 
   * Fix for missing service file. (Closes: #764836)
diff -Nru ganglia-3.6.0/debian/control ganglia-3.6.0/debian/control
--- ganglia-3.6.0/debian/control	2014-09-11 11:59:34.0 +0200
+++ ganglia-3.6.0/debian/control	2016-05-06 20:20:12.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Debian Monitoring Maintainers 
 Uploaders: Stuart Teasdale , Daniel Pocock 
 Homepage: http://ganglia.info/
-Build-Depends: debhelper (>> 9.0.0), librrd2-dev, autoconf, autotools-dev, automake, libapr1-dev, libexpat1-dev, python-dev, libconfuse-dev, po-debconf, libxml2-dev, libdbi0-dev, libpcre3-dev, gperf, libtool, rsync, libkvm-dev [kfreebsd-any]
+Build-Depends: debhelper (>> 9.0.0), librrd-dev, autoconf, autotools-dev, automake, libapr1-dev, libexpat1-dev, python-dev, libconfuse-dev, po-debconf, libxml2-dev, libdbi0-dev, libpcre3-dev, gperf, libtool, rsync, libkvm-dev [kfreebsd-any], pkg-config, libz-dev
 Standards-Version: 3.9.4
 Vcs-Git: git://anonscm.debian.org/pkg-monitoring/ganglia.git
 Vcs-Browser: http://anonscm.debian.org/cgit/pkg-monitoring/ganglia.git


Bug#823530: systemd 228 reduced maximum number of tasks in a cgroup to 512 by default

2016-05-06 Thread Antonio Terceiro
Control: severity -1 important

On Thu, 05 May 2016 20:14:20 +0200 Sebastian Schmidt  wrote:
> Package: systemd
> Version: 229-3
> Severity: normal
> Tags: upstream
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Hi,
> 
> Whilst debugging why Chrome would regularly fail to create new
> threads[1] and zsh couldn’t fork I noticed that:
> - - All affected processes run in the /system.slice/xdm.service cgroup
> - - “systemctl status xdm.service” says “Tasks: 476 (limit: 512)”
> - - The changelog for systemd 228 reads[2]:
> 
> There's a new system.conf setting DefaultTasksMax= to control
> the default TasksMax= setting for services and scopes running on
> the system.
> […]
> The setting now defaults to 512, which means services that are
> not explicitly configured otherwise will only be able to create
> 512 processes or threads at maximum, from this version on.
> 
> - - Nothing in xdm’s PAM configuration would load pam_systemd for creating
>   a session.
> 
> I’m not sure whether using pam_systemd would actually fix that; but
> even then I find this new limit per cgroup at least surprising and
> it apparently breaks a lot of software.
> 
> Sebastian
> 
> 1: https://crbug.com/602002
> 2: 
> https://github.com/systemd/systemd/blob/ccddd104fc95e0e769142af6e1fe1edec5be70a6/NEWS#L373-393

I am seeing some inconsistency in this. On my laptop, I don't see any
limits being applied, even though I am on a fully up to date unstable
(tried both with my main account from a terminal emulator in GNOME, and
from a console login with a freshly created user account):

$ ulimit -u 22988

On a newly created VM, also on unstable, I do see limits, e.g. after
logging in on the console:

terceiro@sid:~$ ulimit -u 384

This has already biten my in 2 occasions:

* for several reasons, the arm64 machines I am using on ci.debian.net
  need a 4.4 kernel and systemd 228, so I several tests are failing on
  arm64 with "Can't fork: resource temporarily unavailable" during
  *package installation*.

* A bug was just reported against ruby2.3 because of a FTBFS on a stretch
  VM, apperently caused by this new systemd behavior (#823604)

I do appreciate the idea of systemd imposing sane limits on tasks, but
this will cause A LOT of breakage in all sorts of places, and we need
figure out a plan forward. Will every package need to start declaring
higher limits explicitly?


signature.asc
Description: PGP signature


Bug#823623: libceres-dev: config.h missing

2016-05-06 Thread Francisco Rafael Leon
Package: libceres-dev
Version: 1.11.0~dfsg0-2+b1
Severity: important

Dear Maintainer,

g++ -c -o helloworld.o helloworld.cc -O2 -DNDEBUG -std=c++0x 
-I/usr/include/eigen3
In file included from /usr/include/ceres/types.h:42:0,
 from /usr/include/ceres/internal/variadic_evaluate.h:38,
 from /usr/include/ceres/internal/autodiff.h:148,
 from /usr/include/ceres/autodiff_cost_function.h:132,
 from /usr/include/ceres/ceres.h:37,
 from helloworld.cc:5:
/usr/include/ceres/internal/port.h:37:35: fatal error: ceres/internal/config.h: 
No such file or directory
compilation terminated.

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

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

Versions of packages libceres-dev depends on:
ii  libceres1   1.11.0~dfsg0-2+b1
ii  libeigen3-dev   3.3~beta1-2
ii  libgflags-dev   2.1.2-3
ii  libgoogle-glog-dev  0.3.4-2
ii  libsuitesparse-dev  1:4.4.6-1

libceres-dev recommends no packages.

libceres-dev suggests no packages.

-- no debconf information



Bug#786730: ITP: python-pychromecast -- Python library for communicating with Google Chromecast

2016-05-06 Thread Ruben Undheim
Hi Muammar,

The reason for that it's not in, is because of the dependency on protobuf 3.0, 
which
is not yet in Debian. See https://bugs.debian.org/795841


However, I made an attempt now today to restore protobuf 2 support in the 
newest pychromecast
version. You can have a look here:
  
https://anonscm.debian.org/cgit/python-modules/packages/pychromecast.git/log/?h=before_protobuf3_in_debian
 or clone with:
  git clone 
https://anonscm.debian.org/git/python-modules/packages/pychromecast.git -b 
before_protobuf3_in_debian


Perhaps we could get that into Debian. Note that we can only make Python 2 
packages since
python-protobuf is only for Python 2 so far.


Ruben

On Fri, May 06, 2016 at 04:02:07PM +0200, Muammar El Khatib wrote:
> Hi Ruben,
> 
> On Mon, 25 May 2015 01:59:53 +0200 Ruben Undheim  
> wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Ruben Undheim 
> >
> > * Package name: python-pychromecast
> >   Version : 0.6
> >   Upstream Author : Paulus Schoutsen
> > * URL : https://github.com/balloob/pychromecast
> > * License : MIT
> >   Programming Lang: Python
> >   Description : Python library for communicating with Google Chromecast
> >
> >
> > This library makes it easy to communicate with a Chromecast device using
> > Python.
> >
> > It currently supports:
> >
> >  - Auto discovering connected Chromecasts on the network
> >  - Start the default media receiver and play any online media
> >  - Control playback of current playing media
> >  - Implement Google Chromecast api v2
> >  - Communicate with apps via channels
> >  - Easily extendable to add support for unsupported namespaces
> >
> >
> 
> 
> I was wondering what is the status of your efforts to get python-pychromecast 
> in
> the archive?.
> 
> Cheers,
> 
> --
> Muammar El Khatib.
> http://muammar.me | http://proyectociencia.org



Bug#823418: Info received (Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA)

2016-05-06 Thread Andreas Metzler
On 2016-05-06 David Hill  wrote:
> This solved this issue ... Now, why is this enforced ?  This is a new
> behavior and a lot of smtp servers are not enforcing this limitation like
> hotmail and some banks.

https://bugs.exim.org/show_bug.cgi?id=1684



Bug#820480: pocl: New version pocl 0.13

2016-05-06 Thread Matthias Klose

Control: tags -1 + patch

fyi, I upgraded the package here:
https://launchpad.net/ubuntu/+source/pocl/0.13-0ubuntu2

As mentioned in #823528, you might want to introduce some new binary package, or 
rename the library package. I think some symbols were lost too in 0.13.


I haven't checked if the glibc-2.23 fix works this way with 2.22.



Bug#822431: systemd: Boot stalls for 90 s at early boot (system-generators terminated by signal ALRM)

2016-05-06 Thread Alexandre Detiste
Found it :-)

This is a Python bug: https://bugs.python.org/issue26839

Sorry for cross posting to the three bugs.

I don't know, how/wether these 3 bugs should those been merged.

Martin/Matthias, can you handle this ?

-

How I found it:

The first line I get in dmesg after typing something at the keyboard is  
"random: nonblocking pool is initialized"

systemd-cron does uses Python's hashlib to compute md5's; but that doesn't need 
any source of randomness at all.

Now I see even an empty python program
with only the shebang line would still trigger this delay;
so this had to be a python runtime related bug.


Alexandre



Bug#642354: [patch] make the freetype -dev package M-A: same

2016-05-06 Thread Matthias Klose

Control: tags -1 + patch

- Make libfreetype6-dev M-A: same.
- Error out on the use of the freetype-config --libtool option.
- Don't add multiarch libdirs for freetype-config --libs.
- Install the freetype2/freetype/config headers into the multiarch
  include path and provide an arch-independent header in /usr/include.

The approach here is to make the freetype-config binary architecture independent 
(from your point of view, it's obsolete anyway), and error out on the --libs 
option.  The alternative would be to split out this binary into it's own package 
libfreetype6-bin.


The solution for the header ensures that the header is still found in the 
arch-independent include dir, and that you don't need to specify a second 
include dir.
- Make libfreetype6-dev M-A: same.
- Error out on the use of the freetype-config --libtool option.
- Don't add multiarch libdirs for freetype-config --libs.
- Install the freetype2/freetype/config headers into the multiarch
  include path and provide an arch-independent header in /usr/include.

diff -pruN 2.6.3-3/debian/control 2.6.3-3ubuntu1/debian/control
--- 2.6.3-3/debian/control	2016-04-28 20:08:35.0 +
+++ 2.6.3-3ubuntu1/debian/control	2016-04-28 20:08:36.0 +
@@ -48,6 +49,7 @@ Description: FreeType 2 font engine, sha
 
 Package: libfreetype6-dev
 Architecture: any
+Multi-Arch: same
 Section: libdevel
 Depends: libfreetype6 (= ${binary:Version}), libc6-dev | libc-dev, zlib1g-dev | libz-dev, libpng-dev, ${misc:Depends}
 Description: FreeType 2 font engine, development files
diff -pruN 2.6.3-3/debian/multiarch.h.in 2.6.3-3ubuntu1/debian/multiarch.h.in
--- 2.6.3-3/debian/multiarch.h.in	1970-01-01 00:00:00.0 +
+++ 2.6.3-3ubuntu1/debian/multiarch.h.in	2016-04-28 20:08:36.0 +
@@ -0,0 +1,79 @@
+#if defined(__linux__)
+# if defined(__x86_64__) && defined(__LP64__)
+#  include 
+# elif defined(__x86_64__) && defined(__ILP32__)
+#  include 
+# elif defined(__i386__)
+#  include 
+# elif defined(__aarch64__) && defined(__AARCH64EL__)
+#  include 
+# elif defined(__alpha__)
+#  include 
+# elif defined(__ARM_EABI__) && defined(__ARM_PCS_VFP)
+#  include 
+# elif defined(__ARM_EABI__) && !defined(__ARM_PCS_VFP)
+#  include 
+# elif defined(__hppa__)
+#  include 
+# elif defined(__ia64__)
+#  include 
+# elif defined(__m68k__) && !defined(__mcoldfire__)
+#  include 
+# elif defined(__mips_hard_float) && defined(_MIPSEL)
+#  if _MIPS_SIM == _ABIO32
+#   include 
+#  elif _MIPS_SIM == _ABIN32
+#   include 
+#  elif _MIPS_SIM == _ABI64
+#   include 
+#  else
+#   error unknown multiarch location for @header@
+#  endif
+# elif defined(__mips_hard_float)
+#  if _MIPS_SIM == _ABIO32
+#   include 
+#  elif _MIPS_SIM == _ABIN32
+#   include 
+#  elif _MIPS_SIM == _ABI64
+#   include 
+#  else
+#   error unknown multiarch location for @header@
+#  endif
+# elif defined(__or1k__)
+#  include 
+# elif defined(__powerpc__) && defined(__SPE__)
+#  include 
+# elif defined(__powerpc64__)
+#  if defined(__LITTLE_ENDIAN__)
+#include 
+#  else
+#include 
+#  endif
+# elif defined(__powerpc__)
+#  include 
+# elif defined(__s390x__)
+#  include 
+# elif defined(__s390__)
+#  include 
+# elif defined(__sh__) && defined(__LITTLE_ENDIAN__)
+#  include 
+# elif defined(__sparc__) && defined(__arch64__)
+#  include 
+# elif defined(__sparc__)
+#  include 
+# else
+#   error unknown multiarch location for @header@
+# endif
+#elif defined(__FreeBSD_kernel__)
+# if defined(__LP64__)
+#  include 
+# elif defined(__i386__)
+#  include 
+# else
+#   error unknown multiarch location for @header@
+# endif
+#elif defined(__gnu_hurd__)
+# include 
+#else
+# error unknown multiarch location for @header@
+#endif
diff -pruN 2.6.3-3/debian/patches-freetype/freetype-config.diff 2.6.3-3ubuntu1/debian/patches-freetype/freetype-config.diff
--- 2.6.3-3/debian/patches-freetype/freetype-config.diff	1970-01-01 00:00:00.0 +
+++ 2.6.3-3ubuntu1/debian/patches-freetype/freetype-config.diff	2016-04-28 20:08:36.0 +
@@ -0,0 +1,35 @@
+Index: freetype-2.6.1/builds/unix/freetype-config.in
+===
+--- freetype-2.6.1.orig/builds/unix/freetype-config.in	2016-02-17 10:26:16.681010303 -0500
 freetype-2.6.1/builds/unix/freetype-config.in	2016-02-17 10:27:26.377806639 -0500
+@@ -16,7 +16,6 @@
+ exec_prefix="%exec_prefix%"
+ exec_prefix_set="no"
+ includedir="%includedir%"
+-libdir="%libdir%"
+ 
+ usage()
+ {
+@@ -88,6 +87,8 @@
+ ;;
+   --libtool)
+ echo_libtool=yes
++echo 2>&1 "the use of the libfreetype6.la file is deprecated in Debian/Ubuntu"
++exit 1
+ ;;
+   --static)
+ show_static=yes
+@@ -145,12 +146,7 @@
+   if test "$show_static" = "yes" ; then
+ libs="$staticlibs"
+   fi
+-  if test "${SYSROOT}$libdir" != "/usr/lib"  &&
+- test "${SYSROOT}$libdir" != "/usr/lib64"; then
+-echo -L${SYSROOT}$libdir $libs
+-  else
+-

Bug#823621: openvpn: CapabilityBoundingSet prevents use of network namespaces in route-up script

2016-05-06 Thread root
Package: openvpn
Version: 2.3.10-1
Severity: normal

Dear Maintainer,

the systemd unit of openvpn 2.3.10-1 in stretch prevents the use of network 
namespaces
in route-up scripts, as this requires the CAP_SYS_ADMIN to be able to call 
setns(2).

Unfortunately the log output is not very verbose and only reports the generic 
failure when
executing the route-up script.

> WARNING: Failed running command (--route-up): external program exited with 
> error status: 1

This is a regression, when upgrading from jessie.


Best regards,

hexa-

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

Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  init-system-helpers1.31
ii  initscripts2.88dsf-59.3
ii  iproute2   4.3.0-1+b1
ii  libc6  2.22-7
ii  liblzo2-2  2.08-1.2
ii  libpam0g   1.1.8-3.2
ii  libpkcs11-helper1  1.11-5
ii  libssl1.0.21.0.2g-2
ii  libsystemd0229-5

Versions of packages openvpn recommends:
pn  easy-rsa  

Versions of packages openvpn suggests:
ii  openssl 1.0.2g-2
pn  resolvconf  

-- debconf information:
  openvpn/create_tun: false



Bug#823622: CVE-2015-4901 CVE-2015-4906 CVE-2015-4908 CVE-2015-4916

2016-05-06 Thread Moritz Muehlenhoff
Source: openjfx
Severity: grave
Tags: security

The four security issues from October's Java CPU are still unfixed, right?
http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html 

Cheers,
Moritz



Bug#823620: Multiple security issues

2016-05-06 Thread Moritz Muehlenhoff
Source: xen
Severity: grave
Tags: security

Multiple vulnerabilities are unfixed in xen:

CVE-2015-5307:
http://xenbits.xen.org/xsa/advisory-156.html

CVE-2016-3960
http://xenbits.xen.org/xsa/advisory-173.html

CVE-2016-3159 / CVE-2016-3158
http://xenbits.xen.org/xsa/advisory-172.html

CVE-2016-2271
http://xenbits.xen.org/xsa/advisory-170.html

CVE-2016-2270
http://xenbits.xen.org/xsa/advisory-154.html

CVE-2016-1571
http://xenbits.xen.org/xsa/advisory-168.html

CVE-2016-1570
http://xenbits.xen.org/xsa/advisory-167.html

CVE-2015-8615
http://xenbits.xen.org/xsa/advisory-169.html

CVE-2015-8555
http://xenbits.xen.org/xsa/advisory-165.html

CVE-2015-8550
http://xenbits.xen.org/xsa/advisory-155.html

CVE-2015-8341
http://xenbits.xen.org/xsa/advisory-160.html

CVE-2015-8340 / CVE-2015-8339
http://xenbits.xen.org/xsa/advisory-159.html

CVE-2015-8338
http://xenbits.xen.org/xsa/advisory-158.html

CVE-2015-8104
http://xenbits.xen.org/xsa/advisory-156.html
 
CVE-2015-7311
http://xenbits.xen.org/xsa/advisory-142.html

CVE-2015-6654
http://xenbits.xen.org/xsa/advisory-141.html



   



Bug#823619: GNU triplet for i386 should now be i686-linux-gnu

2016-05-06 Thread Ben Hutchings
Package: src:dpkg
Version: 1.18.6
Severity: normal
Tags: patch

gcc in unstable now generates code for i686, not i586, and cross-build
tools are named accordingly.  Please update the architecture table in
dpkg.

Ben.

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From be324041443b7acbe1970474b37c0072b20458f6 Mon Sep 17 00:00:00 2001
From: Ben Hutchings 
Date: Tue, 3 May 2016 00:53:25 +0200
Subject: [PATCH] Bump the i386 architecture GNU triplet to i686-linux-gnu to
 match the change in gcc

---
 cputable | 2 +-
 debian/changelog | 4 
 debian/rules | 7 ---
 3 files changed, 5 insertions(+), 8 deletions(-)

diff --git a/cputable b/cputable
index 2177200089b3..2088d8eef112 100644
--- a/cputable
+++ b/cputable
@@ -14,7 +14,7 @@
 # Column 5 is the endianness (byte ordering in numbers)
 #
 # 
-i386		i586		(i[34567]86|pentium)	32	little
+i386		i686		(i[34567]86|pentium)	32	little
 ia64		ia64		ia64			64	little
 alpha		alpha		alpha.*			64	little
 amd64		x86_64		(amd64|x86_64)		64	little
diff --git a/debian/changelog b/debian/changelog
index 0d3360c3b557..fcc5c71f20f4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,10 @@ dpkg (1.18.7) UNRELEASED; urgency=medium
   [ Updated manpages translations ]
   * German (Helge Kreutzmann).
 
+  [ Ben Hutchings ]
+  * Bump the i386 architecture GNU triplet to i686-linux-gnu to match the
+change in gcc.
+
  -- Guillem Jover   Tue, 03 May 2016 21:07:19 +0200
 
 dpkg (1.18.6) unstable; urgency=medium
diff --git a/debian/rules b/debian/rules
index 5d515e8a2e9b..146f3c266407 100755
--- a/debian/rules
+++ b/debian/rules
@@ -86,13 +86,6 @@ install: check
 
 	cd build-tree && $(MAKE) DESTDIR=$(D) install
 
-ifeq (yes,$(shell dpkg-vendor --derives-from Ubuntu && echo yes))
-	# Ubuntu's «i386» architecture is built for i686 (the Debian default
-	# is i586).
-	sed -ri 's/^(i386[[:space:]]+)[^[:space:]]+/\1i686/' \
-	$(D)/usr/share/dpkg/cputable
-endif
-
 define dpkg-installmanl10n
 for f in `sed -e 's:\*:*/*:' debian/$(1).manpages`; do \
 	test -e $$f && \


Bug#823195: evince-common: Mouse Inverted Reversed Scrolling Does not Function

2016-05-06 Thread Carl Nikolov
In xfce the settings don't adapt to system wide setting

Carl
  Original Message  
From: Jason Crain
Sent: Friday, May 6, 2016 12:39 PM
To: 823195-submit...@bugs.debian.org
Reply To: 823...@bugs.debian.org
Subject: Bug#823195: evince-common: Mouse Inverted Reversed Scrolling Does not 
Function

On Mon, May 02, 2016 at 01:53:32AM -0400, Carl Nikolov wrote:
> Evince does not adhere to system wide setting of inverted scrolling.
> 
> Can you change your scrolling method to inverted in X server and report back?
> 
> I am running Evince V3.20.

Do you mean the new "Natural Scrolling" setting in Gnome? It works fine
when I change it in the Gnome control center.



Bug#823584: [PATCH] Correct top-level directory name in repackaged tarballs

2016-05-06 Thread Jakub Wilk

* Tormod Volden , 2016-05-06, 11:21:

-packagename-upstream-version.orig
 as the
+packagename-upstream-version+dfsg
 as the


NACK. That would be misleading if the tarball was repacked for reason 
unrelated to DFSG.


Once we fix #560287, we could perhaps say that the directory should be:

--

or something similar.

Related bugs: #470960

--
Jakub Wilk



Bug#823604: ruby2.3: FTBFS in testing

2016-05-06 Thread Santiago Vila
Related bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823530



Bug#823618: apache2: inconsistent help messages

2016-05-06 Thread Marcos Dione
Package: apache2
Version: 2.4.20-1
Severity: minor

Dear Maintainer,

   * What led up to the situation?

See the following sequence of commands:

$ sudo apachectl --help
Usage: /usr/sbin/apachectl 
start|stop|restart|graceful|graceful-stop|configtest|status|fullstatus|help
   /usr/sbin/apachectl 
   /usr/sbin/apachectl -h(for help on )

$ sudo apachectl -h
Usage: /usr/sbin/apache2 [-D name] [-d directory] [-f file]
 [-C "directive"] [-c "directive"]
 [-k start|restart|graceful|graceful-stop|stop]
 [-v] [-V] [-h] [-l] [-L] [-t] [-T] [-S] [-X]
Options:
  -D name: define a name for use in  directives
  -d directory   : specify an alternate initial ServerRoot
  -f file: specify an alternate ServerConfigFile
  -C "directive" : process directive before reading config files
  -c "directive" : process directive after reading config files
  -e level   : show startup errors of level (see LogLevel)
  -E file: log startup errors to file
  -v : show version number
  -V : show compile settings
  -h : list available command line options (this page)
  -l : list compiled in modules
  -L : list available configuration directives
  -t -D DUMP_VHOSTS  : show parsed vhost settings
  -t -D DUMP_RUN_CFG : show parsed run settings
  -S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG
  -t -D DUMP_MODULES : show all loaded modules
  -M : a synonym for -t -D DUMP_MODULES
  -t : run syntax check for config files
  -T : start without DocumentRoot(s) check
  -X : debug mode (only one worker, do not detach)
Action '-h' failed.
The Apache error log may have more information.

   * What outcome did you expect instead?

A non-failing help message, if possible related to the apachectl utility,
not apache2 binary. I uselessly tried this:

$ sudo apachectl -e debug configtest
Usage: /usr/sbin/apache2 [-D name] [-d directory] [-f file]
 [-C "directive"] [-c "directive"]
 [-k start|restart|graceful|graceful-stop|stop]
 [-v] [-V] [-h] [-l] [-L] [-t] [-T] [-S] [-X]
Options:
  -D name: define a name for use in  directives
  -d directory   : specify an alternate initial ServerRoot
  -f file: specify an alternate ServerConfigFile
  -C "directive" : process directive before reading config files
  -c "directive" : process directive after reading config files
  -e level   : show startup errors of level (see LogLevel)
  -E file: log startup errors to file
  -v : show version number
  -V : show compile settings
  -h : list available command line options (this page)
  -l : list compiled in modules
  -L : list available configuration directives
  -t -D DUMP_VHOSTS  : show parsed vhost settings
  -t -D DUMP_RUN_CFG : show parsed run settings
  -S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG
  -t -D DUMP_MODULES : show all loaded modules
  -M : a synonym for -t -D DUMP_MODULES
  -t : run syntax check for config files
  -T : start without DocumentRoot(s) check
  -X : debug mode (only one worker, do not detach)
Action '-e debug configtest' failed.
The Apache error log may have more information.

-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin2.4.20-1
ii  apache2-data   2.4.20-1
ii  apache2-utils  2.4.20-1
ii  dpkg   1.18.4
ii  lsb-base   9.20160110
ii  mime-support   3.60
ii  perl   5.22.2-1
ii  procps 2:3.3.11-3

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.37

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   50.0.2661.94-1
ii  elinks [www-browser] 0.12~pre6-11+b2
ii  firefox [www-browser]46.0-1
ii  konqueror [www-browser]  4:4.14.2-1
ii  links [www-browser]  2.12-1+b2
ii  links2 [www-browser] 2.12-1+b2
ii  lynx [www-browser]   2.8.9dev9-1

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.2-3
ii  

Bug#823604: ruby2.3: FTBFS in testing

2016-05-06 Thread Santiago Vila
Modifying /etc/systemd/system.conf to read like this:

DefaultTasksMax=infinity

does also fix the issue, which seems related to recent
kernels (>= 4.3) and systemd:

http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel

This is probably why it fails for me on a virtual machine running
stretch and it does not fail on another virtual machine running
stretch with a kernel from jessie.

So: Could you please try to reproduce this on a system running stretch,
including linux-image-4.5.0-1-amd64? (i.e. not just the chroot).

Thanks.



  1   2   3   >