Bug#852545: Config file in xen-hypervisor package likely causes problems on upgrade

[Ian Jackson]

Control: tags -1 - stretch-ignore
Control: tags -1 + buster sid

stretch-ignore would be to ignore an RC bug (which this isn't).  Sorry
for the confusion.

Ian.

Bug#852600: atop: Please drop dependency on initscripts package

[Marc Haber]

On Wed, Jan 25, 2017 at 03:30:26PM +0100, Michael Biebl wrote:
> Am 25.01.2017 um 15:26 schrieb Marc Haber:
> > severity #852600 wishlist
> > tags #852600 confirmed pending
> > merge #852600 #852239
> > thanks
> > 
> > this is a dupe of another bug that is already in the pipe.
> 
> Ah, sorry for that. It didn't show up at [1], that's why I filed it.

No problem, I don't expect you to manually review all packages before
doing an MBF.

Greetings
Marc

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

Bug#852600: atop: Please drop dependency on initscripts package

[Michael Biebl]

Am 25.01.2017 um 15:26 schrieb Marc Haber:
> severity #852600 wishlist
> tags #852600 confirmed pending
> merge #852600 #852239
> thanks
> 
> this is a dupe of another bug that is already in the pipe.

Ah, sorry for that. It didn't show up at [1], that's why I filed it.

Thanks for the quick response.

Michael


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

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



signature.asc
Description: OpenPGP digital signature

Bug#852600: atop: Please drop dependency on initscripts package

[Marc Haber]

reassign #852239 src:atop
merge #852600 #852239
thanks

trying the merge again.

Greetings
Marc

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

Bug#852600: atop: Please drop dependency on initscripts package

[Marc Haber]

severity #852600 wishlist
tags #852600 confirmed pending
merge #852600 #852239
thanks

this is a dupe of another bug that is already in the pipe.

Greetings
Marc

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

Bug#852601: API key is not available

[Haruki TSURUMOTO]

Package: minitube
Version: 2.5.2-2
Severity: important

Dear maintainer,
minitube requires YouTube API keys.(IMO, it required at build time)
Upsteram's binary package (http://flavio.tordini.org/minitube) is
usable,But Debian version is not.

Thanks.
-- 
Haruki TSURUMOTO
PGP Fingerprint:3718 C84E 4EDA 1B5C 4F26 8639 9D3D EE3F 63A6 000E


```
$ uname -a
Linux debian-vm-tsr 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02)
x86_64 GNU/Linux
$ minitube --version
Minitube 2.5.2

Usage: minitube [options]
Options:
  --toggle-playing  Start or pause playback.
  --nextSkip to the next video.
  --previousGo back to the previous video.
  --stop-after-this Stop playback at the end of the video.

$ minitube
QIODevice::read (QFile, ":/functions.js"): device not open
No available API keys
403 "Error transferring
https://www.googleapis.com/youtube/v3/videoCategories?part=snippet=ja-JP=us
- server replied: Forbidden"
QNetworkReply::NetworkError(ContentOperationNotPermittedError)
403 "Error transferring
https://www.googleapis.com/youtube/v3/videos?part=snippet,contentDetails,statistics=mostPopular=1
- server replied: Forbidden"
QNetworkReply::NetworkError(ContentOperationNotPermittedError)
403 "Error transferring
https://www.googleapis.com/youtube/v3/videoCategories?part=snippet=en=us
- server replied: Forbidden"
QNetworkReply::NetworkError(ContentOperationNotPermittedError)
403 "Error transferring
https://www.googleapis.com/youtube/v3/search?part=snippet=video=50=ppap
- server replied: Forbidden"
QNetworkReply::NetworkError(ContentOperationNotPermittedError)
"Error transferring
https://www.googleapis.com/youtube/v3/search?part=snippet=video=50=ppap
- server replied: Forbidden"
```




signature.asc
Description: OpenPGP digital signature

Bug#852600: atop: Please drop dependency on initscripts package

[Michael Biebl]

Source: atop
Version: 2.2.3-1~exp1
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: initscripts-dep

Hi,

your package atop declares a dependency on the initscripts
package.

Please check, if this dependency is actually needed and remove it
otherwise. On a system using systemd, the initscripts package is no
longer required. Removing the dependency from your package will allow
users to remove the initscripts package from their system.

Afaics, the dependency was added for the /run transition. This already
happened in wheezy, so this (versioned) dependency is no longer needed.

Regards,
Michael



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

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

Bug#852596: iio-sensor-proxy: spams syslog with an error message every second

[Julien Cristau]

On 01/25/2017 03:12 PM, Ritesh Raj Sarraf wrote:
> Control: forward -1 https://github.com/hadess/iio-sensor-proxy/issues/134
> 
> On Wed, 2017-01-25 at 14:55 +0100, Julien Cristau wrote:
>> iio-sensor-prox[574]: Could not open input accel '/dev/input/event9':
>> Operation not permitted
> 
>> about once a second.  I don't know why that package is installed or what
>> it does but filling up syslog seems like the wrong thing to do
>> regardless.  /dev/input/event9 is identified as "Acer BMA150
>> accelerometer", fwiw.
> 
> The package gets pulled in mostly because GNOME Shell recommends it. If you
> don't use it, you can consider removing it.
> 
> The package is useful on machines that have an orientation sensor. This sensor
> is commonly seen on hybrid laptops that can also be used as a tablet.
> 
> Recently, on debian-user, an Acer user reported similar issue. This is known 
> to
> be a kernel bug. I'm not sure if this fix will be backported to the 4.9 tree.
> And if that fix can fix your bug in particular.
> 
Thanks.  I think regardless of the kernel bug, iio-sensor-proxy should
just print the error once, not over and over again.

Cheers,
Julien

Bug#852599: texlive-latex-recommended, texlive-latex-recommended-doc: Replaces without Breaks make files disappear from other installed packages

[Andreas Beckmann]

Package: texlive-latex-recommended,texlive-latex-recommended-doc
Version: 2016.20170123-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

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

The installation sequence to reproduce this problem is

  apt-get install $VICTIM
  # (1)
  apt-get install $OFFENDER
  apt-get remove $OFFENDER
  # (2)

for
  VICTIM   texlive-latex-extra-doc=2016.20161130-1
  OFFENDER texlive-latex-recommended-doc=2016.20170123-1
and
  VICTIM   texlive-latex-extra=2016.20161130-1
  OFFENDER texlive-latex-recommended=2016.20170123-1

Note that these are valid partial stretch->sid upgrades.

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


4m35.6s ERROR: FAIL: After purging files have disappeared:
  /usr/share/texlive/texmf-dist/tex/latex/filehook/filehook-fink.sty owned 
by: texlive-latex-recommended
  /usr/share/texlive/texmf-dist/tex/latex/filehook/filehook-listings.sty
 owned by: texlive-latex-recommended
  /usr/share/texlive/texmf-dist/tex/latex/filehook/filehook-memoir.sty   owned 
by: texlive-latex-recommended
  /usr/share/texlive/texmf-dist/tex/latex/filehook/filehook-scrlfile.sty
 owned by: texlive-latex-recommended
  /usr/share/texlive/texmf-dist/tex/latex/filehook/filehook.sty  owned by: 
texlive-latex-recommended
  /usr/share/texlive/texmf-dist/tex/latex/filehook/pgf-filehook.sty  owned 
by: texlive-latex-recommended

4m35.6s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/texlive-latex-extra.listnot owned


3m9.4s ERROR: FAIL: After purging files have disappeared:
  /usr/share/doc/texlive-doc/latex/filehook/README   owned by: 
texlive-latex-recommended-doc
  /usr/share/doc/texlive-doc/latex/filehook/filehook.pdf owned by: 
texlive-latex-recommended-doc

3m9.4s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/texlive-latex-extra-doc.listnot owned


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

Filing only as important to not block migration before the freeze.
Please add Breaks matching all Replaces in the next upload.


cheers,

Andreas

Bug#852596: iio-sensor-proxy: spams syslog with an error message every second

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: forward -1 https://github.com/hadess/iio-sensor-proxy/issues/134

On Wed, 2017-01-25 at 14:55 +0100, Julien Cristau wrote:
> iio-sensor-prox[574]: Could not open input accel '/dev/input/event9':
> Operation not permitted
> 
> about once a second.  I don't know why that package is installed or what
> it does but filling up syslog seems like the wrong thing to do
> regardless.  /dev/input/event9 is identified as "Acer BMA150
> accelerometer", fwiw.

The package gets pulled in mostly because GNOME Shell recommends it. If you
don't use it, you can consider removing it.

The package is useful on machines that have an orientation sensor. This sensor
is commonly seen on hybrid laptops that can also be used as a tablet.

Recently, on debian-user, an Acer user reported similar issue. This is known to
be a kernel bug. I'm not sure if this fix will be backported to the 4.9 tree.
And if that fix can fix your bug in particular.

Reference: https://github.com/hadess/iio-sensor-proxy/issues/134



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

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliIsjsACgkQpjpYo/Lh
dWmZyw/+OwSTmpf4vZHeZHRTc1HcJHTZRJIemuGXxyOWMLpb8QzwZDLGNeCWa+AX
M68FO0Cnagf/zuVc2L4gnf8Wvw3VbhOJeMEWbvGtom6wpXU1elStojLsKkC9Wz+b
44fZvtiWSHKCdoP6Li7gNZYqRprosN4kiU7qBTrE1Cv0P/mA27XBb0UkpedoIlhe
jvEnnjsPvfVvtEyooT2CNfxrc9mbhHLu407zIbzIr984vGOnatdDnTINA73wR3Pl
5f1Zbt/O7r18ayBf6iXIUqbmojz7vSYykOoBw44mAYswTIpLOtB9jai1kXyQCKjV
ogbNHrVmgh/e/i/GqMuC/vABA5187LO7wo9pylZgu3tPWx+dGdcZnitjc4PLw+H+
A47wtC9egK9wn5ofUKGEuRzN+LPDLiuZcexRWkpS8yjGSvJyE+MoPBKnWbxgtJJx
QTVTI807WDiYg70EXwIOfLi3dE7Hf7bFfTjsvatuTOjthgyWpF71icu6ZaXzPf/u
YUCxCgsGhbsYYW732lCUB6G4wv6JANf5AaO0Z9cyD/HP/5gZbaUWRJEEtFlvWQqH
64Sg6QB2rr+r8N3FIVbbMYklCqywntW7T8uLZ6BzZ0S/nrkPzTNjSgZ0Ro1soeNY
7lLTxqk7cJ1KivwvGAwPkoloh4cVeMI/DRaGnzrYi1gssBw2Z5U=
=dpl+
-END PGP SIGNATURE-

Bug#852524: qt3d5-dev ships broken symlinks

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 pending

On miércoles, 25 de enero de 2017 07:35:02 ART Johannes Schauer wrote:
[snip] 
> I guess some Depends are missing from the package?

Yes, when I rebumped the packaging I forgot this. Thanks a lot!

-- 
Without us [Free Software developers], people would study computer science
and programming without ever having seen a real program in its entirety.
That's like becoming writers without ever having read a complete book.
  Matthias Ettrich, founder of the KDE project.
  http://www.efytimes.com/efytimes/25412/news.htm

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

[Simon McVittie]

On Wed, 25 Jan 2017 at 12:52:13 +, Simon McVittie wrote:
> With that incompatibility out of the way, there's another one:
> 
> Jan 25 12:28:31 host gdm-session-worker.really[11355]: 
> pam_unix(gdm-password:auth): conversation failed
> Jan 25 12:28:31 host gdm-session-worker.really[11355]: 
> pam_unix(gdm-password:auth): auth could not identify password for [user]

I think this might be caused by gnome-shell raising an exception when
it fails to load an animation, with the traceback below, and the PAM
conversation not proceeding because gnome-shell is no longer talking
to the gdm-session-worker as a result of that exception.

> Jan 25 12:28:14 host gnome-session[5143]: (gnome-shell:5342): Gjs-WARNING 
> **: JS
>  ERROR: Exception in callback for signal: next: Error: can't convert 
> this._frame
>  to an integer
> Jan 25 12:28:14 host gnome-session[5143]: 
> Animation<._showFrame@resource:///org/
> gnome/shell/ui/animation.js:59
> Jan 25 12:28:14 host gnome-session[5143]: 
> wrapper@resource:///org/gnome/gjs/modules/lang.js:169
> Jan 25 12:28:14 host gnome-session[5143]: 
> Animation<.play@resource:///org/gnome/shell/ui/animation.js:34
> Jan 25 12:28:14 host gnome-session[5143]: 
> wrapper@resource:///org/gnome/gjs/modules/lang.js:169
> Jan 25 12:28:14 host gnome-session[5143]: 
> AuthPrompt<.setActorInDefaultButtonWell@resource:///org/gnome/shell/gdm/authPrompt.js:313
> Jan 25 12:28:14 host gnome-session[5143]: 
> wrapper@resource:///org/gnome/gjs/modules/lang.js:169
> Jan 25 12:28:14 host gnome-session[5143]: 
> AuthPrompt<.startSpinning@resource:///org/gnome/shell/gdm/authPrompt.js:329
> Jan 25 12:28:14 host gnome-session[5143]: 
> wrapper@resource:///org/gnome/gjs/modules/lang.js:169
> Jan 25 12:28:14 host gnome-session[5143]: 
> AuthPrompt<._init/<@resource:///org/gnome/shell/gdm/authPrompt.js:67
> Jan 25 12:28:14 host gnome-session[5143]: 
> _emit@resource:///org/gnome/gjs/modules/signals.js:124
> Jan 25 12:28:14 host gnome-session[5143]: 
> AuthPrompt<._initButtons/<@resource:///org/gnome/shell/gdm/authPrompt.js:191

That looks like https://bugzilla.redhat.com/show_bug.cgi?id=1350303
which is some sort of install-order issue, or possibly the existing
gnome-shell trying to use the old pixbuf loader cache that has been
invalidated in the meantime by upgrading.

There is a workaround for that bug in stretch's gnome-shell, added
by ;
but of course during a live upgrade we're still dealing with jessie's
gnome-shell, not stretch's, so we can't fix bugs.

S

Bug#852598: patch - fix crashes in atril's and evince's thumbnailers on some PDFs

[Vlad Orlov]

Source: poppler
Version: 0.48.0-2
Severity: normal
Tags: patch upstream fixed-upstream
Control: forwarded -1 https://bugs.freedesktop.org/97870
Control: affects -1 atril evince


Due to a bug in poppler [1], thumbnailers of atril and evince were crashing
on some PDFs. It had been fixed upstream in version 0.50.0. Please apply
the patch to 0.48.0 in Sid and Stretch (the debdiff is in the attachment).
If possible, please also patch poppler 0.26.5 in Jessie.

You can find some PDFs for reproducing the crash at [1][2][3][4].


[1] https://bugs.freedesktop.org/97870
[2] https://bugs.launchpad.net/bugs/1635812
[3] https://github.com/mate-desktop/atril/issues/222
[4] https://github.com/mate-desktop/atril/issues/234

poppler-stretch-debdiff
Description: Binary data

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Julien Cristau]

Package: iio-sensor-proxy
Severity: serious
Version: 2.0-1

I just purged iio-sensor-proxy, but:

$ ps 574
  PID TTY  STAT   TIME COMMAND
  574 ?Ssl4:10 /usr/sbin/iio-sensor-proxy

The process should stop running on removing the package.

Cheers,
Julien

Bug#852596: iio-sensor-proxy: spams syslog with an error message every second

[Julien Cristau]

Package: iio-sensor-proxy
Version: 2.0-1
Severity: important

Dear Maintainer,

my syslog is full of messages like

iio-sensor-prox[574]: Could not open input accel '/dev/input/event9':
Operation not permitted

about once a second.  I don't know why that package is installed or what
it does but filling up syslog seems like the wrong thing to do
regardless.  /dev/input/event9 is identified as "Acer BMA150
accelerometer", fwiw.

Cheers,
Julien

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

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

Versions of packages iio-sensor-proxy depends on:
ii  libc6   2.24-8
ii  libglib2.0-02.50.2-2
ii  libgudev-1.0-0  230-3
ii  systemd 232-8

iio-sensor-proxy recommends no packages.

