Bug#830947: w3m: Wrong table rendering

[Kamil Jonca]

Package: w3m
Version: 0.5.3-28
Severity: normal
Tags: upstream

When try to render any table it is rendered incorrectly. 
border are shortert than cell contents. 
MOreover it looks like is something wrong with redrawing when scroll page, 
and after somoe scrolls up/down screen is pretty unusable.


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

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

Versions of packages w3m depends on:
ii  libc62.23-1
ii  libgc1c2 1:7.4.2-8
ii  libgpm2  1.20.4-6.2
ii  libssl1.0.2  1.0.2h-1
ii  libtinfo56.0+20160625-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages w3m recommends:
ii  ca-certificates  20160104

Versions of packages w3m suggests:
pn  cmigemo   
ii  curl  7.47.0-1
pn  libsixel-bin  
ii  man-db2.7.5-1
ii  mime-support  3.60
pn  mpv   
pn  w3m-el
pn  w3m-img   
ii  wget  1.18-2
ii  xdg-utils 1.1.1-1
pn  xsel  

-- debconf-show failed

Bug#830946: ITP: onedrive -- folder synchronization with OneDrive

[Norbert Preining]

On Wed, 13 Jul 2016, Aron Xu wrote:
> The package name could be a trademark misuse, mind to rename it?

Do you have a suggestion?
o-d-linux
?
linuxdrive
?

The upstream name is onedrive, though.

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#830946: ITP: onedrive -- folder synchronization with OneDrive

[Aron Xu]

> On Jul 13, 2016, at 13:11, Norbert Preining  wrote:
> 
> Package: wnpp
> Severity: wishlist
> Owner: Norbert Preining 
> 
> * Package name: onedrive
>  Version : 1.1~20160713
>  Upstream Author : skilion 
> * URL : http://skilion.github.io/onedrive/
> * License : GPLv3
>  Programming Lang: D
>  Description : folder synchronization with OneDrive
> 
> OneDrive is the cloud storage system of Microsoft. This package provides
> the command line client specialising in synchronizing with OneDrive cloud 
> storage.
> 

The package name could be a trademark misuse, mind to rename it?

Regards,
Aron

Bug#830937: [Bash-completion-devel] Bug#830937: Please support dynamically loading completions from $HOME

[Ville Skyttä]

We (upstream) already do this in bash-completion >= 2.2.

Bug#784612: [anki] Qt4's WebKit removal

[Nicolas Kuttler]

There are alpha builds with Qt5 available,

http://ankisrs.net/download/mirror/alpha/

https://anki.tenderapp.com/discussions/beta-testing/172-anki-210-alpha-1

https://anki.tenderapp.com/discussions/beta-testing/174-anki-210-alpha-2

Bug#830946: ITP: onedrive -- folder synchronization with OneDrive

[Norbert Preining]

Package: wnpp
Severity: wishlist
Owner: Norbert Preining 

* Package name: onedrive
  Version : 1.1~20160713
  Upstream Author : skilion 
* URL : http://skilion.github.io/onedrive/
* License : GPLv3
  Programming Lang: D
  Description : folder synchronization with OneDrive

OneDrive is the cloud storage system of Microsoft. This package provides
the command line client specialising in synchronizing with OneDrive cloud 
storage.

Bug#757760: debian-policy: please document build profiles

[Johannes Schauer]

Hi,

Quoting Javier Serrano Polo (2016-07-13 01:04:43)
> Sorry, I missed your message.
> 
> > I'm removing #757760 from the recipients because that bug should
> > contain a discussion about the implementation of the current build
> > profile spec and should not be a discussion platform for further
> > additions or changes to the spec. Lets use debian-dpkg@ to discuss
> > this issue.
> 
> The BTS is my only way to keep an open discussion. I really cannot post to
> lists.debian.org (I can to Alioth lists);

because of technical reasons?

> should I try to fix that?

If you want to discuss this issue, then yes.

> We can discuss in #830524.

A bug against Debian policy is not the right platform to discuss new features
or changes to existing functionality. Things get documented in Debian policy
*after* it has been agreed upon how we want them to work on other mailing
lists, IRC and/or real life. Then, the debian policy bts can be used to find
the right wording to express all this properly in natural language. Usually
discussions about project-wide features like this would happen on debian-devel@
but other lists are also possible. At maximum, I'd discuss changes like this in
a bug against dpkg, for example.

Also note, that I don't seem to be able to send you email directly because:

: host www.jasp.net[62.43.138.54] said: 550-The message does
not meet the trust level of one recipient at least 550-See
http://www.jasp.net/smtp/trust.xhtml 550 Administrative prohibition (in
reply to end of DATA command)

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#830742: src:fcgiwrap: Relicense Debian packaging to allow upstreaming of patches

[Peter Colberg]

On Mon, Jul 11, 2016 at 02:44:08AM +0200, Jordi Mallach wrote:
> On Sun, Jul 10, 2016 at 06:46:36PM -0400, Peter Colberg wrote:
> > Would you agree to relicense the Debian packaging for fcgiwrap to the
> > Expat license? This will allow us to submit Debian patches upstream.
> 
> Oops. Yes, no objection.

