Bug#816517: ulem.sty from texlive-generic- recommended

[Norbert Preining]

Hi all,

> or wait until I have uploaded the new package.

Which has happened just now, so should be available in a day.
Simply closing the FTBFS after a pbuilder/cowbuilder check should
suffice. No need for new uploads.

Or you reassign to texlive-htmlxml and merge with the closed bug
816584 where exactly this probelms was described and explained.

Thanks

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#817263: [debian-mysql] Bug#817263: Removed package(s) from unstable

[Adam D. Barratt]

On 2016-03-10 7:02, Otto Kekäläinen wrote:
2016-03-10 0:13 GMT+02:00 Debian FTP Masters 
:

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable: mariadb-10.0


Oh crap. Now all of our build logs (very important to debug various
build/testsuite failures and their occurences on different platforms)
have been lost,


https://buildd.debian.org/status/logs.php?pkg=mariadb-10.0 doesn't look 
very lost (one click away from 
https://buildd.debian.org/status/package.php?p=mariadb-10.0)



also all bugs have been lost etc..


No, they're not. Worst case you need to re-open them. Please be less 
melodramatic.


Regards,

Adam

Bug#817782: apticron: Anacron job 'cron.daily' error downloading files

[Norbert Schulz]

Package: apticron
Version: 1.1.42
Severity: normal


Since some days files for updating the system are not found:

/etc/cron.daily/apticron:
W: error downloading  http://http.debian.net/debian/dists/squeeze-lts/Release  
Unable to find expected entry  main/binary-amd64/Packages in Meta-index file 
(malformed Release file?)

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze/main/source/Sources.gz  404  Not 
Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze/contrib/source/Sources.gz  404  
Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze/non-free/source/Sources.gz  404  
Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze/main/binary-amd64/Packages.gz  
404  Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze/contrib/binary-amd64/Packages.gz  
404  Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze/non-free/binary-amd64/Packages.gz 
 404  Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze-updates/main/source/Sources.gz  
404  Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze-updates/contrib/source/Sources.gz 
 404  Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze-updates/non-free/source/Sources.gz
  404  Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze-updates/main/binary-amd64/Packages.gz
  404  Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze-updates/contrib/binary-amd64/Packages.gz
  404  Not Found

W: error downloading 
http://ftp.de.debian.org/debian/dists/squeeze-updates/non-free/binary-amd64/Packages.gz
  404  Not Found

some index files could not be downloaded, ...


Norbert




-- System Information:
Debian Release: 6.0.10
  APT prefers squeeze-lts
  APT policy: (500, 'squeeze-lts'), (500, 'oldoldstable-updates'), (500, 
'oldoldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apticron depends on:
ii  apt 0.8.10.3+squeeze7Advanced front-end for dpkg
ii  bsd-mailx [ 8.1.2-0.20100314cvs-1+deb6u1 simple mail user agent
ii  cron3.0pl1-116   process scheduling daemon
ii  debconf [de 1.5.36.1 Debian configuration management sy
ii  ucf 3.0025+nmu1  Update Configuration File: preserv

Versions of packages apticron recommends:
ii  apt-listchanges  2.85.7+squeeze1 package change history notificatio
ii  iproute  20100519-3  networking and traffic control too

apticron suggests no packages.

-- debconf information:
  apticron/notification: root

Bug#816924: GNU GLOBAL 6.5.2 available

[Alberto Luaces]

Hi Wei,

I am also interested in having the latest version of GNU GLOBAL.  Do you
have any references about the technical disagreement between this
package and upstream?

I am not referring to all the ancient mails you mentioned, just a little
pointer in order to see if it could be maybe possible to have an
alternate package of GNU GLOBAL which can add the recent improvements,
and let the users decide in an individual basis which one fits best
their needs.

Regards.

Bug#817783: chromium: IPv6 broken?

[clayton]

Package: chromium
Version: 49.0.2623.75-2
Severity: normal

I am using miredo to provide basic IPv6 connectivity on my desktop for testing,
it is point-and-shoot: just install it and turn on the daemon. Then:

ping6 ipv6.google.com works fine.

Firefox and w3m work fine on http://v6.testmyipv6.com/

But if I direct chromium to the same link, I get:

This site can’t be reached
v6.testmyipv6.com’s server DNS address could not be found.
DNS_PROBE_FINISHED_BAD_CONFIG

even if I start this way: chromium --enable-ipv6

However, dig works fine on the same machine:

$ dig v6.testmyipv6.com 
;; ANSWER SECTION:
v6.testmyipv6.com.  1186IN  2001:4830:2502:8001::a00:a

It looks to me like my machine is handling IPv6 alright, but Chromium is not.

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

Kernel: Linux 4.3.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 chromium depends on:
ii  libasound21.1.0-1
ii  libatk1.0-0   2.18.0-1
ii  libavcodec-ffmpeg56   7:2.8.6-1+b1
ii  libavformat-ffmpeg56  7:2.8.6-1+b1
ii  libavutil-ffmpeg547:2.8.6-1+b1
ii  libc6 2.21-9
ii  libcairo2 1.14.6-1
ii  libcups2  2.1.3-3
ii  libdbus-1-3   1.10.6-1
ii  libexpat1 2.1.0-7
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6.3-3
ii  libgcc1   1:5.3.1-10
ii  libgdk-pixbuf2.0-02.32.3-1.2
ii  libglib2.0-0  2.46.2-3
ii  libgnome-keyring0 3.12.0-1+b1
ii  libgtk2.0-0   2.24.29-1
ii  libjpeg62-turbo   1:1.4.2-2
ii  libnspr4  2:4.11-1
ii  libnss3   2:3.21-1.1
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpci3   1:3.3.1-1.1
ii  libspeechd2   0.8-7
ii  libsrtp0  1.4.5~20130609~dfsg-1.1
ii  libstdc++65.3.1-10
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxi62:1.7.6-1
ii  libxml2   2.9.3+dfsg1-1
ii  libxrandr22:1.5.0-1
ii  libxrender1   1:0.9.9-2
ii  libxslt1.11.1.28-2.1
ii  libxss1   1:1.2.2-1
ii  libxtst6  2:1.2.2-1+b1
ii  x11-utils 7.7+3
ii  xdg-utils 1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1.07.4-1

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#817263: [debian-mysql] Bug#817263: Removed package(s) from unstable

[Otto Kekäläinen]

Hello!

2016-03-10 10:22 GMT+02:00 Adam D. Barratt :
>> Oh crap. Now all of our build logs (very important to debug various
>> build/testsuite failures and their occurences on different platforms)
>> have been lost,
>
>
> https://buildd.debian.org/status/logs.php?pkg=mariadb-10.0 doesn't look very
> lost (one click away from
> https://buildd.debian.org/status/package.php?p=mariadb-10.0)

Thanks for pointing that out. I only looked at
https://buildd.debian.org/status/package.php?p=mariadb-10.0 which was
empty.

>> also all bugs have been lost etc..
>
>
> No, they're not. Worst case you need to re-open them. Please be less
> melodramatic.

Yes, it seems they are still there but in closed state:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb-10.0

There is still quite a lot of extra work to do here to recover, as I
need to check everything that is stored externally from the package
(bugs, debtags etc) and asses what needs to be recovered and then
execute the recovery. Some melodramatism is surely justified :)

Bug#815919: nmu: tesseract_3.04.01-3 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-1 sikuli_1.0~x~rc3.tesseract3-dfsg1-12

[Philip Rinn]

Hi,

On Wed, 9 Mar 2016 19:57:45 +0100 Andreas Beckmann  wrote:
> Control: retitle -1 nmu: gimagereader_3.1.2+git368fa8f-2 
> sikuli_1.0~x~rc3.tesseract3-dfsg1-12
> 
> On Thu, 25 Feb 2016 18:50:49 +0100 Andreas Beckmann  wrote:
> > The ABI change has been reverted and the transition to
> > libtesseract4 has to be undone (#815056).
> 
> tesseract and openalpr had source uploads. gimagereader, too, but
> picked up the old lib on hurd. So this leaves us with

True, but also picked -3 on all other archs which breaks ABI, -4 restores the 
old
ABI so we really need to rebuild an all archs, that why #816857 happened.

nmu gimagereader_3.1.2+git368fa8f-2 . ANY . unstable . -m "Rebuild against
libtesseract3."

Best,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#807996: apt: "apt-get update" gives 'repository cdrom://... does not have a Release file' warning

[Igor Liferenko]

In apt-secure(8) manpage it is said that there must be Release.gpg or
InRelease in addition to Release.

Is there a way to disable this warning? Maybe this Release.gpg or
InRelease should be provided by default on official iso image, because
it is already verified by checksum?

Bug#815888: nvidia-detect: GF119M [GeForce 610M] nvidia-detect=ok for nvidia-driver . . . not ok

[Luca Boccassi]

On Mar 9, 2016 14:29, "Fulano Diego Perez" 
wrote:
>
>
>
> Luca Boccassi:
> > On 9 March 2016 at 13:42, Fulano Diego Perez 
wrote:
> >>
> >>
> >> Luca Boccassi:
> >>> On 9 March 2016 at 11:49, Fulano Diego Perez <
fulanope...@cryptolab.net> wrote:
>  hi luca,
> 
>  Luca Boccassi:
> > On 9 March 2016 at 10:05, Fulano Diego Perez <
fulanope...@cryptolab.net> wrote:
> >> hi luca
> >>
> >> Luca Boccassi:
> >>> Control: package -1 nvidia-driver
> >>> Control: tag -1 moreinfo
> >>> Control: severity -1 normal
> >>>
> >>> On Thu, 2016-02-25 at 23:34 +1100, Fulano Diego Perez wrote:
>  Package: nvidia-detect
>  Severity: grave
>  Justification: renders package unusable
> 
> 
>  _disclaimer_
> 
>  1.
>  i do not know if the problem lies with nvidia-detect,
nvidia-driver and its
>  dependencies, or neither
> 
>  2.
>  this bug report was submitted after removal and revert back to
nouveau
> 
>  3.
>  applies to intel ivy bridge chipset with built-in intel graphics
+
>  nvidia below
> 
> 
> 
>  nvidia-detect recommends nvidia-driver
> 
>  i then install nvidia-driver, its dependencies and nvidia-xconfig
> 
>  NB i attempted this ~6 months ago and yesterday, i do not know
the affect of
>  the recent nvidia updates to xserver and whether nvidia-xconfig
is still
>  necessary
> 
>  gdm3 cannot proceed after reboot
> 
>  please advise any further log provision where necessary:
> >>>
> >>> Hi,
> >>>
> >>> It looks like you have a laptop with a switchable Optimus system
(610M).
> >>> If that's indeed the case, you cannot just install the nvidia
stack, as
> >>> your hardware is wired to use the Intel card to drive the display.
> >>>
> >>> If you want to use the discrete Nvidia card, you must do so
through
> >>> bumblebee. Please install
> >>>
> >>> bumblebee-nvidia
> >>>
> >>> Then run:
> >>>
> >>> sudo update-glx --config glx
> >>>
> >>> And make sure nvidia/bumblebee is selected, if not pick it.
> >>
> >> done above
> >>
> >>>
> >>> If the problem persists, please add more information by running:
> >>>
> >>> reportbug -N 815888
> >>
> >> sorry, this is out ATM, nevertheless...
> >>
> >>> Kind regards,
> >>> Luca Boccassi
> >>
> >> i get the following:
> >>
> >> $ primusrun glxgears
> >> primus: fatal: Bumblebee daemon reported: error: [XORG] (EE)
> >>
> >> $ optirun glxgears
> >> [23162.070642] [ERROR]Cannot access secondary GPU - error: [XORG]
(EE)
> >>
> >> ive tried various basic amendments such as
> >>
> >> adding my user to the bumblebee group;
> >>
> >> manually specifying the nvidia option in
/etc/bumblebee/bumblebee.conf;
> >>
> >> manually specifying BusID "PCI:1:0:0" in
/etc/bumblebee/xorg.conf.nvidia
> >> (from the github FAQ)
> >>
> >> $ lspci | egrep 'VGA|3D'
> >> 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
> >> processor Graphics Controller (rev 09)
> >> 01:00.0 VGA compatible controller: NVIDIA Corporation GF119M
[GeForce
> >> 610M] (rev a1)
> >>
> >> i admit im stuck
> >
> > Hi,
> >
> > Sorry for your troubles.
> >
> > Unfortunately there's not much I can do without looking at the full
> > system report. If reportbug -N is not working for you, could you
> > please manually attach the output of:
> 
>  sure makes sense
> 
> > reportbug --template nvidia-driver
> 
>  i enclose
> 
>  thanks for your help
> >>>
> >>> Hi,
> >>>
> >>> >From the log, it looks like nouveau is being loaded:
> >>>
> >>> 2367.838] (II) LoadModule: "nouveau"
> >>> [  2367.838] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
> >>> [  2367.838] (II) Module nouveau: vendor="X.Org Foundation"
> >>> [  2367.838] compiled for 1.18.0, module version = 1.0.12
> >>> [  2367.838] Module class: X.Org Video Driver
> >>> [  2367.838] ABI class: X.Org Video Driver, version 20.0
> >>>
> >>> 
> >>>
> >>> [  2367.839] (II) NOUVEAU driver Date:   Tue Dec 8 15:52:25 2015 +1000
> >>> [  2367.839] (II) NOUVEAU driver for NVIDIA chipset families :
> >>> [  2367.839] RIVA TNT(NV04)
> >>> [  2367.839] RIVA TNT2   (NV05)
> >>> [  2367.840] GeForce 256 (NV10)
> >>> [  2367.840] GeForce 2   (NV11, NV15)
> >>> [  2367.840] GeForce 4MX (NV17, NV18)
> >>> [  2367.840] GeForce 3   (NV20)
> >>> [  2367.840] GeForce 4Ti (NV25, NV28)
> >>> [  2367.840] GeForce FX  (NV3x)
> >>> [  2367.840] GeForce 6   (NV4x)
> >>> [  2367.840] GeForce 7   (G7x)
> >>> [  2367.840] GeForce 8   (G8x)
> >>> [  2367.840] GeForce GTX 200 (NVA0)
> >>>

Bug#817139: [Pkg-sass-devel] Bug#817139: sassc: trying to overwrite '/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1

[Frederic Bonnard]

On Wed, 09 Mar 2016 17:27:35 +0100, Jonas Smedegaard  wrote:
> 
> Hi Frederic,
> 
> Quoting Frederic Bonnard (2016-03-09 15:36:53)
> >> The name "sassc" means "Sass implemented in C".
> >>
> >> Since the package name "pysassc" seems to imply "sassc wrapper 
> >> implemented in Python", I believe the proper fix here is for pysassc 
> >> to not provide binary "sassc" but instead "pysassc".
> >
> > right
> >
> >> ...or simply drop the package pysassc, because there should be no 
> >> need for that wrapper on systems where the real sassc is available.
> >
> > sure ; but I'd prefer to let users choose.
> >
> > Actually one of the project I use, needed as a build-dep sassc from 
> > python-libsass, because as many python projects they drag build-deps 
> > with pip and don't bother with original C projects with native tools.
> 
> pip means sidestepping Debian packaging, and is therefore irrelevant for 
> Debian packaging.
> 
> 
> > And the latter has specific options also, different from the one from 
> > sassc package with is embarassing for dependant projects.
> 
> Varying options is a real pain, however.
> 
> 
> > I see 3 possibilities :
> > - we remove sassc from python-libsass but we'll have to do something 
> >   for projects using it as build-deps.
> > - we rename sassc in python-libsass pysassc, same point.
> >   In both last 2 points, we could see with upstream libsass-python if 
> >   they can do the same on python sassc script to prevent more deb/ 
> >   work to patch other projects depending in python sassc, but it's 
> >   unsure they'll follow.
> > - or I put in python-libsass's control an exclude with sassc
> > 
> > Last point would be the least work solution on all sides, and that'd 
> > be up to users to choose if they want the "real" sassc or the pythonic 
> > one. Any thoughts ?
> 
> If by last option you mean mark the package as conflicting with sassc, 
> then that is a bad approach, as that makes it impossible to use sassc 
> for some things and the Python flavor for other things - on same system.

Indeed, that is restrictive.

> I recommend option 2 (rename binary).  And I recommend to get in touch 
> with upstream and recommend them to do the same, to avoid confusion over 
> two implementations with same name having different options.
> 
> As _extension_ to option 2 - you could document in README.Debian for 
> your package how the local admin can locally register that binary as an 
> alternative to sassc.  I feel it is bad for the package to do so, 
> however, due to those varying options (unless it is a strict superset of 
> the options of sassc).  You could contact upstream and try convince them 
> to coordinate aligning options with sassc authors, and when aligned the 
> package could register as alternative.

Perfect, I'm going to talk to upstream libsass-python.
Thanks a lot Jonas for helping,

F.

Bug#817277: phantomjs: PhantomJS fails to run headless

[Stéphane Railhet]

Thanks about this explanation, hope this will be solved by upstream in 
future releases.


Best Regards,

Stéphane Railhet

On Wednesday, 9 March 2016 6:35:08 PM AEDT Stéphane Railhet wrote:

PhantomJS cannot run if there is no X server available whereas it should be
able to work headless since version 1.5.

Unfortunately it can not be fixed in Debian. To achieve headless-ness
upstream statically link with customised QT + Webkit. We don't want to ship
forks of those projects. It would be great to eventually convince upstream to
use standard libraries.

Meanwhile you can use "xvfb-run" from "xvfb" package.

I'll update README.Debian to include a note about that.

Bug#810968: [debian-mysql] Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

[Sergey Vojtovich]

FYI: applied to MariaDB 10.0 
https://github.com/MariaDB/server/commit/8942824a5304e23f765b88d07498786d80092843

Bug#817784: xserver-xorg-video-intel: gnome dont load after xserver-xorg-video-intel upgrade

[Mario Geiger]

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20160218-1
Severity: important

Dear Maintainer,

After upgrade xserver-xorg-video-intel to version 2:2.99.917+git20160307-1 
(with sudo apt-get upgrade)
gdm3 load but after typing my password gnome dont load.

After downgrade package to version 2:2.99.917+git20160218-1 it works again. 
(changed source.list to stretch and run sudo apt-get install 
xserver-xorg-video-intel=2:2.99.917+git20160218-1).

I have a thinkpad X1 Yoga with processor i7-6500U and there is already problem 
in linux related to it, see 
https://bugzilla.kernel.org/show_bug.cgi?id=110941

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Feb 26 21:58 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Feb  9 12:12 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated 
Graphics [8086:1916] (rev 07)

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

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

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

Kernel version (/proc/version):
---
Linux version 4.4.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160224 (Debian 5.3.1-10) ) #1 SMP Debian 4.4.4-2 (2016-03-09)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 33982 Feb 27 11:15 /var/log/Xorg.1.log
-rw-r--r-- 1 root root  4644 Mar 10 09:30 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[10.142] (--) Log file renamed from "/var/log/Xorg.pid-.log" to 
"/var/log/Xorg.0.log"
[10.142] 
X.Org X Server 1.18.1
Release Date: 2016-02-08
[10.142] X Protocol Version 11, Revision 0
[10.142] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[10.142] Current Operating System: Linux x1yoga 4.4.0-1-amd64 #1 SMP Debian 
4.4.4-2 (2016-03-09) x86_64
[10.142] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-1-amd64 
root=UUID=60bf5148-49fb-4392-a79c-3ff7993ed683 ro intel_pstate=no_hwp quiet
[10.143] Build Date: 09 February 2016  11:06:03AM
[10.143] xorg-server 2:1.18.1-1 (http://www.debian.org/support) 
[10.143] Current version of pixman: 0.33.6
[10.143]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[10.143] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[10.143] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar 10 09:30:20 
2016
[10.143] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[10.143] (==) No Layout section.  Using the first Screen section.
[10.143] (==) No screen section available. Using defaults.
[10.143] (**) |-->Screen "Default Screen Section" (0)
[10.143] (**) |   |-->Monitor ""
[10.143] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[10.143] (**) |   |-->Device "Intel Graphics"
[10.143] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[10.143] (==) Automatically adding devices
[10.143] (==) Automatically enabling devices
[10.143] (==) Automatically adding GPU devices
[10.143] (==) Max clients allowed: 256, resource mask: 0x1f
[10.143] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[10.143]Entry deleted from font path.
[10.143] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[10.143] (==) ModulePath set to "/usr/lib/xorg/modules"
[10.143] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[10.143] (II) Loader magic: 0x564321433dc0
[10.143] (II) Module ABI versions:
[10.143]X.Org ANSI C Emulation: 0.4
[10.143]X.Org Video Driver: 20.0
[10.143]X.Org XInput driver : 22.1
[10.143]X.Org Server Extension : 9.0
[10.143] (++) using VT number 7

[10.143] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[10.144] (II) xfree86: Adding drm device (/dev/dri/card0)
[10.145] (--) PCI:*(0:0:2:0) 8086:1916:17aa:2238 rev 7, Mem @ 
0xe000/16777216, 0xc000/536870912, I/O @ 0xe000/64
[10.146] (II) LoadModule: "glx"
[10.146] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[10.146] (II)

Bug#815919: nmu: tesseract_3.04.01-3 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-1 sikuli_1.0~x~rc3.tesseract3-dfsg1-12

[Emilio Pozuelo Monfort]

On 10/03/16 10:00, Philip Rinn wrote:

Hi,

On Wed, 9 Mar 2016 19:57:45 +0100 Andreas Beckmann  wrote:

Control: retitle -1 nmu: gimagereader_3.1.2+git368fa8f-2 
sikuli_1.0~x~rc3.tesseract3-dfsg1-12

On Thu, 25 Feb 2016 18:50:49 +0100 Andreas Beckmann  wrote:

The ABI change has been reverted and the transition to
libtesseract4 has to be undone (#815056).


tesseract and openalpr had source uploads. gimagereader, too, but
picked up the old lib on hurd. So this leaves us with


True, but also picked -3 on all other archs which breaks ABI, -4 restores the 
old
ABI so we really need to rebuild an all archs, that why #816857 happened.

nmu gimagereader_3.1.2+git368fa8f-2 . ANY . unstable . -m "Rebuild against
libtesseract3."


Scheduled.

Emilio

Bug#817149: [INTL:it] updated Italian postfix's debconf translation [Forgotten a

[Dario]

Package: postfix
Version: 3.0.4-3
Tags: l10n, patch
Severity: wishlist
X-Debbugs-CC: debian-l10n-ital...@lists.debian.org


forgotten attachment,
sorry.

Best regards,
Dario


it.po.gz
Description: application/gzip

Bug#691487: bsdmainutils: Segfault, easy to reproduce

[Michael Meskes]

On Thu, Mar 10, 2016 at 07:39:04AM +0100, Philipp Marek wrote:
> Well, it only got easier - just start it:
> 
> $ column
> Speicherzugriffsfehler
> ...

Let me guess, you've set ulimits on the process? column needs quite a bit of
heap space for statically allocated buffers. Yes, it'd be nice if it was
patched to use malloc, but the segfault is not really columns fault in this 
case.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#691487: bsdmainutils: Segfault, easy to reproduce

[Philipp Marek]

> > Well, it only got easier - just start it:
> > 
> > $ column
> > Speicherzugriffsfehler
> > ...
> 
> Let me guess, you've set ulimits on the process? column needs quite a bit of
> heap space for statically allocated buffers. Yes, it'd be nice if it was
> patched to use malloc, but the segfault is not really columns fault in this 
> case.
Yeah, right!

Thanks for the tip... somewhere between "ulimit -s4100" and "ulimit -s4200" 
there's the limit for being able to start column.


Well, whose fault would it be? My default is 1M stack size, and all other 
programs seem to be fine with that...


Thank you very much, and sorry for the noise.

Bug#817785: libqglviewer2: libs built against qt5 should have -qt5 appended

[Václav Šmilauer]

Package: libqglviewer2
Version: 2.6.3+dfsg1-1
Severity: normal

Dear Maintainer(s),

the current state of QGLViewer is that the version linking against qt5 is
called libQGLViewer while the older version linking against qt4 is called
libQGLViewer-qt4. While this is a fair short-term solution, it has some
shortcomings.

In particular, to support multiple Debian versions, one has to check whether
QGLViewer links against qt4 (older versions) or qt5 (newer version). Second,
when qt6 comes, what will happen?

Following the principle that "explicit is better than implicit", I'd be for
appending "-qt5" to the package name (libqglviewer2-qt5, libqglviewer2-qt5-dev)
and also the the library name (libQGLViewer-qt5.so) so that those are
unambiguous.

As side-effect, this might remove the highly undesirable conflict between
libglviewer-qt4-dev and libqtglviewer-dev. Just like I need both Qt4 and Qt5
dev files installed, I would like to install headers for both version of
QGLViewer and there is no reason why this should not be supported.

Best regards,

Václav



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

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

Versions of packages libqglviewer2 depends on:
ii  libc6 2.21-0ubuntu6
ii  libgcc1   1:6-20160227-0ubuntu1
ii  libgl1-mesa-glx [libgl1]  11.1.2-1ubuntu1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libqt5core5a  5.5.1+dfsg-15ubuntu1
ii  libqt5gui55.5.1+dfsg-15ubuntu1
ii  libqt5opengl5 5.5.1+dfsg-15ubuntu1
ii  libqt5widgets55.5.1+dfsg-15ubuntu1
ii  libqt5xml55.5.1+dfsg-15ubuntu1
ii  libstdc++65.3.1-10ubuntu2

libqglviewer2 recommends no packages.

libqglviewer2 suggests no packages.

-- no debconf information

Bug#806082: multipath-tools: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Hello.

Sorry for the reopening, but this bug is still present in version 
0.5.0+git1.656f8865-5.

This is the way it fails now:


 debian/rules build-indep
make: Nothing to be done for 'build-indep'.
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
dh_prep
dh_installdirs
# initramfs stuff:
install -D -m 755 debian/initramfs/hooks 
/<>/multipath-tools-0.5.0+git1.656f8865/debian/multipath-tools-boot/usr/share/initramfs-tools//hooks/multipath
install -D -m 755 debian/initramfs/local-top \

/<>/multipath-tools-0.5.0+git1.656f8865/debian/multipath-tools-boot/usr/share/initramfs-tools//scripts/local-top/multipath
install -D -m 755 debian/initramfs/init-top \

/<>/multipath-tools-0.5.0+git1.656f8865/debian/multipath-tools-boot/usr/share/initramfs-tools//scripts/init-top/multipath
# reportbug:
for pkg in "multipath-tools" "multipath-tools-boot"; do \
install -D -m 755 debian/reportbug/script 
debian/${pkg}/usr/share/bug/${pkg}/script; \
done
 dpkg-genchanges -A >../multipath-tools_0.5.0+git1.656f8865-5_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


I can diagnose this for you: This is what I found in debian/rules:

binary-indep: build-indep install-indep

but the target is empty otherwise.

Since there is no dh_builddeb anywhere in such target, no architecture
independent .deb is created at all.

Please do actually try "dpkg-buildpackage -A" before considering this
fixed, you don't need any special tools for that, nor you need anybody
else to do it for you.

Thanks.

Bug#556953: Missing ioctl

[Dmitry Eremin-Solenikov]

reassign 556953 linux-image-2.6.32-5-amd64
thanks

This bug is indeed a bad interaction of amd64 kernel and 32-bit userspace.
It was fixed in mainline kernel, version 2.6.37 by the commit
a254dba37c5a372fc8b44ba29509ba052d4e859d


-- 
With best wishes
Dmitry

Bug#817786: One of vars comment needs to be upgraded

[Jean-Michel Vourgère]

Package: easy-rsa
Version: 2.2.2-1
Severity: minor

Hi

vars file contains:
# Increase this to 2048 if you
# are paranoid.  This will slow
# down TLS negotiation performance
# as well as the one-time DH parms
# generation process.
export KEY_SIZE=2048

I suggest the comment to be upraded to 4096, especially since the
README.Debian points at such set up.

Thank you for taking care of easy-rsa

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

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

Versions of packages easy-rsa depends on:
ii  openssl  1.0.1k-3+deb8u4

Versions of packages easy-rsa recommends:
ii  opensc  0.14.0-2

easy-rsa suggests no packages.

-- no debconf information

Bug#780940: hdparm freezes the system's start up

[Raphael Hertzog]

On Wed, 09 Mar 2016, Alex Mestiashvili wrote:
> Placing a binary package to a non-debian site doesn't sound good to me.
> I personally wouldn't install it.
> The current packaging status is definitely good for the experimental
> or even for unstable in my opinion.
> Shell I open RFS bug for that ?

I can do the upload but I would like to see a fix for the only RC bug left
(#725284).

I believe I gave you some indications in my last review mail. Dropping the
init script would fix this bug too as without any init script, the startup
can't be frozen... (except if the udev script can have a similar effect, I
don't know).

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#817787: slim: leaks open file descriptor

[Nicolas Schier]

Package: slim
Version: 1.3.6-4
Severity: normal


Dear Maintainer,

slim leaks a read-write open file descriptor (/var/log/slim.log) to
child processes.  I discovered it by running 'pvcreate':

nicolas@deb:~$ pvcreate
File descriptor 3 (/var/log/slim.log) leaked on pvcreate invocation. 
Parent PID 4446: bash


Thus, also my window-manager (i3) and all bashs started within to have
this descriptor open; modification is easily possible:

nicolas@deb:~$ readlink -v /proc/$(pidof i3)/fd/3
/var/log/slim.log
nicolas@deb:~$ pidof bash | tr " " "\n" | xargs -n1 -IPID readlink 
/proc/PID/fd/3
/var/log/slim.log
/var/log/slim.log
/var/log/slim.log
/var/log/slim.log
nicolas@deb:~$ echo bla >&3
nicolas@deb:~$ cp /proc/$$/fd/3 /tmp/fd3 && cat /tmp/fd3

slim: waiting for X server to shut down.



slim: waiting for X server to begin accepting connections.

slim: waiting for X server to shut down



slim: waiting for X server to begin accepting connections.
..
bla
nicolas@deb:~$ 


Kind regards,
Nicolas



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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=nb:nn:dk:se:de:en:C, LC_CTYPE=nb:nn:dk:se:de:en:C (charmap=UTF-8) 
(ignored: LC_ALL set to nb_NO.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages slim depends on:
ii  dbus   1.10.6-1
ii  debconf [debconf-2.0]  1.5.58
ii  libc6  2.21-9
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.3-3
ii  libgcc11:5.3.1-10
ii  libjpeg62-turbo1:1.4.2-2
ii  libpam0g   1.1.8-3.2
ii  libpng12-0 1.2.54-4
ii  libstdc++6 5.3.1-10
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxft22.3.2-1
ii  libxmu62:1.1.2-2
ii  libxrandr2 2:1.5.0-1
ii  libxrender11:0.9.9-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages slim recommends:
ii  xterm  322-1

Versions of packages slim suggests:
ii  scrot  0.8-17
ii  xauth  1:1.0.9-1

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

-- debconf information excluded

-- 
Nicolas Schier
Tel: +49 30 39976-790
Fax: +49 30 39976-255
Mail: n.sch...@avm.de
https://avm.de/
 
AVM Audiovisuelles Marketing und Computersysteme GmbH, Alt-Moabit 95, 10559 
Berlin
HRB 23075 AG Charlottenburg, Geschäftsführer: Johannes Nill


signature.asc
Description: Digital signature

Bug#817240: mirrors: errors with ftp.fr.debian.org

[Peter Palfrader]

reassign 817240 apt
thanks

On Wed, 09 Mar 2016, Vincent Lefevre wrote:

> # apt-get update
> [...]
> Err:24 http://ftp.fr.debian.org/debian unstable/main amd64 DEP-11 Metadata
>  
>   Hash Sum mismatch
> [...]
> Err:31 http://ftp.fr.debian.org/debian unstable/main DEP-11 64x64 Icons   
>  
>   Hash Sum mismatch
> [...]
> Err:37 http://ftp.fr.debian.org/debian unstable/non-free amd64 DEP-11 Metadata
>   Hash Sum mismatch
> [...]
> Err:38 http://ftp.fr.debian.org/debian unstable/non-free DEP-11 64x64 Icons
>   Hash Sum mismatch
> Get:39 http://ftp.fr.debian.org/debian unstable/main Sources 
> 2016-03-07-1455.48.pdiff [18.7 kB]
> 24% [39 Sources 14.2 kB/18.7 kB 76%]E: Unpatched file  doesn't exist 
> (anymore)!
> Get:40 http://ftp.fr.debian.org/debian unstable/main Sources 
> 2016-03-07-2055.20.pdiff [10.1 kB]
> 24% [40 Sources 10.1 kB/10.1 kB 100%]E: Unpatched file  doesn't exist 
> (anymore)!
> [...]
> E: Unpatched file  doesn't exist (anymore)!
> E: Unpatched file  doesn't exist (anymore)!

This might also be an apt bug (in particular the "Unpatched file
doesn't exist" thing), thus re-assigning.

In any case, if it's not an apt bug per se, then apt provides too little
information to track down the issue.

What it might want to do is provide
 - expected digest of file expected,
 - actual digest of file on disk,
 - mtime of file on disk/last update,
 - digest and mtime of the file that provided the expected digest,
   i.e. probably of the Release file.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#817769: [php-maint] Bug#817769: problem with include_path

[Ivan Sergio Borgonovo]

Downgrading fix the problem.
Simply reinstalling new versions break stuff again.

Before downgrading I have
root@caronte:~/pkg# php5 -r 'echo(get_include_path());'
.::/usr/share/pear
after downgrading
root@caronte:~/pkg# php5 -r 'echo(get_include_path());'
.:/usr/share/php:/usr/share/pear

So the include_path as was clear from the log is wrong, but the main 
suspect still remain one of those packages.


I've been trying to guess which package among the suspects exactly 
defined a default include_path but grep and diff were not enough useful 
since the only possible interesting differences were in binary files.


php.ini files for modules seems to be generated in postinst but all the 
instance of include_path seems to be commented out in both versions in 
/etc/php5.


Considering that php5 in console still has the wrong path I would 
exclude from the list of suspects php5-fpm.


The remaining candidates are php5 , php5-common and php5-cli.

On 03/10/2016 12:51 AM, Ondřej Surý wrote:

It seems that your include_path is wrong, as Horde resides in:

/usr/share/php/Horde/Autoloader/Default.php

Doesn't seem to be php5 fault as /usr/share/php is missing from your
include_path and the default include_path is:

include_path = ".:/usr/share/php"

Cheers,



--
Ivan Sergio Borgonovo
http://www.webthatworks.it

Bug#691487: bsdmainutils: Segfault, easy to reproduce

[Michael Meskes]

> Well, whose fault would it be? My default is 1M stack size, and all
> other 
> programs seem to be fine with that...

Sorry, my message was confusing. This bug report was about a different
problem, the stack size one is still open. Besides, while I do agree
that memory handling should be changed, which would be a feature
request IMO, the segfault itself does not come from a bug in column.
Anyway, nitpicking, the code needs improvements. :)

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#780988: mirrors: ftp.hk.debian.org is out of sync with the archive.

[Peter Palfrader]

On Sun, 22 Mar 2015, Donald Norwood wrote:

> Your mirror located at ftp.hk.debian.org is out of sync with the rest of
> the archive.

The mirror ftp.debian.org.hk is two years out of date:
  http://ftp.debian.org.hk/debian/project/trace/

I intend to remove it from the mirrors list shortly.

Should you plan to bring it back, however, please let me know.

Thanks,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#814432: [Pkg-privacy-maintainers] Bug#814432: tails-installer should download and authenticate live ISO images

[intrigeri]

Control: forwarded -1 https://labs.riseup.net/code/issues/9798

Hi,

Antoine Beaupré wrote (11 Feb 2016 14:39:39 GMT) :
> I am exaggerating, of course, but I was expecting something more like
> the tor browser launcher, which actually downloads the software for me
> and does the busy things of verifying crypto signatures and
> everything.

OK, so we have two problems here:

1. You were expecting something else than what the software actually
   does; the package description reads "Tails Installer is a graphical
   tool to install or upgrade Tails on a USB stick from an ISO image";
   I'm not quite sure how we can improve it to make it clearer that
   one needs to have "an ISO image" to start with. Any suggestion?

2. Tails Installer currently can't download and verify the ISO image
   itself. This is an upstream feature request, that is being tracked
   at https://labs.riseup.net/code/issues/9798.

> That way there is a trust path between me and the
> developpers that does not depend on the CA cartel (as I understand the
> current approach seem to depend on).

Almost: the current approach depends on one specific CA.

Cheers,
-- 
intrigeri

Bug#817789: FTBFS: pep8 module is now in python-pep8 package

[Edward Betts]

Source: blockdiag
Version: 1.4.7-2
Severity: normal
Tags: patch

The pep8 module is now in python-pep8 package, so the Build-Depends for this
package need to be updated. Here is a patch.

--- debian/control.orig 2016-03-10 10:30:58.612028956 +
+++ debian/control  2016-03-10 10:31:45.312231146 +
@@ -7,7 +7,7 @@
python-all,
python-setuptools,
python-unittest2,
-   pep8 (>= 1.3),
+   python-pep8,
python-nose,
python-zc.buildout,
python-funcparserlib (>= 0.3.4),

Bug#817788: libpam-modules: pam_unix does not respect disabled account aging

[Andreas]

Package: libpam-modules
Version: 1.1.3-7.1
Severity: normal
Tags: d-i upstream

Dear Maintainer,

I discovered that pam_unix does not respect on account aging that is
turned off on a certain account. Manual (shadow(5)) says about 3rd (last
password changed) field: "An empty field means that password aging
features are disabled."

When I erease that filed 'passwd -S' reports 12/31/1969 - it seems ok,
since empty date and day fields considered to be -1. But when I login
with impacted account, it does not seem to interpret this value as
special and continuing to respect on min days, max days fields.

I think "password aging" mentioned above in manual means there is no
password expirity nor minimum age. As I observed, vassverify.c does the
lack.

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

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

Versions of packages libpam-modules depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libc6  2.13-38+deb7u10
ii  libdb5.1   5.1.29-5
ii  libpam-modules-bin 1.1.3-7.1
ii  libpam0g   1.1.3-7.1
ii  libselinux12.1.9-5

libpam-modules recommends no packages.

libpam-modules suggests no packages.

-- Configuration Files:
/etc/security/access.conf changed [not included]
/etc/security/limits.conf changed [not included]

-- debconf information excluded

Bug#817769: [php-maint] Bug#817769: Bug#817769: problem with include_path

[Ondřej Surý]

You might be right, the PHP packages stopped building PEAR between
5.6.18 and 5.6.19, because it's a separate source package now and
perhaps the defaults has changed because of this.

I'll investige more later this or next week.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Thu, Mar 10, 2016, at 11:18, Ivan Sergio Borgonovo wrote:
> Downgrading fix the problem.
> Simply reinstalling new versions break stuff again.
> 
> Before downgrading I have
> root@caronte:~/pkg# php5 -r 'echo(get_include_path());'
> .::/usr/share/pear
> after downgrading
> root@caronte:~/pkg# php5 -r 'echo(get_include_path());'
> .:/usr/share/php:/usr/share/pear
> 
> So the include_path as was clear from the log is wrong, but the main 
> suspect still remain one of those packages.
> 
> I've been trying to guess which package among the suspects exactly 
> defined a default include_path but grep and diff were not enough useful 
> since the only possible interesting differences were in binary files.
> 
> php.ini files for modules seems to be generated in postinst but all the 
> instance of include_path seems to be commented out in both versions in 
> /etc/php5.
> 
> Considering that php5 in console still has the wrong path I would 
> exclude from the list of suspects php5-fpm.
> 
> The remaining candidates are php5 , php5-common and php5-cli.
> 
> On 03/10/2016 12:51 AM, Ondřej Surý wrote:
> > It seems that your include_path is wrong, as Horde resides in:
> >
> > /usr/share/php/Horde/Autoloader/Default.php
> >
> > Doesn't seem to be php5 fault as /usr/share/php is missing from your
> > include_path and the default include_path is:
> >
> > include_path = ".:/usr/share/php"
> >
> > Cheers,
> >
> 
> -- 
> Ivan Sergio Borgonovo
> http://www.webthatworks.it
> 
> ___
> pkg-php-maint mailing list
> pkg-php-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint

Bug#806082: multipath-tools: FTBFS when built with dpkg-buildpackage -A

[Ritesh Raj Sarraf]

Hello Santiago,

On Thu, 2016-03-10 at 10:01 +, Santiago Vila wrote:
> 
> I can diagnose this for you: This is what I found in debian/rules:
> 
> binary-indep: build-indep install-indep
> 
> but the target is empty otherwise.
> 
> Since there is no dh_builddeb anywhere in such target, no
> architecture
> independent .deb is created at all.
> 
> Please do actually try "dpkg-buildpackage -A" before considering this
> fixed, you don't need any special tools for that, nor you need
> anybody
> else to do it for you.

This should be fixed now with the attached patch. If you want, you can
verify and confirm with the patch (attached).

As you mentioned, I checked the build with `dpkg-buildpackage -A` and
it is building fine now.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
From 6b4d2b2e44db1f9e5120c027b475532a8e54fa41 Mon Sep 17 00:00:00 2001
From: Ritesh Raj Sarraf 
Date: Thu, 10 Mar 2016 16:09:25 +0530
Subject: [PATCH] Build binary independent deb package in respective target

Earlier, we were building it, but not buildign a .deb package.

Thanks: Santiago Vila
Closes: #806082
---
 debian/rules | 21 ++---
 1 file changed, 18 insertions(+), 3 deletions(-)

diff --git a/debian/rules b/debian/rules
index 94e3aab..56333a6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,7 +27,9 @@ include /usr/share/dpkg/buildflags.mk
 build: build-arch build-indep
 
 build-arch: build-multipath-udeb-stamp build-stamp
-build-indep: 
+build-indep:
+	# Nothing to do here.
+	touch $@
 
 build-stamp:
 	dh_testdir
@@ -91,6 +93,21 @@ install: install-indep
 	dh_install -Xkpartx_id -X.rules -X.service -X.socket --fail-missing -pmultipath-udeb --sourcedir=$(CURDIR)/debian/tmp-multipath-udeb
 
 binary-indep: build-indep install-indep
+	dh_testdir
+	dh_testroot
+	dh_installdirs
+	dh_installchangelogs ChangeLog
+	dh_installdocs
+	dh_installexamples
+	dh_installinit -pmultipath-tools --name=multipath-tools-boot --no-start -- start 21 S .
+	dh_installdebconf -pmultipath-tools-boot
+	dh_installman
+	dh_compress
+	dh_fixperms
+	dh_installdeb
+	dh_gencontrol
+	dh_md5sums
+	dh_builddeb
 
 # Build architecture-dependent files here.
 binary-arch: build install
@@ -102,13 +119,11 @@ binary-arch: build install
 	dh_lintian
 	dh_systemd_enable -pmultipath-tools multipathd.service
 	dh_installinit -pmultipath-tools
-	dh_installinit -pmultipath-tools --name=multipath-tools-boot --no-start -- start 21 S .
 	dh_installudev -pkpartx
 	dh_installudev -pmultipath-tools --name=multipath
 	dh_link lib/systemd/system/multipathd.service \
 		lib/systemd/system/multipath-tools.service
 	dh_systemd_start -pmultipath-tools multipathd.service
-	dh_installdebconf -pmultipath-tools-boot
 	dh_installman
 	dh_makeshlibs --add-udeb=multipath-udeb
 	dh_link
-- 
2.7.0



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

Bug#817790: golang-github-aws-aws-sdk-go: new upstream version?

[Filippo Giunchedi]

Package: golang-github-aws-aws-sdk-go
Version: 1.0.7+dfsg-1
Severity: normal

hi,
I noticed prometheus currently FTBFS in unstable, e.g.
https://reproducible.debian.net/rbuild/unstable/amd64/prometheus_0.16.2+ds-1.rbuild.log

with

# github.com/prometheus/prometheus/retrieval/discovery
src/github.com/prometheus/prometheus/retrieval/discovery/ec2.go:58: undefined: 
defaults.DefaultChainCredentials
src/github.com/prometheus/prometheus/retrieval/discovery/ec2.go:107: cannot use 
ed.aws (type *aws.Config) as type client.ConfigProvider in argument to ec2.New: 
*aws.Config does not implement client.ConfigProvider (missing ClientConfig 
method)

likely due to using newer golang-github-aws-aws-sdk-go API, are there plans to
update to newer upstream version?

thanks!

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

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

Bug#817776: [aptitude] SIGABRT when quitting curses mode after unresolvable conflicts

[Manuel A. Fernandez Montecelo]

2016-03-10 01:03 Katsuhiko Nishimra:

Package: aptitude
Version: 0.7.8-1
Severity: minor

Dear maintainers,

As I mentioned in a former bugreport[1], aptitude gets SIGABRT when
quitting curses session after too many conflicts that aptitude cannot
resolve automatically.

How to reproduce:
* Make aptitude gets a lot of conflicts (e.g. Install conflicting
  packages by dpkg and upgrade/downgrade many packages)
* Get the prompt `Resolve these dependencies by hand? [N/+/-/_/:/?]'
  and hit `e' to enter curses mode
* Quit aptitude leaving package state unresolved by hitting `q'

A backtrace from a dumped core is attached.
I hope it helps you.


I see, our friend boost::flyweight again... thanks!

--
Manuel A. Fernandez Montecelo 

Bug#622277:

[allan]

Confirmed with Sid.  Forcing performance governor after things are stable
has no effect.  My 1.73Ghz i7 won't run faster than 933MHz.

Bug#731318: aptitude: keeps switching a package between architectures on safe-upgrade

[Manuel A. Fernandez Montecelo]

2016-03-09 22:45 GMT+00:00 Shai Berger :
> Hi Manuel,
>
> On Tuesday 08 March 2016 00:52:36 Manuel A. Fernandez Montecelo wrote:
>>
>> Did you keep observing this problem in recent years/releases?
>>
>
> I'm not sure when was the last time I saw the problem; anyway, since the last
> major ABI transitions (gcc 5 together with KDE5, IIRC) I have not updated the
> system regularly and so I cannot comment.

OK, thanks for the feedback!

-- 
Manuel A. Fernandez Montecelo 

Bug#812852: Vigra auf ppc64el -- continues a little bit

[Ullrich Koethe]

* Remove all occurencies of threading::memory_order* in multi_array_chunked.hxx 
(or equivalently, replace them with threading::memory_order_seq_cst). This will 
force all atomic accesses to use sequentially consistent ordering, the most 
strict possibility.


That worked out ... much thanks!


- First of all, there was a little mistake, that was the wrong log file. 
Unfortunately, the
   problem with test_multiarray_chunked resp. multi_array_chunked.hxx on 
ppc64el/le remains also
   with changing `memory_order_release/acquire` to `memory_order_seq_cst`.


bummer!


I'm further experimenting with VIGRA_SINGLE_THREADED but no breakthrough so far 
...


Looking at the log again, it occured to me that the error might not be 
related to multi-threading at all. Possibly, all failing tests are on 
ChunkedArrayCompressed with T being float and double. Can you please 
check this? If this is true, the error might go away be changing the 
compression algorithm in test_chunked.cxx line 121 from LZ4 into 
ZLIB_FAST or NO_COMPRESSION. If this works, there might be a byte order 
problem in the LZ4 algorithm. Endianess is decided in 
/src/impex/lz4.c lines 65 to 79. Please check if the correct 
endianess for your platform is retrieved there, and possibly propose a 
fix if it isn't.


Best
Ulli

Bug#817233: ODP: Bug#817233: CVE-2016-1968

[Tomasz Buchert]

Hi guys,
I'm out of town and cannot work on this. NMUs welcome. :D

Tomasz


Wysłane z telefonu Samsung

Salvatore Bonaccorso  pisze:

null

Bug#770877: New version

[M.]

Any luck in updating to 4.7.2?

Cheers

Bug#517008: alias not expanded with zsh -c

[Christian Heinrich]

Hi,

I just verified that this patch was included in the latest ZSH package
in Stretch. Am I correct that this (pretty old) issue can actually be
closed as resolved?

Best
Christian

On Thu, 26 Mar 2009 09:50:29 + Peter Stephenson 
wrote:
> On Wed, 25 Mar 2009 17:14:31 -0700
> Bart Schaefer  wrote:
> > On Mar 25,  6:20pm, Peter Stephenson wrote:
> > }
> > } But yes, I share your feeling that this isn't a particularly
vital
> > } addition, it just looked easy to do like other shells in
compatability
> > } mode, which is the point of that.
> > 
> > It just seems to me that we're potentially penalizing a script that
does
> > not use aliases in the can't-open-tempfile case in order to support
a
> > script that does not use aliases.
> > 
> > Given potential security problems with using tempfiles and the
likelyhood
> > of a script using an alias vs. the likelyhood of file creation
failing,
> > which case ought we be catering too?
> 
> From what I've heard, it doesn't sound like it's worth more than a
> warning.
> 
> Index: Doc/Zsh/options.yo
> ===
> RCS file: /cvsroot/zsh/zsh/Doc/Zsh/options.yo,v
> retrieving revision 1.78
> diff -u -r1.78 options.yo
> --- Doc/Zsh/options.yo3 Mar 2009 17:35:29 -   1.78
> +++ Doc/Zsh/options.yo26 Mar 2009 09:49:05 -
> @@ -1721,7 +1721,12 @@
>  
>  Alias expansion takes place while text is being read; hence when
this
>  option is set it does not take effect until the end of any function
or
> -other piece of shell code evaluated as one unit.
> +other piece of shell code evaluated as one unit.  Note this may
> +cause differences from other shells even when the option is in
> +effect.  For example, when running a command with `tt(zsh -c)' the
> +entire command argument is parsed in one go, so aliases defined
within
> +the argument are not available even in later lines.  If in doubt,
avoid use
> +of aliases in non-interactive code.
>  )
>  pindex(POSIX_BUILTINS)
>  pindex(NO_POSIX_BUILTINS)
> 
> 
> -- 
> Peter Stephenson   Software Engineer
> CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
> Cambridge, CB4 0WZ, UK  Tel: +44 (0)1223
692070
> 
> 
> 

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

Bug#806082: multipath-tools: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

On Thu, Mar 10, 2016 at 04:16:07PM +0530, Ritesh Raj Sarraf wrote:
> This should be fixed now with the attached patch. If you want, you can
> verify and confirm with the patch (attached).
> 
> As you mentioned, I checked the build with `dpkg-buildpackage -A` and
> it is building fine now.

Now it does not FTBFS anymore, which is good.

But the packaging is still not ok: After "dpkg-buildpackage -A" I see
the following packages created:

kpartx_0.5.0+git1.656f8865-5_amd64.deb
kpartx-udeb_0.5.0+git1.656f8865-5_amd64.udeb
multipath-tools_0.5.0+git1.656f8865-5_amd64.deb
multipath-tools-boot_0.5.0+git1.656f8865-5_all.deb
multipath-tools-dbg_0.5.0+git1.656f8865-5_amd64.deb
multipath-udeb_0.5.0+git1.656f8865-5_amd64.udeb

It should only create "multipath-tools-boot".


Hint: You should probably add option '-a' to every dh_* call in
binary-arch and option '-i' to every dh_* call in binary-indep.


However, if you have time and motivation, I would really consider
switching to "dh". A debian/rules using "dh" is usually a lot more
readable and "nicer".

Thanks.

Bug#817776: [aptitude] SIGABRT when quitting curses mode after unresolvable conflicts

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi again,

2016-03-10 10:53 To Katsuhiko Nishimra:

2016-03-10 01:03 Katsuhiko Nishimra:

Package: aptitude
Version: 0.7.8-1
Severity: minor

Dear maintainers,

As I mentioned in a former bugreport[1], aptitude gets SIGABRT when
quitting curses session after too many conflicts that aptitude cannot
resolve automatically.

How to reproduce:
* Make aptitude gets a lot of conflicts (e.g. Install conflicting
 packages by dpkg and upgrade/downgrade many packages)
* Get the prompt `Resolve these dependencies by hand? [N/+/-/_/:/?]'
 and hit `e' to enter curses mode
* Quit aptitude leaving package state unresolved by hitting `q'

A backtrace from a dumped core is attached.
I hope it helps you.


I see, our friend boost::flyweight again... thanks!


I think that I solved the problem in a similar way as the other one.

The problem is that I cannot reproduce the situation by getting the
"Resolve these dependencies by hand?", so I cannot test whether it
worked or not.

I forcibly install and remove some packages with dpkg to conflict with
installed ones, and then do a variety of actions (upgrades, purges etc;
of important packages such as libc6 or systemd), using full resolver,
safe resolver, enabling and disabling auto-fix-broken... but in all
cases, either I get the typical prompt "Accept solution?" or the
resolver spends lots and lots of time (> 10 minutes) trying to solve the
problem without offering me to resolve by hand.

I cannot to afford at this moment to try too hard and risk breaking the
system for real, so it would be very nice if you (or other readers)
could check if this indeeds solves the situation in the next release and
report back whether it worked or not -- I am quite confident that it
does, so marking as +pending.


... and thanks for the detailed reports and persistence, in any case!


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#806082: multipath-tools: FTBFS when built with dpkg-buildpackage -A

[Ritesh Raj Sarraf]

Hello Santiago,

On Thu, 2016-03-10 at 11:29 +, Santiago Vila wrote:
> Now it does not FTBFS anymore, which is good.
> 

Great.

> But the packaging is still not ok: After "dpkg-buildpackage -A" I see
> the following packages created:
> 
> kpartx_0.5.0+git1.656f8865-5_amd64.deb
> kpartx-udeb_0.5.0+git1.656f8865-5_amd64.udeb
> multipath-tools_0.5.0+git1.656f8865-5_amd64.deb
> multipath-tools-boot_0.5.0+git1.656f8865-5_all.deb
> multipath-tools-dbg_0.5.0+git1.656f8865-5_amd64.deb
> multipath-udeb_0.5.0+git1.656f8865-5_amd64.udeb
> 
> It should only create "multipath-tools-boot".
> 
> Hint: You should probably add option '-a' to every dh_* call in
> binary-arch and option '-i' to every dh_* call in binary-indep.
> 

Ah ha... I wondered how to do that. But didn't bother much because a
full build, when triggered, will run both the targets.

But this is good to know.

> 
> 
> However, if you have time and motivation, I would really consider
> switching to "dh". A debian/rules using "dh" is usually a lot more
> readable and "nicer".

I definitely want to move to the new build setup, but it is the lack of
time which has held me.

Maybe I'll just do it once and for all (move to new dh). Lets keep the
bug open. Whichever build setup we choose, this bug will be closed back
once the build is fixed.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#817249: liferea keeps animating images even when the window is hidde

[Paul Gevers]

Hi Enrico,

On 10-03-16 08:23, Enrico Zini wrote:
> My personal workaround for this is currently to ensure that I do not
> have a feed item currently open before I close the liferea window.
> 
> This suggests me a potential hack for working around the webkit
> limitation: when the window hide signal is received, the webkit widget
> contents are cleared. When the window is shown again, the entry that was
> displayed on hide gets reloaded.
> 
> Do you think upstream would be ok with that?

No idea, but I'll relay the idea.

>> Do you want to try and see if Webkit can be persuaded to add such a
>> feature? You can reassign this bug if you find that appropriate.
> 
> It may be worth reassigning or opening a bug to webkit, too, possibly
> also referencing how many people are currently working around it by
> sending SIGSTOP to browsers (I got a couple of private replies to
> http://www.enricozini.org/blog/2016/debian/simple-one-liner-to-save-battery-life-and-reduce-system-latency/
> from people who were already doing it, and even scripted awesome to do
> it automatically).
> 
> I don't know much about the webkit ecosystem: what would be the right
> package to file such a bug?

Just like you I have no clue.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#817791: check-all-the-things: [shellcheck] and [checkbashisms] should check all shell scripts

[Ben Wiederhake]

Package: check-all-the-things
Version: 2015.12.10
Severity: normal
Tags: patch

Hello,

currently, checkbashisms and shellcheck only look for files ending in '.sh'.
However, there are people who believe that executables should not be named
after the language in which they're currently implemented. For example, there
is "check-all-the-things" but not "check-all-the-things.py". Personally, I
advocate this, but for this report it only matters that a significant portion
of scripts does not end in '.sh'.

Using the existing syntax of catt, it's rather easy to extend the checks, and
filter by "file | grep | cat". Please see below for example runs on some
project I'm working on.

Impact:
- positive->negative can only occur for files whose name end in '.sh' but are
not shell scripts. I consider this a good thing, but I'm not sure why this
would ever happen.
- negative->positive can only occur for files whose name does NOT end in '.sh',
but ARE shell scripts, and DO trigger warnings/errors in the linting tools.
That's the point of this patch, so it's a good thing, too.

Is there a linter for the checks?
Should I adapt other checks, too?
In how far does this affect #791722, which seems to revolve mostly around
python scripts?

Cheers,
Ben Wiederhake



user@machine:~/workspace/telegram-purple$ # Run installed, non-patched version
on some project
user@machine:~/workspace/telegram-purple$ check-all-the-things --checks
=checkbashisms --checks +shellcheck
Skipped and hidden checks:
- cmdline disabled check: 7z-test acheck ansible-lint appstream-util-validate
appstreamcli-validate bashate bfbtester ...
- dangerous check: bfbtester perl-b-lint perl-syntax-check
- help needed: acheck ansible-lint appstream-util-validate appstreamcli-
validate build-log-scanner cbmc chk-origtargz ...
- no matching files: 7z-test bfbtester blhc build-log-errors build-log-warnings
bzip2-test cabal chk-origtargz ...
- no output: checkbashisms shellcheck



user@machine:~/workspace/telegram-purple$ # Run local, patched version on some
project
user@machine:~/workspace/telegram-purple$ ../check-all-the-things/check-all-
the-things --checks =checkbashisms --checks +shellcheck
$ find \( -name .git -o -name .svn -o -name .bzr -o -name CVS -o -name .hg -o
-name _darcs -o -name _FOSSIL_ -o -name .sgdrawer -o -name configure -o -name
config.status -o -name config.sub -o -name config.guess -o -name install-sh -o
-name install.sh \) -prune -o -type f -print0 | xargs -0 file -F "   " -N |
grep -a 'shell script' | cut -f 1 | xargs -d"\n" --no-run-if-empty
checkbashisms
possible bashism in ./commit.h.gen line 23 ('command' with option other than
-p):
if ! (command -v git && git status) >/dev/null 2>&1

$ find \( -name .git -o -name .svn -o -name .bzr -o -name CVS -o -name .hg -o
-name _darcs -o -name _FOSSIL_ -o -name .sgdrawer -o -name configure -o -name
config.status -o -name config.sub -o -name config.guess -o -name install-sh -o
-name install.sh \) -prune -o -type f -print0 | xargs -0 file -F "   " -N |
grep -a 'shell script' | cut -f 1 | xargs -d"\n" --no-run-if-empty shellcheck

In ./commit.h.gen line 35:
GIT_COMMIT=`git rev-parse HEAD | cut -c1-10`
   ^-- SC2006: Use $(..) instead of legacy `..`.

In ./gen-origtar line 47:
TARNAME="telegram-purple_`git describe --tags | sed s/^v// `.orig.tar.gz"
 ^-- SC2006: Use $(..) instead of legacy `..`.

In ./gen-origtar line 49:
echo mv -f bin/result.tar.gz $TARNAME
 ^-- SC2086: Double quote to prevent globbing and
word splitting.

In ./gen-origtar line 50:
mv -f bin/result.tar.gz $TARNAME
^-- SC2086: Double quote to prevent globbing and word
splitting.

Skipped and hidden checks:
- cmdline disabled check: 7z-test acheck afl ansible-lint appstream-util-
validate appstreamcli-validate autodep8 bashate ...
- dangerous check: bfbtester perl-b-lint perl-syntax-check
- help needed: acheck ansible-lint cbmc checkmp3 chk-origtargz clang-check
clang-tidy cppclean doc8 embedding-restrictions ...
- no matching files: 7z-test acheck afl ansible-lint appstream-util-validate
appstreamcli-validate autodep8 bashate ...
>From 7f782a324333fce427d2369b7ec96ae99f61f8c5 Mon Sep 17 00:00:00 2001
From: Ben Wiederhake 
Date: Thu, 10 Mar 2016 12:11:54 +0100
Subject: [PATCH] Improve detection of shell scripts

Affects [checkbashisms] and [shellcheck]
---
 data/sh | 18 ++
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/data/sh b/data/sh
index 2389117..32469e6 100644
--- a/data/sh
+++ b/data/sh
@@ -4,13 +4,23 @@ command = sh -n {file}
 
 [checkbashisms]
 apt = devscripts
-files = *.sh
-command = checkbashisms {files}
+# TODO: replace not-dirs with --ignore option
+not-dirs = .git .svn .bzr CVS .hg _darcs _FOSSIL_ .sgdrawer
+# TODO: replace not-files with recursive option (#780197)
+not-files =
+ configure config.status config.sub config.guess install-sh install.sh
+# Careful: file -F "" ... cut -d ""
+command = file -F "	" 

Bug#809318: bts: overrides user-specified value of sendmail

[Osamu Aoki]

Package: devscripts
Followup-For: Bug #809318

As I understand, the normal bug is about "DEFAULTING TO DEFAULT sendmail".

Then its fix should be "die" instead of stop doing sanity check.

What do you think of attached patch.

Osamu

>From ee5b19c7fc488cc503c7ede427492f40e3c5c3da Mon Sep 17 00:00:00 2001
From: Osamu Aoki 
Date: Thu, 10 Mar 2016 20:25:49 +
Subject: [PATCH] bts: Fail if sendmail is broken

---
 scripts/bts.pl | 12 
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/scripts/bts.pl b/scripts/bts.pl
index e431c6f..8d64f6e 100755
--- a/scripts/bts.pl
+++ b/scripts/bts.pl
@@ -542,11 +542,9 @@ if (@ARGV and $ARGV[0] =~ /^--no-?conf$/) {
 and $config_vars{'BTS_SENDMAIL_COMMAND'} ne '/usr/sbin/sendmail') {
 	my $cmd = (split ' ', $config_vars{'BTS_SENDMAIL_COMMAND'})[0];
 	unless ($cmd =~ /^~?[A-Za-z0-9_\-\+\.\/]*$/) {
-	warn "BTS_SENDMAIL_COMMAND contained funny characters: $cmd\nReverting to default value /usr/sbin/sendmail\n";
-	$config_vars{'BTS_SENDMAIL_COMMAND'}='/usr/sbin/sendmail';
+	die "BTS_SENDMAIL_COMMAND contained funny characters: $cmd\nPlease fix configuration file.\n";
 	} elsif (system("command -v $cmd >/dev/null 2>&1") != 0) {
-	warn "BTS_SENDMAIL_COMMAND $cmd could not be executed.\nReverting to default value /usr/sbin/sendmail\n";
-	$config_vars{'BTS_SENDMAIL_COMMAND'}='/usr/sbin/sendmail';
+	die "BTS_SENDMAIL_COMMAND $cmd could not be executed.\nPlease fix configuration file.\n";
 	}
 }
 
@@ -678,11 +676,9 @@ if ($opt_sendmail) {
 	and $opt_sendmail ne $sendmailcmd) {
 	my $cmd = (split ' ', $opt_sendmail)[0];
 	unless ($cmd =~ /^~?[A-Za-z0-9_\-\+\.\/]*$/) {
-	warn "--sendmail command contained funny characters: $cmd\nReverting to default value $sendmailcmd\n";
-	undef $opt_sendmail;
+	die "--sendmail command contained funny characters: $cmd\n";
 	} elsif (system("command -v $cmd >/dev/null 2>&1") != 0) {
-	warn "--sendmail command $cmd could not be executed.\nReverting to default value $sendmailcmd\n";
-	undef $opt_sendmail;
+	die "--sendmail command $cmd could not be executed.\n";
 	}
 }
 }
-- 
2.7.0

Bug#784397: Fix debian-changelog-mode instead, please

[Osamu Aoki]

control: severity -1 wishlist

As I read the BTS discussion, this could be a wishlist bug but not a minor bug.
Considering multiple commands need to be updated to allow debian-changelog-mode
style changelog entry, it is better to fix debian-changelog-mode to make proper
changelog entry expected by other tools.

Osamu

PS: I am going over non-wishlist bugs with patches :-)

Bug#817171: module needs rebuild?

[Lukas Degener]

Same problem here. I tried to work around this problem by creating
some symlinks in /usr/lib/x86_64-linux-gnu/irssi/modules.

Now, I get this error:

 -!- Irssi: xmpp/core is ABI version 0 but Irssi is version 1, cannot load
 -!- Irssi: Error loading module xmpp/fe: 
/usr/lib/x86_64-linux-gnu/irssi/modules/libfe_xmpp.so: undefined symbol: 
xmpp_subscription
 -!- Irssi: xmpp/core is ABI version 0 but Irssi is version 1, cannot load
 -!- Irssi: Unknown chat protocol: XMPP

Maybe the plugin simply needs to be recompiled against the new irssi
version?


signature.asc
Description: PGP signature

Bug#719624: Upgrading xrdp

[Andreas Tille]

On Tue, Mar 08, 2016 at 11:21:32PM +0100, Dominik George wrote:
> 
> In that case, please let us finalise the work ;). I expect it to be done 
> until 
> middle of the week.

Just for my understanding: To what repository are you pushing
intermediate changes to follow your steps? 

Kind regards and thanks for working on this

Andreas.

-- 
http://fam-tille.de

Bug#738350: aptitude #738350: "Reconfiguring" and "Report Bug" missing in menu

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


2015-10-12 23:12 To Axel Beckert:


I still didn't go ahead removing reportbug


Removed a while ago.


there is the parallel issue of the call to
dpkg-reconfigure, which I don't know if it's better to keep, add to the
menu and fix some issues (#680334) or remove it altogether.


Will be removed now...


For reportbug there's the possibility of implementing the drop of
privileges, but for dpkg-reconfigure we need root anyway, it's not a
security issue but there is some work to do to bring it to first-level
functionality.  I still think that it's probably better to remove both
reportbug and dpkg-reconfigure -- perhaps I am wrong, but I don't think
that they are very used/important features.


... so this bug can be closed.


--
Manuel A. Fernandez Montecelo 

Bug#817791: check-all-the-things: [shellcheck] and [checkbashisms] should check all shell scripts

[Paul Wise]

Control: forcemerge 791722 -1
Control: retitle 791722 add support for matching files based on MIME types

On Thu, 2016-03-10 at 12:51 +0100, Ben Wiederhake wrote:

> Using the existing syntax of catt, it's rather easy to extend the checks, and
> filter by "file | grep | cat".

Implementing this once per check is not ideal, I would prefer to have
support in the file matcher and in the command generator. There is
work-in-progress for this in the wip/mime branch for bug #791722.

> Is there a linter for the checks?

Not yet, that would be a good idea but probably hard to do since most
of the things that go wrong from doc/README need a human to detect. I
would be happy to get a patch for this if you can think of some checks.

> Should I adapt other checks, too?

See my answer above.

> In how far does this affect #791722, which seems to revolve mostly around
> python scripts?

Same issue.

> +not-files =
> + configure config.status config.sub config.guess install-sh install.sh

I don't think this is appropriate, these could have bugs/bashisms too
and for configure this would be indicative of bugs in configure.ac.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#812852: Vigra auf ppc64el -- continues a little bit

[Ullrich Koethe]

I upgraded the RC to use the newest LZ4 version which has significantly 
better byte order handling. Hopefully, this fixes the problem. One could 
also add a cmake option to use a pre-installed LZ4 library when 
available and just fall-back to the internal version if not.


Best
Ulli

Bug#564781: [mk-build-deps] Nudge aptitude ...

[Osamu Aoki]

Hi,

aptitude used to mass remove packages.  It got better these days.

It looks like it is due somewhat by improved aptitude dependency resolver but
also improved archive maintenance of testing.

Is this bug: https://bugs.debian.org/564781 still valid?

Is the fix proposed still worth it?

   system shellwords($install_tool), '-f', 'install',
map("$_-build-deps", @packages);

Please give us update.

Regards,

Osamu

PS:  This is the one last non-wishlist bug with patch which is in zombee state.

Bug#817792: Unavailable dependencies on unstable

[Yuri D'Elia]

Package: roundcube-core
Severity: normal

The current dependencies on php-net-idna2/php-mail-mime/etc make this package
currently uninstallable on unstable.

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

Kernel: Linux 4.5.0-rc7-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)

Bug#517008: alias not expanded with zsh -c

[Vincent Lefevre]

Control: found -1 5.2-3

On 2016-03-10 12:23:38 +0100, Christian Heinrich wrote:
> I just verified that this patch was included in the latest ZSH package
> in Stretch. Am I correct that this (pretty old) issue can actually be
> closed as resolved?

I can still reproduce it with zsh 5.2-3, which is the current package
in testing and unstable.

Note: In the bug report, I said that pdksh has the same bug. Since then,
pdksh has been replaced by mksh, which no longer has this bug.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#680334: aptitude: incorrect dpkg* calls

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending
Control: owner -1 !


2012-07-05 05:12 Daniel Hartwig:

Aptitude is not effected by this particular bug *for package holds*,
due to the aforementioned #137771.  However, it does turn up in
src/pkg_item.cc which has code to this effect:

sucmd="dpkg-reconfigure '%s'";
snprintf(buf, 512, sucmd,
 package.FullName().c_str());

with these problems:

- arch-qualified names are always used, even if dpkg is not
 multi-arch aware;
- arch:all packages are treated as arch:native by APT but not
 dpkg (as discussed above by David) -- must use
 VerIterator::FullName instead.

That call also ignores DPkg::Options


dpkg-reconfigure to be removed, so this problem gone.



and download_install_manager.cc
has a similar call to "dpkg --configure -a".


I tried to see if I could outsource the responsibility to do this to
apt, running with DPkg::Options and all, but it seems that there isn't a
way.

That call is infrequent enough (happens only in the cases of some
detected breakage) and DPkg::Options probably not used widely enough
that this problem (if somebody stumbled upon it at all) was not reported
for years in aptitude.

In fact, despite being marked as "important", there is not real bug
report in aptitude and the messages are largely about theoretical cases,
no report came in the last few years related with it.


So with the removal of dpkg-configure, marking this bug as +pending.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#686626: aptitude Bug#686626: Should not arch-qualfy arch-less packages on dpkg calls

[Manuel A. Fernandez Montecelo]

Control: owner -1 !
Control: tags -1 +pending


2012-09-09 01:03 Daniel Hartwig:


Directly, this only concerns “Reconfigure package” action in the
interactive interface


Feature to be removed, so bug marked as +pending.

--
Manuel A. Fernandez Montecelo 

Bug#817793: qt3d-opensource-src: B-D on obsolete package libqt5xcbqpa5

[Andreas Beckmann]

Source: qt3d-opensource-src
Version: 5.5.1-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package Build-Depends on the obsolete transitional package
libqt5xcbqpa5 which is no longer built by qtbase-opensource-src. Please
switch to libqt5gui5.


Andreas

Bug#817794: qtsensors-opensource-src: B-D on obsolete package libqt5xcbqpa5

[Andreas Beckmann]

Source: qtsensors-opensource-src
Version: 5.5.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package Build-Depends on the obsolete transitional package
libqt5xcbqpa5 which is no longer built by qtbase-opensource-src. Please
switch to libqt5gui5.


Andreas

Bug#817796: lxc: Add dependency on uidmap

[George B.]

Package: lxc
Version: 1:1.1.5-1
Severity: normal

Hello,

Please add a dependency on the uidmap package as without it
unpriviledged containers do not work:

```
$ lxc-create -t download -n u1 -- -d ubuntu -r trusty -a amd64
error mapping child
setgid: Invalid argument
lxc-create: lxccontainer.c: do_create_container_dir: 879 Failed to chown
container dir
lxc-create: lxc_create.c: main: 274 Error creating container u1
```

(Credit to http://www.polarsparc.com/xhtml/LXC.html for the solution.)


Thanks,

George

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

Versions of packages lxc depends on:
ii  init-system-helpers  1.29
ii  libapparmor1 2.10-3+b1
ii  libc62.22-1
ii  libcap2  1:2.24-12
ii  liblxc1  1:1.1.5-1
ii  libseccomp2  2.2.3-3
ii  libselinux1  2.4-3+b1
ii  python3  3.5.1-2

Versions of packages lxc recommends:
ii  apparmor  2.10-3+b1
ii  bridge-utils  1.5-9
ii  cgmanager 0.39-2
ii  debootstrap   1.0.79
ii  dnsmasq-base  2.75-1
ii  iptables  1.6.0-2
ii  openssl   1.0.2g-1
ii  rsync 3.1.1-3

Versions of packages lxc suggests:
ii  btrfs-tools  4.4-1
ii  lua5.2   5.2.4-1
ii  lvm2 2.02.142-1+b1

-- no debconf information

Bug#815888: nvidia-detect: GF119M [GeForce 610M] nvidia-detect=ok for nvidia-driver . . . not ok

[Fulano Diego Perez]

Luca Boccassi:
> On Mar 9, 2016 14:29, "Fulano Diego Perez" 
> wrote:
>>
>>
>>
>> Luca Boccassi:
>>> On 9 March 2016 at 13:42, Fulano Diego Perez 
> wrote:


 Luca Boccassi:
> On 9 March 2016 at 11:49, Fulano Diego Perez <
> fulanope...@cryptolab.net> wrote:
>> hi luca,
>>
>> Luca Boccassi:
>>> On 9 March 2016 at 10:05, Fulano Diego Perez <
> fulanope...@cryptolab.net> wrote:
 hi luca

 Luca Boccassi:
> Control: package -1 nvidia-driver
> Control: tag -1 moreinfo
> Control: severity -1 normal
>
> On Thu, 2016-02-25 at 23:34 +1100, Fulano Diego Perez wrote:
>> Package: nvidia-detect
>> Severity: grave
>> Justification: renders package unusable
>>
>>
>> _disclaimer_
>>
>> 1.
>> i do not know if the problem lies with nvidia-detect,
> nvidia-driver and its
>> dependencies, or neither
>>
>> 2.
>> this bug report was submitted after removal and revert back to
> nouveau
>>
>> 3.
>> applies to intel ivy bridge chipset with built-in intel graphics
> +
>> nvidia below
>>
>>
>>
>> nvidia-detect recommends nvidia-driver
>>
>> i then install nvidia-driver, its dependencies and nvidia-xconfig
>>
>> NB i attempted this ~6 months ago and yesterday, i do not know
> the affect of
>> the recent nvidia updates to xserver and whether nvidia-xconfig
> is still
>> necessary
>>
>> gdm3 cannot proceed after reboot
>>
>> please advise any further log provision where necessary:
>
> Hi,
>
> It looks like you have a laptop with a switchable Optimus system
> (610M).
> If that's indeed the case, you cannot just install the nvidia
> stack, as
> your hardware is wired to use the Intel card to drive the display.
>
> If you want to use the discrete Nvidia card, you must do so
> through
> bumblebee. Please install
>
> bumblebee-nvidia
>
> Then run:
>
> sudo update-glx --config glx
>
> And make sure nvidia/bumblebee is selected, if not pick it.

 done above

>
> If the problem persists, please add more information by running:
>
> reportbug -N 815888

 sorry, this is out ATM, nevertheless...

> Kind regards,
> Luca Boccassi

 i get the following:

 $ primusrun glxgears
 primus: fatal: Bumblebee daemon reported: error: [XORG] (EE)

 $ optirun glxgears
 [23162.070642] [ERROR]Cannot access secondary GPU - error: [XORG]
> (EE)

 ive tried various basic amendments such as

 adding my user to the bumblebee group;

 manually specifying the nvidia option in
> /etc/bumblebee/bumblebee.conf;

 manually specifying BusID "PCI:1:0:0" in
> /etc/bumblebee/xorg.conf.nvidia
 (from the github FAQ)

 $ lspci | egrep 'VGA|3D'
 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
 processor Graphics Controller (rev 09)
 01:00.0 VGA compatible controller: NVIDIA Corporation GF119M
> [GeForce
 610M] (rev a1)

 i admit im stuck
>>>
>>> Hi,
>>>
>>> Sorry for your troubles.
>>>
>>> Unfortunately there's not much I can do without looking at the full
>>> system report. If reportbug -N is not working for you, could you
>>> please manually attach the output of:
>>
>> sure makes sense
>>
>>> reportbug --template nvidia-driver
>>
>> i enclose
>>
>> thanks for your help
>
> Hi,
>
> >From the log, it looks like nouveau is being loaded:
>
> 2367.838] (II) LoadModule: "nouveau"
> [  2367.838] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
> [  2367.838] (II) Module nouveau: vendor="X.Org Foundation"
> [  2367.838] compiled for 1.18.0, module version = 1.0.12
> [  2367.838] Module class: X.Org Video Driver
> [  2367.838] ABI class: X.Org Video Driver, version 20.0
>
> 
>
> [  2367.839] (II) NOUVEAU driver Date:   Tue Dec 8 15:52:25 2015 +1000
> [  2367.839] (II) NOUVEAU driver for NVIDIA chipset families :
> [  2367.839] RIVA TNT(NV04)
> [  2367.839] RIVA TNT2   (NV05)
> [  2367.840] GeForce 256 (NV10)
> [  2367.840] GeForce 2   (NV11, NV15)
> [  2367.840] GeForce 4MX (NV17, NV18)
> [  2367.840] GeForce 3   (NV20)
> [  2367.840] GeForce 4Ti (NV25, NV28)
> [  2367.840] GeForce FX  (NV3x)
> [  2367.840] GeForce 6   (NV4x)
> [  2367.840] GeForce 7   (G7x)
> [  2367.840] GeForce 8 

Bug#817795: sysvinit-utils - Contains pre-depends loop

[Bastian Blank]

Package: sysvinit-utils
Version: 2.88dsf-59.3
Severity: grave

In sysvinit-utils or somewhere of it's dependency chain is a
pre-dependency/conflict loop, which apt is unable to break.  This breaks
the upgrade from Jessie.

| # apt install sysvinit-utils
| Reading package lists... Done
| Building dependency tree   
| Reading state information... Done
| The following additional packages will be installed:
|   init-system-helpers libfdisk1 libncurses5 libncursesw5 libsmartcols1 
libtinfo5 util-linux
| Suggested packages:
|   bootlogd sash dosfstools kbd | console-tools util-linux-locales
| The following NEW packages will be installed:
|   libfdisk1
| The following packages will be upgraded:
|   init-system-helpers libncurses5 libncursesw5 libsmartcols1 libtinfo5 
sysvinit-utils util-linux
| 7 upgraded, 1 newly installed, 0 to remove and 215 not upgraded.
| Need to get 0 B/1.816 kB of archives.
| After this operation, 882 kB of additional disk space will be used.
| Do you want to continue? [Y/n] 
| E: This installation run will require temporarily removing the essential 
package sysvinit-utils:amd64 due to a Conflicts/Pre-Depends loop. This is often 
bad, but if you really want to do it, activate the APT::Force-LoopBreak option.

Bastian

-- 
Bastian Blank
Berater
Telefon: +49 2161 / 4643-194
E-Mail: bastian.bl...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Hohenzollernstr. 133, 41061 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer

Bug#817784: xserver-xorg-video-intel: gnome dont load after xserver-xorg-video-intel upgrade

[Timo Aaltonen]

10.03.2016, 11:23, Mario Geiger kirjoitti:
> Package: xserver-xorg-video-intel
> Version: 2:2.99.917+git20160218-1
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrade xserver-xorg-video-intel to version 2:2.99.917+git20160307-1 
> (with sudo apt-get upgrade)
> gdm3 load but after typing my password gnome dont load.
> 
> After downgrade package to version 2:2.99.917+git20160218-1 it works again. 
> (changed source.list to stretch and run sudo apt-get install 
> xserver-xorg-video-intel=2:2.99.917+git20160218-1).
> 
> I have a thinkpad X1 Yoga with processor i7-6500U and there is already 
> problem in linux related to it, see 
> https://bugzilla.kernel.org/show_bug.cgi?id=110941

Interesting, you should have
/usr/lib/xorg/modules/drivers/modesetting_drv.so shipped by
xserver-xorg-core which would be used on Skylake... can you verify it's
there?


-- 
t

Bug#817371: systemd-sysv: circular pre-dependency

[Felipe Sateler]

On 10 March 2016 at 04:15, Andreas Henriksson  wrote:
> Hello all!
>
> Thanks for the bug report and *sigh*.
>
> On Wed, Mar 09, 2016 at 09:15:12PM +0100, Michael Biebl wrote:
>> Control: reassign -1 util-linux
>>
>> Am 09.03.2016 um 20:46 schrieb Bill Allombert:
>> > Package: systemd-sysv
>> > Version: 229-2
>> > Severity: important
>> >
>> > Hello Debian systemd Maintainers,
>> >
>> > There is a circular dependency between systemd-sysv, systemd and 
>> > util-linux:
>> >
>> > systemd-sysv:Pre-Depends: systemd
>> > systemd :Depends: util-linux (>= 2.27.1)
>> > util-linux  :Depends: systemd-sysv
>> >
>> > Circular pre-dependencies are not supported by dpkg.
>>
>> This dependency was introduced by util-linux, so I'm reassigning.
>> I also don't quite understand the alternative dependency on tzdata |
>> systemd-sysv. That's something Andreas most likely can answer.
>
> The reason for tzdata dependency is a bit vague to begin with
> but it's definitely related to the hwclock.sh init script somehow.
> Possibly that can be dropped, but I was hoping it would be safer
> to just append "if you're using systemd, then this dependency is
> definitely optional".
>
> If anyone has any ideas or guesses about why the tzdata dependency was
> introduced to begin with I'd be interested to hear them. The one
> provided by Felipe Sateler sounds very plausible.
>
> For my testing everything worked out  fine here and I was hoping an
> *alternative* would have no real effect, but I guess I was wrong then.
>
> Unless anyone sees any problem I guess the best course of action is to
> just drop both of 'tzdata (>= ...) | systemd-sysv'.

Some more information:

Util-linux bug #660365 (fixed a while ago), changed the hwclock.sh
script to no longer use /etc/localtime. So these are the relevant
snippets:

util-linux (2.12r-13) unstable; urgency=low
 * Move hwclock.sh to 8 since localtime is now a file, not a symlink.
   Adds Depends: tzdata (>=2006c-2)
   Closes: #342887

util-linux (2.20.1-5) unstable; urgency=low
  * Improve handling of the hardware clock
   - Remove redundant hwclockfirst.sh and hwclock.sh.  The reason for
 this redundant script existing (/etc/localtime not being present
 until after /usr was mounted AFAICT) no longer exists.  The
 hwclock script has been adjusted to run before checkroot.
 Closes: #660365

So it seems that the reason for the dependency not only was for
transitional purposes, but also the motive is moot as well as (1)
hwclock no longer reads /etc/localtime and (2) /usr is mounted in the
initramfs.

Semi-related, due to (2), tzdata turned /etc/localtime back into a
symlink on version 2016a-1.

-- 

Saludos,
Felipe Sateler

Bug#817784: xserver-xorg-video-intel: gnome dont load after xserver-xorg-video-intel upgrade

[Mario Geiger]

> Interesting, you should have
> /usr/lib/xorg/modules/drivers/modesetting_drv.so shipped by
> xserver-xorg-core which would be used on Skylake... can you verify it's
> there?

Yes, the file exists.

Bug#817797: openvpn: OpenVPN with LDAP+TLS authentication runs into file exhaustion (again?)

[Mark Dieterich]

Package: openvpn
Version: 2.3.4-5+deb8u1
Severity: important

Dear Maintainer,

With the retirement of squeeze LTS, we've been forced to upgrade our OpenVPN 
server to 
jessie. Unfortunately, we seem to have run across an old bug again (#543941), 
whereby
using LDAP+TLS for authentication of OpenVPN sessions ultimately leads to file 
handle
exhaustion becasue of stale references to /dev/urandom. We had no problems on 
our
squeeze machine with this. I've tried the LD_PRELOAD workaround suggested in 
the 
Readme.Debian doc, but it does not appear to have any affect. I also backported 
the
latest version of OpenVPN (2.3.10-1) and it still suffered from the same issue. 
 It 
appears the original bug reports was resolved because libgcrypt11 was being 
dropped.

Any suggested workarounds? Is this even an OpenVPN bug or should this be 
reported to
the libgcrypt maintainers?

I'm happy to help try and debug this in any way I can.

Thanks!

Mark

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (750, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  init-system-helpers1.22
ii  initscripts2.88dsf-59
ii  iproute2   3.16.0-2
ii  libc6  2.19-18+deb8u3
ii  liblzo2-2  2.08-1.2
ii  libpam0g   1.1.8-3.1+deb8u1
ii  libpkcs11-helper1  1.11-2
ii  libssl1.0.01.0.1k-3+deb8u4

Versions of packages openvpn recommends:
pn  easy-rsa  

Versions of packages openvpn suggests:
ii  openssl 1.0.1k-3+deb8u4
pn  resolvconf  

-- Configuration Files:
/etc/init.d/openvpn changed [not included]

-- debconf-show failed

Bug#817756: pulseaudio: load-module module-alsa-sink device=plug:dmixer breaks choosing path-file

[Jakob Schürz]

Am 2016-03-09 um 23:37 schrieb Felipe Sateler:
> Control: tags -1 moreinfo
> 
> On 9 March 2016 at 18:50, Jakobus Schürz  wrote:
>> Package: pulseaudio
>> Version: 8.0-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> I had for a year a config working on my laptop. I have a asound.conf
>> which defines a dmixer-device. Pulseaudio uses this dmix-device for
>> output (so i can play music from a systemwide-mpd simultanious to watching a
>> video as logged in user).
>>
>> I also have my own configuration on profile-sets and path-files. Because
>> plug in and out my headphones mutet the master and my laptop was totally
>> mutet and didn't get unmutet.
>>
>> This all worked until a short time. Since there, plug in or out my
>> headphones never changed the mute-state from the headphone- and
>> pcm-mixer.
> 
> Maybe you need updating the path files?

Udevadm gives no reaction on plugging the headphones, when this line is
active. Deactivation this line, udevadm monitor gives the correct
reaction...

> 
>>
>> I found out, when i comment out the line
>>
>> load-module module-alsa-sink device=plug:dmixer
> 
> I'm not even sure this is supported.
> 

I just downgraded to PA 7.1-2~bpo8+1, and now it works again as before
upgrade to 8.0.1.
So yes, it IS supported.

>>
>> in /etc/pulse/default.pa, choosing the path works again.
>> But when i comment this line, i can't hear music from mpd, when the
>> pulseaudo from the user is playing sound and vice versa.
>>
>> So now i can choose hearing all the sounds (from user-pulse and
>> systemwide mpd) OR plug in and out some headphones, and change soundpath
>> to headphones or internal speakers... but not both together.
> 
> I suggest make mpd talk to your pulseaudio daemon, and have the daemon
> run permanently instead of just on login.
> 

MPD is talking only to pulseaudio. Two pulse-daemons are running at the
same time (even 3...) One from the logged in user, one from mpd and one
from gdm3.

When every pulseaudio-daemon talkes to the dmix-device, i can hear every
output at the same time. That's what i want.

jakob

Bug#817798: crash fails to load with 4.4+ kernels

[Louis Bouchard]

Package: crash
Version: 7.1.4-1ubuntu1
Severity: normal

Dear Maintainer,

When loading a crash dump on 4.4+ kernel, crash fails to load with the 
following msg :

root@DEVAC02:/var/crash/201603092003# crash 
/usr/lib/debug/boot/vmlinux-4.4.0-11-generic dump.201603092003

crash 7.1.4
Copyright (C) 2002-2015 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.

GNU gdb (GDB) 7.6
Copyright (C) 2013 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 "s390x-ibm-linux-gnu"...

please wait... (gathering module symbol data)
crash: invalid structure member offset: module_core_size
   FILE: kernel.c LINE: 3422 FUNCTION: module_init()

[/usr/bin/crash] error trace: 2aa19f62a78 => 2aa19fe1de6 => 2aa1a026e2c => 
2aa1a026d88

This has been reported upstream here :

https://www.redhat.com/archives/crash-utility/2016-January/msg00031.html

Crash version on Xenial should be upgraded to crash-7.1.5

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages crash depends on:
ii  binutils 2.26-5ubuntu1
ii  libc62.21-0ubuntu6
ii  libncurses5  6.0+20160213-1ubuntu1
ii  libtinfo56.0+20160213-1ubuntu1
ii  zlib1g   1:1.2.8.dfsg-2ubuntu4

crash recommends no packages.

Versions of packages crash suggests:
ii  kexec-tools   1:2.0.10-1ubuntu1
ii  makedumpfile  1:1.5.9-5

-- no debconf information

Bug#817756: pulseaudio: load-module module-alsa-sink device=plug:dmixer breaks choosing path-file

[Jakobus Schürz]

Another issue with pulseaudio 8.0.1 is gone on downgrade to 7.1-2~bpo8+1.

I had troubles with VLC. Changing Volume makes VLC stuttering, it causes
problems in the video (not only sound), and sometimes vlc stops playing
the video. Some underflow-errors where reportet in the output.

Downgrading pulse to backport-versions solved this issue with vlc also.
Even tickeling and volume-spikes on volume-changes in totem and from the
gnome3-panel are gone on the downgrade.

jakob

-- 
Jakobus Schürz
Roseggergasse 37/21
1160 Wien

+43/699/107 66 126

http://xundeenergie.at
http://cogitationum.wordpress.com/
http://verkehrsloesungen.wordpress.com/

Bug#814036: initramfs-tools: mdadm doesn't assemble disk

[Samuel Thibault]

Hello,

Dmitry Smirnov, on Mon 29 Feb 2016 18:46:10 +1100, wrote:
> I tried adding "rootdelay=4" to kernel boot parameters but it did not help.

I had tried rootdelay=15, it didn't help me either.

Samuel

Bug#817795: sysvinit-utils - Contains pre-depends loop

[Petter Reinholdtsen]

[Bastian Blank]
> In sysvinit-utils or somewhere of it's dependency chain is a
> pre-dependency/conflict loop, which apt is unable to break.  This breaks
> the upgrade from Jessie.

Could this be caused by util-linux?  It modified its dependencies
related to initscripts:

util-linux (2.27.1-4) unstable; urgency=medium

  * Drop initscripts dependency now that update-rc.d no longer
requires it to process init scripts with LSB header dependencies.
- note that it's still likely to be installed (even under systemd)
  since it's priority is required, it's just that util-linux no longer
  needs to require it to be around.
  * Add dependency on init-system-helpers (>= 1.29~) which contains
the previously mentioned update-rc.d fix.
- this can be dropped once init-system-helpers is always >= 1.29~.
  * Drop lsb-base dependency
- strictly speaking we should have it since hwclock.sh uses
  lsb-base, but initscripts will pull it in for us anyway under
  sysvinit(-core) so this dependency makes no practical gain.
  Dropping it avoids pulling it in when we don't need it (eg. under
  systemd-sysv where hwclock.sh is masked by the systemd package).
  * Add systemd-sysv as an alternative to tzdata dependency.
- tzdata was according to this changelog added for the benefit of
  the hwclock.sh init script. (Not sure it's required.)
  It's among the top size of debootstrap --variant=minbase packages
  so might be useful to make it uninstallable on minimal containers,
  which this change should accomplish (under systemd-sysv atleast).
  * Finally move sysvinit-utils back to Breaks instead of Depends
- now that initscript dependency is dropped, the issue with cyclic
  dependency should be no more and we can properly describe the
  relation.
  * Add debian/patches/build-sys-use-PKG_CONFIG.patch
- cherry-picked from upstream git, fixes crossbuilding (Closes: #811546)

 -- Andreas Henriksson   Thu, 03 Mar 2016 14:30:19 +0100

-- 
Happy hacking
Petter Reinholdtsen

Bug#817115: [Pkg-utopia-maintainers] Bug#817115: [network-manager] Wireless Device Support Regression (wext)

[Antonio Russo]

Upstream has posted a patch which resolves this bug. Thanks for the guidance!

Bug#817784: xserver-xorg-video-intel: gnome dont load after xserver-xorg-video-intel upgrade

[Timo Aaltonen]

10.03.2016, 15:23, Mario Geiger kirjoitti:
>> Interesting, you should have
>> /usr/lib/xorg/modules/drivers/modesetting_drv.so shipped by
>> xserver-xorg-core which would be used on Skylake... can you verify it's
>> there?
> 
> Yes, the file exists.

Right, but you also have an xorg.conf somewhere? Try removing at least
the device section from it.

-- 
t

Bug#817799: libotr5: Exploitable integer overflow vulnerability (CVE-2016-2851)

[Michail Bachmann]

Package: libotr5
Version: 4.1.0-7
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

the libotr versions prior to 4.1.1 contain an integer overflow vulnerability.
This can cause buffer overflow that could lead to code execution. The
vulnerability has been assigned the CVE-2016-2851.

You can find more information here:

https://www.x41-dsec.de/lab/advisories/x41-2016-001-libotr/

Sincerely,

Michail Bachmann



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C.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 libotr5 depends on:
ii  libc62.22-2
ii  libgcrypt20  1.6.5-2

libotr5 recommends no packages.

Versions of packages libotr5 suggests:
pn  libotr5-bin  

-- no debconf information

Bug#817801: dd reports incorrect SI units when given USR1 signal

[Rares Marian]

Package: dd
Version: 8.25
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Ran a dd cloning command and request progress.

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

kill -USR1 

   * What was the outcome of this action?

It produces a report of its progress with MB sizes larger than the SI 
units (MiB).


   * What outcome did you expect instead?

The reverse. SI units sizes should be larger because X bytes / 1,048,576 
(for Megabytes) is going to be smaller than X bytes / 1,000,000 (for 
Mibibytes).

Bug#817800: RM: haskell-mtl-compat/experimental -- RoQA; Unneeded compat package; already removed from unstable

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

haskell-mtl-compat was already removed from unstable (#807644), it's
useless in experimental, too.


Andreas

Bug#757529: debnap should run dscverify

[Osamu Aoki]

Hi,

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

This wishlist bug is an interesting one since it does not only execute debsnap
but also execute dscverify before executing debdiff.

Maybe we should run dscverify within debsnap.

If no one complains about this, I will close this bug if this is done.  Having
too much narrow scope commands is bad for us.  If debsnap and debdiff are
enough, we should be happy.  Whenever we need local needs, we can always use
a shell script etc., to cope with such situation.

Regards,

Osamu

Bug#633577: Add EXAMPLE to chdist

[Osamu Aoki]

Hi,

Instead of adding yet-another-narrow-scope-script-no-one-knows, it may be
better to add example to the manpage of the existing tool.

I will close this bug if chdist manpage has example addressing mentor.
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633577

I hope this is OK.

Regards,

Osamu

Bug#817784: xserver-xorg-video-intel: gnome dont load after xserver-xorg-video-intel upgrade

[Mario Geiger]

>>> Interesting, you should have
>>> /usr/lib/xorg/modules/drivers/modesetting_drv.so shipped by
>>> xserver-xorg-core which would be used on Skylake... can you verify it's
>>> there?
>>
>> Yes, the file exists.
>
> Right, but you also have an xorg.conf somewhere? Try removing at least
> the device section from it.

I never created any xorg.conf file. I installed debian and then didn't
change anything in the X configuration.

Bug#817802: chromium: Scrolling over tabs doesn't work as expected.

[Awtul Awtul]

Package: chromium
Version: 49.0.2623.87-1
Severity: normal

Dear Maintainers,

After the last or two last Chromium updates I have to scroll up/down
over tabs twice instead of once to switch between tabs when/if the
mouse pointer is placed outside of/leaves the Chromium window.

Thanks for your work,

Awal

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

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

Versions of packages chromium depends on:
ii  libasound2 1.1.0-1
ii  libatk1.0-02.18.0-1
ii  libavcodec-ffmpeg-extra56  7:2.8.6-1+b1
ii  libavformat-ffmpeg56   7:2.8.6-1+b1
ii  libavutil-ffmpeg54 7:2.8.6-1+b1
ii  libc6  2.22-2
ii  libcairo2  1.14.6-1
ii  libcups2   2.1.3-3
ii  libdbus-1-31.10.8-1
ii  libexpat1  2.1.0-7
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.3-3
ii  libgcc11:5.3.1-11
ii  libgdk-pixbuf2.0-0 2.32.3-1.2
ii  libglib2.0-0   2.46.2-3
ii  libgnome-keyring0  3.12.0-1+b1
ii  libgtk2.0-02.24.30-1
ii  libjpeg62-turbo1:1.4.2-2
ii  libnspr4   2:4.12-1
ii  libnss32:3.23-1
ii  libpango-1.0-0 1.38.1-1
ii  libpangocairo-1.0-01.38.1-1
ii  libpci31:3.3.1-1.1
ii  libspeechd20.8-7
ii  libsrtp0   1.4.5~20130609~dfsg-1.1
ii  libstdc++6 5.3.1-11
ii  libx11-6   2:1.6.3-1
ii  libxcomposite1 1:0.4.4-1
ii  libxcursor11:1.1.14-1+b1
ii  libxdamage11:1.1.4-2+b1
ii  libxext6   2:1.3.3-1
ii  libxfixes3 1:5.0.1-2+b2
ii  libxi6 2:1.7.6-1
ii  libxml22.9.3+dfsg1-1
ii  libxrandr2 2:1.5.0-1
ii  libxrender11:0.9.9-2
ii  libxslt1.1 1.1.28-2.1
ii  libxss11:1.2.2-1
ii  libxtst6   2:1.2.2-1+b1
ii  x11-utils  7.7+3
ii  xdg-utils  1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1.07.4-1

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#814145: please backport to jessie!

[Antoine Beaupré]

On 2016-02-18 18:54:47, Adam Borowski wrote:
>> please backport to jessie!
>
> As endless-sky migrated to testing today, I've just uploaded a backport.
>
>> I have tried using the packages from sid, the Ubuntu PPA (trusty and
>> vivid), and all of them segfaulted shortly after the UI showed up.
>>
>> When building from the git source (scons; ./endless-sky), everything
>> works fine and I was able to play for hours last night. Which is bad,
>> for my social life and health, but is great from a software
>> perspective. :)
>
> Uh oh... this doesn't exactly sound like a good thing.  Could you please
> file a separate bug report with more information?  Because of your address
> I assume you know how to file a meaningful report.
>
> The package in sid works for me, and as there's already popcon count of 40
> (plus many more users who don't run popcon...), I guess your setup is
> somehow special.

I confirm that the Debian backport works fine in Debian Jessie.

Thanks!

A.

-- 
Les plus beaux chants sont les chants de revendications
Le vers doit faire l'amour dans la tête des populations.
À l'école de la poésie, on n'apprend pas: on se bat!
- Léo Ferré, "Préface"

Bug#817769: [php-maint] Bug#817769: Bug#817769: problem with include_path

[Ivan Sergio Borgonovo]

On 03/10/2016 11:38 AM, Ondřej Surý wrote:

You might be right, the PHP packages stopped building PEAR between
5.6.18 and 5.6.19, because it's a separate source package now and
perhaps the defaults has changed because of this.

I'll investige more later this or next week.


BTW if it can be of help to diagnose the problem, php7 on my workstation 
seems unaffected


ivan@gloom:~$ php7.0 -r 'echo(get_include_path());'
.:/usr/share/php:

But here I dont have php5 installed.

On the other hand on my home server
php7.0-common and php7.0-xml were installed as dependencies of something 
but no other php7 package was installed.


--
Ivan Sergio Borgonovo
http://www.webthatworks.it

Bug#816788: borgbackup-doc: api.html build embeds datetime and i/o charset, thus making package unreproducible

[anarcat]

https://github.com/borgbackup/borg/issues/399

It would be useful to contribute / share information with upstream
regarding this here. 

A.

-- 
Dr. King’s major assumption was that if you are nonviolent, if you
suffer, your opponent will see your suffering and will be moved to
change his heart. He only made one fallacious assumption: In order for
nonviolence to work, your opponent must have a conscience. The United
States has none.
- Stokely Carmichael


signature.asc
Description: Digital signature

Bug#817803: please specify metadata-by-hash

[Peter Palfrader]

Package: apt
Severity: wishlist
X-Debbugs-Cc: debian-...@lists.debian.org

Hi,

apt supports content-addressed metadata files (Translations, Packages, Sources, 
..).

With this feature, we can have significantly more robust Debian mirrors.

Please provide a spec of what apt expects from the archive so our friendly
ftpteam can implement this archive side.

Thanks,

Bug#817804: RFS: tinymux/2.6.5.34-1 NMU

[Stephen Dennis]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

 Package name: tinymux
 Version : 2.6.5.34-1
 Upstream Author : Stephen Dennis 
 URL : http://www.tinymux.org
 License : GPL
 Section : games

It builds those binary packages:

  tinymux- text-based multi-user virtual world server

To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/tinymux


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

  dget -x 
http://mentors.debian.net/debian/pool/main/t/tinymux/tinymux_2.6.5.34-1.dsc

More information about hello can be obtained from http://www.example.com.

Changes since the last upload:

tinymux (2.6.5.34-1) unstable; urgency=low

  * Non-maintainer upload
  * Fix "FTBFS with GCC 6: narrowing conversion"  (Closes: #811780)
  * Fix "use autotools-dev to update config.{sub,guess} for new arches"
 (Closes: #736863)
  * Fix "[Mayhem] Bug report on tinymux: netmux crashes with exit status
139"  (Closes: #716615)
  * Fix "run dh-autoreconf to update for new architectures"  (Closes: #759448)

 -- Stephen Dennis   Thu, 10 Mar 2016 06:01:09 +


Regards,
Stephen Dennis

Bug#817805: develop a means for apt-get update to learn about new archive signing subkeys

[Peter Palfrader]

Package: apt
Severity: wishlist
X-Debbugs-Cc: debian-...@lists.debian.org, debian-de...@lists.debian.org

We would like to start creating the keys that sign unstable in crypto
tokens, so that they are never seen by a general purpose comuting
devices.

These keys would probably be subkeys of the ftpmaster's archive signing
key.  We can't backup such subkeys sanely.  Tokens might break or
mistakes might be made.

There should be a way for us to easily rotate these signing subkeys.

Ideally, apt would accept any Release file signed by a valid subkey of
an openpgp key it trusts.  Therefore, it needs a way to learn about new,
valid subkeys[*].

Maybe we can ship a set of openpgp key updates on the mirrors next to
the Release file, or somewhere in /project, and apt would merge keys
from there.  Care needs to be taken so we don't start trusting
completely new keys just because they were on a mirror.


We should to figure out a way how to properly do this.


Cheers,
weasel

* and while we're at it, it might also learn about subkey revocations.
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#817806: please upload fresh bugfix (4.4.4)

[Yaroslav Halchenko]

Package: btrfs-tools
Version: 4.4-1
Severity: wishlist

I am experiencing interesting bugs (e.g. fi usage reporting 16.00EiB of
unallocated space), so thought to check if new version would fix it at the
level of tools.  apparently quite a few bugs were addressed since 4.4.

Cheers and thanks in advance!

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

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

Versions of packages btrfs-tools depends on:
ii  e2fslibs1.42.13-1
ii  libblkid1   2.27.1-1
ii  libc6   2.21-6
ii  libcomerr2  1.42.13-1
ii  liblzo2-2   2.08-1.2
ii  libuuid12.27.1-3
ii  zlib1g  1:1.2.8.dfsg-2+b1

btrfs-tools recommends no packages.

btrfs-tools suggests no packages.

-- no debconf information

Bug#817807: needrestart: shouldn't restart xendomains by default

[Samuel Thibault]

Package: needrestart
Version: 1.2-8+deb8u1
Severity: normal

Hello,

Sometimes needrestart proposes to restart the xendomains service, and
that choice is enabled by default. This is not a good idea, since
restarting the xen domains can have very serious consequences.

So even if it is proposed, I'd say the choice shouldn't be enabled by
default.

Thanks,
Samuel

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

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

-- 
Samuel
 tohi.cybercable.fr (212.198.0.3) si une personne se reconnait derriere
 cette adresse que ce soit un pirate ou une victime qu'il se manifeste,
 cette personne pourrait bien etre un petit malin
 -+- Fred in NPC : Maman, y a le routeur qui veut me hacker -+-

Bug#633577: Add EXAMPLE to chdist

[Paul Wise]

On Thu, 2016-03-10 at 14:20 +, Osamu Aoki wrote:

> Instead of adding yet-another-narrow-scope-script-no-one-knows, it may be
> better to add example to the manpage of the existing tool.

I don't think that would be useful.

> I will close this bug if chdist manpage has example addressing mentor.
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633577
> 
> I hope this is OK.

I suggest just tag this bug wontfix and closing it instead.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#817244: exim4-base: cron noise re environment

[The Wanderer]

I get this same behavior.

> The Debian configuration sets add_environment:
> 
> ametzler@argenau:~$ /usr/sbin/exim4 -bP | grep environment
> add_environment = <; PATH=/bin:/usr/bin
> keep_environment =

$ /usr/sbin/exim4 -bP | grep environment
LOG: MAIN
  WARNING: purging the environment.
 Suggested action: use keep_environment and add_environment.

add_environment =
keep_environment =

> Are you using Debian's configuration scheme?

As far as I know, yes; I certainly don't remember making any changes to
it. If my current exim4 configuration is not the Debian default, I'm
reasonably sure that's news to me.

> ametzler@argenau:~$ /usr/sbin/exim4 -bV | tail -n1

$ /usr/sbin/exim4 -bV | tail -n1
Configuration file is /var/lib/exim4/config.autogenerated

> grep -rl _environment /etc/exim4/

$ grep -rl _environment /etc/exim4/
grep: /etc/exim4/passwd.client: Permission denied

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Bug#817808: php-kolab: postrm is buggy, breaks upgrades

[Andreas Beckmann]

Package: php-kolab
Version: 0.6.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid'.
It installed fine in 'sid', then the upgrade to 'experimental' fails.

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

  Preparing to unpack .../php-kolab_1.0.2-1_amd64.deb ...
  Unpacking php-kolab (1.0.2-1) over (0.6.0-2) ...
  /var/lib/dpkg/info/php-kolab.postrm: 11: local: 1.0.2-1: bad variable name
  dpkg: warning: subprocess old post-removal script returned error exit status 2
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/postrm: 11: local: 0.6.0-2: bad variable name
  dpkg: error processing archive 
/var/cache/apt/archives/php-kolab_1.0.2-1_amd64.deb (--unpack):
   subprocess new post-removal script returned error exit status 2
  /var/lib/dpkg/tmp.ci/postrm: 11: local: 0.6.0-2: bad variable name
  dpkg: error while cleaning up:
   subprocess new post-removal script returned error exit status 2
  Processing triggers for libc-bin (2.21-9) ...
  Processing triggers for systemd (229-2) ...
  Processing triggers for fontconfig (2.11.0-6.3) ...
  Processing triggers for udev (229-2) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/php-kolab_1.0.2-1_amd64.deb

There seemes to be some quoting missing quoting ...

remove_module () {
local step=$1 module=$2 inifile=$2.ini package=$3 args=$4
...
}

remove_module $1 kolab php-kolab "$*"
remove_module $1 kolabdummy php-kolab "$*"


Looks like you wanted 

remove_module $1 kolab php-kolab "$@"
remove_module $1 kolabdummy php-kolab "$@"


cheers,

Andreas


php-kolab_1.0.2-1.log.gz
Description: application/gzip

Bug#816919: RFS: newsbeuter/2.9-1 [ITA]

[Nikos Tsipinakis]

On Wed, Mar 09, 2016 at 11:25:01PM +0100, gregor herrmann wrote:
> Thanks for your interest in newsbeuter; I like it and use it daily :)
> And I was looking forward to a version which needs less memory than
> Iceweasel; but for me 2.9 has a massive problem:
> 
> The highlighting feature seems to be broken (no idea if this is a
> problem in newsbeuter or ncurses; I haven't retried to rebuild 2.8-2
> to check). Too show what I mean: I have in my ~/.newsbeuter/config

Apparently this issue was already reported and fixed upstream. Added a patch 
and it should work as intended now.

-- 
Best Regards,
Nikos Tsipinakis

Bug#817263: About ftp-master processes and #817263: mariadb-10.0 removed from unstable

[Scott Kitterman]

On March 10, 2016 2:20:10 AM EST, "Otto Kekäläinen"  wrote:
>Hello Andreas and ftp-masters!
>
>First, thanks to Andreas for looking after the mariadb-10.0 package
>and helping with it.
>
>However, please note that your bug report #817263 did not reach the
>maintainers/uploaders of the mariadb-10.0 package and we had no idea
>that you where requesting cruft removal in parallel with our work.
>Please next time make sure the bug report is CC'd to
>mariadb-10.0@p.b.o or some equivalent address.
>
>The original plan was to wait until the package renaming/refactoring
>process was complete and then file the removal of all correct packages
>in one go. It would have been nice to have a chance to discuss this
>earlier and not just find out things after the fact when somebody else
>did something different, unnecessary and potentially even harmful.
>
>Scott and other FTP-masters: please check with package
>maintainers/uploaders before executing any kind of small or large
>removal requests from non-maintainers.
>
>Andreas: we appreciate your help and QA work and we want you to help
>us in the future too. Please just remember to send an e-mail or file a
>bug against the package so that maintainers can review things the next
>time - do not execute upload or "unupload" actions on your own before
>consulting maintainers first. Thanks!

>From an FTP team perspective that doesn't scale very well.  Perhaps the best 
>way is to have reportbug automatically CC the maintainer on an rm bug.

Scott K

P.S. Apologies for the mess.  I have a copy of all the bugs that got closed and 
will reopen them if no one else gets to it first.

Bug#814036: initramfs-tools: mdadm doesn't assemble disk

[Samuel Thibault]

Samuel Thibault, on Thu 10 Mar 2016 14:45:20 +0100, wrote:
> Dmitry Smirnov, on Mon 29 Feb 2016 18:46:10 +1100, wrote:
> > I tried adding "rootdelay=4" to kernel boot parameters but it did not help.
> 
> I had tried rootdelay=15, it didn't help me either.

Ok, I had to increase that to 45 seconds to get it working
automatically.  Leaving notes here for people with the same problem,
needing a workaround until this gets fixed.

More precisely, here is the boot log with that I get with rootdelay=15
only:

[5.720053] floppy0: no floppy controllers found
[5.729329] work still pending

Here it pauses for about 10 seconds more, i.e. up to the rootdelay, then
this:

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
Warning: starting local-top mdadm
Warning: MD_DEVS is all
Begin: Assembling all MD arrays ... mdadm: No devices listed in conf file were 
found.
Failure: failed to assemble all arrays.
done.

I.e. it failed to assemble. Then it pauses again for about 15 more seconds.

[   32.775174] scsi0 : ioc0: LSISAS1068E B3, FwRev=00192f00h, Ports=1, 
MaxQ=266, IRQ=16

At last scsi responds...

[   32.828520] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 0, phy 
0, sas_addr 0x5000cca00758d704
[   32.848561] scsi 0:0:0:0: Direct-Access HITACHI  HUS151414VLS300  A48B 
PQ: 0 ANSI: 5
[   32.869051] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 1, phy 
1, sas_addr 0x5000cca00759b0d4
[   32.889048] scsi 0:0:1:0: Direct-Access HITACHI  HUS151414VLS300  A48B 
PQ: 0 ANSI: 5
[   32.909548] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 4, phy 
4, sas_addr 0x12210400
[   32.931826] scsi 0:0:2:0: Direct-Access ATA  Samsung SSD 850  2B6Q 
PQ: 0 ANSI: 5
[   32.951748] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 5, phy 
5, sas_addr 0x12210500
[   32.974070] scsi 0:0:3:0: Direct-Access ATA  Samsung SSD 850  2B6Q 
PQ: 0 ANSI: 5
[   33.003539] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   33.014259] sd 0:0:0:0: [sda] 286749480 512-byte logical blocks: (146 GB/136 
GiB)
[   33.029511] sd 0:0:1:0: Attached scsi generic sg1 type 0
[   33.040297] sd 0:0:2:0: Attached scsi generic sg2 type 0
[   33.050973] sd 0:0:3:0: [sdd] 2000409264 512-byte logical blocks: (1.02 
TB/953 GiB)
[   33.066336] sd 0:0:1:0: [sdb] 286749480 512-byte logical blocks: (146 GB/136 
GiB)
[   33.081347] sd 0:0:2:0: [sdc] 2000409264 512-byte logical blocks: (1.02 
TB/953 GiB)
[   33.096778] sd 0:0:3:0: Attached scsi generic sg3 type 0
[   33.107452] sd 0:0:0:0: [sda] Write Protect is off
[   33.120484] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, 
supports DPO and FUA
[   33.137758] sd 0:0:1:0: [sdb] Write Protect is off
[   33.148356] sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, 
supports DPO and FUA
[   33.165631] sd 0:0:3:0: [sdd] Write Protect is off
[   33.175250] sd 0:0:2:0: [sdc] Write Protect is off
[   33.185825] sd 0:0:3:0: [sdd] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   33.203960] sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   33.229427]  sdd: sdd1
[   33.234218]  sdc: sdc1
[   33.246768] sd 0:0:3:0: [sdd] Attached SCSI disk
[   33.257655] sd 0:0:2:0: [sdc] Attached SCSI disk
[   33.281649]  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 >
[   33.292320]  sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 sdb8 sdb9 >
[   33.312635] sd 0:0:0:0: [sda] Attached SCSI disk
[   33.323737] sd 0:0:1:0: [sdb] Attached SCSI disk
[   33.333010] random: nonblocking pool is initialized
[   33.606845] device-mapper: uevent: version 1.0.3
[   33.616518] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: 
dm-de...@redhat.com
done.
Begin: Running /[   33.640698] PM: Starting manual resume from disk
scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... 
done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.

etc.

When I set rootdelay to 45, scsi responds at 32s, and assembly is tried
at 45s and can now succeed.

Samuel

Bug#817809: sbuild: breaks if the binnmu changelog contains a newline

[Emilio Pozuelo Monfort]

Package: sbuild
Version: 0.68.0-1
Severity: important

Hi,

I scheduled a binNMU with a newline in the changelog entry (by mistake
because of some copy&paste from an email), and that broke the buildds.

It'd be good to either accept that or at least fail gracefully.

Emilio

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

[Manuel A. Fernandez Montecelo]

Control: tags -1 - moreinfo + pending


Hi,

2016-03-09 15:31 Vincent Lefevre:


But I notice the same issue on a different machine, where last in
/var/log/aptitude, I get:

Aptitude 0.7.8: log report
Mon, Mar  7 2016 14:22:40 +0100

but:

-rw-r--r-- 1 root root 9490347 2016-03-07 14:04:58 pkgstates
-rw-r--r-- 1 root root 9489801 2016-03-07 14:03:27 pkgstates.old

with lots of "Upgrade: yes" in pkgstates (all these packages
are at their latest version, so that the bug is not visible
when running aptitude).


I detected the (I think) only one case where it didn't remove "Upgrade:
yes" lines as soon as the package is in the desired version, and forces
to write pkgstates in that case, so I think that this will be fixed now.

If this keeps happening in the next versions, please reopen.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#817763: Please backport pinentry-gtk2 to jessie-backports

[Daniel Kahn Gillmor]

Control: tags 817763 + pending

On Wed 2016-03-09 17:38:46 -0500, segfault wrote:

> pinentry > 0.9.6 supports copy/paste. This makes it more usable with
> KeePassX, so we'd like to ship pinentry-gtk2 > 0.9.6 in Tails [1]. It
> would be great if someone would backport it.

I've just built, tested, and uploaded 0.9.7-5_bpo8+1 to
jessie-backports.  Please let me know if it doesn't meet your needs.

 --dkg


signature.asc
Description: PGP signature

Bug#817810: emscripten: FTBFS when built with dpkg-buildpackage -A (ln: failed to create symbolic link)

[Santiago Vila]

Package: src:emscripten
Version: 1.22.1-1
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   dh_auto_test -i
 fakeroot debian/rules binary-indep
dh binary-indep --with python2
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
rm -f system/include/libcxx/LICENSE.txt system/lib/compiler-rt/LICENSE.TXT 
system/lib/libcxx/LICENSE.txt system/lib/libcxxabi/LICENSE.TXT 
tests/bullet/LICENSE tests/enet/LICENSE 
tests/freetype/LiberationSansBoldLICENSE.txt tests/freetype/docs/LICENSE.TXT 
tests/openjpeg/LICENSE tests/python/LICENSE tests/sounds/LICENSE.txt 
tests/poppler/COPYING tests/freetype/LiberationSansBoldLICENSE.txt 
tests/freealut/COPYING tests/bullet/COPYING system/lib/libcxx/LICENSE.txt 
system/lib/libcxxabi/LICENSE.TXT tests/bullet/BulletLicense.txt 
system/include/SDL/COPYING tests/enet/docs/license.dox tests/box2d/License.txt 
tests/box2d/freeglut/COPYING tools/node_modules/source-map/LICENSE 
tools/node_modules/source-map/node_modules/amdefine/LICENSE 
tests/freetype/docs/GPL.TXT
rm -f tools/eliminator/node_modules/uglify-js/.gitignore
rm -f `find . -iname '*.vcproj' -o -iname '*.sln' -o -iname '*.dsp' -o -iname 
'*.dsw'`
chmod +x tests/embind/build_benchmark
dh_install
mkdir -p /<>/debian/emscripten/usr/bin
cd /<>/debian/emscripten/usr/bin; \
for f in em++ emar emcc emcc.py em-config emconfigure emmake emranlib 
emscripten.py emscons; do \
ln -s ../share/emscripten/$f; \
done
cd 
/<>/debian/emscripten/usr/share/emscripten/tools/eliminator/node_modules/uglify-js/;
 \
rm -rf lib/* bin/uglifyjs; \
ln -s /usr/bin/uglifyjs bin/; \
cd lib; for f in /usr/lib/nodejs/uglify-js/*; do ln -s $f .; done
/bin/sh: 1: cd: can't cd to 
/<>/debian/emscripten/usr/share/emscripten/tools/eliminator/node_modules/uglify-js/
ln: target 'bin/' is not a directory: No such file or directory
/bin/sh: 4: cd: can't cd to lib
ln: failed to create symbolic link './package.json': File exists
ln: failed to create symbolic link './tools': File exists
debian/rules:15: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:11: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.

Bug#803828: karlyriceditor: FTBFS with FFmpeg 2.9

[Martin Steghöfer]

Felipe Sateler wrote:

Please update the changelog fully to add the bug closure and upload
distro (if you want, you can do it on a different branch that is only
merged to master once the package is in the archive).


Sorry. Please find the updated changelog in 
https://github.com/martin-steghoefer/debian-karlyriceditor/commits/1.11-2 (branch 
"1.11-2" of the same repository as before).


Cheers,
Martin

Bug#817263: About ftp-master processes and #817263: mariadb-10.0 removed from unstable

[Andreas Beckmann]

Oops, what happened here?

Complete removal of mariadb-10.0 from unstable was of course not my
intention. (And so far I cannot remember any of my (many many) RoQA RM
requests causing such fallout.) Only some of the obsolete packages
should go away, since automatic cruft removal sometimes has problems if
both arch:all and arch:any packages are involved.

Hmm, my Subject translated into a valid dak command ... which was used
instead of the one that I pasted from the cruft report. If I had used
  RM: mariadb-test [all] -- RoQA; obsolete arch:all package
instead, nothing (unexpected) would have happened. (But I only realized
right now that mariadb-test switched from all to any)

> From an FTP team perspective that doesn't scale very well.

And RMs are usually moreinfo-ed if they cause dependency problems.

> Perhaps the best way is to have reportbug automatically CC the
maintainer on an rm bug.

Which sounds like a good idea.

Sorry for the mess and extra work this causes.


Andreas