iio-sensor-proxy suggests no packages.

-- no debconf information

Bug#757851: accessibility: orca says always "not selected"

[Mike Gabriel]

Control: tags -1 - pending

Hi,

On  Mo 11 Aug 2014 21:27:40 CEST, Jean-Philippe MENGUAL wrote:


Package: caja
Version: 1.8.1-2
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where  
appropriate ***


   * What led up to the situation?

I use Orca, screen reader, to vocalize MATE. For this I export gail  
and atk-bridge

GTK_MODULES. I open caja and try to select several files.

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

I press shift key, then arrow keys, to choose the files I want to  
select. They

are selected, since I can copy, move or remove them.

   * What was the outcome of this action?

But orca (gnome-orca) says "not selected".

   * What outcome did you expect instead?

It should say "selected", and nothing when nothing is selected. I'll  
forward to

Orca team too, but I think Orca speaks this because a wrong info are sent to
at-spi.

*** End of the template - remove these template lines ***

Thanks,


This issue has been tagged as pending, which is a false tag. Upstream  
has a fix for GTK-2 build of caja, but not for the GTK-3 build.


Thus, removing the "pending" tag.

Mike
--

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

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



pgpUVyXnkr8jw.pgp
Description: Digitale PGP-Signatur

Bug#852557: bucklespring: FTBFS on non-linux architectures

[Dominik George]

Source: bucklespring
Version: 1.4.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
Control: forwarded -1 https://github.com/zevv/bucklespring/issues/44

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

bucklespring only implements the scan() function for Windows, macOS and
Linux, which means the package cannot build on non-linux architectures
in Debian:

gcc -o buckle  main.o scan-linux.o scan-windows.o scan-mac.o  -fPIE -pie 
-Wl,-z,relro -Wl,-z,now -g -lalure -lopenal -lXtst -lX11 
main.o: In function 
ain':
./main.c:143: undefined reference to can'
./main.c:109: undefined reference to en_console'
collect2: error: ld returned 1 exit status

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

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

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAliIqxsxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pbgJQ/+O/PjLJByqdSR9BW30a31EXP6y8io
I/pslikalBgjxdq/+WwaJiQzOI+sr38tMxHqC02YyxK2MuKBVieIIgUc5sEu71Z2
rKIL2pKPXdKsHkqE4IUASCOlrKK4Y14lHe3WvA7RDuk1HTWKcbRyGoCjqoflZVaq
LlXk1WVdAIPkWSM4fR9O1NieQWcniu0F1iwtYd6W9tZIkhJnlG0+XYHLlpq+kUwN
6M+KSbwbG3b+UKdaq2wH+aCe3FINK4Ueu28iwdkgmK3C4laF9WWYZ09nDZ24yWUD
XLOIcoAuqqWsCftJQGAEY+cCNF3y9EjI8kFdcqEWV0pKRCoeECmteBQuPevRtWWK
IPeMp4UkF/pCTYiSD2lydfARk0c01IHSaOyfgZXuP1Y0uSK5PTEfqsjJWGDEKoPd
oKo20bn/wCgp9y9AlyPvDn5P6xMdt3+AORQ+TiTkMH1lOEfsKe0+83YujMpepB/M
cRJDKVH0CvtQ/ZbSW4l/F2ZfVuG8zPv3S8FhTvSPjzIAqZ5OUJYu6xzXckURR9m2
EKx7BH+lqsd0VJ5R8tWLQi+YJorcyexrfLYHehEtG4Vb5kFVn1ZvSvTrKpySMbdb
8oNNZFPg1QLeN6m2V7EEKf2bF0nqEncBfRakTSDcTaVuvanW7ETOiaZ7tJ8DdjZS
uDVgNqwsZhGoW9I=
=awqR
-END PGP SIGNATURE-

Bug#852556: linux-image-4.9.0-1-amd64: [Regression] Trendnet's TU-ET100C Pegasus II based LAN to USB adapter stopped to work

[Lisandro Damián Nicanor Pérez Meyer]

Package: src:linux
Version: 4.9.2-2
Severity: important

Hi! Running this version of the kernel I get:

[   86.479474] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet 
driver
[   86.480195] [ cut here ]
[   86.480219] WARNING: CPU: 0 PID: 2043 at 
/build/linux-fgnWKv/linux-4.9.2/drivers/usb/core/hcd.c:1584 
usb_hcd_map_urb_for_dma+0x37c/0x570 [usbcore]
[   86.480221] transfer buffer not dma capable
[   86.480223] Modules linked in: pegasus(+) mii pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport iptable_filter 8021q 
garp mrp stp llc uinput binfmt_misc wl(POE) iTCO_wdt iTCO_vendor_support 
dell_wmi sparse_keymap dell_rbtn pcmcia kvm_intel dell_laptop dell_smbios 
dcdbas snd_hda_codec_hdmi kvm dell_smm_hwmon snd_hda_codec_idt i915 
snd_hda_codec_generic irqbypass cfg80211 yenta_socket evdev pcmcia_rsrc 
pcmcia_core joydev pcspkr snd_hda_intel serio_raw snd_hda_codec lpc_ich 
snd_hda_core mfd_core sg snd_hwdep snd_pcm rfkill snd_timer snd soundcore 
drm_kms_helper shpchp wmi drm i2c_algo_bit acpi_cpufreq video ac battery button 
tpm_tis tpm_tis_core tpm coretemp parport_pc ppdev lp parport ip_tables 
x_tables autofs4 ext4 crc16 jbd2 fscrypto ecb lrw glue_helper ablk_helper cryptd
[   86.480294]  aes_x86_64 mbcache xts gf128mul algif_skcipher af_alg dm_crypt 
dm_mod raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear 
md_mod sr_mod cdrom sd_mod psmouse i2c_i801 i2c_smbus ahci libahci libata 
sdhci_pci sdhci scsi_mod mmc_core firewire_ohci firewire_core crc_itu_t tg3 ptp 
pps_core libphy ehci_pci uhci_hcd ehci_hcd thermal usbcore usb_common
[   86.480339] CPU: 0 PID: 2043 Comm: systemd-udevd Tainted: P   OE   
4.9.0-1-amd64 #1 Debian 4.9.2-2
[   86.480341] Hardware name: Dell Inc. Latitude E5500  
/0X796D, BIOS A08 01/05/2009
[   86.480343]   9f728b84 b14681eef840 

[   86.480347]  9f476dbe a05a571ffd80 b14681eef898 

[   86.480351]  b14681eefa4c a05a558e7000 0001 
9f476e3f
[   86.480354] Call Trace:
[   86.480361]  [] ? dump_stack+0x5c/0x78
[   86.480365]  [] ? __warn+0xbe/0xe0
[   86.480368]  [] ? warn_slowpath_fmt+0x5f/0x80
[   86.480372]  [] ? schedule+0x32/0x80
[   86.480382]  [] ? usb_hcd_map_urb_for_dma+0x37c/0x570 
[usbcore]
[   86.480392]  [] ? usb_hcd_submit_urb+0x330/0xaa0 [usbcore]
[   86.480395]  [] ? enqueue_entity+0x30e/0x920
[   86.480398]  [] ? enqueue_task_fair+0x82/0x940
[   86.480408]  [] ? usb_start_wait_urb+0x6d/0x170 [usbcore]
[   86.480419]  [] ? usb_control_msg+0xdc/0x130 [usbcore]
[   86.480425]  [] ? set_register+0x50/0xa0 [pegasus]
[   86.480429]  [] ? read_eprom_word+0x31/0x100 [pegasus]
[   86.480433]  [] ? pegasus_probe+0x20c/0x840 [pegasus]
[   86.480437]  [] ? __pm_runtime_set_status+0x1bd/0x270
[   86.480447]  [] ? usb_probe_interface+0x15d/0x2c0 [usbcore]
[   86.480451]  [] ? driver_probe_device+0x21a/0x420
[   86.480453]  [] ? __driver_attach+0xda/0xe0
[   86.480456]  [] ? driver_probe_device+0x420/0x420
[   86.480459]  [] ? bus_for_each_dev+0x67/0xb0
[   86.480461]  [] ? bus_add_driver+0x16a/0x260
[   86.480464]  [] ? driver_register+0x57/0xc0
[   86.480474]  [] ? usb_register_driver+0x7b/0x130 [usbcore]
[   86.480476]  [] ? 0xc1155000
[   86.480480]  [] ? pegasus_init+0x164/0x1000 [pegasus]
[   86.480482]  [] ? 0xc1155000
[   86.480486]  [] ? do_one_initcall+0x4b/0x180
[   86.480490]  [] ? __vunmap+0x6d/0xc0
[   86.480493]  [] ? do_init_module+0x5b/0x1ed
[   86.480496]  [] ? load_module+0x2523/0x2a00
[   86.480499]  [] ? __symbol_put+0x60/0x60
[   86.480502]  [] ? SYSC_finit_module+0xc6/0xf0
[   86.480505]  [] ? do_syscall_64+0x7c/0xf0
[   86.480508]  [] ? entry_SYSCALL64_slow_path+0x25/0x25
[   86.480510] ---[ end trace 92d967e7878ff49b ]---
[   86.480618] (unnamed net_device) (uninitialized): read_eprom_word failed
[   86.480725] pegasus 6-2:1.0: can't reset MAC
[   86.480770] pegasus: probe of 6-2:1.0 failed with error -5
[   86.480803] usbcore: registered new interface driver pegasus

While with 4.8.15-2 the adapter works perfectly:

[   35.736110] usb 4-2: new full-speed USB device number 2 using uhci_hcd
[   35.934290] usb 4-2: New USB device found, idVendor=07a6, idProduct=8511
[   35.938057] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   35.941703] usb 4-2: Product: USB To LAN Converter
[   35.945312] usb 4-2: Manufacturer: ADMtek
[   35.948604] usb 4-2: SerialNumber: 0001
[   36.026297] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet 
driver
[   36.043232] pegasus 4-2:1.0: setup Pegasus II specific registers
[   36.164794] pegasus 4-2:1.0: eth0, ADMtek ADM8511 "Pegasus II" USB Ethernet, 
00:14:d1:1b:df:5c
[   36.167350] usbcore: registered new interface driver pegasus
[   36.182117] pegasus 4-2:1.0 enx0014d11bdf5c: renamed from eth0

Bug#851437: astroplan: FTBFS (requires Internet to build)

[Ole Streicher]