Sergio, do you also agree to relicense fcgiwrap/debian/* to Expat?

Regards,
Peter


signature.asc
Description: PGP signature

Bug#787569: ufraw: Errors converting Nikkon NEF files

[Sérgio Basto]

On Wed, 03 Jun 2015 21:18:34 -0400 Hubert Chathi 
wrote:


> If you this fixes it for you, I'd like to forward the image and
> parameters to the upstream developer to see if he can determine
whether
> it's a bug in LensFun, or a bug in how ufraw interfaces with LensFun.
> 
> Hubert

yes , I just hit the same bug in Fedora 24 , my workaround is build
ufraw without LensFun 

https://bugzilla.redhat.com/show_bug.cgi?id=1350210

Thanks,
-- 
Sérgio M. B.

Bug#830889: Looks like my patch violates RFC3501

[Nye Liu]

While it seems you can examine once and keep calling status (violates 
RFC), if you close before calling status, it doesn't work.. you have to 
keep calling examine/close before each status


So three choices:

RFC broken 2 ways (status while folder is open, using status to count 
UNSEEN):

login
examine
while 1
  status (MESSAGES UNSEEN)
done

Fully RFC compliant:

login
examine
while 1
  search(SEEN)
  search(UNSEEN)
done

or

Somewhat RFC broken (uses status to count UNSEEN)

login
while 1
  examine
  close
  status (MESSAGES UNSEEN)
done

The downside to search is that the results might be very long for a 
large mailbox with many, many messages, and that result has to be split up.

Bug#830828: wfmath: Symbols file compatibility with -O3

[Olek]

Hi Steve,

On 07/11/2016 07:04 PM, Steve Langasek wrote:

Hi Olek,

The Ubuntu ppc64el port uses -O3 optimization for package builds by default.
Under -O3, there are a number of additional template symbols that are not
exported in libwfmath because they wind up inlined instead.  As a result,
wfmath fails to build with a mismatched symbols file error.

The attached patch has been applied in Ubuntu to mark these additional
symbols optional, since they are not part of the ABI, and allows the package
to build wherever -O3 is used.

Thanks for considering the patch.


Thank you for pointing this out and thanks for the patch! I've applied 
it to my working branch and will upload shortly.


Have a great day!

-Olek

Bug#830945: php-dompdf: use A4 papersize per default

[Christoph Anton Mitterer]

Package: php-dompdf
Severity: wishlist


Hi.

The whole world (except the US) use A4 rather then letter as
default format; also A4 is the ISO standard.

Wouldn't it make sense to have the configuration default to that
instead of letter?

Cheers,
Chris.

Bug#830942: pdns: FTBFS on m68k and powerpcspe: missing __atomic_{load,fetch_add}_8

[Aaron M. Ucko]

Source: pdns
Version: 4.0.0-1
Severity: important
Justification: fails to build from source (but built successfully in the past)

The m68k and powerpcspe builds of pdns failed:

  /bin/bash ../libtool  --tag=CXX   --mode=link m68k-linux-gnu-g++ 
-DSYSCONFDIR=\"/etc/powerdns\" -DPKGLIBDIR=\"/usr/lib/m68k-linux-gnu/pdns\" 
-DLOCALSTATEDIR=\"/var/run\" -fPIE -DPIE -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 
--param ssp-buffer-size=4 -fstack-protector -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -DPACKAGEVERSION='"4.0.0-1.Debian"' 
-std=gnu++11 -pie  -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z,relro -o 
dumresp dnslabeltext.o dnsname.o dumresp.o logger.o misc.o statbag.o 
unix_utility.o qtype.o  
  libtool: link: m68k-linux-gnu-g++ -DSYSCONFDIR=\"/etc/powerdns\" 
-DPKGLIBDIR=\"/usr/lib/m68k-linux-gnu/pdns\" -DLOCALSTATEDIR=\"/var/run\" -fPIE 
-DPIE -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 --param ssp-buffer-size=4 
-fstack-protector -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -DPACKAGEVERSION=\"4.0.0-1.Debian\" -std=gnu++11 -pie 
-pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,relro -o dumresp 
dnslabeltext.o dnsname.o dumresp.o logger.o misc.o statbag.o unix_utility.o 
qtype.o  -pthread
  dumresp.o: In function `std::__atomic_base::load(std::memory_order) const':
  /usr/include/c++/5/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
  /usr/include/c++/5/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
  /usr/include/c++/5/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
  /usr/include/c++/5/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
  /usr/include/c++/5/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
  dumresp.o:/usr/include/c++/5/bits/atomic_base.h:396: more undefined 
references to `__atomic_load_8' follow
  dumresp.o: In function `std::__atomic_base::fetch_add(unsigned long long, std::memory_order)':
  /usr/include/c++/5/bits/atomic_base.h:514: undefined reference to 
`__atomic_fetch_add_8'
  collect2: error: ld returned 1 exit status
  Makefile:2281: recipe for target 'dumresp' failed
  make[5]: *** [dumresp] Error 1

Please try explicitly linking against -latomic, perhaps with
-Wl,--as-needed to avoid incurring a dependency on it on other
architectures.

Thanks!

Bug#830944: ruby-validate-url: /usr/lib/ruby/vendor_ruby/locale/en.yml also in ruby-validate-email

[Aaron M. Ucko]

Package: ruby-validate-url
Version: 1.0.2-1
Severity: normal

ruby-validate-url is impossible to install alongside ruby-validate-email:

  Unpacking ruby-validate-url (1.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-validate-url_1.0.2-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/locale/en.yml', which is also 
in package ruby-validate-email 0.1.6-1

Please give this YAML file a more distinctive name (and do likewise
in ruby-validate-email).

Thanks!

Bug#830940: mirrors: more files should be excluded in stage1 sync

[Shengjing Zhu]

Package: mirrors
Severity: important

Dear Maintainer,

With recent updates of apt, when `apt update`, it will fetch dep11
(if appstream is installed) and Contents file(if apt-file is installed).

These conf can be seen in /etc/apt/apt.conf.d/50appstream
and /etc/apt/apt.conf.d/50apt-file.conf

Related packages are appstream and apt-file.

So the possible stage1 sync option should be:

RSYNC_OPTIONS1=${RSYNC_OPTIONS1:-"--exclude=Packages* --exclude=Sources*
--exclude=Release* --exclude=InRelease --exclude=ls-lR* --include=by-hash/**
--exclude=Contents* --exclude=dep11/* --exclude=i18n/*"}

Bug#830939: knot-resolver: FTBFS: missing files: usr/lib/knot-resolver/tinyweb/*

[Aaron M. Ucko]

Source: knot-resolver
Version: 1.1.0~git2016070600-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of knot-resolver on mips(el) and powerpc(spe) have been failing:

  Optional
  
  [yes] doxygen (doc)
  [no] go (modules/go, Go buildmode=c-shared support)
  [no] geoip (modules/tinyweb, github.com/abh/geoip)
  [...]
  dh_install --fail-missing
  dh_install: Cannot find (any matches for) "usr/lib/knot-resolver/tinyweb/*" 
(tried in "." and "debian/tmp")
  dh_install: knot-resolver-module-tinyweb missing files: 
usr/lib/knot-resolver/tinyweb/*
  dh_install: missing files, aborting
  debian/rules:76: recipe for target 'override_dh_install' failed

Could you please take a look?  With any luck, it should suffice to declare

  Architecture: amd64 i386 armhf armel arm64

for knot-resolver-module-tinyweb, in keeping with the relevant build
dependencies' architecture restrictions.

Thanks!

Bug#830765: (no subject)

[gustavo panizzo (gfa)]

Hello

I will maintain this package from now on

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: http://keybase.io/gfa

Bug#830941: icingaweb2: don't mangle around in the Apache configs

[Christoph Anton Mitterer]

Source: icingaweb2
Version: 2.3.4-1
Severity: normal
Tags: security


Hi.

The postinst of this package automatically enables some
config snippets as well as some modules.

Please don't do that, not only has it the simple potential
to break existing setups but also to introduce security holes.


In general it's alrady a bad idea if an apache module package
enables it's own module (i.e. a2enmod).
It may not be configured, and depending on the layout of the
apache configuration loading it in general may not be desired
but e.g. rather for specific sites only.
When some 3rd party package enables another module that's IMHO
even worse.

mod_rewrite may easily introduce security issues or simply be
undesired in some sites running on a node (and icingaweb2 may
not be the only one).


Similar, enabling /etc/apache2/conf-available/icingaweb2.conf
shouldn't be done either.
AFAICS, it's not even enforing SSL.
It further cannot be assumed that the URL space / isn't already
used somehow (e.g. via other generic rewritings) and it should
be the user who decides whether he wants to make Icinga Web 2
to /icingaweb2.



I think a good alternative would be simply to document in
README.Debian wich modules are required and that there is
an out-of-the box config snippet (icingaweb2.conf) which people
could either use directly or integrate into their more powerful
setup.
Alternatively one could use debconf to at least ask whether
that auto-configuration should be done.

I think that would be still easy for people to get it running
while not possibly breaking more advanced setups or even
automatically "starting" Icinga Web2 in a fashion that is not
as tightly locked down as the site would want it.


Cheers,
Chris.


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

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

Bug#828106:

[Michael Catanzaro]

Dear maintainer, I have committed a fix upstream. Ryan's suggestion was
almost correct; the trick is that the RNG really ought to be seeded
exactly once, and in our case has to be else it will break the print
feature that generates multiple puzzles per second... and this is
threaded code, so a mutex is required to implement that. The best way
to do that is to use std::call_once, but I also wrote an alternate fix
using GMutex that would be easier to backport for Debian:

https://git.gnome.org/browse/gnome-sudoku/commit/?h=gnome-3-20=30065efc87d381991f51c2a2d39b0ffb0b04425b

Of course it'd be even better for qqwing to use a modern C++ RNG that doesn't 
depend on shared state, but this will do for us

Bug#830943: php7.0-common: possibly wrongly documented default value for assert.exception

[Christoph Anton Mitterer]

Package: php7.0-common
Version: 7.0.7-5
Severity: normal


Hi.

The example php.ini's as well as the web docs seem to imply
that the default value for assert.exception is On.

However, looking at the code it seems (though I may be wrong)
that it's actually Off.

Cheers,
Chris.


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

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

Bug#773762: apt-listdifferences: diff goes outside package tree

[Michael Gilbert]

control: severity -1 wishlist
control: reassign -1 devscripts
control: affects -1 apt-listdifferences
control: retitle -1 [debdiff] option to avoid dereferencing symlinks

On Mon, Dec 22, 2014 at 7:03 PM, Achim Schaefer wrote:
> when running apt-listdifferences, it happens sometimes, diff is comparing 
> data outside the tmp source dir.
> E.g. this now happens with docker.io:
> diff: /tmp/BsDox6gACB/docker.io-1.3.2~dfsg1/pkg/symlink/testdata/fs/a/d: 
> Datei oder Verzeichnis nicht gefunden
> diff: 
> /tmp/BsDox6gACB/docker.io-1.3.2~dfsg1/pkg/symlink/testdata/fs/a/e/h/.kde/socket-data:
>  Datei oder Verzeichnis nicht gefunden
> This is basically in my home dir.
> Here one of the examples, what we see in the original source:
> root@data:/tmp/BsDox6gACB/docker.io-1.3.2~dfsg1/pkg/symlink/testdata/fs# ls -l
> insgesamt 0
> drwxr-xr-x 2 root root 100 Nov 24 18:38 a
> drwxr-xr-x 2 root root  60 Nov 24 18:38 b
> lrwxrwxrwx 1 root root  40 Nov 24 18:38 g -> 
> ../../../../../../../../../../../../root
> lrwxrwxrwx 1 root root   1 Nov 24 18:38 i -> a
> drwxr-xr-x 2 root root  60 Nov 24 18:38 j

debdiff would need to provide an option that passes --no-dereference to diff.

Best wishes,
Mike

Bug#830938: icingaweb2: /etc/bash_completion.d/icingacli should be in the icingacli package

[Christoph Anton Mitterer]

Source: icingaweb2
Version: 2.3.4-1
Severity: normal


Hi.

Probably,
/etc/bash_completion.d
/etc/bash_completion.d/icingacli
should be in the icingacli rather than icingaweb2.

Cheers,
Chris.

Bug#830936: prometheus-alertmanager: FTBFS on arm64: dispatch_test.go:132: received batch to[o] early

[Aaron M. Ucko]

Source: prometheus-alertmanager
Version: 0.3.0+ds-1
Severity: important
Justification: fails to build from source

The arm64 build of prometheus-alertmanager failed:

  === RUN   TestAggrGroup
  --- FAIL: TestAggrGroup (1.30s)
dispatch_test.go:132: received batch to early after 299.982ms
  === RUN   TestInhibitRuleHasEqual
  --- PASS: TestInhibitRuleHasEqual (0.00s)
  === RUN   TestInhibitRuleGC
  --- PASS: TestInhibitRuleGC (0.00s)
  === RUN   TestRouteMatch
  --- PASS: TestRouteMatch (0.00s)
  FAIL
  FAIL  github.com/prometheus/alertmanager  1.314s

Could you please take a look?

Thanks!

Bug#830937: Please support dynamically loading completions from $HOME

[Josh Triplett]

Package: bash-completion
Version: 1:2.1-4.3
Severity: wishlist

bash-completion supports dynamically loading completions from
/usr/share/bash-completion/completions.  Please consider adding support
for dynamically loading completions from
$XDG_DATA_HOME/bash-completion/completions (defaulting to
~/.local/share/bash-completion/completions with $XDG_DATA_HOME unset).

This would allow installations of software into ~/.local to include bash
completion files.

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

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

Versions of packages bash-completion depends on:
ii  bash  4.3-15
ii  dpkg  1.18.9

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information

Bug#830935: pdns: FTBFS on kFreeBSD: Unable to find a suitable libsystemd library

[Aaron M. Ucko]

Source: pdns
Version: 4.0.0-1
Severity: important
Justification: fails to build from source (but built successfully in the past)

Builds of pdns 4 for kFreeBSD failed:

  checking systemd/sd-daemon.h usability... no
  checking systemd/sd-daemon.h presence... yes
  configure: WARNING: systemd/sd-daemon.h: present but cannot be compiled
  configure: WARNING: systemd/sd-daemon.h: check for missing prerequisite 
headers?
  configure: WARNING: systemd/sd-daemon.h: see the Autoconf documentation
  configure: WARNING: systemd/sd-daemon.h: section "Present But Cannot Be 
Compiled"
  configure: WARNING: systemd/sd-daemon.h: proceeding with the compiler's result
  checking for systemd/sd-daemon.h... no
  configure: error: Unable to find a suitable libsystemd library
  debian/rules:20: recipe for target 'override_dh_auto_configure' failed
  make[1]: *** [override_dh_auto_configure] Error 1
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  debian/rules:14: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

It looks like the version of libsystemd-dev available on kFreeBSD (and
the Hurd), 222-1, is too old for pdns's purposes.  Please version the
build dependency appropriately.

Thanks!

Bug#830683: no sound anymore after upgrade to 9.0-1.1

[Tsu Jan]

The same thing happened here. I first downgraded to 8.0-2+b2 and had 
sound again. Then Google lead me to this report and I upgraded 
pulseaudio but, this time, installed pulseaudio-module-udev too, which 
solved the problem.

Therefore, for some reason, pulseaudio-module-udev was quite needed here.
IMO, pulseaudio-module-udev shouldn't be among "Recommends" anymore. 
After all, recommending something means that it is NOT essential to the 
functioning.

Bug#830934: knot-resolver: FTBFS on kFreeBSD: mdb.c needs pthread extensions

[Aaron M. Ucko]

Source: knot-resolver
Version: 1.1.0~git2016070600-1
Severity: important
Justification: fails to build from source (but built successfully in the past)

The kfreebsd-i386 build of knot-resolver failed:

  contrib/lmdb/mdb.c: In function 'mdb_env_setup_locks':
  contrib/lmdb/mdb.c:4625:13: warning: implicit declaration of function 
'pthread_mutexattr_setrobust' [-Wimplicit-function-declaration]
  || (rc = pthread_mutexattr_setrobust(, PTHREAD_MUTEX_ROBUST))
   ^
  contrib/lmdb/mdb.c:4625:49: error: 'PTHREAD_MUTEX_ROBUST' undeclared (first 
use in this function)
  || (rc = pthread_mutexattr_setrobust(, PTHREAD_MUTEX_ROBUST))
   ^
  contrib/lmdb/mdb.c:4625:49: note: each undeclared identifier is reported only 
once for each function it appears in
  contrib/lmdb/mdb.c: In function 'mdb_mutex_failed':
  contrib/lmdb/mdb.c:351:37: warning: implicit declaration of function 
'pthread_mutex_consistent' [-Wimplicit-function-declaration]
   #define mdb_mutex_consistent(mutex) pthread_mutex_consistent(mutex)
   ^
  contrib/lmdb/mdb.c:10002:10: note: in expansion of macro 
'mdb_mutex_consistent'
  rc2 = mdb_mutex_consistent(mutex);
^
  contrib/contrib.mk:20: recipe for target 'contrib/lmdb/mdb.o' failed
  make[2]: *** [contrib/lmdb/mdb.o] Error 1

Could you please take a look?  Per Policy 4.13, the best solution (if
feasible) would be to build against externally packaged liblmdb-dev,
which supports kFreeBSD and for which the build system even already
appears to check:

  Dependencies
  
  [yes] libknot (lib)
  [no] lmdb (lib)
  [yes] luajit (daemon)
  [yes] libuv (daemon)

However, if that's somehow not an option, perhaps you can look at what
it does on kFreeBSD and do the same locally.

Thanks!

Bug#830841: linux-image-4.1.0-1-amd64: something bad happened when working with filesystem on loop dev on external harddrive with ntfs

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 2016-07-12 at 08:38 +0200, treaki wrote:
> Package: src:linux
> Version: 4.1.3-1
[...]

This is old and not supported in Debian.  Please upgrade to the current
version 4.6.3-1 and re-test.

Ben.

-- 

Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.


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

Bug#795841: 3.0.0~beta3.3

[Dmitry Smirnov]

Hi protobuf team,

Upstream says 3.0.0~beta3.4 is going to be the last beta release while
final release of 3.0.0 is planned for end of July.  This year!  ;)

I've committed some updates to "experimental" branch at old collab-maint
repository [1]. Hopefully it would help to upload new beta. Please review.

google-mock still needs more work to fix tests but package already builds
with

DEB_BUILD_OPTIONS=nocheck

For now I'm leaving it with you as I don't have time to continue working on
it today.

Thanks.

[1]: 
https://anonscm.debian.org/cgit/collab-maint/protobuf.git/log/?h=experimental

-- 
Best wishes,
 Dmitry Smirnov.

---

It is no use saying, 'We are doing our best.' You have got to succeed
in doing what is necessary.
-- Winston Churchill


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

Bug#830930: lintian: dh --with systemd is now builtin

[Christian Hofstaedtler]

* Michael Biebl  [160713 00:38]:
> > starting in debhelper 9.20160709, "--with systemd" support is built
> > into debhelper. As such, the following lintian error is now wrong:
[..]

> I would keep the warning but it should say that it needs a versioned
> b-dep on debhelper instead.

I assume this needs special casing, given all the references to
dh-systemd vanish when one calls `private/refresh-debhelper-data` in
lintians source.

Also, checks/systemd.desc probably needs a text update now (it says
"please use the dh-systemd debhelper").

Thanks!
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#830930: lintian: dh --with systemd is now builtin

[Michael Biebl]

Am 13.07.2016 um 02:21 schrieb Christian Hofstaedtler:
> Package: lintian
> Severity: normal
> X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org
> 
> Dear Lintian Maintainers,
> 
> starting in debhelper 9.20160709, "--with systemd" support is built
> into debhelper. As such, the following lintian error is now wrong:
> 
> source: missing-build-dependency-for-dh-addon systemd => dh-systemd

I would keep the warning but it should say that it needs a versioned
b-dep on debhelper instead.


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



signature.asc
Description: OpenPGP digital signature

Bug#830930: lintian: dh --with systemd is now builtin

[Christian Hofstaedtler]

Package: lintian
Severity: normal
X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org

Dear Lintian Maintainers,

starting in debhelper 9.20160709, "--with systemd" support is built
into debhelper. As such, the following lintian error is now wrong:

source: missing-build-dependency-for-dh-addon systemd => dh-systemd

--with systemd can (and needs to be!) given on the dh command line,
even if dh-systemd is not in Build-Depends any more.

Best,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#792746: Upgrading to 4.0.8-1 kernel makes external monitors unusable

[Nathaniel Smith]

Yes, I haven't seen one of these crashes in quite some time -- sorry for
not updating.
On Jul 12, 2016 6:54 PM, "Ben Hutchings"  wrote:

> On Mon, 2016-07-11 at 22:45 +0200, Enrico Zini wrote:
> > On Sat, May 28, 2016 at 06:21:34PM +0200, Enrico Zini wrote:
> >
> > > When the problem happens, this appears on dmesg:
> > > [227725.132861] [drm:ironlake_irq_handler [i915]] *ERROR* PCH
> > > transcoder B FIFO underrun
> >
> > This seems fixed in 4.6.0-1-amd64:
> >
> >$ uptime
> > 22:44:00 up 6 days,  7:52,  1 user,  load average: 0.28, 0.34, 0.24
> >$ dmesg|grep transcoder
> >$
>
> Is this problem also fixed on your system, Nathaniel?
>
> Ben.
>
> --
>
> Ben Hutchings
> Sturgeon's Law: Ninety percent of everything is crap.
>

Bug#792746: Upgrading to 4.0.8-1 kernel makes external monitors unusable

[Ben Hutchings]

On Mon, 2016-07-11 at 22:45 +0200, Enrico Zini wrote:
> On Sat, May 28, 2016 at 06:21:34PM +0200, Enrico Zini wrote:
> 
> > When the problem happens, this appears on dmesg:
> > [227725.132861] [drm:ironlake_irq_handler [i915]] *ERROR* PCH
> > transcoder B FIFO underrun
> 
> This seems fixed in 4.6.0-1-amd64:
> 
>    $ uptime
> 22:44:00 up 6 days,  7:52,  1 user,  load average: 0.28, 0.34, 0.24
>    $ dmesg|grep transcoder
>    $ 

Is this problem also fixed on your system, Nathaniel?

Ben.

-- 

Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.


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

Bug#830922: kernel-handbook: please make the build reproducible

[Dhole]

Source: kernel-handbook
Version: 1.0.17+nm
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that kernel-handbook could not be built reproducibly.

A date and timestamp is embedded in the documentation using the local
timezone and locale.

The attached patch fixes this by fixing the timezone to UTC and the
locale to "C" in the timestamp. Once applied, kernel-handbook can be
built reproducibly in our current experimental framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds

Regards,
-- 
Dhole
diff -Nru kernel-handbook-1.0.17/debian/changelog 
kernel-handbook-1.0.17+nmu1/debian/changelog
--- kernel-handbook-1.0.17/debian/changelog 2016-03-07 03:08:15.0 
+0100
+++ kernel-handbook-1.0.17+nmu1/debian/changelog2016-07-13 
01:29:10.0 +0200
@@ -1,3 +1,10 @@
+kernel-handbook (1.0.17+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix locale and timezone in embedded timestamp to make it reproducible.
+
+ -- Eduard Sanou   Wed, 13 Jul 2016 01:28:52 +0200
+
 kernel-handbook (1.0.17) unstable; urgency=medium
 
   * debian/control: Change Vcs-Git and Vcs-Browser to canonical HTTP-S URLs
diff -Nru kernel-handbook-1.0.17/Makefile kernel-handbook-1.0.17+nmu1/Makefile
--- kernel-handbook-1.0.17/Makefile 2015-11-13 22:33:04.0 +0100
+++ kernel-handbook-1.0.17+nmu1/Makefile2016-07-13 01:37:47.0 
+0200
@@ -1,5 +1,5 @@
 version := $(shell dpkg-parsechangelog -SVersion)
-date:= $(shell date -d "$$(dpkg-parsechangelog -SDate)")
+date:= $(shell LC_ALL=C date --utc -d "$$(dpkg-parsechangelog -SDate)")
 
 LANG_PO := ja
 LANG_EN := en


signature.asc
Description: PGP signature

Bug#816439: linux-grsec: feeding the seed with SOURCE_DATE_EPOCH

[Steven Chamberlain]

tags 816439 + patch
thanks

Hi,

> > Contrary to: https://bugs.debian.org/816439, RANDSTRUCT is
> > actually compatible with reproducible builds, just need to
> > keep randomize_layout_seed.h.
> > https://twitter.com/grsecurity/status/704869584218685440

Holger Levsen wrote:
> seens like the it should be seeded with 
> https://reproducible-builds.org/specs/source-date-epoch/

Patch attached!  (please read it for the long description)

I'm afraid I couldn't find where to do this in linux-grsec Git.
So I've attached it in debdiff form instead.

There might still be other reproducibility issues after this.

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
diff -Nru 
linux-grsec-4.6.3/debian/patches/features/all/grsec/reproducible-randstruct.patch
 
linux-grsec-4.6.3/debian/patches/features/all/grsec/reproducible-randstruct.patch
--- 
linux-grsec-4.6.3/debian/patches/features/all/grsec/reproducible-randstruct.patch
   1970-01-01 00:00:00.0 +
+++ 
linux-grsec-4.6.3/debian/patches/features/all/grsec/reproducible-randstruct.patch
   2016-07-12 22:02:33.0 +
@@ -0,0 +1,29 @@
+Date: Tue, 12 Jul 2016 22:59:00 +0100
+From: Steven Chamberlain 
+Subject: make reproducible randomize_layout_seed.h
+
+If the SOURCE_DATE_EPOCH environment variable is defined, use the
+SHA-256 hash of that value, instead of /dev/urandom, to initialise
+randstruct_seed in randomize_layout_seed.h
+
+This allows the build to be reproducible.  In order to force a new seed,
+modify the SOURCE_DATE_EPOCH.  (In Debian, bumping the package version
+and adding a new debian/changelog entry will have that effect).
+
+Signed-off-by: Steven Chamberlain 
+
+--- a/scripts/gcc-plugins/gen-random-seed.sh
 b/scripts/gcc-plugins/gen-random-seed.sh
+@@ -1,7 +1,11 @@
+ #!/bin/sh
+ 
+ if [ ! -f "$1" ]; then
+-  SEED=`od -A n -t x8 -N 32 /dev/urandom | tr -d ' \n'`
++  if [ ! -z "$SOURCE_DATE_EPOCH" ]; then
++  SEED=`echo -n "$SOURCE_DATE_EPOCH" | sha256sum | cut -d" " -f1`
++  else
++  SEED=`od -A n -t x8 -N 32 /dev/urandom | tr -d ' \n'`
++  fi
+   echo "const char *randstruct_seed = \"$SEED\";" > "$1"
+   HASH=`echo -n "$SEED" | sha256sum | cut -d" " -f1 | tr -d ' \n'`
+   echo "#define RANDSTRUCT_HASHED_SEED \"$HASH\"" > "$2"
diff -Nru linux-grsec-4.6.3/debian/patches/series-grsec 
linux-grsec-4.6.3/debian/patches/series-grsec
--- linux-grsec-4.6.3/debian/patches/series-grsec   2016-07-07 
05:17:23.0 +
+++ linux-grsec-4.6.3/debian/patches/series-grsec   2016-07-12 
21:57:58.0 +
@@ -1 +1,2 @@
 features/all/grsec/grsecurity-3.1-4.6.3-201607062159+debian.patch
+features/all/grsec/reproducible-randstruct.patch


signature.asc
Description: Digital signature

Bug#760041: (no subject)

[zeha]

Cc:
Bcc: 
Subject: nullmailer: diff for NMU version 1:1.13-1.1
Date: Wed, 13 Jul 2016 01:17:31 +0200
X-NMUDIFF-Version: 2.16.6

Hi Michael,

thanks for checking the diff.

Here's a new one, which has removed mail-transport-agent.target,
fixed Documentation= and uses Type=forking instead.

I'm going to upload this to DELAYED/5.

Best,
Chris


diff -Nru nullmailer-1.13/debian/changelog nullmailer-1.13/debian/changelog
--- nullmailer-1.13/debian/changelog2014-08-08 02:19:32.0 +0200
+++ nullmailer-1.13/debian/changelog2016-07-13 01:15:52.0 +0200
@@ -1,3 +1,17 @@
+nullmailer (1:1.13-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Alexis Bienvenüe ]
+  * Deterministic file order in archives. (Closes: #820661)
+
+  [ Christian Hofstaedtler ]
+  * Bump Standards-Version to 3.9.8.
+  * Add native systemd units, based on initial patch supplied
+by Viktar Vauchkevich. (Closes: #760041)
+
+ -- Christian Hofstaedtler   Wed, 13 Jul 2016 01:15:46 +0200
+
 nullmailer (1:1.13-1) unstable; urgency=low
 
   * Ack NMU, thankyou for your help with this package.
diff -Nru nullmailer-1.13/debian/control nullmailer-1.13/debian/control
--- nullmailer-1.13/debian/control  2014-08-06 22:42:09.0 +0200
+++ nullmailer-1.13/debian/control  2016-07-13 01:11:38.0 +0200
@@ -2,14 +2,21 @@
 Section: mail
 Priority: extra
 Maintainer: Nick Leverton 
-Build-Depends: debhelper (>= 9), po-debconf, automake, autoconf,
- dh-autoreconf, libgnutls28-dev | libgnutls-dev
-Standards-Version: 3.9.5
+Build-Depends: autoconf,
+   automake,
+   debhelper (>= 9),
+   dh-autoreconf,
+   dh-systemd,
+   libgnutls28-dev | libgnutls-dev,
+   po-debconf
+Standards-Version: 3.9.8
 Homepage: http://untroubled.org/nullmailer/
 
 Package: nullmailer
 Architecture: any
-Depends: lsb-base, ${misc:Depends}, ${shlibs:Depends}
+Depends: lsb-base,
+ ${misc:Depends},
+ ${shlibs:Depends}
 Recommends: rsyslog | system-log-daemon
 Conflicts: mail-transport-agent
 Provides: mail-transport-agent
diff -Nru nullmailer-1.13/debian/links nullmailer-1.13/debian/links
--- nullmailer-1.13/debian/links2011-03-01 22:23:44.0 +0100
+++ nullmailer-1.13/debian/links2016-07-02 15:33:53.0 +0200
@@ -1,9 +1,9 @@
 bin/true usr/bin/newaliases
 usr/sbin/sendmail usr/lib/sendmail
-usr/share/man/man7/nullmailer.7.gz usr/share/man/man1/mailq.1.gz
-usr/share/man/man8/nullmailer-queue.8.gz usr/share/man/man5/adminaddr.5.gz
 usr/share/man/man1/nullmailer-inject.1.gz usr/share/man/man5/defaultdomain.5.gz
 usr/share/man/man1/nullmailer-inject.1.gz usr/share/man/man5/defaulthost.5.gz
 usr/share/man/man1/nullmailer-inject.1.gz usr/share/man/man5/idhost.5.gz
+usr/share/man/man7/nullmailer.7.gz usr/share/man/man1/mailq.1.gz
+usr/share/man/man8/nullmailer-queue.8.gz usr/share/man/man5/adminaddr.5.gz
 usr/share/man/man8/nullmailer-send.8.gz usr/share/man/man5/pausetime.5.gz
 usr/share/man/man8/nullmailer-send.8.gz usr/share/man/man5/remotes.5.gz
diff -Nru nullmailer-1.13/debian/manpages nullmailer-1.13/debian/manpages
--- nullmailer-1.13/debian/manpages 2012-05-16 21:45:16.0 +0200
+++ nullmailer-1.13/debian/manpages 2016-07-02 15:33:53.0 +0200
@@ -1,2 +1,2 @@
-doc/sendmail.1
 debian/man/*
+doc/sendmail.1
diff -Nru nullmailer-1.13/debian/nullmailer.service 
nullmailer-1.13/debian/nullmailer.service
--- nullmailer-1.13/debian/nullmailer.service   1970-01-01 01:00:00.0 
+0100
+++ nullmailer-1.13/debian/nullmailer.service   2016-07-13 01:06:08.0 
+0200
@@ -0,0 +1,11 @@
+[Unit]
+Description=Mail Transport Agent
+Documentation=man:nullmailer(7)
+
+[Service]
+Type=forking
+ExecStart=/usr/sbin/nullmailer-send --daemon
+User=mail
+
+[Install]
+WantedBy=multi-user.target
diff -Nru nullmailer-1.13/debian/patches/15_sort_files_in_archive.diff 
nullmailer-1.13/debian/patches/15_sort_files_in_archive.diff
--- nullmailer-1.13/debian/patches/15_sort_files_in_archive.diff
1970-01-01 01:00:00.0 +0100
+++ nullmailer-1.13/debian/patches/15_sort_files_in_archive.diff
2016-07-02 15:32:32.0 +0200
@@ -0,0 +1,16 @@
+Description: Sort files in archive
+ Sort files when using mergelib to create libnullmailer.a, to get
+ reproducible build
+Author: Alexis Bienvenüe 
+
+Index: nullmailer-1.13/lib/mergelib.sh
+===
+--- nullmailer-1.13.orig/lib/mergelib.sh
 nullmailer-1.13/lib/mergelib.sh
+@@ -12,5 +12,5 @@ for input in "$@"; do
+   ar x ../../"$input"
+   cd ..
+ done
+-ar rc ../"$archive" */*
++ar rc ../"$archive" `LC_ALL=C ls */*`
+ ranlib ../"$archive"
diff -Nru nullmailer-1.13/debian/patches/series 
nullmailer-1.13/debian/patches/series
--- nullmailer-1.13/debian/patches/series   2014-08-07 10:01:55.0 
+0200
+++ 