There are quite a couple of problems, some of which are due to bugs in
astropy (namely #852550), and others already solved upstream:

https://github.com/astropy/astroplan/pull/273
https://github.com/astropy/astroplan/pull/274
https://github.com/astropy/astroplan/pull/281
https://github.com/astropy/astroplan/files/726302/diff.txt

The remaining problems are in test_transitioner,
test_priority_scheduler, test_sequential_scheduler:

__ test_transitioner ___
self = 
instance = <[ValueError("attribute obstime should be scalar or have shape (2, 
1), but is has shape (2,) and could not be broadcast.") raised in repr()] AltAz 
object at 0x7f8032fb2470>
frame_cls = 

def __get__(self, instance, frame_cls=None):
[...]
if instance is not None:
instance_shape = getattr(instance, 'shape', None)
if instance_shape is not None and (getattr(out, 'size', 1) > 1 and
   out.shape != instance_shape):
# If the shapes do not match, try broadcasting.
try:
if isinstance(out, ShapedLikeNDArray):
out = out._apply(np_broadcast_to, shape=instance_shape,
>subok=True)


[...]
/usr/lib/python3/dist-packages/numpy/lib/stride_tricks.py:174: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

array = array([ 2457424.5,  2457424.5]), shape = (2, 1), subok = True
readonly = True

def _broadcast_to(array, shape, subok, readonly):
[...]
broadcast = np.nditer(
(array,), flags=['multi_index', 'refs_ok', 'zerosize_ok'] + extras,
>   op_flags=[op_flag], itershape=shape, order='C').itviews[0]
E   ValueError: operands could not be broadcast together with remapped 
shapes [original->remapped]: (2,) and requested shape (2,1)

/usr/lib/python3/dist-packages/numpy/lib/stride_tricks.py:129: ValueError


It is unclear (to me) whether this is a problem in astroplan or in astropy.

Bug#852555: minify-maven-plugin: please remove me from Uploaders

[Dominik George]

Source: minify-maven-plugin
Version: 1.7.4-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As I never intended to (co-)maintain this package, please remove me from 
Uploaders.

Thanks,
Nik

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

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

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAliIplUxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pbjnBAAiwBwOWAweni8ophVnCrd0wxEu1gE
xk7nVEh2x8YkAlx4rnl0jHZWGci1z3jiAxhM4GObPFVnHyj53OiSmRZnsTsW3Ino
qPXO5dclBQHFgKQtMRu2qgRfPUWZeDgKopJ5Xsh5wt0+EUsoJ2iYd5O4TgI8vunD
bjD91l7UKhTtYRl8wq8AUi6fsUtXyqbTQcRI87bIpBdsepJuCBif9ldlTuI1huyi
kf3p373sD9+JKN/JLjK0SxSlPaLBg/bBNUr0QWcvUQR+FQ6D0ak2zGZRN1EloNpT
7Ri04RMgcvHR4i3ShqshxNL7TaRrZocdqLeLZKp9VSWy+WzbkqVWRvWxzJ6XqyUD
NxyiLZfsCZrwS6dhG6Sl9EXNnrAUeWgUkrA1x3tLsQPRzbZQS5dhK4SKhNTRTpni
TQj7xKuQQp3KIxmBoUlPrNhAS6lfVMrvYiFz+is9hP0/gJefMl3+W6EgleU2on7B
HbVEM/B1fwXqLPD2A/UBOqasdm4UOcREwMFAXgyFhFxjK3DOxmwYzCwbTfk2x0H8
e20cE1kFlGzfvrUYo0PHcKdNqsb4GDvjuEHTodkHDLwcnqIwCMwUopx1KirfIK8O
JMo5Ci/HU09uT2KCsb82WnTdhQ+whr6Qtx8D1wrLiXaNzCHDtTYuZtWfbd09Ibsc
egW1YtlZHKM9MpA=
=uOyk
-END PGP SIGNATURE-

Bug#852554: angular-maven-plugin: please remove me from Uploaders

[Dominik George]

Source: angular-maven-plugin
Version: 0.3.4-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As I never intended to (co-)maintain this package, please remove me from
Uploaders.

Thanks!

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

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

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAliIpgQxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pYohxAAkrXE4H65rudiOOrqZJQNQ/BaIM/W
ugQm6eEYtWTVZd/LY1M790rj0hwM3CrFJFIPWXaBRoSkbQWFykcJAItx5vnfHwxI
LV8fEo8oiq9CGTdALI2EgDRetp7z0zXM/fCMdywHOm+/uL1xQLcA/C4h/EHPazRR
AU7Eiq+OSXryHmqyijlGF1imniJkWAMGQw2anIKQqWNUwS9op0B+GyruAKhdI/MJ
3V9TFi9xNcbmPgSuDYfxs8Y/zjLa4WW/oVKzQVwHn+3hgEM8cD6k3sYEJr8PYzEM
we468Zl54xEi1e3fUqfzl8vrrMvbO9cpuk2A3Lnza2HkW6HxhgrZ0ZCMqCXM1p3u
BUufCeLu8CFzcIjTvX/9wm5cH0mHdNTamG7JtcecC9KOgDkqIn+6m1GgRWKq0x/4
4lvrSFwzgxwUW9j87YihLfbJjpWUIfzcAqoIEOnExi0+dzrGP2mCBhuwEwdsAtbE
qTE6+8W015pJUOwt+oOh6WNzBqNIw4SgrBdYXLuKI6VnOFjWakCfWmegVwvSRutE
KoIcWKp8H4svG808OWoh55H1gpK0q/3mWUqXylONL14Zj5LIeqYPDzfwiPVnx47f
ti33PqX/UBwle9F2yXt/9pVnkQmAuLdjYisEWi7c4TAdLx0Rnb8fMm9Smvn1SaRk
09wgk7uLhCmNQdc=
=BRuX
-END PGP SIGNATURE-

Bug#840789: #840789: ruby-gettext: FTBFS: Error: test_relative ... undefined method `stub

[Santiago Vila]

reopen 840789
thanks

On Mon, 23 Jan 2017, Christian Hofstaedtler wrote:

> Hi Chris,
> 
> I've just tried to repro this in unstable today, but haven't been
> successful. I imagine a dependency change has fixed this. If you're
> still seeing this FTBFS, please reopen.

This is still happening, both here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-gettext.html

and also in my own autobuilders, so I'm reopening.

Thanks.

Bug#852346: kdenlive: crash on startup

[George B.]

On 25/01/17 13:09, Luca Boccassi wrote:

NVIDIA Corporation GM107GLM [Quadro M1000M]

Do you have an Optimus laptop by any chance? What's the exact model?


I do: Dell Precision 7510.

I have had to disable the Intel graphics card in the BIOS to get the thing to 
work with 2 external screens so it's only Optimus in theory. ;)


George

Bug#852553: libkf5su-bin: 'kdesu dbus-launch dolphin' leaves files in / directory

[Hans Schwimmbeck]

Package: libkf5su-bin
Version: 5.28.0-1
Severity: normal
Tags: upstream

Dear Maintainer,

running 'kdesu dbus-launch dolphin' leaves over time a lot of 
klauncher*.slave-socket files in / directory.

There seems to be an upstream patch:
https://cgit.kde.org/kdesu.git/commit/?id=e3ff52adec249b7cfa1a375866c268485a1cd344

Regards,
Hans Schwimmbeck


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

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

Versions of packages libkf5su-bin depends on:
ii  libc6  2.24-8
ii  libkf5coreaddons5  5.28.0-1
ii  libkf5i18n55.28.0-1
ii  libkf5su5  5.28.0-1
ii  libqt5core5a   5.7.1+dfsg-3
ii  libstdc++6 6.2.1-5
ii  libx11-6   2:1.6.4-2

libkf5su-bin recommends no packages.

libkf5su-bin suggests no packages.

-- no debconf information

Bug#852346: kdenlive: crash on startup

[Luca Boccassi]

On Wed, 2017-01-25 at 13:57 +0100, Andreas Beckmann wrote:
> On 2017-01-25 13:52, Luca Boccassi wrote:
> > Otherwise you can try to run the script manually, but you'll need to
> > copy it and comment out the "exec" command near the top:
> > 
> > /usr/share/bug/nvidia-driver/script
> 
> or just
> 
> /usr/share/bug/nvidia-driver/script 3>outputfile
> 
> 
> Andreas

Yes that's better :-D

Kind regards,
Luca Boccassi


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

Bug#852552: ocserv: Build fail on arm patch inc

[Phillip Camp]

Package: ocserv
Version: 0.11.6-1~bpo8+1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

build is failing for arm have tested this patch on armhf, on backported
package results in installable package, fails on other arms from
autobuild logs this may fix them aswell.

Keep up the hard work would be grateful if you could fix up the
backports etc.

Thanks

Phill.


--- ocserv-0.11.6.orig/debian/rules 2017-01-02 16:18:52.0 +
+++ ocserv-0.11.6/debian/rules  2017-01-25 12:31:01.117711166 +
@@ -14,6 +14,11 @@
OTHER_CONF_OPTS = --enable-systemd --enable-linux-namespaces
 #endif
 
+DEB_BUILD_ARCH_CPU = $(dpkg-architecture -qDEB_BUILD_ARCH_CPU)
+#ifeq ($(DEB_BUILD_ARCH_CPU),arm)
+   OTHER_CONF_OPTS = --enable-systemd --enable-linux-namespaces 
--disable-seccomp
+#endif
+
 %:
dh $@ --with systemd
 

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 8.0 (jessie)
Release:8.0
Codename:   jessie
Architecture: armv7l

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

Versions of packages ocserv depends on:
ii  dbus 1.8.22-0+deb8u1
ii  init-system-helpers  1.22
ii  libc62.19-18+deb8u7
ii  libev4   1:4.15-3
ii  libgnutls-deb0-283.3.8-6+deb8u4
ii  libgssapi-krb5-2 1.12.1+dfsg-19+deb8u2
ii  libhttp-parser2.12.1-2
ii  liblz4-1 0.0~r122-2
ii  libnettle4   2.7.1-5+deb8u2
ii  libnl-3-200  3.2.24-2
ii  libnl-route-3-2003.2.24-2
ii  liboath0 2.4.1-1
ii  libopts251:5.18.4-3
ii  libpam0g 1.1.8-3.1+deb8u2
ii  libpcl1  1.6-1
ii  libprotobuf-c1   1.0.2-1+b1
ii  libradcli4   1.2.6-3~bpo8+1
ii  libreadline6 6.3-8
ii  libsystemd0  215-17+deb8u6
ii  libtalloc2   2.1.2-0+deb8u1
ii  libtasn1-6   4.2-3+deb8u2
ii  libwrap0 7.6.q-25
ii  lsb-base 4.1+Debian13+rpi1+nmu1
ii  ssl-cert 1.0.35

Versions of packages ocserv recommends:
ii  ca-certificates  20141019+deb8u2

ocserv suggests no packages.

-- no debconf information

Bug#852551: gcc-7: avx512vpopcntdqintrin.h is missing from libgcc-7-dev

[Sylvestre Ledru]

same with sgxintrin.h

Bug#852346: kdenlive: crash on startup

[Luca Boccassi]

On Wed, 2017-01-25 at 13:03 +, George B. wrote:
> affects 852346 kdenlive
> thanks
> 
> On 25/01/17 12:52, Luca Boccassi wrote:
> > Otherwise you can try to run the script manually, but you'll need to
> > copy it and comment out the "exec" command near the top:
> >
> > /usr/share/bug/nvidia-driver/script
> 
> Thanks - reportbug still failed but I was able to run the script because of 
> your instructions. :-)
> 
> Output attached.
> 
> 
> Best regards,
> 
> George

NVIDIA Corporation GM107GLM [Quadro M1000M]

Do you have an Optimus laptop by any chance? What's the exact model?

Kind regards,
Luca Boccassi


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

Bug#852346: kdenlive: crash on startup

[Andreas Beckmann]

On 2017-01-25 13:52, Luca Boccassi wrote:
> Otherwise you can try to run the script manually, but you'll need to
> copy it and comment out the "exec" command near the top:
> 
> /usr/share/bug/nvidia-driver/script

or just

/usr/share/bug/nvidia-driver/script 3>outputfile


Andreas

Bug#852551: gcc-7: avx512vpopcntdqintrin.h is missing from libgcc-7-dev

[Sylvestre Ledru]

Package: gcc-7
Version: 7-20161125-1
Severity: important

3:22.53 /usr/lib/gcc/x86_64-linux-gnu/7/include/immintrin.h:75:10: fatal error: 
avx512vpopcntdqintrin.h: No such file or directory
 3:22.54  #include 
 3:22.54   ^
 3:22.54 compilation terminated.
 3:22.55 

Just like #846075

Bug#848616: mysql_install_db creates unusable root user

[Dominik George]

> > as the deadline for uploading any affected packages for stretch is
> > approaching, something really needs to be done.
> 
> I hear this is fixed in mariadb-10.1, see #851131. Can you test again on an
> up-to-date sid? Hopefully python3-testing.mysqld can be updated now.

Yep, works, thanks!

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Maintainer

LPIC-3 Linux Enterprise Professional (Security)


signature.asc
Description: PGP signature

Bug#852083: closed by Thomas Lange <la...@debian.org> (Bug#852083: fixed in dracut 044+241-1)

[Alexander Kurtz]

reopen 852083
notfixed 852083 044+241-1
found 852083 044+241-1
thanks

Hi!

> From bde65565af5928567dabf7af8b0d5dacd27bad52 Mon Sep 17 00:00:00 2001
> From: Thomas Lange 
> Date: Mon, 23 Jan 2017 19:42:17 +0100
> Subject: [PATCH] add recommends, Closes: #852083
> 
> ---
>  debian/control | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/debian/control b/debian/control
> index 06e9fc10..a0dff8d2 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -23,7 +23,7 @@ Description: Low-level tool for generating an initramfs 
> image (automation)
>  Package: dracut-core
>  Architecture: any
>  Multi-Arch: foreign
> -Recommends: cryptsetup, dmsetup, dmraid, lvm2, mdadm, console-setup
> +Recommends: cryptsetup, dmsetup, dmraid, lvm2, mdadm, console-setup, objcopy
>  Depends: cpio, kmod, udev, kpartx, util-linux (>= 2.20), pkg-config, 
> libkmod2, ${shlibs:Depends}, ${misc:Depends}
>  Breaks: dracut-network (<< 043-2), dracut (<< 044+3-2~)
>  Replaces: dracut-network (<< 043-2), dracut (<< 044+3-2~)
> -- 
> 2.11.0

Thanks for your quick response, but I think there are two issues here:

   1. objcopy is the binary, which is in the binutils package.
   2. the systemd package is equally required for the --uefi option to
  work, but hasn't been added to the Recommends: list.

Best regards

Alexander Kurtz

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

Bug#852100: yc-el: please migrate to emacs25 soon

[Yukiharu YABUKI]

Thank you for reporting.

I tried to the changes. But I am not able to manage dbgsym package.
If you take care of these, I would like to refer your nmu package.

https://github.com/yabuki/yc-el

Best Yukiharu

On Sat, 21 Jan 2017 11:32:50 -0600
Rob Browning  wrote:

> 
> Package: yc-el
> Version: 5.0.0-6
> User: debian-emac...@lists.debian.org
> Usertags: debian-emac...@lists.debian.org
> 
> We'd like to remove emacs24 from the archive, so please try to upgrade
> to emacs25, or add optional support for emacs25 as soon as you can.
> 
> For example, assuming the package works with emacs25, a dependency like
> 
>   emacs25-nox | emacs25 | emacs24 | ...
> 
> should suffice.
> 
> If you don't have time to handle this yourself, we'd be happy to try to
> assist with an NMU (please let us know).
> 
> Our original goal was to finish this for stretch, but we missed your
> package in our initial analysis, so there are only a couple of days or
> so left to upload this kind of change.
> 
> Thanks
> -- 
> Rob Browning
> rlb @defaultvalue.org and @debian.org
> GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
> GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


--
++++++++++++++
KIIRE JAPAN Inc. http://www.kiire.co.jp/
TEL : 090-2041-8170 
Yukiharu YABUKI (矢吹幸治) email : yab...@kiire.co.jp
++++++++++++++

Bug#852346: kdenlive: crash on startup

[Luca Boccassi]

On Wed, 2017-01-25 at 12:31 +, George B. wrote:
> Hi Luca,
> 
> On 24/01/17 22:41, Luca Boccassi wrote:
> > Please run:
> >
> > reportbug -N 852346
> >
> > to attach the full system information and logs
> 
> Unfortunately I am unable to do this due to a bug[1] with reportbug. :-(
> 
> Can I get you some information by hand?
> 
> 
> Best regards,
> 
> George

If reportbug can work locally it can print the report to the console:

reportbug --template nvidia-driver

Otherwise you can try to run the script manually, but you'll need to
copy it and comment out the "exec" command near the top:

/usr/share/bug/nvidia-driver/script

Kind regards,
Luca Boccassi


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

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

[Simon McVittie]

On Sun, 11 Oct 2015 at 15:48:10 -0700, Josh Triplett wrote:
> I just encountered this problem again, and in addition to the repeated
> authentication failure messages, I also saw a message on the lock screen
> matching this one I later found in logs:
> 
> gnome-session[551]: (gnome-shell:956): Gjs-WARNING **: JS ERROR: Failed to 
> start verification for user: Gio.DBusError: 
> GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: 
> GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Type of message, 
> '(sssb)', does not match expected type '(sssbb)'

This is really a gdm3 issue, which is why I've reassigned it there.
gnome-shell uses libgdm to communicate with a process called
gdm-session-worker, so that the actual authentication (PAM) can happen in
a privileged process. Unfortunately, the old gnome-shell will be using
jessie's libgdm, which expects a D-Bus API from jessie; and the
gdm-session-worker is started on-demand, so you got one that is using
stretch's libgdm, which expects a D-Bus API from stretch (with an extra
parameter).

It's possible to hack around this in stretch's gdm (patch attached),
but the best workaround I can see is still horrible, and so far I
haven't actually got unlocking to work again. With that
incompatibility out of the way, there's another one:

Jan 25 12:28:31 host gdm-session-worker.really[11355]: 
pam_unix(gdm-password:auth): conversation failed
Jan 25 12:28:31 host gdm-session-worker.really[11355]: 
pam_unix(gdm-password:auth): auth could not identify password for [user]

(gdm-session-worker.really is the real gdm-session-worker - I've used
dpkg-divert to inject more logging on my test system).

Possibly related, or perhaps just a side-effect of failing authentication:

Jan 25 12:28:14 host gnome-session[5143]: (gnome-shell:5342): Gjs-WARNING 
**: JS
 ERROR: Exception in callback for signal: next: Error: can't convert 
this._frame
 to an integer
Jan 25 12:28:14 host gnome-session[5143]: 
Animation<._showFrame@resource:///org/
gnome/shell/ui/animation.js:59
Jan 25 12:28:14 host gnome-session[5143]: 
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 25 12:28:14 host gnome-session[5143]: 
Animation<.play@resource:///org/gnome/shell/ui/animation.js:34
Jan 25 12:28:14 host gnome-session[5143]: 
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 25 12:28:14 host gnome-session[5143]: 
AuthPrompt<.setActorInDefaultButtonWell@resource:///org/gnome/shell/gdm/authPrompt.js:313
Jan 25 12:28:14 host gnome-session[5143]: 
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 25 12:28:14 host gnome-session[5143]: 
AuthPrompt<.startSpinning@resource:///org/gnome/shell/gdm/authPrompt.js:329
Jan 25 12:28:14 host gnome-session[5143]: 
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 25 12:28:14 host gnome-session[5143]: 
AuthPrompt<._init/<@resource:///org/gnome/shell/gdm/authPrompt.js:67
Jan 25 12:28:14 host gnome-session[5143]: 
_emit@resource:///org/gnome/gjs/modules/signals.js:124
Jan 25 12:28:14 host gnome-session[5143]: 
AuthPrompt<._initButtons/<@resource:///org/gnome/shell/gdm/authPrompt.js:191

I broadly agree with upstream on this issue: the more distribution
development I do, the less faith I have in our ability to support
in-place major upgrades, which change relatively fundamental things while
the OS is still fully active. We already don't actually restart gdm,
because that would terminate all user X/Wayland sessions, or dbus, because
that would terminate all D-Bus connections.

We can get away with in-place upgrades for stable updates, because they
already don't change very much, but for stable -> next-stable or for
testing/unstable, it's very easy to create a situation that can't work.

unattended-upgrades has an InstallOnShutdown mode, which is what SteamOS
uses (with some patches that I wrote a couple of years ago to improve it,
). systemd has systemd.offline-updates(7),
which PackageKit and GNOME Software can use.

S
Index: debian/changelog
===
--- debian/changelog	(revision 51941)
+++ debian/changelog	(working copy)
@@ -1,7 +1,16 @@
 gdm3 (3.22.1-2) UNRELEASED; urgency=medium
 
+  [ Michael Biebl ]
   * Stop setting authdir, has beend dropped upstream in favour of xauthdir.
 
+  [ Simon McVittie ]
+  * Add a non-upstreamable patch to edit D-Bus messages from libgdm
+to the session worker and adapt them from the pre-3.16 interface
+to the post-3.16 interface. Only do this if a flag file in /run
+has been created, so that this workaround will only be active
+until the next reboot.
+  * gdm3.preinst: Create that flag file on upgrades. (Closes: #789118)
+
  -- Michael Biebl   Mon, 17 Oct 2016 01:07:52 +0200
 
 gdm3 (3.22.1-1) unstable; urgency=medium
Index: debian/gdm3.preinst

Bug#852550: doctests fail for affiliated package

[Ole Streicher]

Package: python-astropy
Version: 1.3-7
Severity: important
Forwarded: https://github.com/astropy/astropy/issues/5670
Control: affects -1 astroplan
Control: fixed -1 1.3-8~exp2

When using pytest-3, the doctests of astropy and some affiliated
packages (namely astroplan) fail. While the failure of the internal
doctest is tolerable (and may be hidden by just disabling them during
the build), failures of external packages will create a problem when
they are built.

A fix already exists upstream:

https://github.com/astropy/astropy/pull/5678
https://github.com/astropy/astropy/pull/5682
https://github.com/astropy/astropy/pull/5688

This is applied to 1.3-8~exp2 in Debian experimental, but still not in
unstable/testing.

Bug#849944: dpkg-genbuildinfo: Can't use an undefined value as an ARRAY reference

[Johannes Schauer]

Hi,

On Mon, 2 Jan 2017 14:53:07 +0100 Botond Botyanszki 
 wrote:
> Some recent changes in dpkg-dev are causing a regression building a deb
> package.  The error I get is as follows:
> 
> dpkg-deb: building package 'x' in '../x.deb'.
>  dpkg-genbuildinfo --build=binary
> Can't use an undefined value as an ARRAY reference at 
> /usr/bin/dpkg-genbuildinfo line 212.
> dpkg-buildpackage: error: dpkg-genbuildinfo --build=binary gave error exit 
> status 255
> 
> The package builds fine on wheezy and jessie, only stretch is affected.  I
> see that dpkg-genbuildinfo is new code which was not available before.

based on guillem's testcase, I reduced the problem to the following:

Build-Depends: genbuildinfo-archqual-bug:i386

Package: genbuildinfo-archqual-bug
Version: 1.equivs-dummy
Depends: genbuildinfo-archqual-bug-virtual
Architecture: i386

Package: genbuildinfo-archqual-bug-provider
Version: 1.equivs-dummy
Provides: genbuildinfo-archqual-bug-virtual
Architecture: i386

I build the latter two packages via equivs.

My native architecture is amd64. The bug is *not* triggered if the packages are
amd64 or if the source package directly depends on the virtual one.

cheers, josch


signature.asc
Description: signature

Bug#852545: Config file in xen-hypervisor package likely causes problems on upgrade

[Ian Jackson]

Control: tags -1 stretch-ignore

Ian Jackson writes ("Bug#852545: Config file in xen-hypervisor package likely 
causes problems on upgrade"):
> Control: tags -1 confirmed
> 
> I have generated some emergency holographic Xen 4.9 packages and
> indeed
> 
> dpkg: error processing archive
> i/xen-hypervisor-4.9-amd64_4.9.0~~not-1iwj_amd64.deb (--install):
>  trying to overwrite '/etc/default/grub.d/xen.cfg', which is also in
>  package xen-hypervisor-4.8-amd64 4.8.1~pre.2017.01.23-1

I made some experimental packages which have the grub default file in
this new package:

 Package: xen-hypervisor-common
 Source: xen
 Version: 4.9.0~~not-1iwj
 Architecture: all
 Maintainer: Debian Xen Team 
 Installed-Size: 44
 Replaces: xen-hypervisor-4.8-amd64, xen-hypervisor-4.8-arm64, 
xen-hypervisor-4.8-armhf
 Section: kernel
 Priority: optional
 Description: Xen Hypervisor - common files
  The configuration which arranges for an installed hypervisor to be booted
  as default, with the right command line arguments passed to both
  hypervisor and host (Domain 0) kernel.
  .
  This package is only required on the host system (Domain 0) and not on the
  virtual guest systems (Domain U).

I was able to coinstall this with xen-hypervisor-4.8-amd64 and even
got the right conffile prompt (which I induced by editing the file
both on the test system and in the package).

So I think this problem can be postponed for now.  It will need to be
addressed when anyone packages Xen 4.9 for Debian.

The things I had to do to the packaging to make it generate my test
packages are too horrible (and useless) to share.  I thought I would
quote the generated control file instead.

Ian.

Bug#785149: re

[Sandra Head]

Hi Dear, I have a Proposal for you, Get back to me via: frym...@gmail.com


CONFIDENTIALITY NOTICE: This message is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is privileged, confidential and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient you are hereby 
notified that any dissemination, distribution or copying of this transmission 
is prohibited. If you have received this transmission in error, please notify 
us immediately by return telephone, fax or email, and destroy the transmission 
by deleting the file and/or shredding any paper copy.

Bug#852549: do not list /usr/lib/x86_64-linux-gnu/gio/modules

[cgzones]

Package: libglib2.0-0
Version: 2.50.2-2

cruft creates a report regarding this package:

 missing: dpkg 
   /usr/lib/x86_64-linux-gnu/gio
   /usr/lib/x86_64-linux-gnu/gio/modules

This is due to libglib2.0-0 lists this directory and file but does not
ship it by default.
The postinst script contains the following comment:

# The /usr/lib/gio/modules directory is no longer shipped by
# libglib2.0 itself so we need to check to avoid a warning from
# gio-querymodules

Bug#852542: Running initscripts: invoke-rc.d is now in an essential package

[Andreas Henriksson]

Control: forcemerge 833177 852542

On Wed, Jan 25, 2017 at 11:38:32AM +, Julian Gilbey wrote:
> As invoke-rc.d is now (in stretch) in an essential package, I propose
> simplifying the script example in policy to remove the test for its
> existence (debhelper already does this):

This is already filed and fix pending upload.

Merging duplicate.

(FWIW the *-rc.d tools where previously in a package which was
depended-on by essential packages, so it's not really something new that
we can rely on the tools always being available. The previous policy
text seems to be a remnance from then the *-rc.d tools where first
introduced.)

Regards,
Andreas Henriksson

Bug#852509: tightvncserver: much reduced performance and wrong colours since tigervnc switch

[Thorsten Glaser]

On Wed, 25 Jan 2017, Thorsten Glaser wrote:

> ever since the switch to the tigervnc server implementation, when
> accessing a VNC server over the network (client is TightVNC viewer
> version 1.2.7 on MirBSD), I’m observing wrong colours (for example,

All bugs also occur when using vncviewer (TigerVNC Viewer 32-bit v1.7.0)
on localhost.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Enrico Tassi]

On Wed, Jan 25, 2017 at 10:24:25AM +0100, Michael Meskes wrote:
> > Hopefully somebody is prepared to fix all rdepends.
> 
> Or better reverts the API change.

I gave a quick look at the problem.

I don't know why Mathieu packaged a new upstream snapshot exactly,
I hope it is not for the new unix.tcp/udp feature.  If so, reverting the
API change is as simple as reverting

  aa1b8cc9bc35e56de15eeb153c899e4c51de82a8

There is just a trivial conflict on the makefile.

Mathieu, does luasandbox need the new unix sockets?

Best,
-- 
Enrico Tassi

Bug#264952: re

[Sandra Head]

Hi Dear, I have a Proposal for you, Get back to me via: frym...@gmail.com


CONFIDENTIALITY NOTICE: This message is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is privileged, confidential and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient you are hereby 
notified that any dissemination, distribution or copying of this transmission 
is prohibited. If you have received this transmission in error, please notify 
us immediately by return telephone, fax or email, and destroy the transmission 
by deleting the file and/or shredding any paper copy.

Bug#852346: kdenlive: crash on startup

[George B.]

Hi Luca,

On 24/01/17 22:41, Luca Boccassi wrote:

Please run:

reportbug -N 852346

to attach the full system information and logs


Unfortunately I am unable to do this due to a bug[1] with reportbug. :-(

Can I get you some information by hand?


Best regards,

George

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848729

Bug#848729: fails with UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa3 in position 4341: invalid start byte

[George B.]

Package: reportbug
Version: 7.1.4
Followup-For: Bug #848729

Hello,

I am also hitting this issue trying to submit some followup information
to bug 848729.

I have tried the workaround suggested above and it did not work for me.
:-(

```
# reportbug -N 852346
Warning: no reportbug configuration found.  Proceeding in novice mode.
Running 'reportbug' as root is probably insecure! Continue [y|N|q|?]? y
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'root ' as your from address.
Retrieving report #852346 from Debian bug tracking system...
What do you want to do now? [N|x|o|r|b|e|q|?]? x
Getting status for nvidia-driver...
Checking for newer versions at madison...
Will send report to Debian (per lsb_release).
Maintainer for nvidia-driver is 'Debian NVIDIA Maintainers 
'.
Looking up dependencies of nvidia-driver...
Getting status for related package nvidia-driver-libs...
Looking up 'depends' of related package nvidia-driver-libs...
Looking up 'recommends' of related package nvidia-driver-libs...
Getting status for related package nvidia-glx...
Getting status for related package libgl1-nvidia-glx...
Getting status for related package libgl1-glvnd-nvidia-glx...
Looking up 'depends' of related package libgl1-glvnd-nvidia-glx...
Getting status for related package xserver-xorg-video-nvidia...
Looking up 'depends' of related package xserver-xorg-video-nvidia...
Looking up 'recommends' of related package xserver-xorg-video-nvidia...
Looking up 'suggests' of related package xserver-xorg-video-nvidia...
Getting status for related package nvidia-alternative...
Looking up 'depends' of related package nvidia-alternative...
Getting status for related package nvidia-kernel-dkms...
Looking up 'depends' of related package nvidia-kernel-dkms...
Looking up 'recommends' of related package nvidia-kernel-dkms...
Getting status for related package nvidia-kernel-source...
Getting status for related package glx-alternative-nvidia...
Looking up 'depends' of related package glx-alternative-nvidia...
Looking up 'suggests' of related package glx-alternative-nvidia...
Getting status for related package xserver-xorg-video-intel...
Looking up 'depends' of related package xserver-xorg-video-intel...
Looking up status of additional packages...

Please provide a subject for your response.
[Re: kdenlive: crash on startup]> 
Does this bug still exist in version 375.26-2 of this package? [y|N|q|?]? y
Gathering additional data, this may take a while...
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2234, in 
main()
  File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 2058, in user_interface
utils.exec_and_parse_bugscript(handler, bugexec)
  File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 1239, in 
exec_and_parse_bugscript
for line in fp.readlines():
  File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 1330: 
invalid start byte
```


Thanks,

George


-- Package-specific info:
** /home/borisov/.reportbugrc:
no-check-available
realname "George B."
email "i93.b...@gmail.com"
editor vim
mode advanced
smtphost localhost

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

Kernel: Linux 4.9.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 reportbug depends on:
ii  apt1.4~beta4
ii  python3-reportbug  7.1.4
pn  python3:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs23-bin-common | emacs24-bin-common
ii  exim4  4.88-5
ii  exim4-daemon-light [mail-transport-agent]  4.88-5
ii  file   1:5.29-2
ii  gir1.2-gtk-3.0 3.22.7-2
pn  gir1.2-vte-2.91
ii  gnupg  2.1.18-1
ii  python3-gi 3.22.0-2
ii  python3-gi-cairo   3.22.0-2
pn  python3-gtkspellcheck  
pn  python3-urwid  
ii  xdg-utils  1.1.1-1

Versions of packages python3-reportbug depends on:
ii  apt1.4~beta4
ii  file   1:5.29-2
ii  python3-debian 0.1.30
ii  python3-debianbts  2.6.1
ii  python3-requests   2.12.4-1
pn  

Bug#495795: Suggested fix

[Sven Oliver Moll]

The attached archive contains a suggestion on how scp could be added.

Winke: o/~
SvOlli
--
|  ___   |
| (  /\  | Such Dir 'nen Baum begiesse ihn
|__)v\/lli a.k.a.| und schau den Voegeln nach, die nach Sueden ziehn.
|Sven Oliver Moll|   -- Stoppok, "Happy End"

dropbear_2016.74-2.1.debian.tar.xz
Description: application/xz

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Enrico Tassi]

On Wed, Jan 25, 2017 at 10:24:25AM +0100, Michael Meskes wrote:
> > Hopefully somebody is prepared to fix all rdepends.
> 
> Or better reverts the API change.

The bug is definitely important.

Mathieu can you take care of it?

Best,
-- 
Enrico Tassi

Bug#852545: Config file in xen-hypervisor package likely causes problems on upgrade

[Ian Jackson]

Control: tags -1 confirmed

I have generated some emergency holographic Xen 4.9 packages and
indeed

dpkg: error processing archive
i/xen-hypervisor-4.9-amd64_4.9.0~~not-1iwj_amd64.deb (--install):
 trying to overwrite '/etc/default/grub.d/xen.cfg', which is also in
 package xen-hypervisor-4.8-amd64 4.8.1~pre.2017.01.23-1

Ian.

Bug#852546: [Debian-med-packaging] Bug#852546: bowtie2 build-depends on non-free libmath-random-perl

[Sascha Steinbiss]

Hi Adrian,

[...]
> bowtie2 (2.3.0-1) unstable; urgency=medium
> ...
>   [ Andreas Tille ]
> ...
>   * Remove code from test suite that is requiring non-free package
> libmath-random-perl
> ...
>   [ Sascha Steinbiss ]
>   * Even more new Build-Depends: libmath-random-perl, libtest-deep-perl
> ...
>  -- Sascha Steinbiss   Sat, 14 Jan 2017 07:50:51 +

Thanks for noticing -- since I broke it, I'll look into fixing it as well.

Cheers
Sascha

Bug#852547: copy between separate x-protocol screens (e.g. no xinerama) doesn't work with gtk3-apps

[bee GmbH | Pasqual Brettner]

Package: libgtk-3-0
Version: 3.14.5-1+deb8u1


Dear Maintainer,

when using GTK3-Apps on a system with at least two physical displays which
are configured without "Xinerama" (separate x-protocol displays)
one is unable to copy between GTK3 apps and other apps running on 
different screens.

The bug is confirmed and afaik also fixed upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=755116

Please include the fix in the current jessie stable.


Kind regards,
Pasqual Brettner
--
┌─┐
│   ││ ││ ││ │bee Baastrup EDV-Entwicklung GmbH  Pasqual Brettner │
│ ││││ ││ ││ │Schwanenwall 40   Anwendungsentwicklung │
│ ││\\ //\\ //\\ │44135 Dortmund / Deutschland  p.brett...@bee.de │
│ ││// \\¯¯ \\¯¯ │Fon: 0231 / 58719 - 0www.bee.de │
│   ││ ││ ││ │Fax: 0231 / 58719 - 50  xing.to/PasqualBrettner │
│─│
││GeschäftsführerStefan Rower │
││Handelsregistergericht Amtsgericht Dortmund │
││Handelsregisternummer HRB 12333 │
└─┘

Bug#852546: bowtie2 build-depends on non-free libmath-random-perl

[Adrian Bunk]

Source: bowtie2
Version: 2.3.0-1
Severity: serious


bowtie2 (2.3.0-1) unstable; urgency=medium
...
  [ Andreas Tille ]
...
  * Remove code from test suite that is requiring non-free package
libmath-random-perl
...
  [ Sascha Steinbiss ]
  * Even more new Build-Depends: libmath-random-perl, libtest-deep-perl
...
 -- Sascha Steinbiss   Sat, 14 Jan 2017 07:50:51 +

Bug#852544: aptitude: Suggestion for clarifying letters to tables in man page

[alexlin]

Package: aptitude
Version: 0.6.11-1+b1
Severity: wishlist

The letter shorthands are listed in the man page for aptitude, but it might be
nice to clarify what they mean in the table for "aptitude why/why not". It's a
fairly common thing that people are going to look for to reference, especially
beginners.



-- Package-specific info:
$TERM not set.
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.11 compiled at Nov  8 2014 13:34:39
Compiler: g++ 4.9.1
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.4.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20140913
  cwidget version: 0.5.17
  Apt version: 4.12.0

aptitude linkage:
linux-vdso.so.1 (0x7ffd891e8000)
libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 
(0x7fc51cf55000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fc51cd1f000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fc51caf5000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fc51c8ef000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7fc51c5d9000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fc51c31)
libboost_iostreams.so.1.55.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x7fc51c0f8000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7fc51bce7000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fc51baca000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fc51b7bf000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fc51b4be000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fc51b2a8000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc51aefd000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fc51acfa000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fc51aaf6000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fc51a8db000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fc51a6cb000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fc51a4a8000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fc51a2a)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fc51a09b000)
/lib64/ld-linux-x86-64.so.2 (0x7fc51d918000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common   0.6.11-1
ii  libapt-pkg4.121.0.9.8.4
ii  libboost-iostreams1.55.0  1.55.0+dfsg-3
ii  libc6 2.19-18+deb8u7
ii  libcwidget3   0.5.17-2
ii  libgcc1   1:4.9.2-10
ii  libncursesw5  5.9+20140913-1+b1
ii  libsigc++-2.0-0c2a2.4.0-1
ii  libsqlite3-0  3.8.7.1-1+deb8u2
ii  libstdc++64.9.2-10
ii  libtinfo5 5.9+20140913-1+b1
ii  libxapian22   1.2.19-1+deb8u1

Versions of packages aptitude recommends:
ii  aptitude-doc-en [aptitude-doc]  0.6.11-1
ii  libparse-debianchangelog-perl   1.2.0-1.1
ii  sensible-utils  0.0.9

Versions of packages aptitude suggests:
pn  apt-xapian-index  
pn  debtags   
ii  tasksel   3.31+deb8u1

-- no debconf information

Bug#852543: Apache doesn't start anymore with sysvinit

[Stephan Seitz]

Package: apache2
Version: 2.4.25-2
Severity: important

Dear Maintainer,

I’m using sysvinit as my init system.

Since the update to version 2.4.25-2 apache isn’t starting anymore 
because apache2ctl tries to invoke systemctl which will fail of course.


It seems that the fix for 839227 creates this problem.

If I comment the systemd checks in apache2ctl I can start my apache 
again.


Many greetings,

Stephan

-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin  2.4.25-2
ii  apache2-data 2.4.25-2
ii  apache2-utils2.4.25-2
ii  dpkg 1.18.18
ii  init-system-helpers  1.46
ii  lsb-base 9.20161125
ii  mime-support 3.60
ii  perl 5.24.1~rc4-1
ii  procps   2:3.3.12-3

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.38

Versions of packages apache2 suggests:
ii  elinks [www-browser] 0.12~pre6-12
ii  epiphany-browser [www-browser]   3.22.4-1
ii  firefox-esr [www-browser]45.6.0esr-1
ii  konqueror [www-browser]  4:16.08.3-1
ii  links [www-browser]  2.14-2
ii  lynx [www-browser]   2.8.9dev11-1
ii  opera-stable [www-browser]   42.0.2393.351
ii  w3m [www-browser]0.5.3-34

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.2-5
ii  libaprutil1  1.5.4-3
ii  libaprutil1-dbd-mysql1.5.4-3
ii  libaprutil1-dbd-pgsql1.5.4-3
ii  libaprutil1-dbd-sqlite3  1.5.4-3
ii  libaprutil1-ldap 1.5.4-3
ii  libc62.24-8
ii  libldap-2.4-22.4.44+dfsg-3
ii  liblua5.2-0  5.2.4-1.1+b1
ii  libnghttp2-141.17.0-1
ii  libpcre3 2:8.39-2
ii  libssl1.0.2  1.0.2j-5
ii  libxml2  2.9.4+dfsg1-2.1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages apache2-bin suggests:
ii  elinks [www-browser] 0.12~pre6-12
ii  epiphany-browser [www-browser]   3.22.4-1
ii  firefox-esr [www-browser]45.6.0esr-1
ii  konqueror [www-browser]  4:16.08.3-1
ii  links [www-browser]  2.14-2
ii  lynx [www-browser]   2.8.9dev11-1
ii  opera-stable [www-browser]   42.0.2393.351
ii  w3m [www-browser]0.5.3-34

Versions of packages apache2 is related to:
ii  apache2  2.4.25-2
ii  apache2-bin  2.4.25-2

-- Configuration Files:
/etc/apache2/mods-available/ssl.conf changed [not included]
/etc/apache2/sites-available/000-default.conf changed [not included]
/etc/apache2/sites-available/default-ssl.conf changed [not included]

-- no debconf information

--
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |


smime.p7s
Description: S/MIME cryptographic signature

Bug#852545: Config file in xen-hypervisor package likely causes problems on upgrade

[Stefan Bader]

Package: xen
Version: 4.8.0-1
Severity: important

Starting with 4.8 the xen-hypervisor-4.8* package will contain a grub config
file in /etc/default/grub.d/xen.cfg. This will be causing problem when moving to
Xen 4.9 because then xen-hypervisor-4.9* will try to install the same file 
again.
This will prevent two versions of the hypervisor to be co-installable. Maybe the
solution would be to have a xen-hypervisor-common package that solely contains
the config.

Bug#852542: Running initscripts: invoke-rc.d is now in an essential package

[Julian Gilbey]

Package: debian-policy
Version: 3.9.8.0
Severity: normal
Tags: patch

As invoke-rc.d is now (in stretch) in an essential package, I propose
simplifying the script example in policy to remove the test for its
existence (debhelper already does this):

--- /tmp/policy.sgml.orig   2017-01-25 11:35:34.787735041 +
+++ /tmp/policy.sgml2017-01-25 11:36:39.075433047 +
@@ -7767,11 +7767,7 @@
  action in their postinst
  and prerm scripts to:
  
-   if which invoke-rc.d >/dev/null 2>&1; then
-   invoke-rc.d package action
-   else
-   /etc/init.d/package action
-   fi
+   invoke-rc.d package action
  

 
Best wishes,

   Julian

-- System Information:
Debian Release: 9.0
  APT prefers jessie
  APT policy: (500, 'jessie'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

debian-policy depends on no packages.

debian-policy recommends no packages.

Versions of packages debian-policy suggests:
ii  doc-base  0.10.7

-- no debconf information
--- /tmp/policy.sgml.orig   2017-01-25 11:35:34.787735041 +
+++ /tmp/policy.sgml2017-01-25 11:36:39.075433047 +
@@ -7767,11 +7767,7 @@
  action in their postinst
  and prerm scripts to:
  
-   if which invoke-rc.d >/dev/null 2>&1; then
-   invoke-rc.d package action
-   else
-   /etc/init.d/package action
-   fi
+   invoke-rc.d package action
  

 

Bug#852541: RM: cardstories -- RoQA; not part of stable or stretch

[Adrian Bunk]

Package: ftp.debian.org
Severity: normal

cardstories is not part of stable or stretch.

It was orphaned in https://tracker.debian.org/news/834757
and is also dead upstream.

The binary from that package was already a victim of the
cruft-removal bug since the -all build failed on the buildd.

Bug#852540: pam_selinux: add new option to select from default_contexts

[cgzones]

Package: libpam-modules
Version: 1.1.8-3.5
User: selinux-de...@lists.alioth.debian.org
Usertags: selinux

When an SELinux unaware login application, like sddm, tries to set up
sessions via pam, it is not possible to set the new SELinux context
accordingly.

This patch adds an option to pam_selinux.so, so that via different pam
configurations, like sddm does it
https://github.com/sddm/sddm/blob/develop/src/helper/backend/PamBackend.cpp#L220,
different contexts can be assigned.

From: cgzones 
Date: Tue, 3 Jan 2017 12:04:20 +0100
Subject: [PATCH] pam_selinux: add select_default_context option

---
modules/pam_selinux/README| 11 +
modules/pam_selinux/pam_selinux.8 | 11 -
modules/pam_selinux/pam_selinux.8.xml | 19 +++
modules/pam_selinux/pam_selinux.c | 46 ++-
4 files changed, 80 insertions(+), 7 deletions(-)

diff --git a/modules/pam_selinux/README b/modules/pam_selinux/README
index fb4d449..b1b6be2 100644
--- a/modules/pam_selinux/README
+++ b/modules/pam_selinux/README
@@ -72,6 +72,17 @@ use_current_range
instead of the default level. Also suppresses asking of the sensitivity
level from the user or obtaining it from PAM environment.

+select_default_context=
+
+Select a specific context from the list of default contexts for the login
+user returned by SELinux. By default the first entry is taken.
+Valid values are 'last' or positiv numbers, to select a different context.
+The list of available contexts can be viewed by 'compute_user
src_context seuser'.
+
+Usage:
+select_default_context=2
+select_default_context=last
+
EXAMPLES

auth required  pam_unix.so
diff --git a/modules/pam_selinux/pam_selinux.8
b/modules/pam_selinux/pam_selinux.8
index acd4f0d..d936cb9 100644
--- a/modules/pam_selinux/pam_selinux.8
+++ b/modules/pam_selinux/pam_selinux.8
@@ -31,7 +31,7 @@
pam_selinux \- PAM module to set the default security context
.SH "SYNOPSIS"
.HP \w'\fBpam_selinux\&.so\fR\ 'u
-\fBpam_selinux\&.so\fR [open] [close] [restore] [nottys] [debug]
[verbose] [select_context] [env_params] [use_current_range]
+\fBpam_selinux\&.so\fR [open] [close] [restore] [nottys] [debug]
[verbose] [select_context] [env_params] [use_current_range]
[select_default_context=\fIlast|context_number\fR]
.SH "DESCRIPTION"
.PP
pam_selinux is a PAM module that sets up the default SELinux security
context for the next executed process\&.
@@ -99,6 +99,15 @@ Attempt to obtain a custom security context role
from PAM environment\&. If MLS
.RS 4
Use the sensitivity level of the current process for the user context
instead of the default level\&. Also suppresses asking of the
sensitivity level from the user or obtaining it from PAM
environment\&.
.RE
+.PP
+\fBselect_default_context\fR
+.RS 4
+Select a specific context from the list of default contexts for the
login user returned by SELinux\&. By default the first entry is
taken\&. Valid values are 'last' or positiv numbers, to select a
different context\&. The list of a
vailable contexts can be viewed by 'compute_user src_context seuser'\&.
+.RS 2
+Usage:
+.RS 2
+select_default_context=2
+.RE
.SH "MODULE TYPES PROVIDED"
.PP
Only the
diff --git a/modules/pam_selinux/pam_selinux.8.xml
b/modules/pam_selinux/pam_selinux.8.xml
index 28d465f..210e262 100644
--- a/modules/pam_selinux/pam_selinux.8.xml
+++ b/modules/pam_selinux/pam_selinux.8.xml
@@ -45,6 +45,9 @@
  
   use_current_range
  
+  
+select_default_context=conf-file
+  

  

@@ -188,6 +191,22 @@
  

  
+  
+
+  
select_default_context=last|context_number
+
+
+  
+Select a specific context from the list of default
contexts for the login
+user returned by SELinux. By default the first entry is taken.
+Valid values are 'last' or positiv numbers, to select a
different context.
+The list of available contexts can be viewed by
'compute_user src_context seuser'.
+Usage:
+  select_default_context=2
+  select_default_context=last
+  
+
+  

  

diff --git a/modules/pam_selinux/pam_selinux.c
b/modules/pam_selinux/pam_selinux.c
index b96cc23..446b4fb 100644
--- a/modules/pam_selinux/pam_selinux.c
+++ b/modules/pam_selinux/pam_selinux.c
@@ -63,8 +63,6 @@

#include 
#include 
-#include 
-#include 
#include 
#include 
#include 
@@ -480,7 +478,8 @@ set_file_context(const pam_handle_t *pamh,
security_context_t context,
static int
compute_exec_context(pam_handle_t *pamh, module_data_t *data,
int select_context, int use_current_range,
-int env_params, int debug)
+int env_params, int debug,
+const char *select_default_context)
{
  const char *username;

@@ -491,6 +490,7 @@ compute_exec_context(pam_handle_t *pamh,
module_data_t *data,
  

Bug#852530: terminix: Terminix fails to start

[Matthias Klumpp]

2017-01-25 9:30 GMT+01:00 eNovance :
> Package: terminix
> Version: 1.4.2-2
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Since the update to version 1.4.2, terminix fails to start with the
> following message :
>
> terminix: symbol lookup error: terminix: undefined symbol:
> _D7gobject7ObjectG7ObjectG11addOnNotifyMFDFC7gobject9ParamSpec9ParamSpecC7gobject7ObjectG7ObjectGZvAyaE4gtkc12gobjecttypes13GConnectFlagsZv

This is a D ABI issue, Terminix needs a rebuild with newer GtkD.
I will make an upload tightening the dependencies when I am back home today.

Cheers,
Matthias

Bug#852495: [debian-mysql] Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

[Julian Gilbey]

On Wed, Jan 25, 2017 at 11:26:00AM +0200, Otto Kekäläinen wrote:
> Tags: unreproducible
> 
> 2017-01-25 0:21 GMT+02:00 Julian Gilbey :
> > After upgrading to 10.1 from 10.0, I purged the old
> > mariadb-server-10.0 package, but this had two quite unpleasant
> > effects: it shut down the server and it removed the init.d links.
> > This is because:
> 
> I was not able to reproduce this. The 10.1 packages conflict the 10.0
> packages, so it is not possible to have them installed at the same
> time, and thus end up in a situation where you would remove the 10.0
> packages while 10.1 is already installed.
> 
> What versions of the packages (including revision numbers) did you
> have? What should I do to reproduce this?

How to reproduce:

(1) Install mariadb-server-10.0

(2) Upgrade to mariadb-server-10.1.  Note that this removes the
mariadb-server-10.0 package but does not purge it - its
configuration files and postrm are left (so it's in state "rc" as
displayed by dpkg -l)

(3) Tidy up by purging mariadb-server-10.0

Best wishes,

   Julian

Bug#852530:

[michal]

Problem persists even after downgrading Terminix packages to previous versions.

Bug#852539: dpkg: run maintainer scripts with SELinux user system_u

[cgzones]

Package: dpkg
Version: 1.18.18
User: selinux-de...@lists.alioth.debian.org
Usertags: selinux

Currently, dpkg runs its maintainer tasks in the SELinux type
dpkg_script_t without changing the SELinux user or role.
So when running root as sysadm_u:sysadm_r:sysadm_t, the tasks will be
run in unconfined_u:unconfined_r:dpkg_script_t.
The problem are the postinst scripts: They create files and run binaries.
Almost all the files created in this way do not have the correct file
context system_u:object_r:*, which can break a ubac enabled system.
e.g.:

Would relabel /usr/share/info/dir.old from staff_u:object_r:usr_t:s0
to system_u:object_r:usr_t:s0
Would relabel /usr/share/info/dir from staff_u:object_r:usr_t:s0 to
system_u:object_r:usr_t:s0
Would relabel /var/cache/man/pt/index.db from
unconfined_u:object_r:man_cache_t:s0 to
system_u:object_r:man_cache_t:s0

Also, for example, the exim4 post install script does some work
leading to run exim in system_mail_t, which is not allowed to run
under the roles sysadm_r/unconfined_r.

type=PROCTITLE msg=audit(01/24/17 15:51:28.963:2602) :
proctitle=/usr/sbin/exim4 -C /var/lib/exim4/config.autogenerated.tmp
-bV
type=SYSCALL msg=audit(01/24/17 15:51:28.963:2602) : arch=armeb
syscall=socket per=PER_LINUX_32BIT success=yes exit=4 a0=local
a1=SOCK_STREAM a2=ip a3=0x0 items=0 ppid=22511 pid=22748
auid=christian uid=root gid=root euid=root suid=root fsuid=root
egid=root sgid=root fsgid=root tty=pts1 ses=359 comm=exim4
exe=/usr/sbin/exim4 subj=staff_u:sysadm_r:system_mail_t:s0 key=(null)
type=SELINUX_ERR msg=audit(01/24/17 15:51:28.963:2602) :
op=security_compute_sid
invalid_context=staff_u:sysadm_r:system_mail_t:s0
scontext=staff_u:sysadm_r:system_mail_t:s0
tcontext=staff_u:sysadm_r:system_mail_t:s0 tclass=unix_stream_socket

This can cause issues when upgrading packages in enforced mode even as
unconfined user.

The following dpkg patch runs the maintainer tasks in the context
system_u:system_r:dpkg_script_t (may be altered inside the SELinux
policy):

Note: The patch does not touch the SELinux detection in the build
logic and the SELinux policy has to be updated beforehand.

From: root 
Date: Mon, 9 Jan 2017 22:42:03 +0100
Subject: [PATCH] dpkg: fix maintainer SELinux context

---
src/script.c | 95 +---
1 file changed, 85 insertions(+), 10 deletions(-)

diff --git a/src/script.c b/src/script.c
index 2f252ae..72b92cf 100644
--- a/src/script.c
+++ b/src/script.c
@@ -32,6 +32,7 @@
#include 

#ifdef WITH_LIBSELINUX
+#include  // isspace
#include 
#endif

@@ -141,23 +142,97 @@ maintscript_pre_exec(struct command *cmd)
   return cmd->filename + instdirlen;
}

+#ifdef WITH_LIBSELINUX
+/*
+ * derived from get_init_context()
+ * 
https://github.com/SELinuxProject/selinux/blob/master/policycoreutils/run_init/run_init.c
+ *
+ * Get the CONTEXT associated with the context for the dpkg maint scripts.
+ *
+ * in:  nothing
+ * out: The CONTEXT associated with the context.
+ * return:  0 on success, -1 on failure.
+ */
+static int
+get_dpkg_context(char **context)
+{
+   FILE *fp;
+   char buf[255], *bufp;
+   size_t buf_len;
+   char context_file[4096];
+   snprintf(context_file, sizeof(context_file) - 1, "%s/%s",
selinux_contexts_path(), "dpkg_context");
+   fp = fopen(context_file, "r");
+   if (!fp) {
+   ohshite(_("Could not open file %s\n"), context_file);
+   return -1;
+   }
+
+   while (1) { /* loop until we find a non-empty line */
+
+   if (!fgets(buf, sizeof buf, fp)) {
+   break;
+   }
+
+   buf_len = strlen(buf);
+   if (buf[buf_len - 1] == '\n') {
+buf[buf_len - 1] = 0;
+   }
+
+   bufp = buf;
+   while (*bufp && isspace(*bufp)) {
+bufp++;
+   }
+
+   if (*bufp) {
+   *context = strdup(bufp);
+   if (!(*context)) {
+   goto out;
+   }
+   fclose(fp);
+   return 0;
+   }
+   }
+  out:
+   fclose(fp);
+   ohshit(_("No context in file %s\n"), context_file);
+   return -1;
+}
+#endif
+
/**
 * Set a new security execution context for the maintainer script.
- *
- * Try to create a new execution context based on the current one and the
- * specific maintainer script filename. If it's the same as the current
- * one, use the given fallback.
 */
static int
-maintscript_set_exec_context(struct command *cmd, const char *fallback)
+maintscript_set_exec_context(void)
{
+#ifdef WITH_LIBSELINUX
   int rc = 0;
+   char *dpkg_context = NULL;

-#ifdef WITH_LIBSELINUX
-   rc = setexecfilecon(cmd->filename, fallback);
-#endif
+   if (is_selinux_enabled() < 1) {
+   return 0;
+ 

Bug#852538: libwnck-3-0: wnck_screen_get() segfaults under non-X11

[Simon McVittie]

Package: libwnck-3-0
Version: 3.20.1-2
Severity: important
Tags: patch upstream pending

d-feet segfaults in Wayland:

/usr/lib/python3/dist-packages/dfeet/wnck_utils.py:9: PyGIWarning: Wnck was 
imported without specifying a version first. Use gi.require_version('Wnck', 
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Wnck
[1]29521 segmentation fault (core dumped)  d-feet

#0  0x7f6098dade65 in wnck_screen_get () at 
/usr/lib/x86_64-linux-gnu/libwnck-3.so.0

This is known and fixed upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=775116

Regards,
S

Bug#852495: [debian-mysql] Bug#852495: Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

[Kristian Nielsen]

Otto Kekäläinen  writes:

> Tags: unreproducible
>
> 2017-01-25 0:21 GMT+02:00 Julian Gilbey :
>> After upgrading to 10.1 from 10.0, I purged the old
>> mariadb-server-10.0 package, but this had two quite unpleasant
>> effects: it shut down the server and it removed the init.d links.
>> This is because:
>
> I was not able to reproduce this. The 10.1 packages conflict the 10.0
> packages, so it is not possible to have them installed at the same
> time, and thus end up in a situation where you would remove the 10.0
> packages while 10.1 is already installed.

Note the wording "purge". I'm guessing that the 10.0 package was removed
(but not purged). And that a later purge step of the already-removed package
caused the observed behaviour.

So to try to reproduce you could just apt-get remove mariadb-server-10.0 (or
apt-get install mariadb-server 10.1 without --purge option). And then
afterwards try apt-get purge mariadb-server-10.0.

 - Kristian.

Bug#819781: screen: decide whether to build with utempter support

[Axel Beckert]

Control: reopen -1

Hi,

after https://bugs.debian.org/852484 happened and I'm now well aware
of the implications of such a security issue, I will surely reconsider
this decision.

Sven Joachim wrote:
> If libutempter-dev is installed on the build system, configure uses it
> by default to build screen with utempter support.  At least the sh4
> package of screen, apparently uploaded by a porter, depends on
> libutempter0.
> 
> Unfortunately there is no "--disable-utempter" switch for configure,

That's a pity. Especially my current idea is to build the screen
package with utempter support, but not the screen-udeb to avoid having
utempter being packaged as udeb, too, and because it IMHO doesn't make
sense in the udeb.

This is definitely something that needs investigation before
implementing utempter support in Debian's screen package.

> and while enabling utempter support certainly makes sense, it
> probably won't suffice to avoid installing screen setgid utmp, since
> screen needs write access to the /run/screen directory.

As a followup to the potential root exploit tracked in Debian in
#852484, there was a nice outline posted by Solar Designer on the
OSS-Security mailing list on how other distributions implement
utempter support in screen:
http://www.openwall.com/lists/oss-security/2017/01/25/1

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

Bug#852495: [debian-mysql] Bug#852495: Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

[Otto Kekäläinen]

Hello!

I tested the scenario where a system had mariadb-server-10.0 et al
installed in Jessie, and then upgrades to Stretch. In Streatch
mariadb-server-10.0 is replaced by 10.1 but not purged.

Then I ran
$ apt-get purge mariadb-*-10.0

The following packages will be REMOVED:
  mariadb-client-10.0* mariadb-server-10.0*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 45411 files and directories currently installed.)
Purging configuration files for mariadb-server-10.0 (10.0.29-0+deb8u1) ...
Purging configuration files for mariadb-client-10.0 (10.0.29-0+deb8u1) ...

root@purge-test:~# ls -la /etc/init.d/mysql
-rwxr-xr-x 1 root root 5929 Jan 19 20:54 /etc/init.d/mysql

root@purge-test:~# grep mysql /var/log/syslog | tail -n 5
Jan 25 10:34:18 mysqld_safe[27837]: 2017-01-25 10:34:18
139642039747136 [Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB-2)
starting as process 27836 ...
Jan 25 10:34:22  mysqld[28032]: 2017-01-25 10:34:22 140657493631552
[Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB-2) starting as process
28032 ...
(nothing around 10:40)


The init file remained after purge and mysqld did not restart. I even
had a console open to mysqld during the purge and it did not
close/restart.

I am happy to accept patches though for this issue if somebody else
can better reproduce the problem and then verify that the patches work
when written.

Bug#852493: Please enable Thunder NIC virtual function driver

[Punit Agrawal]

On Wed, Jan 25, 2017 at 2:05 AM, Ben Hutchings  wrote:
> Control: tag -1 moreinfo
>
> On Tue, 2017-01-24 at 22:13 +, Punit Agrawal wrote:
>> Source: linux
>> Severity: wishlist
>> Tags: patch
>>
>> While testing device passthrough with a debian guest on a Cavium
>> Thunder, I found that the virtual function(VF) driver for the built in
>> nic is not available.
>>
>> Please enable CONFIG_THUNDER_NIC_VF in the debian kernel config.
>
> So long as this hardware is part of specific SoCs, we should only
> enable it for the CPU architectures used in those SoCs.  That's arm64,
> right?  (Possibly also mips64, but we don't support Cavium MIPS SoCs at
> all yet.)

That's right, I am using it on arm64. I'm not sure whether the Cavium
mips parts include this nic.

>
> Shouldn't we also enable CONFIG_THUNDER_NIC_{PF,BGX,RGX} along with
> this?

I wasn't sure what the policy is on enabling drivers for the kernel so
I only asked to enable the module I'd be using. I haven't yet had a
chance to run the debian kernel on the host.

The above configs would definitely be needed on the host. But in
addition, there are a few others required as well -

CONFIG_PCI_HOST_THUNDER_ECAM
CONFIG_PCI_HOST_THUNDER_PEM

Thanks,
Punit

>
> Ben.
>
> --
> Ben Hutchings
> It is easier to write an incorrect program than to understand a correct
> one.

Bug#846998: Fixed with editing the conf

[Georg Klimm Lohn24.de GmbH]

a fast fix is to rename the section

[/opt/ltsp/stretch] to [opt/ltsp/stretch]

then everything works fine.


A request to the developer:
"Negotiation failed/8a: Requested export not found" doesnt help on debugging.
I have to trace the nbd-server to find my solution.

Please give us a parameter for the loglevel and make a more verbose log:
"Negotiation failed/8a: Requested export not found: $request"

This could help a lot!

Thanks!

Bug#851132: [debian-mysql] Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

[Matthew Sackman]

On Wed, Jan 25, 2017 at 12:21:09PM +0200, Otto Kekäläinen wrote:
> I am sorry but we have basically been forbidden from using OpenSSL in
> Debian due to license reasons:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761911
> 
> If you can get somebody to change their opinion, then we could use
> OpenSSL. But still it is sad OpenSSL has such an license. In the long
> term migrating to something else would be good.

Understood. I'm sorry if I came across as whining - been a long week.

I would just hope that these issues are thoroughly and prominently
documented so that we can take extra steps to try to secure
installations and make informed decisions.

Matthew

Bug#851132: [debian-mysql] Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

[Otto Kekäläinen]

2017-01-25 12:10 GMT+02:00 Matthew Sackman :
> On Wed, Jan 25, 2017 at 09:44:00AM +0200, Otto Kekäläinen wrote:
>> Ok, this is now figured out.
>>
>> To activate YaSSL you must have 'ssl=on' in the config and no
>> ssl_cipher defined.
>
> Erm, ok, but this is somewhat terrifying - I can't disable insecure and
> broken ciphers? I basically would consider anything < TLSv1.2
> insecure and I would expect to be able to restrict even the ciphers
> within TLSv1.2. This is in keeping with standard practise for apache,
> dovecot, postfix etc etc.

I am sorry but we have basically been forbidden from using OpenSSL in
Debian due to license reasons:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761911

If you can get somebody to change their opinion, then we could use
OpenSSL. But still it is sad OpenSSL has such an license. In the long
term migrating to something else would be good.

Bug#707903: drgeo: Migrate to guile-2.0?

[Petter Reinholdtsen]

Hi.  Are there any plans to migrate drgeo to guile-2.0?  It is a bit sad
to not have drgeo available in Debian Edu.

-- 
Happy hacking
Petter Reinholdtsen

Bug#852537: uscan: "warn: strange ... unknown pgpmode = auto" despite manpage documenting it

[Mattia Rizzolo]

Package: devscripts
Version: 2.17.0
User: devscri...@packages.debian.org
Usertags: uscan


mattia@warren ~/devel/inkscape/inkscape (git)-[master] % cat debian/watch 
version=4

opts="\
uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha|b|a)[\-\.]?\d*)$/$1~$2/,
 \
dversionmangle=s/\+(debian|dfsg|ds|deb)\d*$//, \
pgpmode=auto" \
https://launchpad.net/inkscape/+download \
(?:.*/)?inkscape[_\-\.]?(\d\S+)\.(?:tgz|txz|tar\.(?:bz2|gz|z2|xz)) debian
mattia@warren ~/devel/inkscape/inkscape (git)-[master] % uscan --report 
--force-download
uscan info: uscan (version 2.17.0) See uscan(1) for help
uscan info: Scan watch files in .
...
uscan info:=> Package is up to date for from
  
https://launchpad.net/inkscape/0.92.x/0.92/+download/inkscape-0.92.0.tar.bz2
uscan info:=> Forcing download as requested
uscan info: Downloading upstream package: inkscape-0.92.0.tar.bz2
uscan info: Requesting URL:
   https://launchpad.net/inkscape/0.92.x/0.92/+download/inkscape-0.92.0.tar.bz2
uscan info: Successfully downloaded package: inkscape-0.92.0.tar.bz2
uscan info: Start checking for common possible upstream OpenPGP signature files
uscan info: End checking for common possible upstream OpenPGP signature files
uscan warn: strange ... unknown pgpmode = auto
uscan info: Scan finished
mattia@warren ~/devel/inkscape/inkscape (git)-[master] % 


But pgpmode=auto is a fine option according to the manpage.


Now, I tried that watchfile trying to understand/fix the warning
reported on https://qa.debian.org/cgi-bin/watch?pkg=inkscape
Unable to set versionmode=prev for the line without
opts=pgpmode=prev in debian/watch, skipping:
https://launchpad.net/inkscape/+download 
(?:.*/)?inkscape[_\-\.]?(\d\S+)\.(?:tgz|txz|tar\.(?:bz2|gz|z2|xz)).(?:asc|pgp|gpg|sig)
 previous 
Even if, as you can see in the current watchfile that opts=pgpmode=prev
is set (probably this is some bug, but given it could be my fault I'm
not filing it as so, yet).


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#851132: [debian-mysql] Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

[Matthew Sackman]

On Wed, Jan 25, 2017 at 09:44:00AM +0200, Otto Kekäläinen wrote:
> Ok, this is now figured out.
> 
> To activate YaSSL you must have 'ssl=on' in the config and no
> ssl_cipher defined.

Erm, ok, but this is somewhat terrifying - I can't disable insecure and
broken ciphers? I basically would consider anything < TLSv1.2
insecure and I would expect to be able to restrict even the ciphers
within TLSv1.2. This is in keeping with standard practise for apache,
dovecot, postfix etc etc.

Matthew

Bug#852536: Fail to encode distinguished name (ldap) with special character

[Nagarasa Sakirnth]

Package: keystone
Version: 2:10.0.0-6
Tags: patch

Hello,

We have installed keystone with ldap integration and if a user with a special 
character (ä,ö,ü ...) in the distinguished name (dn) tries to log in to horzion 
it fails.
With the following error message:

2017-01-18 16:01:04.740536 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi Traceback (most recent call last):
2017-01-18 16:01:04.740540 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py", line 225, in 
__call__
2017-01-18 16:01:04.740544 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi result = method(req, **params)
2017-01-18 16:01:04.740547 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/auth/controllers.py", line 401, in 
authenticate_for_token
2017-01-18 16:01:04.740561 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi self.authenticate(request, auth_info, auth_context)
2017-01-18 16:01:04.740565 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/auth/controllers.py", line 528, in 
authenticate
2017-01-18 16:01:04.740568 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi auth_context)
2017-01-18 16:01:04.740572 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/auth/plugins/password.py", line 36, 
in authenticate
2017-01-18 16:01:04.740576 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi password=user_info.password)
2017-01-18 16:01:04.740579 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 124, in 
wrapped
2017-01-18 16:01:04.740583 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi __ret_val = __f(*args, **kwargs)
2017-01-18 16:01:04.740587 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/notifications.py", line 488, in 
wrapper
2017-01-18 16:01:04.740590 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi result = f(wrapped_self, request, user_id, *args, 
**kwargs)
2017-01-18 16:01:04.740594 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 416, in 
wrapper
2017-01-18 16:01:04.740598 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi return f(self, *args, **kwargs)
2017-01-18 16:01:04.740601 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 426, in 
wrapper
2017-01-18 16:01:04.740605 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi return f(self, *args, **kwargs)
2017-01-18 16:01:04.740608 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 832, in 
authenticate
2017-01-18 16:01:04.740612 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi ref = driver.authenticate(entity_id, password)
2017-01-18 16:01:04.740616 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap/core.py", 
line 59, in authenticate
2017-01-18 16:01:04.740619 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi user_ref = self._get_user(user_id)
2017-01-18 16:01:04.740623 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap/core.py", 
line 78, in _get_user
2017-01-18 16:01:04.740626 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi return self.user.get(user_id)
2017-01-18 16:01:04.740630 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap/common.py", 
line 1911, in get
2017-01-18 16:01:04.740634 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi ref = super(EnabledEmuMixIn, self).get(object_id, 
ldap_filter)
2017-01-18 16:01:04.740637 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap/common.py", 
line 1518, in get
2017-01-18 16:01:04.740641 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi res = self._ldap_get(object_id, ldap_filter)
2017-01-18 16:01:04.740645 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap/common.py", 
line 1454, in _ldap_get
2017-01-18 16:01:04.740648 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi attrs)
2017-01-18 16:01:04.740652 2017-01-18 16:01:04.736 20713 ERROR 
keystone.common.wsgi   File 
"/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap/common.py", 
line 947, in search_s
2017-01-18 16:01:04.740656 2017-01-18 16:01:04.736 20713 ERROR 

Bug#850115: [Pkg-samba-maint] Bug#850115: samba: create mask = 0700

[Mathieu Parent]

2017-01-25 9:14 GMT+01:00 Olaf van der Spek :
> 2017-01-24 21:29 GMT+01:00 Mathieu Parent :
>> 2017-01-24 10:18 GMT+01:00 Olaf van der Spek :
>>> 2017-01-05 9:10 GMT+01:00 Olaf van der Spek :
> Also take a look at your "map archive" param which is enabled by default..

 Thanks for the tip
>>>
>>> Could map archive be added to the default smb.conf file?
>>
>> Why? It's enabled by default. Also, we want to keep default smb.conf small.
>
> Because the behavior seems to confuse (some) users and some don't find
> it desirable.
>
> I'm also wondering what programs still depend on this behavior.

You can report this upstream. And point from here.

-- 
Mathieu

Bug#567600: ghemical should depend on xfonts-75dpi

[Graham Inggs]

I ran into this problem and tried installing the following packages:

> [INSTALL] x11-xfs-utils
> [INSTALL] xfonts-100dpi
> [INSTALL] xfonts-75dpi
> [INSTALL] xfonts-scalable
> [INSTALL] xfs

Xfs no longer exists, and I installed xfstt as well.  The problem 
persisted, but went away after rebooting.


I also tried rebuilding ghemical after replacing 'courier 12' with 
'Monospace' in the following files:


> src/p1dview_wcl.cpp:171:ogl_InitPangoFont("courier 12");
> src/eldview_wcl.cpp:135:ogl_InitPangoFont("courier 12");
> src/oglview_wcl.cpp:929:ogl_InitPangoFont("courier 12");
> src/p2dview_wcl.cpp:207:ogl_InitPangoFont("courier 12");
> src/gpcview_wcl.cpp:61:ogl_InitPangoFont("courier 12");

That just gave me the following error, even after installing 
ttf-dejavu-core:

*** ERROR : Can't load font 'Monospace'
I continued to get this error, even after rebooting and the 'courier 12' 
version of ghemical started working.


A similar issue was 'gracefully' fixed in #670613 by adding the Recommends.

Bug#844601: forwarded to new upstream bug

[Ghislain Vaillant]

control: forwarded -1 https://github.com/spyder-ide/spyder/issues/4049

Bug#852455: RM: alsa-base -- ROM; No longer needed, obsolete

[Jordi Mallach]

Hi Scott,

El dc 25 de 01 de 2017 a les 00:14 -0500, en/na Scott Kitterman va
escriure:
> On Tue, 24 Jan 2017 18:04:39 +0100 Jordi Mallach 
> wrote:
> > Package: ftp.debian.org
> > Severity: normal
> > 
> > Hello ftp-master,
> > 
> > I just found out alsa-base is still in the archive.
> > 
> > This source only generates a alsa-base with maintscripts to remove
> > old conffiles, and should have been safe to remove from the archive
> > post-jessie.
> > 
> > Let's kill it before a new release happens, thanks!
> 
> This will have to be addressed first:
> 
> Checking reverse dependencies...
> # Broken Depends:
> mkchromecast: mkchromecast-alsa
> 
> Dependency problem found.
> 
> Please remove the moreinfo tag once it's resolved.

Bug filed and block tag added to this bug.

Thanks!

-- 
Jordi Mallach Pérez  --  Debian developer http://www.debian.org/
jo...@sindominio.net jo...@debian.org http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/

Bug#852213: tigervnc: Buffer overflow in ModifiablePixelBuffer::fillRect

[Salvatore Bonaccorso]

Control: retitle -1 tigervnc: CVE-2017-5581: Buffer overflow in 
ModifiablePixelBuffer::fillRect

On Sun, Jan 22, 2017 at 04:25:22PM +0100, Salvatore Bonaccorso wrote:
> Source: tigervnc
> Version: 1.7.0+dfsg-2
> Severity: grave
> Tags: patch security upstream
> Justification: user security hole
> Forwarded: https://github.com/TigerVNC/tigervnc/pull/399
> 
> Hi
> 
> Cf. http://www.openwall.com/lists/oss-security/2017/01/22/1 where as
> well a CVE was requested for this issue.
> 
> Upstream bug: https://github.com/TigerVNC/tigervnc/pull/399
> Commit: 
> https://github.com/TigerVNC/tigervnc/commit/18c020124ff1b2441f714da2017f63dba50720ba

This has been assigned CVE-2017-5581.

Regards,
Salvatore

Bug#852431: Fwd: Bug#852431: installer broken: multipath-udeb depends on missing libmpathcmd.so.0

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: tag -1 -moreinfo +confirmed,pending

Hello Allan,

Thank you for the extra information.

On Wed, 2017-01-25 at 10:04 +0100, Allan Jacobsen wrote:
> 
> During multipath install, the installer tries to load dm-emc module
> which it should not do, then tries to run /sbin/multipath which gives
> the error:
> 
> disk-detect: /sbin/multipath: error while loading shared libraries:
> libmpathcmd.so.0: cannot open shared object file: No such file or
> directory
> 

Thanks. I just checked, and yes, the shipped binary in the udeb does mention a
library dependency on mpathcmd.

>  
> > How do I reproduce this locally ? A simple LUN discovery through the Stretch
> > installer ? Would be nice if you give me your steps to reproduce.
> > 
> 
> I have not tried it, but i guess if you install multipath-tools on a local
> stretch, and then delete /lib/libmpathcmd.so.0 you would get the same error.
> 
> Best regards
> Allan
> 
- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliIdD8ACgkQpjpYo/Lh
dWnBeQ/7BSSfxDpHN8PswEkX8IoFq7ycW7rdj331oUKDj4imI/1w0hfMd3fENeVo
1B4WUEyVPxyvVukGNXOwxHyD2dzB6jIJ3AYfF3PyRttcfg0fGwocOWCBHWMWpbjc
973q6VhnT99uj+oStn/W+sftyXSNPuZrlzVnqT0u44E4odUOPZJxq/0x9NI7vDVL
kqZNDSx0iMV+Xa+ACo4RT3tRL0YxjbDT5qh2zrfoe44TjPp2tyMtfsV+mE5QOsc2
W+jPJhw2lBJNrkiFjU+VmWbMP1zY7wfd2CtfE9wWomN9Y6y/RObRwqEysReGgXZc
C2uZ1lo2yUQXAs9/P8xnDOQ0dfnsYHYRvyTEiVV9WGlzmnCIadAm09ZlmpCVWtzY
7EteKOmlr8rSXHXj8Dvhntd8xbaz4kiQgE9ggKWVKnGt+soujjgJN7zSYOnk0JoS
SmOLUeow4suOzjTpxLHXcv1ZUBEsBWh4+roIMWd69BMgqqbZ4CadAPrhDeJf50QU
D/kRdOxaQhmj1Q1rA7Po5N2YBh8Hey1QbLa6IuhWIg0RvNsDbloUCywVlgvhic/b
9XgO9P9TABGEDQ1ImYyLVCm9Y4h0FizpfG7KhEeRYhtXhAF8/tHVSvFXSlmJwiuK
IhjP7mb6ZSc7T7hbak/FUiVpl/BpLrBYuXR8q72w1P5TGETUUXo=
=PulZ
-END PGP SIGNATURE-

Bug#851647: hypersan: upstream v4.4 and 'fat runtime' vs suricata

[Sascha Steinbiss]

reassign 851647 suricata
thanks


Hi all,

[...]
>> You could add:
>>
>> Tested-by: Arturo Borrero Gonzalez 
> 
> Done... and force-pushed the --amended commit to my branch.
> 
> I'll open a ticket in the Suricata Redmine then to check with upstream.
> They'll be able to comment further, let's see what they say.

Done, PR is in: https://github.com/inliniac/suricata/pull/2517

Reassigning to suricata as well since Hyperscan is updated now.

Cheers
Sascha



signature.asc
Description: OpenPGP digital signature

Bug#844601: forwarded upstream

[Ghislain Vaillant]

control: forwarded -1 https://github.com/spyder-ide/spyder/issues/4014

Bug#852535: qtile: FTBFS: ::test_multiple_stretches FAILED

[Chris Lamb]

Source: qtile
Version: 0.10.6-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

qtile fails to build from source in unstable/amd64:

  […]

  copying libqtile/widget/memory.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/wallpaper.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/notify.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/sep.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/bitcoin_ticker.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/df.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/groupbox.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/windowname.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/tasklist.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/prompt.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/currentlayout.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/canto.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/wlan.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/mpriswidget.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/imapwidget.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/systray.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/cmus.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/khal_calendar.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/backlight.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/clipboard.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/countdown.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/launchbar.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/moc.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/yahoo_weather.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/she.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  copying libqtile/widget/textbox.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/widget
  creating «BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources
  copying libqtile/resources/__init__.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources
  copying libqtile/resources/default_config.py -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources
  creating 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-empty.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-caution-charging.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-good-charging.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-low.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-full.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-low-charging.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-full-charging.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-missing.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-caution.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-full-charged.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  copying libqtile/resources/battery-icons/battery-good.png -> 
«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/resources/battery-icons
  generating cffi module 
'«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/_ffi_pango.py'
  generating cffi module 
'«BUILDDIR»/.pybuild/pythonX.Y_3.5/build/libqtile/_ffi_xcursors.py'
  running build_scripts
  creating 

Bug#732949: spyder: Internal console spamming

[Ghislain Vaillant]

On Mon, 23 Dec 2013 00:27:56 +0100 =?utf-8?q?=C3=89lie_Gouzien?= 
 wrote:
> Package: spyder
> Version: 2.1.10-2
> Severity: important

This version is now significantly outdated. Could you please verify
whether the issue is still happening on one of the recent versions
being packaged (3.1.2 at the time of writing).

 
> When there is an internal error in spyder, the error shows up and the cursor
> move to it. De-selecting the internal console from the display menu changes
> nothing.
> If for developers it's good, it turns to be a plague for users: if there is a
> recurrent error for any reason (even a "negligeable" error) you are disturbed
> every time a message shows up and have to go back to the line you were editing
> (which mean we have to take the mouse).
> 
> In my case I do have the following error:
> 
> File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/editor.py", line 228,
> in update_queue
> end_callback = self.end_callbacks.pop(id(thread))
> KeyError: 67235920
> 
> and it shows up every 10 s. Working with spyder turns to be impossible with
> it.
> 
> A (according to me) better behavior would be:
> -When you do activate the internal console, errors show up like it is doing 
> now
> -When you do not activate the internal console, it never shows up.

I cannot reproduce this on the new version.

Ghis

Bug#852495: [debian-mysql] Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

[Otto Kekäläinen]

Tags: unreproducible

2017-01-25 0:21 GMT+02:00 Julian Gilbey :
> After upgrading to 10.1 from 10.0, I purged the old
> mariadb-server-10.0 package, but this had two quite unpleasant
> effects: it shut down the server and it removed the init.d links.
> This is because:

I was not able to reproduce this. The 10.1 packages conflict the 10.0
packages, so it is not possible to have them installed at the same
time, and thus end up in a situation where you would remove the 10.0
packages while 10.1 is already installed.

What versions of the packages (including revision numbers) did you
have? What should I do to reproduce this?

Bug#826069: libghemical5v5: breaks color rendering and atom generation in ghemical

[Graham Inggs]

Control: severity -1 important

Has anyone else confirmed this bug report?

I saw the greyscale issue on two different amd64 machines.  I was able 
to add atoms to a molecule, but they didn't appear where I expected 
them.  That could just be me not being familiar with the interface.


It occurred to me later that both machines I tested on had Nvidia 
graphics cards and used the non-free driver.  I then tried on an i386 
netbook with integrated Intel graphics.  At first I ran into #567600, 
but after rebooting after installing the packages suggested in that bug, 
ghemical worked in full colour.


I'm therefore downgrading the severity of this bug.
I also think it may be easier to find if it were reassigned against 
ghemical.

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Michael Meskes]

> Hopefully somebody is prepared to fix all rdepends.

Or better reverts the API change.

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#850211: open-iscsi: Boot with systemd hangs for iSCSI+LUKS+LVM volume

[Christian Seiler]

Control: severity -1 important
Control: clone -1 -2
Control: reassign -2 systemd 230-7
Control: affects -1 cryptsetup
Control: affects -2 open-iscsi cryptsetup
Control: retitle -1 open-iscsi: No support for disabling LUKS volumes on 
shutdown
Control: retitle -2 systemd: cryptsetup-generator does not support LUKS on 
network devices
Control: tags -1 + confirmed stretch sid
Control: tags -2 + upstream

First of all, sorry for the late reply, but I was ill for a while and
then I was quite busy with catching up with other stuff.

The immediate bug you're experiencing is a problem with systemd, so I
am cloning the bug report and reassigning it to the systemd package.
However, in reviewing your setup I've also noticed that there is a
separate problem for your kind of setup in open-iscsi.

I'm including the main part of your bug report for the systemd
maintainers' benefit.

> This is how I setup my volume:
> 
> # The iSCSI part works fine.
> iscsiadm … --login
> 
> # Device shows up as /dev/sdb; I create a /dev/sdb1 partition using
> # fdisk, of type 8e.
> 
> # Create encrypted LUKS volume on /dev/sdb1, open and map as
> # /dev/mapper/sdb1_crypt.
> cryptsetup luksFormat /dev/sdb1
> cryptsetup luksOpen /dev/sdb1 sdb1_crypt \
> --key-file /root/blackbird-ullu
> 
> # Set up LVM PV, VG, and LV mapped to /dev/mapper/blackbird-ullu,
> # with an ext4 filesystem on top.
> pvcreate /dev/mapper/sdb1_crypt
> vgcreate blackbird /dev/mapper/sdb1_crypt
> lvcreate -n ullu -l 100%VG blackbird
> mkfs.ext4 /dev/mapper/blackbird-ullu
> 
> mount /dev/mapper/blackbird-ullu /media/nas
> 
> I have an entry in /etc/crypttab like this:
> 
> sdb1_crypt UUID=ae6b9263-d63c-4515-b7ce-51e5cc4caa9f /root/blackbird-ullu 
> luks
> 
> And an entry in /etc/fstab like this (I've tried various variants here,
> see below):
> 
> /dev/mapper/blackbird-ullu /media/nas ext4 defaults,nofail,_netdev 0 6
> 
> There are three devices involved:
> 
> - /dev/disk/by-uuid/: is the iSCSI target (/dev/sdb)
> - /dev/mapper/sdb1_crypt: result of cryptsetup luksOpen /dev/sdb1 
> - /dev/mapper/blackbird-ullu: LV built on top of sdb1_crypt
> 
> Now I suffer from the 90s wait on startup (before network-online), where
> systemd waits for the dev-mapper-blackbird\x2dullu.device to become
> available, along with dev-disk-by\x2duuid-.device and
> dev-mapper-sdb1_crypt.device.

The problem here is that the cryptsetup-generator in systemd only
supports local block devices, and the dependencies it generates
assume that everything orders indirectly before the local
filesystems.

This causes systemd to wait for the block device underlying the
LUKS encryption _before_ open-iscsi is even started.

This can clearly also be seen by the ordering cycle that's
generated if you manually force the dependencies:

> open-iscsi.service: Found ordering cycle on open-iscsi.service/start
> open-iscsi.service: Found dependency on network-online.target/start
> open-iscsi.service: Found dependency on networking.service/start
> open-iscsi.service: Found dependency on local-fs.target/start
> open-iscsi.service: Found dependency on lvm2-activation.service/start
> open-iscsi.service: Found dependency on cryptsetup.target/start
> open-iscsi.service: Found dependency on 
> systemd-cryptsetup@sdb1_crypt.service/start
> open-iscsi.service: Found dependency on 
> dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device/start
> open-iscsi.service: Found dependency on open-iscsi.service/start

Here you see that systemd-cryptsetup@sdb1_crypt.service depends
on open-iscsi.service (because of your manual dependency), but that
cryptsetup.target depends on systemd-cryptsetup@sdb1_crypt.service,
local-fs.target depends on cryptsetup.target and open-iscsi.service
(correctly) depends on local-fs.target.

Your trick in lowering the device timeout to 1s instead of the explicit
ordering makes this "work" because it causes systemd to immediately
fail systemd-cryptsetup@sdb1_crypt.service immediately at early boot
(before open-iscsi.service is started), and systemd will then start it
again once the device actually appears after open-iscsi logs in to the
target.

Ideally one would want to have an option like _netdev also for
/etc/crypttab, so that it's clear that this specific block device
will only appear later. Unfortunately that doesn't exist yet. [1] So
your workaround in explicitly lowering the device timeout (you can
just do that for
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device
btw., you don't need to set it for other devices) is the only thing
that will make this "work" currently though.





As for the open-iscsi bug I also noticed: on shutdown open-iscsi
tries to tear down all mounts on iSCSI, including layers such as LVM
or multipath, but it doesn't detect LUKS yet, so data may not be
written to disk properly once the iSCSI logout happens.

I plan on doing an upload of 

Bug#852451: ITP: rname -- invoke a program under a different name

[Peter Pentchev]

On Wed, Jan 25, 2017 at 10:13:13AM +0100, Bastian Blank wrote:
> On Tue, Jan 24, 2017 at 05:19:49PM +0200, Peter Pentchev wrote:
> > The rname utility invokes a specified program, passing a different name
> > instead of the name of the program executable.
> 
> You are searching for symbolic links?

Errr, I do believe there was something about ephemeral symbolic links
a couple of lines further down :)

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#851839: Pending fixes for bugs in the java-gnome package

[pkg-java-maintainers]

tag 851839 + pending
thanks

Some bugs in the java-gnome package are closed in revision
f5d8dc31d2bbc276c074d14c8e226eb04f8ce709 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/java-gnome.git/commit/?id=f5d8dc3

Commit message:

Skip the verification of the Java runtime (Closes: #851839)

Bug#852451: ITP: rname -- invoke a program under a different name

[Bastian Blank]

On Tue, Jan 24, 2017 at 05:19:49PM +0200, Peter Pentchev wrote:
> The rname utility invokes a specified program, passing a different name
> instead of the name of the program executable.

You are searching for symbolic links?

Bastian

-- 
"That unit is a woman."
"A mass of conflicting impulses."
-- Spock and Nomad, "The Changeling", stardate 3541.9

Bug#852533: apt-listchanges: [INTL:fr] French translation

[jean-pierre giraud]

Package: apt-listchanges
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french translation, proofread
by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

jipege



fr.po.gz
Description: application/gzip

Bug#852431: Fwd: Bug#852431: installer broken: multipath-udeb depends on missing libmpathcmd.so.0

[Allan Jacobsen]

-- Forwarded message --
From: Allan Jacobsen 
Date: 2017-01-25 7:38 GMT+01:00
Subject: Re: Bug#852431: installer broken: multipath-udeb depends on
missing libmpathcmd.so.0
To: r...@debian.org


Hi Ritesh

Sorry I should have quoted my bugreport againt debian-installer

2017-01-24 15:22 GMT+01:00 Ritesh Raj Sarraf :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Control: tag -1 +moreinfo
>
> On Tue, 2017-01-24 at 12:27 +0100, Allan Jacobsen wrote:
> > I am testing the installer for stretch, and there is an error in the
> > multipath-udeb, as the library libmpathcmd.so is missing from the
> package.
> >
>
> Can you please share what the error is ? Does the error happen during
> multipath
> map creation ?
>
> Package: installation-reports

Boot method: PXE (network install)
Image version: 
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/debian-installer/amd64/
Date: 20170123

Machine: Cisco UCSB-B200-M4
Processor: Intel Xeon E5-2660
Memory: 32Gbyte
Partitions: Not found, that is the problem.

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [E]
Detect hard drives: [E]

During multipath install, the installer tries to load dm-emc module
which it should not do, then tries to run /sbin/multipath which gives
the error:

disk-detect: /sbin/multipath: error while loading shared libraries:
libmpathcmd.so.0: cannot open shared object file: No such file or
directory



> How do I reproduce this locally ? A simple LUN discovery through the
> Stretch
> installer ? Would be nice if you give me your steps to reproduce.
>
> I have not tried it, but i guess if you install multipath-tools on a local
stretch, and then delete /lib/libmpathcmd.so.0 you would get the same error.

Best regards
Allan

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Michael Meskes]

On Mon, Jan 23, 2017 at 09:43:40PM -0600, Courtney Bane wrote:
> I just ran in to this problem affecting my ekeyd installation (just
> reported as #852380). Unix domain sockets are available, but the API
> changed in the new version.
> 
> Instead of calling socket.unix() to create a socket, you now need to
> call socket.unix.tcp(). Note that there is another API change coming
> that changes this to socket.unix.stream(). (This change is not yet in
> Debian. It's upstream commit 3a33c37b;
> https://github.com/diegonehab/luasocket/commit/3a33c37b9ce852d0b3531e82c6ffdb47bb937f0a.)

Wait, are you saying that we plan to release with a version of lua-socket that
is undergoing API changes that break software using it? While we are in freeze? 

Great plan, if you ask me, sigh.

Hopefully somebody is prepared to fix all rdepends.

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#852532: olvwm: source code not 64-bit clean, SIGSEGV everywhere

[Adam M. Costello]

Package: olvwm
Version: 4.4.3.2p1.4-28.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The latest version (4.4.3.2p1.4-28.2) immediately crashes with SIGSEGV
on my x86_64 system.  I tried building it from source with debug
symbols, and discovered that it is not 64-bit clean (examples below).

The previous version (4.4.3.2p1.4-28.1), which was built 4 years ago,
works.  It can no longer be built (because glibc no longer supports some
old APIs), but I'm guessing that the build tools from 4 years ago must
have produced machine code where all the addresses fall in the bottom
4GB of the virtual address space, so that the 64-bit uncleanliness is
hidden.

I'm not sure what to do about this.  Fixing all the source code is
likely to be a large project.  Is there a way to tell today's build
tools to produce machine code confined to the bottom 4GB of the virtual
address space?

Example SIGSEGVs:

In clients/olvwm-4.1/cursors.c in InitCursors() there is a gratuitous
cast of a pointer to an int before it is passed to a function that takes
a pointer:

st_insert(cursorTable, (int) p->name, (char *) p->num);

After I fixed that, there was SIGSEGV in image.c in this line:

b = (Button *) MemAlloc(sizeof(Button));

The problem is that mem.h is not included, so the compiler assumes that
MemAlloc() returns an int rather than a pointer, so the pointer gets
truncated to 32 bits.

After I fixed that, there was a SIGSEGV in states.c in this line:

cli->wmState = initstate;

but gdb said cli was optimized out, so I don't know what's going on
there.  I suspect that these 64-bit issues are pervasive.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages olvwm depends on:
ii  libc6 2.24-8
ii  libx11-6  2:1.6.4-2
ii  libxext6  2:1.3.3-1
ii  libxpm4   1:3.5.12-1

olvwm recommends no packages.

Versions of packages olvwm suggests:
pn  menu   
pn  olwm   
pn  xview-clients  

-- no debconf information

Bug#852451: ITP: rname -- invoke a program under a different name

[Peter Pentchev]

On Wed, Jan 25, 2017 at 11:11:31AM +0300, Dmitry Bogatov wrote:
> 
> [2017-01-24 17:19] Peter Pentchev 
> >
> > Package: wnpp
> > Severity: wishlist
> > Owner: Peter Pentchev 
> >
> > * Package name: rname
> >   Version : 1.0.2
> >   Upstream Author : Peter Pentchev 
> > * URL : https://devel.ringlet.net/sysutils/rname/
> > * License : BSD-2-clause
> >   Programming Lang: C
> >   Description : invoke a program under a different name
> >
> > The rname utility invokes a specified program, passing a different name
> > instead of the name of the program executable.  This could be useful in
> > a number of cases, both during software development, testing, and in
> > production use.  There are many programs that do different things based
> > on what name they have been invoked under; the rname utility avoids
> > the need to e.g. create ephemeral symlinks to run these programs in
> > some conditions when they have not been completely installed.
> >
> > I originally wrote this tool in 2000 and I'm resurrecting it now for
> > the purpose of writing unit and integration tests for just such
> > a multifaceted program.
> 
> One more argv0 implementation? I know at least two:
> 
> $ dpkg -S argv0
> ucspi-tcp: /usr/bin/argv0
> [...]
> $ dpkg -S chpst
> runit: /usr/bin/chpst
> [...]
> 
> Probably, there is already a lot.

OK, so this is embarrassing :)  The rname webpage even refers to
ucspi-tcp as the reason I wrote this back in 2000; guess I didn't
notice argv0 there even then :/

Thanks for pointing this out!

And as for Christian and Josh's emails, yes, I should've mentioned
straight up front that I did indeed know about exec -a and I did
know that I can do this with Perl and Python.  However, for many
command-line tools that I write (and I've written quite a lot, even
though not all of them have seen the light of day), the test suite
is one of these three:
- a Perl t/*.t script using Test::Command
- a POSIX shell t/*.t script outputting TAP
- just a couple of lines in a Makefile's "test" target

Of these, only Test::Command looks like it might be possible to be
extended in a sensible way.  Of course, the other two may go for
"bash required, it's available almost everywhere anyway", but I do
tend to steer clear of this point of view (long-time FreeBSD user
and, once upon a time, committer; also more hours than I like to
remember invested in former jobs herding Solaris and HP/UX boxes...).

However, since there is already an argv0 in uscpi-tcp (argh!),
I'm closing this.  Thanks for all the responses!

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#849192: netcat-openbsd: different behaviour - outout vanished

[Stefan Bader]

On Fri, 23 Dec 2016 12:47:10 +0100 (CET) Cristian Ionescu-Idbohrn
 wrote:
> Package: netcat-openbsd
> Version: 1.130-1

> 
>   $ echo 'ehlo itsme' | nc.openbsd host.example.com 25
> 
> There is _no_ output.
> 


This particular problem (along with the same no-output when using "nc -d -l")
seems to be caused by a Debian change which introduces the -q option[1]. This
causes the readwrite loop to exit before handling possible return data or the
received data in the listen case.
One draw back with the proposed fix: while this now allows to receive the data
sent back, it will hang there until stopped. That problem comes from upstream
changes. They added a -N flag to send shutdown messages to the remote socket
when the input stream was closed (which was the default in the old version of
nc). So:

echo 'ehlo itsme' | nc.openbsd -N host.example.com 25

would then behave as expected. Not sure how to handle this. IMO it would have
been better if upstream kept the old behaviour as default and added an option to
*not* do the shutdown. But now that its done that way it might be confusing to
change it.

-Stefan



[1] 0005-quit-timer.patch

--- one possible fix ---

Description: Fix handling of delayed exit option
 The option for delayed exit (-q#) existed before but since upstream
 rewrote the readwrite call the patch adding it had to be adapted.
 However the current implementation causes the loop to exit too early.
 Move the exit handling to those places which do exit the loop in the
 original code. While on it also add some code to close the net_fd on
 delayed exit.
Author: Stefan Bader 

Index: netcat-openbsd-1.130/netcat.c
===
--- netcat-openbsd-1.130.orig/netcat.c
+++ netcat-openbsd-1.130/netcat.c
@@ -178,6 +178,8 @@ char*proto_name(int uflag, int dccpf

 static int connect_with_timeout(int fd, const struct sockaddr *sa,
 socklen_t salen, int ctimeout);
+
+intquit_fd = -1;
 static void quit();

 int
@@ -1028,19 +1030,31 @@ readwrite(int net_fd)
/* both inputs are gone, buffers are empty, we are done */
if (pfd[POLL_STDIN].fd == -1 && pfd[POLL_NETIN].fd == -1
&& stdinbufpos == 0 && netinbufpos == 0) {
-   close(net_fd);
-   return;
+   if (qflag == 0) {
+   close(net_fd);
+   return;
+   }
+   goto delay_exit;
}
/* both outputs are gone, we can't continue */
if (pfd[POLL_NETOUT].fd == -1 && pfd[POLL_STDOUT].fd == -1) {
-   close(net_fd);
-   return;
+   if (qflag == 0) {
+   close(net_fd);
+   return;
+   }
+   goto delay_exit;
}
/* listen and net in gone, queues empty, done */
if (lflag && pfd[POLL_NETIN].fd == -1
&& stdinbufpos == 0 && netinbufpos == 0) {
-   close(net_fd);
-   return;
+   if (qflag == 0) {
+   close(net_fd);
+   return;
+   }
+delay_exit:
+   quit_fd = net_fd;
+   signal(SIGALRM, quit);
+   alarm(qflag);
}

/* poll */
@@ -1159,20 +1173,10 @@ readwrite(int net_fd)
if (pfd[POLL_NETOUT].fd != -1 && Nflag)
shutdown(pfd[POLL_NETOUT].fd, SHUT_WR);
pfd[POLL_NETOUT].fd = -1;
-   goto exit_on_eof;
}
/* net in gone and queue empty? */
if (pfd[POLL_NETIN].fd == -1 && netinbufpos == 0) {
pfd[POLL_STDOUT].fd = -1;
-   exit_on_eof:
-   /* if the user asked to exit on EOF, do it */
-   if (qflag == 0)
-   return;
-   /* if user asked to die after a while, arrange 
for it */
-   else if (qflag > 0) {
-   signal(SIGALRM, quit);
-   alarm(qflag);
-   }
}
}
 }
@@ -1615,6 +1619,8 @@ usage(int ret)
  */
 static void quit()
 {
-/* XXX: should explicitly close fds here */
+if (quit_fd >= 0)
+   close(quit_fd);
+
 exit(0);
 }



signature.asc
Description: OpenPGP digital signature

Bug#852531: mkchromecast-alsa: Depends on obsolete package alsa-base

[Jordi Mallach]

Package: mkchromecast-alsa
Version: 0.3.6-3
Severity: important

Hi Muammar,

Your package depends on alsa-base, which has been an empty, featureless
package for many years.

Please drop this dependency: what alsa-base did in the past is now done
by kmod itself and hence you don't need to replace it with other
dependencies.

My goal is to get rid of alsa-base for stretch, so please upload even if the
freeze is ongoing, I'll try to get an exception for your change.

Thanks,
Jordi

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

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

Bug#851195: [debian-mysql] Bug#851195: Bug#851195: Bug#851195: mariadb-server-10.1: Time Zone system tables are empty

[Otto Kekäläinen]

I tested this with the upstream version too:


Server version: 10.1.21-MariaDB-1~sid mariadb.org binary distribution

Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> SELECT COUNT(*) FROM mysql.time_zone;
+--+
| COUNT(*) |
+--+
|0 |
+--+
1 row in set (0.00 sec)



Based on discussions on #mariadb it seems that this table is maybe on
purpose empty, and it is up to the database admin to populate and keep
it updated. Anyway, the fix should be done upstream and then
identically applied here in Debian. If you want to invest more time in
this, please file and issue at jira.mariadb.org and mark this Debian
issue with "forwarded https"

Bug#852530: terminix: Terminix fails to start

[eNovance]

Package: terminix
Version: 1.4.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since the update to version 1.4.2, terminix fails to start with the
following message :

terminix: symbol lookup error: terminix: undefined symbol:
_D7gobject7ObjectG7ObjectG11addOnNotifyMFDFC7gobject9ParamSpec9ParamSpecC7gobject7ObjectG7ObjectGZvAyaE4gtkc12gobjecttypes13GConnectFlagsZv

Thanks


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

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

Versions of packages terminix depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  libc62.24-9
ii  libgtkd-3-0  3.5.1-1
ii  libphobos2-ldc71 1:1.1.0+b6-2
ii  libvted-3-0  3.5.1-1
ii  libx11-6 2:1.6.4-2
ii  terminix-common  1.4.2-2

terminix recommends no packages.

terminix suggests no packages.

-- no debconf information