Bug#757760: debian-policy: please document build profiles

[Javier Serrano Polo]

Sorry, I missed your message.

> I'm removing #757760 from the recipients because that bug should
> contain a discussion about the implementation of the current build
> profile spec and should not be a discussion platform for further
> additions or changes to the spec. Lets use debian-dpkg@ to discuss
> this issue.

The BTS is my only way to keep an open discussion. I really cannot post
to lists.debian.org (I can to Alioth lists); should I try to fix that?
We can discuss in #830524.


smime.p7s
Description: S/MIME cryptographic signature

Bug#825699: jessie-pu: package glibc/2.19-18+deb8u5

[Aurelien Jarno]

On 2016-07-12 21:33, Adam D. Barratt wrote:
> On Wed, 2016-06-08 at 00:28 +0200, Aurelien Jarno wrote:
> > On 2016-05-29 17:19, Adam D. Barratt wrote:
> > > Control: tags -1 -moreinfo +confirmed
> > > 
> > > On Sun, 2016-05-29 at 17:53 +0200, Aurelien Jarno wrote:
> > > 
> > > > Can we get this into jessie-proposed-updates just after the 8.5 release,
> > > > so that it doesn't happen again for 8.6? Most of these changes were
> > > > ready in our git repository for over a month, it's just I didn't got 
> > > > time
> > > > this week to finish preparing the final upload.
> > > 
> > > That sounds like a good plan.
> > 
> > Now that the 8.5 release is out, I would like to upload glibc version
> > 2.19-18+deb8u5 to jessie-proposed-updates. You will find the diff below,
> > it only differs to the previous one by the addition of the CVE-2016-4429
> > fix.
> 
> Please go ahead; apologies for the delay.

Thanks, I have just uploaded it.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#830916: ActionView::Template::Error (undefined method `recaptcha_tags` ...)

[Christian Hofstaedtler]

Package: redmine-plugin-recaptcha
Version: 0.1.0+git20121018-3
Severity: serious

Dear Maintainer,

when testing your redmine plugin against the current redmine in
sid (3.2.3-1), I've found that redmine aborts with an internal error when
clicking on the "Register" link. From production.log:

  Started GET "/account/register" for 192.168.234.1 at 2016-07-13 00:37:27 +0200
  Processing by AccountController#register as HTML
Current user: anonymous
Rendered plugins/redmine_recaptcha/app/views/account/register.html.erb 
within layouts/base (775.4ms)
  Completed 500 Internal Server Error in 782ms (ActiveRecord: 0.9ms)
  
  ActionView::Template::Error (undefined method `recaptcha_tags' for 
#<#:0x007f1f95b5d6f8>):
  40: 
  41: 
  42: 
  43: <%= recaptcha_tags :public_key => 
Setting.plugin_redmine_recaptcha['recaptcha_public_key'], :ssl => true %>
  44:  
  45: <%= submit_tag l(:button_submit) %>
  46: <% end %>
plugins/redmine_recaptcha/app/views/account/register.html.erb:43:in `block 
in 
_plugins_redmine_recaptcha_app_views_account_register_html_erb__732500603993694831_69886816182180'
plugins/redmine_recaptcha/app/views/account/register.html.erb:3:in 
`_plugins_redmine_recaptcha_app_views_account_register_html_erb__732500603993694831_69886816182180'
lib/redmine/sudo_mode.rb:63:in `sudo_mode'


-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#757760: debian-policy: please document build profiles

[Javier Serrano Polo]

El dg 10 de 07 de 2016 a les 19:25 +0200, Javier Serrano Polo va
escriure:
> For instance, the linux source
> package should have a way to build only linux-image-4.6.0-1-686 (profile
> pkg.linux.686)

Current linux package already uses build profiles. It looks like the
specification works better in negative form. For instance, the field for
linux-image-4.6.0-1-686 should be:
Build-Profiles: 

Perhaps, the "<>" token is not needed.


smime.p7s
Description: S/MIME cryptographic signature

Bug#830915: pyhoca-gui: Does not start, complains about _PyGObject_API

[Alex Corcoles]

Package: pyhoca-gui
Version: 0.5.0.6-1
Severity: important

Dear Maintainer,

When starting pyhoca-gui I get:

$ pyhoca-gui
Traceback (most recent call last):
  File "/usr/bin/pyhoca-gui", line 35, in 
from pyhoca.wxgui.launcher import PyHocaGUI_Launcher
  File "/usr/lib/python2.7/dist-packages/pyhoca/wxgui/launcher.py",
line 44, in 
from frontend import PyHocaGUI
  File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93,
in __import__
result = _import(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pyhoca/wxgui/frontend.py",
line 45, in 
import notify
  File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93,
in __import__
result = _import(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pyhoca/wxgui/notify.py", line
31, in 
import pynotify as _Notify
  File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93,
in __import__
result = _import(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/gtk-2.0/pynotify/__init__.py",
line 1, in 
from _pynotify import *
  File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93,
in __import__
result = _import(*args, **kwargs)
ImportError: could not import gobject (could not find _PyGObject_API object)

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

Kernel: Linux 4.6.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 pyhoca-gui depends on:
ii  gnome-colors-common5.5.1-2
ii  libpython2.7-stdlib [python-argparse]  2.7.12-1
ii  python 2.7.11-2
ii  python-notify  0.1.1-4
ii  python-pkg-resources   20.10.1-1.1
ii  python-setproctitle1.1.8-1+b2
ii  python-wxgtk3.03.0.2.0+dfsg-2
ii  python-x2go0.5.0.4-1

Versions of packages pyhoca-gui recommends:
ii  mate-notification-daemon [notification-daemon]  1.14.0-1
ii  notification-daemon 3.20.0-1

pyhoca-gui suggests no packages.

-- no debconf information

Bug#830914: Init script should be more LSB compliant

[Christian Hofstaedtler]

Package: aoetools
Version: 36-1
Severity: wishlist
Tags: patch

The init script could be more LSB compliant, and use the lsb
functions for logging errors and such.

See Ubuntus modification for what could be done:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/aoetools/wily/download/head:/aoetools.init-20090813163725-2pomquvdax6c8wjb-52/aoetools.init

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#830913: debian-policy: Allow amd64 systems without /lib64

[Javier Serrano Polo]

Package: debian-policy
Version: 3.9.8.0
Severity: wishlist

Some amd64 systems do not have /lib64, although they can run programs
with the interpreter set to /lib64/ld-linux-x86-64.so.2 . It would be
nice if Debian could allow such systems. In section 9.1.1, where it
says:

The execution time linker/loader, ld*, must still be made
available in the existing location under /lib or /lib64

"must" should be "should".


smime.p7s
Description: S/MIME cryptographic signature

Bug#830912: fakeroot complains about missing acl_* symbols

[Eric Valette]

Package: fakeroot
Version: 1.21-1
Severity: normal

fakeroot
dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_get_fd
dlsym(acl_get_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_get_file
dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_set_fd
dlsym(acl_set_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_set_file
dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_get_fd
dlsym(acl_get_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_get_file
dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_set_fd
dlsym(acl_set_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_set_file
dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_get_fd
dlsym(acl_get_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_get_file
dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_set_fd
dlsym(acl_set_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: 
undefined symbol: acl_set_file

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

Kernel: Linux 4.4.14 (SMP w/8 CPU cores; PREEMPT)
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 fakeroot depends on:
ii  libc62.23.90+20160711.c10f90d-1
ii  libfakeroot  1.21-1

fakeroot recommends no packages.

fakeroot suggests no packages.

-- no debconf information

Bug#828526: racket: FTBFS with openssl 1.1.0

[David Bremner]

Tags: fixed-upstream

Kurt Roeckx  writes:

> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/racket_6.5-1_amd64-20160529-1529
>
> On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of 
> the
> reasons why it might fail.  There are also updated man pages at
> https://www.openssl.org/docs/manmaster/ that should contain useful 
> information.
>
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.
>
> If you have problems making things work, feel free to contact us.
>
>
> Kurt

This is apparently fixed in b0c55b73945d8 [1], which should be part of the
next upstream release of racket. I expect that release to happen within
the next few weeks.

d


[1] 
https://github.com/racket/racket/commit/b0c55b73945d8dab52f8ff86df69dd6cbb0147b4


signature.asc
Description: PGP signature

Bug#830911: Britney git mirrors are broken by release.d.o move

[Niels Thykier]

Package: release.debian.org
Severity: important
User: release.debian@packages.debian.org
Usertags: britney

https://anonscm.debian.org/git/mirror/britney2.git (and similar) are
not being updated.  They pull from release.d.o/git/, but those links
are not functional anymore.

Bug#830910: libterralib: Please drop me as an uploader

[Petter Reinholdtsen]

Package:  src:libterralib
Version:  4.3.0+dfsg.2-7
Severity: wishlist

Hi.  I try to reduce the number of packages I am supposed to look after
and libterralib is one I no longer use much, so I would like to be
removed as an uploader.

-- 
Happy hacking
Petter Reinholdtsen

Bug#830909: samba: Systemd service files use wrong path in PIDFile

[Achim Gottinger]

Package: samba
Version: 2:4.4.5+dfsg-2
Severity: normal

Dear Maintainer,

Current systemd service files use /run as pid folder. Samba binaries uses
(/var)/run/samba instead.

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

Kernel: Linux 3.16.0-4-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 samba depends on:
ii  adduser  3.113+nmu3
ii  dpkg 1.17.27
ii  init-system-helpers  1.22
ii  libbsd0  0.7.0-2
ii  libc62.19-18+deb8u4
ii  libldb1  2:1.1.26-1
ii  libpam-modules   1.1.8-3.1+deb8u1+b1
ii  libpam-runtime   1.1.8-3.1+deb8u1
ii  libpopt0 1.16-10
ii  libpython2.7 2.7.9-2
ii  libtalloc2   2.1.6-1
ii  libtdb1  1.3.9-1
ii  libtevent0   0.9.28-1
ii  libwbclient0 2:4.4.5+dfsg-2
ii  lsb-base 4.1+Debian13+nmu1
ii  multiarch-support2.19-18+deb8u4
ii  procps   2:3.3.9-9
ii  python   2.7.9-1
ii  python-dnspython 1.12.0-1
ii  python-samba 2:4.4.5+dfsg-2
pn  python2.7:any
ii  samba-common 2:4.4.5+dfsg-2
ii  samba-common-bin 2:4.4.5+dfsg-2
ii  samba-libs   2:4.4.5+dfsg-2
ii  tdb-tools1.3.9-1
ii  update-inetd 4.43

Versions of packages samba recommends:
ii  attr1:2.4.47-2
ii  logrotate   3.8.7-1+b1
ii  samba-dsdb-modules  2:4.4.5+dfsg-2
ii  samba-vfs-modules   2:4.4.5+dfsg-2

Versions of packages samba suggests:
ii  bind9  1:9.9.5.dfsg-9+deb8u6
ii  bind9utils 1:9.9.5.dfsg-9+deb8u6
pn  ctdb   
pn  ldb-tools  
pn  ntp
pn  smbldap-tools  
pn  ufw
ii  winbind2:4.4.5+dfsg-2

-- no debconf information

Bug#828401: Pending fixes for bugs in the libnet-ssleay-perl package

[pkg-perl-maintainers]

tag 828401 + pending
thanks

Some bugs in the libnet-ssleay-perl package are closed in revision
a14580e766bc5761d89609f58c9e1f9a1f8a322c in branch '  experimental'
by Dominic Hargreaves

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-ssleay-perl.git/commit/?id=a14580e

Commit message:

OpenSSL 1.1 patch from upstream SVN (Closes: #828401)

Bug#828826: nfs-common: move of rpc_pipefs mountpoint to /run breaks blkmapd

[Michael Biebl]

Control: severity -1 serious

On Tue, 28 Jun 2016 09:21:44 +0200 Christoph Hellwig  wrote:
> Package: nfs-common
> Version: 1:1.2.8-9
> Severity: important
> Tags: patch
> 
> Dear Maintainer,
> 
> commit ba649fa4 ("Migrate the rpc_pipefs mount out of /var/lib to /run, to
> better support /var on NFS.") in the Debian packaging repo completely
> broke blkmapd, which still looks for rpc_pipefs in the old place.
> >From looking in the BTS gssd also seems to have the same problem (#632141).
> 
> diff --git a/utils/blkmapd/device-discovery.c 
> b/utils/blkmapd/device-discovery.c
> index 69f00fa..7b00c90 100644
> --- a/utils/blkmapd/device-discovery.c
> +++ b/utils/blkmapd/device-discovery.c
> @@ -55,9 +55,9 @@
>  #define EVENT_SIZE (sizeof(struct inotify_event))
>  #define EVENT_BUFSIZE (1024 * EVENT_SIZE)
>  
> -#define BL_PIPE_FILE "/var/lib/nfs/rpc_pipefs/nfs/blocklayout"
> -#define NFSPIPE_DIR  "/var/lib/nfs/rpc_pipefs/nfs"
> -#define RPCPIPE_DIR  "/var/lib/nfs/rpc_pipefs"
> +#define BL_PIPE_FILE "/run/rpc_pipefs/nfs/blocklayout"
> +#define NFSPIPE_DIR  "/run/rpc_pipefs/nfs"
> +#define RPCPIPE_DIR  "/run/rpc_pipefs"
>  #define PID_FILE "/run/blkmapd.pid"
>  

Looks to me like this should be RC, i.e. needs to be fixed for the next
Debian release.
Thus bumping the severity.


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



signature.asc
Description: OpenPGP digital signature

Bug#827781: jessie-pu: package lxc/1:1.0.6-6+deb8u3

[Adam D. Barratt]

On Wed, 2016-06-29 at 16:54 -0300, Antonio Terceiro wrote:
> On Tue, Jun 28, 2016 at 12:16:21PM +0200, Julien Cristau wrote:
[...]
> > Ack.  Please go ahead.
> 
> Hi, actually I was just made aware of a regression: including `init` in
> the package list breaks the creation of wheezy containers because `init`
> did not exist then. The regression was fixed in 1:2.0.1-3 just uploaded
> to unstable.
> 
> The updated diff is attached.

Please go ahead.

Regards,

Adam

Bug#829136: jessie-pu: package harfbuzz/0.9.35-2+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2016-06-30 at 22:19 +0200, Moritz Muehlenhoff wrote:
> +harfbuzz (0.9.35-2+deb8u1) jessie; urgency=medium
> +
> +  * Backport upstream commit 613e630617074eb9b62b794cc37c9b42a7fb079b to 
> address
> +CVE-2016-2052

Please go ahead.

Regards,

Adam

Bug#798996: apt-setup: Please refer to httpredir.debian.org over ftp.debian.org in commented-out examples

[Chris Lamb]

retitle 798996 Please refer to deb.debian.org over ftp.debian.org in 
commented-out examples
thanks 

Chris Lamb wrote:

> apt-setup: Please refer to httpredir.debian.org over
> ftp.debian.org in commented-out examples

I find httpredir too unreliable these days, so an updated patch
is attached that uses http://deb.debian.org instead.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/generators/92updates b/generators/92updates
index d68ca89..982be73 100755
--- a/generators/92updates
+++ b/generators/92updates
@@ -47,7 +47,7 @@ else
echo "# are provided as examples, but you should amend them as 
appropriate" >> $file
echo "# for your mirror of choice." >> $file
echo "#" >> $file
-   echo "# deb http://ftp.debian.org/debian/ ${codename}-updates $dists" 
>> $file
+   echo "# deb http://deb.debian.org/debian/ ${codename}-updates $dists" 
>> $file
 fi
 if db_get netcfg/dhcp_options && \
[ "$RET" = "Do not configure the network at this time" ]; then
@@ -72,7 +72,7 @@ fi
 if [ -n "$protocol" ] && [ -n "$host" ]; then
echo "deb-src $protocol://${host}${directory} ${codename}-updates 
$dists" >> $file
 else
-   echo "# deb-src http://ftp.debian.org/debian/ ${codename}-updates 
$dists" >> $file
+   echo "# deb-src http://deb.debian.org/debian/ ${codename}-updates 
$dists" >> $file
 fi
 
 exit $CODE
diff --git a/generators/93backports b/generators/93backports
index 1021d5f..11b12ff 100755
--- a/generators/93backports
+++ b/generators/93backports
@@ -47,7 +47,7 @@ else
echo "# are provided as examples, but you should amend them as 
appropriate" >> $file
echo "# for your mirror of choice." >> $file
echo "#" >> $file
-   echo "# deb http://ftp.debian.org/debian/ ${codename}-backports $dists" 
>> $file
+   echo "# deb http://deb.debian.org/debian/ ${codename}-backports $dists" 
>> $file
 fi
 if db_get netcfg/dhcp_options && \
[ "$RET" = "Do not configure the network at this time" ]; then
@@ -72,7 +72,7 @@ fi
 if [ -n "$protocol" ] && [ -n "$host" ]; then
echo "deb-src $protocol://${host}${directory} ${codename}-backports 
$dists" >> $file
 else
-   echo "# deb-src http://ftp.debian.org/debian/ ${codename}-backports 
$dists" >> $file
+   echo "# deb-src http://deb.debian.org/debian/ ${codename}-backports 
$dists" >> $file
 fi
 
 exit $CODE

Bug#829135: jessie-pu: package python2.7/2.7.9-2+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2016-06-30 at 22:17 +0200, Moritz Muehlenhoff wrote:
> +python2.7 (2.7.9-2+deb8u1) jessie; urgency=medium
> +
> +  * Backport upstream commit b3ce713fb9beebfff9848cefa0acbd59acc68fe9
> +to address StartTLS stripping attack in smtplib (CVE-2016-0772)
> +  * Backport upstream commit 985fc64c60d6adffd1138b6cc46df388ca91ca5d
> +to address integer overflow in zipimporter (CVE-2016-5636)
> +  * Backport upstream commit 1c45047c51020d46246385949d5c02e026d47320
> +to address HTTP header injection (CVE-2016-5699)

Please go ahead.

Regards,

Adam

Bug#829603: jessie-pu: package conkeror/1.0~~pre-1+git141025-1+deb8u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2016-07-04 at 17:29 +0200, Axel Beckert wrote:
> With the update to Firefox 45 in Jessie, it once again caused
> regressions in depending packages due to removed features. For
> conkeror it's this time the removal of some specific syntactic sugar
> around the "let" construct.
> 
> Cherry-picking the according upstream fix solves the issue also in
> Jessie. I've prepared and tested an upload for that and would like to
> upload this to jessie-proposed-updates.

Please go ahead.

Regards,

Adam

Bug#829650: jessie-pu: package ruby-eventmachine/1.0.3-6+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2016-07-05 at 04:40 +0200, Balint Reczey wrote:
> The Security Team suggested fixing the TEMP-0678512-2E167C [1] security
> issue through a point release.
> 
> The issue is a remotely triggerable crash due to stack overflow.

Please go ahead.

Regards,

Adam

Bug#830908: RFS: libu2f-server/1.0.1-1.3 [NMU]

[Nicolas Braud-Santoni]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libu2f-server"

 * Package name: libu2f-server
   Version : 1.0.1-1.3
   Upstream Author : [fill in name and email of upstream]
 * URL : [fill in URL of upstreams web site]
 * License : [fill in]
   Section : utils

It builds those binary packages:

  libu2f-server-dev - Development files for the U2F server C library 
libu2f-server
  libu2f-server0 - Universal 2nd Factor (U2F) server communication C Library
  u2f-server - Command line tool to do Universal 2nd Factor (U2F) operations


My prepared upload is available on mentors.debian.net:

  https://mentors.debian.net/package/libu2f-server

Alternatively, one can download the package with dget:

  dget -x 
https://mentors.debian.net/debian/pool/main/libu/libu2f-server/libu2f-server_1.0.1-1.3.dsc


This upload enables build-time hardening features,
and fixes some minor issues:
- use HTTPS for the Vcs-Git link;
- bump Standards-Version to 3.9.8 (no change required).


I am aware that sponsored NMUs are not a sane way to maintain this
package in the long term.  As such, I reached out to the pkg-auth team,
applied for membership there, and suggested several changes to make the
collaborative maintainance of those packages easier.


Best,

  nicoo

Bug#830805: jessie-pu: package cacti/0.8.8b+dfsg-8+deb8u4

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2016-07-11 at 20:28 +0200, Paul Gevers wrote:
> There are currently three CVE's open against the cacti package in jessie that
> have a patch available¹. Non of the issues are severe enough to warrent a
> security upload, but I still think it is a good idea to get this fixed in
> jessie. Could you please consider the attached debdiff?

Please go ahead.

Regards,

Adam

Bug#823911: jessie-pu: package debian-security-support/2016.05.09+nmu1~deb8u1

[Adam D. Barratt]

On Wed, 2016-06-29 at 16:29 +0200, Santiago Ruano Rincón wrote:
> El 27/05/16 a las 18:17, Adam D. Barratt escribió:
> > Control: tags -1 + confirmed
[...]
> > Please go ahead.
[...]
> A more recent version of debian-security-support fixes two additional
> bugs:
> 
> https://bugs.debian.org/824015
> https://bugs.debian.org/824081
> 
> This new package also updates the security support status for different
> packages, and updates several localization files. Please, find the diff
> below.

fwiw, I don't find > 1000 line inline diffs particularly pleasant to
deal with; attaching it would have been more conventional. (

> Should I go ahead with this new release?

Please feel free.

> Retitling this same bug report is enough, or a new bug is needed?

As you never actually uploaded the previous version, reusing this report
is fine. (Basically one bug per upload, with occasional exceptions for
things like FTBFS issues in uploads.)

Regards,

Adam

Bug#830907: RFS: pam-u2f/1.0.4-0.1 [NMU]

[Nicolas Braud-Santoni]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pam-u2f"

 * Package name: pam-u2f
   Version : 1.0.4-0.1
   Upstream Author : Yubico AG
 * URL : https://developers.yubico.com/pam-u2f/
 * License : BSD
   Section : admin

It builds those binary packages:
  libpam-u2f - universal 2nd factor (U2F) PAM module
  pamu2fcfg  - universal 2nd factor (U2F) PAM module command-line helper tool

My prepared upload can be found on mentors.debian.net:

  https://mentors.debian.net/package/pam-u2f

Alternatively, one can download the package with dget:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pam-u2f/pam-u2f_1.0.4-0.1.dsc


This upload brings v1.0.4 to the archive, which fixes a potential
security issue (see [0] for details), and enables build-time hardening
features.

Moreover, it fixes a number of minor issues:
- use HTTPS for the Vcs-Git link;
- bump Standards-Version to 3.9.8 (no change required);
- install the pam_u2f(8) manpage in the corresponding package,
  rather than in pamu2fcfg.


I am aware that sponsored NMUs are not a sane way to maintain this
package in the long term.  As such, I reached out to the pkg-auth team,
applied for membership there, and suggested several changes to make the
maintainance of those packages easier.


Best,

  nicoo

[0] https://developers.yubico.com/pam-u2f/Release_Notes.html

Bug#830906: freepascal textmode IDE crashes on startup on arm64

[Paul Gevers]

On 12-07-16 22:28, peter green wrote:
> Not sure what is going wrong here.  gdb tells me that P is nil and yet
> there is a gaurd against that in the code. Maybe a miscompilation of
> some sort?
> 
> The issue does not seem to appear with upstream trunk.

Upstream didn't support arm64 in 3.0.0, we patched the source to get it
working. Maybe there are more changes in trunk required for fully
working arm64.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#825699: jessie-pu: package glibc/2.19-18+deb8u5

[Adam D. Barratt]

On Wed, 2016-06-08 at 00:28 +0200, Aurelien Jarno wrote:
> On 2016-05-29 17:19, Adam D. Barratt wrote:
> > Control: tags -1 -moreinfo +confirmed
> > 
> > On Sun, 2016-05-29 at 17:53 +0200, Aurelien Jarno wrote:
> > 
> > > Can we get this into jessie-proposed-updates just after the 8.5 release,
> > > so that it doesn't happen again for 8.6? Most of these changes were
> > > ready in our git repository for over a month, it's just I didn't got time
> > > this week to finish preparing the final upload.
> > 
> > That sounds like a good plan.
> 
> Now that the 8.5 release is out, I would like to upload glibc version
> 2.19-18+deb8u5 to jessie-proposed-updates. You will find the diff below,
> it only differs to the previous one by the addition of the CVE-2016-4429
> fix.

Please go ahead; apologies for the delay.

Regards,

Adam

Bug#830906: freepascal textmode IDE crashes on startup on arm64

[peter green]

Package: fp-ide-3.0.0
Severity: important

The freepascal textmode IDE crashes on startup on arm64. I rebuilt it 
with debug symbols enabled and got the following backtrace.


root@pine64pro:/# gdb /fpc-3.0.0+dfsg/fpcsrc/ide/bin/aarch64-linux/fp
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /fpc-3.0.0+dfsg/fpcsrc/ide/bin/aarch64-linux/fp...done.
(gdb) run
Starting program: /fpc-3.0.0+dfsg/fpcsrc/ide/bin/aarch64-linux/fp

Program received signal SIGSEGV, Segmentation fault.
0x0043851c in REGISTERTYPE (S=...) at 
rtl-extra/src/inc/objects.pp:2935
2935 Do P := P^.Next; { Find end 
of chain }

(gdb) p P
$1 = 0x0
(gdb) bt
#0  0x0043851c in REGISTERTYPE (S=...)
at rtl-extra/src/inc/objects.pp:2935
#1  0x006d1f4c in REGISTERTIMEDDIALOG () at fv/src/timeddlg.pas:246
#2  0x006d1f6c in TIMEDDLG_$$_init () at fv/src/timeddlg.pas:252
#3  0x0041a4cc in fpc_initializeunits () at ../inc/system.inc:895
#4  0x00400888 in main () at fp.pas:350
(gdb) p S
$2 = {OBJTYPE = 98, VMTLINK = 0x8872f8, LOAD = 0x6d1ae8, STORE = 0x6d1c58,
  NEXT = 0x0}
(gdb)

Not sure what is going wrong here.  gdb tells me that P is nil and yet 
there is a gaurd against that in the code. Maybe a miscompilation of 
some sort?


The issue does not seem to appear with upstream trunk.

Bug#783270: shorewall: Triggers deprecation warning for automatic helper assignment

[Roberto C . Sánchez]

On Tue, Jul 12, 2016 at 09:24:26PM +0200, Dominic Hargreaves wrote:
> 
> The problem still occurs on systems with a minimimal config - but I don't
> have a tarball to hand. The systems are jessie, so perhaps the issue is
> fixed in sid (maybe even with a sid kernel the original version of
> shorewall?)
> 
Thanks for the additional information.  I'll try and set up a minimal
Jessie VM to recreate the problem.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Bug#830287: [Freedombox-pkg-team] Bug#830287: pagekite: please make the build reproducible

[Petter Reinholdtsen]

[Chris Lamb]
> Whilst working on the "reproducible builds" effort [0], we noticed
> that pagekite could not be built reproducibly.
>
> Patch attached.
>
>  [0] https://wiki.debian.org/ReproducibleBuilds

Thank you for looking into this.

I tried to apply the patch to git, but someone could not get it to
work.  But the git setup is a bit strange to me, and perhaps Sunil will
have better luck. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#830905: openconnect: Please enable GSSAPI support

[Jochen Hein]

Package: openconnect
Version: 7.06-2
Severity: wishlist

Dear Maintainer,

I'm running a FreeIPA server in my local network and use Kerberos/GSSAPI
for most authentication purposes. Openconnect as compiled for Debian right
now does not include support for GSSAPI.

I've compiled a local package after installing krb5-multidev/libkrb5-dev and
have built openconnect. That package includes GSSAPI support and works
for me.

I'm not sure what beside adding the build-dep to the control file
might be needed, but a GSSAPI enabled package would help in running
Single-Sign-On for me.

Thanks for your consideration
Jochen


-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (500, 'stable'), (99, 
'testing')
Architecture: amd64 (x86_64)

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

Versions of packages openconnect depends on:
ii  libc62.19-18+deb8u4
ii  libgnutls30  3.4.12-1
ii  libopenconnect5  7.06-2
ii  libproxy10.4.11-4+b2
ii  libxml2  2.9.1+dfsg1-5+deb8u2
ii  vpnc-scripts 0.1~git20140806-1

openconnect recommends no packages.

openconnect suggests no packages.

-- no debconf information

Bug#830839: ConnectionError: ('Connection aborted.', ResponseNotReady()) when using Session interface

[Daniele Tricoli]

Hello Roland,
many thanks for this detailed report!

On Tue, 12 Jul 2016 08:05:57 +0200 Roland Hieber  wrote:
> Package: python-requests
> Followup-For: Bug #830839
> 
> Huh. It seems that every other get() call fails:
> 
>   >>> r = session.get(url)
>   >>> r = session.get(url)
>   Traceback (most recent call last):
>   File "", line 1, in 
>   File 
> "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 
477, in get
>   return self.request('GET', url, **kwargs)
>   File 
> "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 
465, in request
>   resp = self.send(prep, **send_kwargs)
>   File 
> "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 
573, in send
>   r = adapter.send(request, **kwargs)
>   File 
> "/usr/local/lib/python2.7/dist-packages/requests/adapters.py", line 
415, in send
>   raise ConnectionError(err, request=request)
>   requests.exceptions.ConnectionError: ('Connection aborted.', 
ResponseNotReady())

Unfortunately I was not able to reproduce it on testing. I used the infinite 
loop and I stopped it after 20 seconds because I did not want to waste your 
resources.

>   >>> r = session.get(url)
>   >>> r.headers
>   {'content-encoding': 'gzip', 'transfer-encoding': 'chunked', 'strict-
transport-security': 'max-age=30758400', 'server': 'nginx/1.6.2', 'last-
modified': 'Sat, 02 Jul 2016 21:32:16 GMT', 'connection': 'keep-alive', 
'date': 'Tue, 12 Jul 2016 05:51:14 GMT', 'content-type': 'text/html'}
>   >>> r = session.get(url)
>   Traceback (most recent call last):
>   File "", line 1, in 
>   File 
> "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 
477, in get
>   return self.request('GET', url, **kwargs)
>   File 
> "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 
465, in request
>   resp = self.send(prep, **send_kwargs)
>   File 
> "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 
573, in send
>   r = adapter.send(request, **kwargs)
>   File 
> "/usr/local/lib/python2.7/dist-packages/requests/adapters.py", line 
415, in send
>   raise ConnectionError(err, request=request)
>   requests.exceptions.ConnectionError: ('Connection aborted.', 
ResponseNotReady())
>   >>> r = session.get(url)
>   >>> r = session.get(url)

Also this is working right now for me. 

I'm sure you tried several time, but please can you try again? Also including 
a pool of destinations to be sure to exclude network issues?

I will investigate this more deeply, and I will repeat tests in a clean chroot 
to be sure.

Kind regards,

-- 
 Daniele Tricoli 'eriol'
 https://mornie.org

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

Bug#830881: shorewall: fails to upgrade: No such meth

[Roberto C . Sánchez]

On Tue, Jul 12, 2016 at 01:41:32PM -0500, Dale Schroeder wrote:
> 
> After removing shorewall.service, I had no luck with "dpkg-reconfigure
> shorewall"; however, "apt-get -f install" finished the install for me.
> 

My mistake.  I should have suggested 'dpkg --pending --configure'.  As
you found, 'apt-get -f install' also accomplishes the same thing.

I apologize for the hassle.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Bug#830904: RFP: puppetserver -- the next-generation application for managing Puppet agents

[Mathieu Parent]

Package: wnpp
Severity: wishlist
Control: block -1 by 819811

* Package name: puppetserver
  Version : 2.4
  Upstream Author : Puppetlabs
* URL : https://docs.puppet.com/puppetserver/latest/
* License : Apache-2.0
  Programming Lang: Clojure, Ruby
  Description : the next-generation application for managing Puppet agents

Puppet Server is the next-generation application for managing Puppet agents. 
This platform implements Puppet's server-side components in a more distributed, 
service-oriented architecture. We've built Puppet Server on top of the same 
technologies that make PuppetDB successful, and which allow us to greatly 
improve performance, scalability, advanced metrics collection, and fine-grained 
control over the Ruby runtime.

This package needs some additionnal dependencies, most of them needed by 
puppetdb too (#673515).

It would also benefit from leiningen (#819811).

Bug#819811: ITP: leiningen -- simple build system for Clojure

[Mathieu Parent]

On Sat, 2 Apr 2016 23:06:58 +0800 ChangZhuo Chen
=?utf-8?B?KOmZs+aYjOWArCk=?=  wrote:
[...]
> * Package name: leiningen
[...]
> The package was once in Debian, and I plan to bring it back.

Hello ChangZhuoChen,

Any new on this?

I don't know anything about Clojure and Leiningen, but I'm waiting for
it for puppetserver and puppetdb.

Regards

Mathieu Parent

Bug#804622: -x auth_info is a required parameter, at least with SQL

[martin f krafft]

also sprach Apollon Oikonomopoulos  [2016-02-23 15:30 
+0100]:
> > When invoking doveadm auth without any -x parameter, the SQL
> > database sees the following invalid query:
> > 
> >pgsql: Query failed, aborting: SELECT p.userid, p.password, u.uid AS 
> > userdb_uid, u.gid AS userdb_gid, u.home AS userdb_home, u.mail AS 
> > userdb_mail FROM dovecotpassword('test','pantsfullofunix.net') p, 
> > dovecotuser('test', 'pantsfullofunix.net') u WHERE doveadm
> >Error: sql(t...@pantsfullofunix.net): Password query failed: ERROR:  
> > column "doveadm" does not exist
> 
> Unfortunately I am not able to reproduce this, however this query looks 
> terribly malformed :) Can you share the actual auth-sql.conf.ext as well 
> as the exact doveadm command that fails?

Attached is the auth conf. The failing command is 'doveadm auth'
without any -x parameter.

Thanks for looking into this, and sorry for the late reply!

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
"america may be unique in being a country which has leapt
 from barbarism to decadence without touching civilization."
  -- john o'hara
# Authentication for SQL users. Included from 10-auth.conf.
#
# 

passdb {
  driver = sql

  # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext
  args = /etc/dovecot/dovecot-sql.conf.ext
}

# "prefetch" user database means that the passdb already provided the
# needed information and there's no need to do a separate userdb lookup.
# 
userdb {
  driver = prefetch
}

userdb {
  driver = sql
  args = /etc/dovecot/dovecot-sql.conf.ext
}

# If you don't have any user-specific settings, you can avoid the user_query
# by using userdb static instead of userdb sql, for example:
# 
#userdb {
  #driver = static
  #args = uid=vmail gid=vmail home=/var/vmail/%u
#}


signature.asc
Description: PGP signature

Bug#830902: openBVE doesn't start

[Elia Argentieri]

Package: openbve
Version: 1.4.0.10-3
Severity: grave

Dear maintainer,

I installed openBVE, but it doesn't start. It just prints these lines in a 
terminal and nothing more happens.
The only thing to do is CTRL+C.

libpng error: invalid after png_start_read_image or png_read_update_info
libpng error: invalid after png_start_read_image or png_read_update_info
libpng error: invalid after png_start_read_image or png_read_update_info
System.ArgumentNullException: Value cannot be null.
Parameter name: value
  at System.Windows.Forms.ImageList+ImageCollection+ImageListItem..ctor 
(System.Drawing.Image value) <0x419f73f0 + 0x00157> in :0 
  at System.Windows.Forms.ImageList+ImageCollection.Add (System.String key, 
System.Drawing.Image image) <0x419f7380 + 0x0003b> in :0 
  at OpenBve.formMain.formMain_Load (System.Object sender, System.EventArgs e) 
<0x419eae80 + 0x04fc3> in :0 
  at System.Windows.Forms.Form.OnLoad (System.EventArgs e) <0x419eacb0 + 
0x00071> in :0 
  at System.Windows.Forms.Form.OnLoadInternal (System.EventArgs e) <0x419eaa90 
+ 0x0007f> in :0 


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

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

Versions of packages openbve depends on:
ii  libmono-corlib4.5-cil4.2.1.102+dfsg2-8
ii  libmono-i18n4.0-all  4.2.1.102+dfsg2-8
ii  libmono-system-drawing4.0-cil4.2.1.102+dfsg2-8
ii  libmono-system-windows-forms4.0-cil  4.2.1.102+dfsg2-8
ii  libmono-system4.0-cil4.2.1.102+dfsg2-8
ii  libtaoframework-openal1.1-cil2.1.svn20090801-14
ii  libtaoframework-opengl3.0-cil2.1.svn20090801-14
ii  libtaoframework-sdl1.2-cil   2.1.svn20090801-14
ii  mono-runtime 4.2.1.102+dfsg2-8
ii  openbve-data 1.4.0.10+dfsg-1

Versions of packages openbve recommends:
pn  bve-route  
pn  bve-train  

openbve suggests no packages.

-- no debconf information

Bug#830903: python3-pyqt4: Package lacks QtWebKit support

[Orestes Mas]

Package: python3-pyqt4
Version: 4.11.4+dfsg-2
Severity: important

Dear Maintainer,

According to apt-file, QtWebKit module should be in this package:

# apt-file search PyQt4 |grep WebKit
(...)
python3-pyqt4: 
/usr/lib/python3/dist-packages/PyQt4/QtWebKit.cpython-34m-x86_64-linux-gnu.so
(...)

but in fact there's not:

# dpkg -L python3-pyqt4
/.
/usr
/usr/lib
/usr/lib/python3
/usr/lib/python3/dist-packages
/usr/lib/python3/dist-packages/PyQt4
/usr/lib/python3/dist-packages/PyQt4/Qt.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtAssistant.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtCore.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtDBus.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtDeclarative.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtDesigner.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtHelp.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtNetwork.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtScript.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtScriptTools.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtSvg.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtTest.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtXml.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/QtXmlPatterns.cpython-35m-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/PyQt4/__init__.py
/usr/lib/python3/dist-packages/PyQt4/pyqtconfig.py
/usr/lib/python3/dist-packages/PyQt4/pyqtconfig_nd5.py
/usr/lib/python3/dist-packages/PyQt4/uic
/usr/lib/python3/dist-packages/PyQt4/uic/Compiler
/usr/lib/python3/dist-packages/PyQt4/uic/Compiler/__init__.py
(...)

This bug makes Spyder3 unisable, as it cannot start without QtWebkit module


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (650, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python3-pyqt4 depends on:
ii  libc6  2.22-13
ii  libgcc11:6.1.1-8
ii  libqt4-dbus4:4.8.7+dfsg-8
ii  libqt4-declarative 4:4.8.7+dfsg-8
ii  libqt4-designer4:4.8.7+dfsg-8
ii  libqt4-help4:4.8.7+dfsg-8
ii  libqt4-network 4:4.8.7+dfsg-8
ii  libqt4-script  4:4.8.7+dfsg-8
ii  libqt4-scripttools 4:4.8.7+dfsg-8
ii  libqt4-svg 4:4.8.7+dfsg-8
ii  libqt4-test4:4.8.7+dfsg-8
ii  libqt4-xml 4:4.8.7+dfsg-8
ii  libqt4-xmlpatterns 4:4.8.7+dfsg-8
ii  libqtassistantclient4  4.6.3-7
ii  libqtcore4 4:4.8.7+dfsg-8
ii  libqtgui4  4:4.8.7+dfsg-8
ii  libstdc++6 6.1.1-8
ii  python33.5.1-4
ii  python3-sip [sip-py3api-11.3]  4.18+dfsg-1

python3-pyqt4 recommends no packages.

Versions of packages python3-pyqt4 suggests:
pn  python3-pyqt4-dbg  

-- debconf-show failed

Bug#830901: override: startpar:admin/optional

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

Hi,

startpar is used by sysv-rc to boot a system when using sysvinit.
With systemd as our default init system, having startpar installed by
default is no longer necessary. I would therefor like to see its
priority demoted to optional.

On a system which uses sysvinit-core as init system, the dependency
sysvinit-core->sysv-rc->startpar will ensure it is installed when
actually needed.

Regards,
Michael

Bug#830900: RM: trn/3.6-24

[Matthew Vernon]

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

Hi,

I write as the trn maintainer.

trn has been removed from unstable and testing, because it is insecure
(see #830294 for the insecurity, #830296 for the removal from
unstable/testing).

I think it should also be removed from stable - people can (and
should) use trn4 instead, and in any case trn shouldn't be used with
untrusted input (e.g. usenet).

Thanks,

Matthew

-- System Information:
Debian Release: 7.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Bug#783270: shorewall: Triggers deprecation warning for automatic helper assignment

[Dominic Hargreaves]

On Sat, Jul 02, 2016 at 03:42:54PM -0400, Roberto C. Sánchez wrote:
> On Fri, Apr 24, 2015 at 10:33:11PM +0100, Dominic Hargreaves wrote:
> > Package: shorewall
> > Version: 4.6.4.3-2
> > Severity: normal
> > 
> > [note: I originally sent this on Tuesday but it doesn't seem to have
> > made it to the BTS; apologies if this somehow becomes a duplicate.]
> > 
> > When shorewall loads its rules it triggers the following kernel warning:
> > 
> > [  112.699592] nf_conntrack: automatic helper assignment is deprecated and 
> > it will be removed soon. Use the iptables CT target to attach helpers 
> > instead.
> > 
> > There are no odd rules relating to connection tracking in the shorewall
> > config.
> > 
> Hi Dominic,
> 
> I cannot seem to reproduce this behavior with the information you
> provided.  Could you confirm that you can stil reproduce this and
> perhaps provide your /etc/shorewall directory as a tarball?  Feel free
> to email it to me directly if you don't want to post it in a reply to
> the bug report.

The problem still occurs on systems with a minimimal config - but I don't
have a tarball to hand. The systems are jessie, so perhaps the issue is
fixed in sid (maybe even with a sid kernel the original version of
shorewall?)

Cheers,
Dominic.

Bug#826896: xul-ext-noscript: incompatible with firefox-esr in jessie

[Rebecca N. Palmer]

Is this going to get a stable update (as previously suggested)?

On 11/06/16 08:04, Rebecca N. Palmer wrote:

a no-change rebuild of the sid
(2.9.0.11-1) source in jessie fixes the problem.[...]Such updates have
previously been allowed in stable: see #744730.)

Bug#830899: spell check no longer works

[積丹尼 Dan Jacobson]

Package: midori
Version: 0.5.12~wk2-exp1

Even though it is turned on in preferences,
there is no longer any red lines indicating mispelling,
e.g., when filling out
https://bugs.launchpad.net/midori/+filebug
etc. forms (which do not turn spellcheck off in their HTML.)

Bug#830889: Looks like my patch violates RFC3501

[Nye Liu]

From 6.3.10:

"the STATUS command SHOULD NOT be used on the currently selected  mailbox."

but in theory, the use of STATUS to ask if new mail has arrived is also 
not legal:


"The STATUS command MUST NOT be used as a "check for new
 messages in the selected mailbox" operation (refer to
 sections 7, 7.3.1, and 7.3.2 for more information about
 the proper method for new message checking)."

6.3.10. STATUS Command

   Arguments:  mailbox name
   status data item names

   Responses:  untagged responses: STATUS

   Result: OK - status completed
   NO - status failure: no status for that name
   BAD - command unknown or arguments invalid

  The STATUS command requests the status of the indicated mailbox.
  It does not change the currently selected mailbox, nor does it
  affect the state of any messages in the queried mailbox (in
  particular, STATUS MUST NOT cause messages to lose the \Recent
  flag).

  The STATUS command provides an alternative to opening a second
  IMAP4rev1 connection and doing an EXAMINE command on a mailbox to
  query that mailbox's status without deselecting the current
  mailbox in the first IMAP4rev1 connection.

  Unlike the LIST command, the STATUS command is not guaranteed to
  be fast in its response.  Under certain circumstances, it can be
  quite slow.  In some implementations, the server is obliged to
  open the mailbox read-only internally to obtain certain status
  information.  Also unlike the LIST command, the STATUS command
  does not accept wildcards.

   Note: The STATUS command is intended to access the
   status of mailboxes other than the currently selected
   mailbox.  Because the STATUS command can cause the
   mailbox to be opened internally, and because this
   information is available by other means on the selected
   mailbox, the STATUS command SHOULD NOT be used on the
   currently selected mailbox.

   The STATUS command MUST NOT be used as a "check for new
   messages in the selected mailbox" operation (refer to
   sections 7, 7.3.1, and 7.3.2 for more information about
   the proper method for new message checking).

   Because the STATUS command is not guaranteed to be fast
   in its results, clients SHOULD NOT expect to be able to
   issue many consecutive STATUS commands and obtain
   reasonable performance.

Bug#830569: RFS: z3/4.4.1-0.1 [NMU] [4xRC]

[Gianfranco Costamagna]

Hi (please cc the bug)


>I removed it, but does it do any harm?


no, I guess not
>Might have something to do with -fPIE vs. -fPIC, but one would have to
>investigate further to be sure. This is definitely not a regression,
>though, since the z3 version currently in the archive has no hardening
>flags enabled, either.

you are building a library, so I think you should use PIC for library, and PIE 
for
binary.


>I have reuploaded the fixed version to Mentors:
seems better, but e.g. it lacks of breaks+replaces, because you moved files 
between
the dev package and the new shiny one you introduced
https://wiki.debian.org/PackageTransition

at least I would expect to forward upstream failing tests


--- z3-4.4.0/examples/python/hamiltonian/hamiltonian.py 2015-06-17 
21:48:28.0 +0200
+++ z3-4.4.1/examples/python/hamiltonian/hamiltonian.py 2016-07-10 
00:23:47.0 +0200
@@ -1,5 +1,5 @@

-# Copyright (c) 2012 Ganesh Gopalakrishnan gan...@cs.utah.edu
+# Copyright (c) Microsoft Corporation. All Rights Reserved. 


please fix debian/copyright


other stuff LGTM

G.

Bug#824196: [Pkg-clamav-devel] Bug#824196: Bug#824196: clamav-daemon: clamd crashes daily

[Sebastian Andrzej Siewior]

On 2016-07-12 00:07:34 [+0200], Sebastian Andrzej Siewior wrote:
> I took 2015.NHMU_.AccessionForm_distributed-2.pdf and the
> local-js-sigs.ndb from the archive and could reproduce the bug on 0.99.2
> without any further changes. I applied the patch from upstream's
> bugzilla #11549 and I could not reproduce the issue anymore.

Will: do you want/need prebuild .deb packages for Squeeze?

Sebastian

Bug#686039: KeyError when trying to sync certain folders

[Ryan Kavanagh]

Hi Ilias,

On Thu, May 05, 2016 at 07:16:28PM +0300, Ilias Tsitsimpis wrote:
> I cannot reproduce this problem. Since this is a very old bug report,
> could you please test if this still occurs in the latest version of
> OfflineIMAP (v6.7.0+dfsg1)?

I no longer use offlineimap. Please feel free to close this bug.

Best wishes,
Ryan

-- 
|_)|_/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
| \| \  https://ryanak.ca/ |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#830869: debootstrap: script fails first stage due to missing devices.tar.gz despite no longer being used

[Alex Bennée]

Hi,

Sorry I misfiled this bug against debhelper, this has now been fixed.

In short there seems to be a bunch of cruft associated with the
devices.tar.gz file which used to be used by the second stage to set up
devices in the bootstrapped chroot. This manifests itself if you run the
script from a SCM checkout without first doing a root based build (which
only works on Debian anyway).

In my case I fixed this by simply making cp || true although I guess
there is a bigger argument for properly excising the code as it is now
longer used AFAICT, see the main script:

if true; then
setup_devices_simple
elif [ -e "$DEVICES_TARGZ" ]; then
zcat "$DEVICES_TARGZ" | (cd "$TARGET"; tar -xf -)
else
error 1 NODEVTGZ "no %s. cannot create devices" 
"$DEVICES_TARGZ"
fi

Sorry for the additional bug noise.

--
Alex Bennée

Bug#830898: Please package extensions (like irssi-scripts)

[martin f krafft]

Package: znc
Version: 1.6.2-2
Severity: wishlist

Would you consider packaging up some of the most common extensions
to znc, like znc-extras used to provide? Not sure why that package
was removed…

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

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


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


signature.asc
Description: PGP signature

Bug#830869: [debhelper-devel] Bug#830869: debhelper: script fails first stage due to missing devices.tar.gz despite no longer being used

[Alex Bennée]

Niels Thykier  writes:

> Alex Bennée:
>>
>> Niels Thykier  writes:
>>
>>> Alex Bennée:
 Package: debhelper
 Severity: normal

>>>
>>> Hi Alex,
>>>
>>> I am a bit confused by this bug. Did you perhaps intend to submit it
>>> against debootstrap instead of debhelper?
>>
>> Apologies, completion fail. I was fighting M-x debian-bug which took
>> several attempts to send the email.
>>
>> Yes it should be against debootstrap. Can I reassign it in BTS?
>>
>>>
>>>[...]
>
> Yes you can. :)
>
> Please see [1] for the how to do it.  You may also want to retitle[2]
> the bug while you are at it (as it says debhelper). :)  Finally, you
> should remove the "moreinfo" tag I added.

OK Thanks, I think I have it figured out now. Sorry for the noise on
your list ;-)

--
Alex Bennée

Bug#830896: b2backend: dies with python Unicode error - unicode characters in bucket name

[Graham Cobb]

Package: duplicity
Followup-For: Bug #830896

It turns out that the bucket name I was using on the command line included
Unicode characters: the "-" were actually some Unicode character that looked
like "-" but was not.  This was because I had copied the bucket name off the
backblaze web page after creating it.

While it would be nice if the b2 backend handled Unicode characters (and either
matched or failed instead of giving a python error message), this is
clearly a lower priority problem than I thought.

-- 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/8 CPU cores)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.utf8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages duplicity depends on:
ii  libc62.22-7
ii  librsync10.9.7-10
ii  python   2.7.11-1
ii  python-lockfile  1:0.12.2-1

Versions of packages duplicity recommends:
ii  python-oauthlib  1.0.3-1
ii  python-paramiko  1.16.0-1
ii  python-urllib3   1.13.1-2
ii  rsync3.1.1-3

Versions of packages duplicity suggests:
pn  lftp
pn  ncftp   
ii  python-boto 2.38.0-1
pn  python-cloudfiles   
pn  python-gdata
pn  python-swiftclient  
pn  tahoe-lafs  

-- no debconf information

Bug#830889: wmbiff: Outlook office365 IMAP servers expect EXAMINE before STATUS, or UNSEEN is always reported as 0

[Doug Torrance]

Control: forwarded -1 wmaker-...@lists.windowmaker.org

Thanks for the report!

CC'ing this to the Window Maker dev list.

On 07/12/2016 01:34 PM, Nye Liu wrote:

Package: wmbiff
Version: 0.4.28-2
Severity: important
Tags: upstream patch

Dear Maintainer,

Outlook Office365 IMAP servers now expect a client to issue at least one
EXAMINE before STATUS, or UNSEEN is always zero:

"unsub" folder has two messages, one unseen.

Broken:

56:04.84 > CJFK1 LOGIN "nyet@xxx" "xxx"
56:21.99 < CJFK1 OK LOGIN completed.
56:21.99 > CJFK2 STATUS unsub (MESSAGES UNSEEN)
56:22.20 < * STATUS unsub (MESSAGES 2 UNSEEN 0)
56:22.20 < CJFK2 OK STATUS completed.

Works:

56:46.04 > BPEB1 LOGIN "nyet@xxx" "xxx"
56:51.43 < BPEB1 OK LOGIN completed.
56:51.43 > BPEB2 EXAMINE unsub
56:51.67 < * 2 EXISTS
56:51.67 < * 0 RECENT
56:51.67 < * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
56:51.67 < * OK [PERMANENTFLAGS ()] Permanent flags
56:51.67 < * OK [UNSEEN 2] Is the first unseen message
56:51.67 < * OK [UIDVALIDITY 164] UIDVALIDITY value
56:51.67 < * OK [UIDNEXT 16] The next unique identifier value
56:51.67 < BPEB2 OK [READ-ONLY] EXAMINE completed.
56:51.67 > BPEB3 STATUS unsub (MESSAGES UNSEEN)
56:51.89 < * STATUS unsub (MESSAGES 2 UNSEEN 1)
56:51.89 < BPEB3 OK STATUS completed.

Attached is a patch to always issue EXAMINE before a STATUS.

It doesn't seem like it has to be done before every STATUS, just at least once.
Is only a proof of concept. I don't presume to know the best way to handle
optimizing it.

-- System Information:
Debian Release: stretch/sid
   APT prefers unstable
   APT policy: (500, '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 wmbiff depends on:
ii  libc6  2.23-1
ii  libgcrypt201.7.0-2
ii  libgnutls-deb0-28  3.3.18-1
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxpm41:3.5.11-1+b1
ii  zlib1g 1:1.2.8.dfsg-2+b1

wmbiff recommends no packages.

Versions of packages wmbiff suggests:
ii  ruby 1:2.3.0+4
ii  ssh-askpass  1:1.2.4.1-9

-- no debconf information

Bug#830881: shorewall: fails to upgrade: No such meth

[Dale Schroeder]

On Tue, 12 Jul 2016 13:54:29 -0400 Roberto 
=?iso-8859-1?Q?C=2E_S=E1nchez?=  wrote:


>
> In the meantime, you can remove /lib/systemd/system/shorewall.service
> and then reconfigure the package.
>
> Regards,
>
> -Roberto
>
> --
> Roberto C. Sánchez
> http://people.connexer.com/~roberto
> http://www.connexer.com

After removing shorewall.service, I had no luck with "dpkg-reconfigure 
shorewall"; however, "apt-get -f install" finished the install for me.


Dale

Bug#830857: [Pkg-libvirt-maintainers] Bug#830857: libvirt-daemon: CPU feature cmt not found

[Ansgar Hegerfeld]

Okay, thanks. I opened a bugreport upstream:
https://bugzilla.redhat.com/show_bug.cgi?id=1355857

Best Regards,
Ansgar

Am 12.07.2016 um 19:21 schrieb Guido Günther:
> On Tue, Jul 12, 2016 at 12:13:13PM +0200, Ansgar Hegerfeld wrote:
>> Package: libvirt-daemon
>> Version: 2.0.0-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> after upgrading libvirt-daemon from 1.3.5-1 to 2.0.0-1 I am unable to start
>> a virtual machine which is configured with these CPU settings:
>>
>> 
>>   foobar
>>   05a431db-0927-4ce2-8fb9-2830c962fa2d
>>   1048576
>>   1048576
>>   4
>>   
>> /machine
>>   
>>   
>> hvm
>> 
>>   
>>   
>> 
>> 
>> 
>>   
>>   
>> 
>>   
>> [...]
>>
>> Important is the . With libvirt-daemon 1.3.5-1 this
>> worked just fine but now you receive an error like this after turning a
>> machine (which was live migrated to the updated host) off and on again:
>>
>> "qemu-system-x86_64: CPU feature cmt not found"
> That's kind of expected, see:
>
> http://www.spinics.net/linux/fedora/libvir/msg132822.html
>
> I'd recommend to take this upstream though (since it breaks backward
> compat), since I won't be able to do this for quiet some time.
>
> Cheers,
>  -- Guido

Bug#830881: Debian Bug #830881

[Dale Schroeder]

On Tue, 12 Jul 2016 13:24:44 -0400 Roberto 
=?iso-8859-1?Q?C=2E_S=E1nchez?=  wrote:

> On Tue, Jul 12, 2016 at 12:12:16PM -0500, Dale Schroeder wrote:
> > Shorewall configuration verified
> > Failed to retrieve unit: No such method 'GetUnit'
> > Failed to restart shorewall.service: No such method 'RestartUnit'
> > See system logs and 'systemctl status shorewall.service' for details.
> > shorewall.service couldn't restart.
> > dpkg: error processing package shorewall (--configure):
> > subprocess installed post-installation script returned error exit 
status 1

> > Errors were encountered while processing:
> > shorewall
> >
> Dale,
>
> Could you open up /var/lib/dpkg/info/shorewall.postinst in an editor,
> add "set -x" just below the #! line and then execute it as root?
>
> /var/lib/dpkg/info/shorewall.postinst configure 5.0.10-1
>
> If you could please send back the resulting output, that would be very
> helpful.
>
> Regards,
>
> -Roberto
>
> --
> Roberto C. Sánchez
> http://people.connexer.com/~roberto
> http://www.connexer.com


Here's the output:

+ . /usr/share/debconf/confmodule
+ [ !  ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [  ]
+ exec /usr/share/debconf/frontend ./shorewall.postinst configure 5.0.10-1
+ . /usr/share/debconf/confmodule
+ [ ! 1 ]
+ [ -z  ]
+ exec
+ [  ]
+ exec
+ DEBCONF_REDIR=1
+ export DEBCONF_REDIR
+ db_reset shorewall/dont_restart
+ _db_cmd RESET shorewall/dont_restart
+ _db_internal_IFS= 

+ IFS=
+ printf %s\n RESET shorewall/dont_restart
+ IFS=  

+ IFS=
 read -r _db_internal_line
+ RET=0
+ return 0
+ db_reset shorewall/major_release
+ _db_cmd RESET shorewall/major_release
+ _db_internal_IFS= 

+ IFS=
+ printf %s\n RESET shorewall/major_release
+ IFS=  

+ IFS=
 read -r _db_internal_line
+ RET=0
+ return 0
+ db_go
+ _db_cmd GO
+ _db_internal_IFS= 

+ IFS=
+ printf %s\n GO
+ IFS=  

+ IFS=
 read -r _db_internal_line
+ RET=ok
+ return 0
+ [ ! -d /var/lib/shorewall ]
+ [ -f /var/lib/dpkg/info/shorewall-common.postrm ]
+ restart=true
+ [ -f /etc/default/shorewall ]
+ . /etc/default/shorewall
+ startup=1
+ OPTIONS=
+ STARTOPTIONS=
+ RELOADOPTIONS=
+ RESTARTOPTIONS=
+ INITLOG=/dev/null
+ SAFESTOP=0
+ [ true = true ]
+ [ 1 = 1 ]
+ /sbin/shorewall check
Checking using Shorewall 5.0.10...
Processing /etc/shorewall/params ...
Processing /etc/shorewall/shorewall.conf...
Loading Modules...
Checking /etc/shorewall/zones...
Checking /etc/shorewall/interfaces...
Determining Hosts in Zones...
Locating Action Files...
Checking /etc/shorewall/policy...
Running /etc/shorewall/initdone...
Adding Anti-smurf Rules
Adding rules for DHCP
Checking TCP Flags filtering...
Checking Kernel Route Filtering...
Checking Martian Logging...
Checking /etc/shorewall/masq...
Checking MAC Filtration -- Phase 1...
Checking /etc/shorewall/blrules...
Checking /etc/shorewall/rules...
Checking /etc/shorewall/conntrack...
Checking MAC Filtration -- Phase 2...
Applying Policies...
Checking /usr/share/shorewall/action.Drop for chain Drop...
Checking /usr/share/shorewall/action.Broadcast for chain Broadcast...
Checking /etc/shorewall/stoppedrules...
Shorewall configuration verified
+ [ -x /usr/bin/deb-systemd-invoke ]
+ [ -f /lib/systemd/system/shorewall.service ]
+ deb-systemd-helper enable shorewall.service
/usr/bin/deb-systemd-helper was not called from dpkg. Exiting.

Dale

Bug#830889: [PATCH] wmbiff: EXAMINE before STATUS

[Doug Torrance]

Patch by Nye Liu  to fix Debian bug #830889 [1].

Dear Maintainer,

Outlook Office365 IMAP servers now expect a client to issue at least one
EXAMINE before STATUS, or UNSEEN is always zero:

"unsub" folder has two messages, one unseen.

Broken:

56:04.84 > CJFK1 LOGIN "nyet@xxx" "xxx"
56:21.99 < CJFK1 OK LOGIN completed.
56:21.99 > CJFK2 STATUS unsub (MESSAGES UNSEEN)
56:22.20 < * STATUS unsub (MESSAGES 2 UNSEEN 0)
56:22.20 < CJFK2 OK STATUS completed.

Works:

56:46.04 > BPEB1 LOGIN "nyet@xxx" "xxx"
56:51.43 < BPEB1 OK LOGIN completed.
56:51.43 > BPEB2 EXAMINE unsub
56:51.67 < * 2 EXISTS
56:51.67 < * 0 RECENT
56:51.67 < * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
56:51.67 < * OK [PERMANENTFLAGS ()] Permanent flags
56:51.67 < * OK [UNSEEN 2] Is the first unseen message
56:51.67 < * OK [UIDVALIDITY 164] UIDVALIDITY value
56:51.67 < * OK [UIDNEXT 16] The next unique identifier value
56:51.67 < BPEB2 OK [READ-ONLY] EXAMINE completed.
56:51.67 > BPEB3 STATUS unsub (MESSAGES UNSEEN)
56:51.89 < * STATUS unsub (MESSAGES 2 UNSEEN 1)
56:51.89 < BPEB3 OK STATUS completed.

Attached is a patch to always issue EXAMINE before a STATUS.

It doesn't seem like it has to be done before every STATUS, just at least once.
Is only a proof of concept. I don't presume to know the best way to handle
optimizing it.

[1] https://bugs.debian.org/830889
---
 wmbiff/wmbiff/Imap4Client.c | 9 +
 1 file changed, 9 insertions(+)

diff --git a/wmbiff/wmbiff/Imap4Client.c b/wmbiff/wmbiff/Imap4Client.c
index 8599f5a..882446d 100644
--- a/wmbiff/wmbiff/Imap4Client.c
+++ b/wmbiff/wmbiff/Imap4Client.c
@@ -294,6 +294,7 @@ int imap_checkmail( /*@notnull@ */ Pop3 pc)
/* recover connection state from the cache */
struct connection_state *scs = state_for_pcu(pc);
char buf[BUF_SIZE];
+   char examine_expect[BUF_SIZE];
static int command_id;
 
/* if it's not in the cache, try to open */
@@ -312,6 +313,14 @@ int imap_checkmail( /*@notnull@ */ Pop3 pc)
return -1;
}
 
+   command_id++;
+   tlscomm_printf(scs, "a%03d EXAMINE %s\r\n", command_id, pc->path);
+   snprintf(examine_expect, BUF_SIZE, "a%03d OK", command_id);
+   if (tlscomm_expect(scs, examine_expect, buf, 127) == 0) {
+   tlscomm_close(unbind(scs));
+   return -1;
+   }
+
/* if we've got it by now, try the status query */
command_id++;
tlscomm_printf(scs, "a%03d STATUS %s (MESSAGES UNSEEN)\r\n",
-- 
2.7.4

Bug#830889: Ignore the patch - it doesn't work properly

[Doug Torrance]

On 07/12/2016 02:16 PM, Nye Liu wrote:
Updated patch 

Thanks!  Forwarding upstream.

Bug#830897: Please drop dependency on sysvinit

[Michael Biebl]

Package: init-select
Version: 1.20140921
Severity: important

Hi,

the init-select package has a dependency on "sysvinit".
In Jesse, the "sysvinit" package has been turned into a transitional
package to pull in the new "init" meta-package.
Now that Jessie has been released, the sysvinit package has served its
purpose and we want to remove it.
I would therefor ask you to remove the dependency on sysvinit.

If you are looking for the package shipping the actual /sbin/init
binary, you need "sysvinit-core" instead.

Regards,
Michael

-- 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-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages init-select depends on:
ii  debconf [debconf-2.0]  1.5.59

Versions of packages init-select recommends:
ii  grub-pc  2.02~beta2-36

Versions of packages init-select suggests:
ii  systemd  230-7

Bug#830889: Ignore the patch - it doesn't work properly

[Nye Liu]

Updated patch

--- a/wmbiff/Imap4Client.c
+++ b/wmbiff/Imap4Client.c
@@ -294,6 +294,7 @@
 	/* recover connection state from the cache */
 	struct connection_state *scs = state_for_pcu(pc);
 	char buf[BUF_SIZE];
+	char examine_expect[BUF_SIZE];
 	static int command_id;
 
 	/* if it's not in the cache, try to open */
@@ -312,6 +313,14 @@
 		return -1;
 	}
 
+	command_id++;
+	tlscomm_printf(scs, "a%03d EXAMINE %s\r\n", command_id, pc->path);
+	snprintf(examine_expect, BUF_SIZE, "a%03d OK", command_id);
+	if (tlscomm_expect(scs, examine_expect, buf, 127) == 0) {
+		tlscomm_close(unbind(scs));
+		return -1;
+	}
+
 	/* if we've got it by now, try the status query */
 	command_id++;
 	tlscomm_printf(scs, "a%03d STATUS %s (MESSAGES UNSEEN)\r\n",

Bug#830896: b2backend: dies with python Unicode error

[Graham Cobb]

Package: duplicity
Version: 0.7.07.1-1
Severity: normal

I created a Backblaze B2 Cloud Storage account and tried to use it with
duplicity.  However all duplicity commands using B2 fail for me with the same
error messages:

/usr/lib/python2.7/dist-packages/duplicity/backends/b2backend.py:211: 
UnicodeWarning: Unicode equal comparison failed to convert both arguments to 
Unicode - interpreting them as being unequal
  if bucket_name not in bucket_names:
FatalBackendException: Bucket cannot be created

A simple command to reproduce the problem is:

duplicity collection-status b2://@test?b2backend?grc/

where  is your account ID.  The bucket is public so should be
accessible from any account. Note that this bucket is actually empty but it
cannot be populated because all duplicity commands fail with the same error.


-- 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/8 CPU cores)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.utf8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages duplicity depends on:
ii  libc62.22-7
ii  librsync10.9.7-10
ii  python   2.7.11-1
ii  python-lockfile  1:0.12.2-1

Versions of packages duplicity recommends:
ii  python-oauthlib  1.0.3-1
ii  python-paramiko  1.16.0-1
ii  python-urllib3   1.13.1-2
ii  rsync3.1.1-3

Versions of packages duplicity suggests:
pn  lftp
pn  ncftp   
ii  python-boto 2.38.0-1
pn  python-cloudfiles   
pn  python-gdata
pn  python-swiftclient  
pn  tahoe-lafs  

-- no debconf information

Bug#808433: nethogs STILL crashes in STABLE (Jessie), two months after bug was closed

[S. G.]

Agreed! Thanks for the backports package.

Am Dienstag, den 12.07.2016, 10:14 +0200 schrieb Luca Capello:
> fixed 808433 0.8.1-1~bpo8+1
> user product...@infomaniak.com
> usertag 808433 + infomaniak.com-network
> thanks
> 
> Hi there,
> 
> On Sun, 12 Jun 2016 10:01:20 +0200, S. G. wrote:
> > I'm desparately waiting to see this fix in jessie.
> > 
> > Is there a schedule for patching 0.8.0?
> 
> No need for a jessie-pu, the problem is fixed for us using the
> jessie-backports package (bug updated).
> 
> Thx, bye,
> Gismo / Luca
> 

Bug#830869: [debhelper-devel] Bug#830869: debhelper: script fails first stage due to missing devices.tar.gz despite no longer being used

[Niels Thykier]

Alex Bennée:
> 
> Niels Thykier  writes:
> 
>> Alex Bennée:
>>> Package: debhelper
>>> Severity: normal
>>>
>>
>> Hi Alex,
>>
>> I am a bit confused by this bug. Did you perhaps intend to submit it
>> against debootstrap instead of debhelper?
> 
> Apologies, completion fail. I was fighting M-x debian-bug which took
> several attempts to send the email.
> 
> Yes it should be against debootstrap. Can I reassign it in BTS?
> 
>>
>>[...]

Yes you can. :)

Please see [1] for the how to do it.  You may also want to retitle[2]
the bug while you are at it (as it says debhelper). :)  Finally, you
should remove the "moreinfo" tag I added.
  Do keep in mind that the maintainers will just see the reassign, but
*not* anything useful beyond that.  I would personally recommend that
you CC the debootstrap maintainers (debian-b...@lists.debian.org) on the
bug with a summary of the bug information, so they know what the bug is
about (or resend the original mail to the above list).

If you have issues with the reassign/retitle/tagging, then let me know
and I will gladly help you out. :)

~Niels

[1] https://www.debian.org/Bugs/server-control

[2] Same URL, but caveat: The retitle command easily break if you mail
agent wraps long lines for you!

Bug#830895: override: sysv-rc:admin/optional

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

Hi,

please consider lowering the priority of sysv-rc from required to
optional. It's no longer needed on a system with systemd as init system.

The sysvinit-core package has explicit dependencies on initscripts and
sysv-rc, making sure that those packages are pulled in if an
alternative init system is used.

Regards,
Michael

Bug#830894: override: initscripts:admin/optional

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

Hi,

on a Debian stretch/unstable system using systemd as init system, the
initscripts package is no longer required. We asked all packages with
explicit dependencies to remove it and it is now possible to uninstall
initscripts without any ill side-effects.
update-rc.d has been updated to cope with the fact that the facilities
defined by initscripts do not exist.
It is therefor safe to no longer install the initscripts package by
default.

Please lower the priority of initscripts accordingly.

Regards,
Michael


[1] 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintain...@lists.alioth.debian.org;tag=initscripts-dep