Bug#822827: python3-pyqt5: qt5-5-1 abi dependencies makes install impossible against Qt5.6

[Marc J. Driftmeyer]

I've installed the PyQt 5.6 and look forward to when Calibre moves away 
from the 5-5-1 hard dependency. For now, I can use their pre-builts.



Thanks for your help,


Marc


On 05/01/2016 10:45 AM, Dmitry Shachnev wrote:

Control: notfound -1 5.6
Control: found -1 pyqt5/5.6+dfsg-1
Control: fixed -1 pyqt5/5.6+dfsg-2

Hi Marc,

On Wed, Apr 27, 2016 at 05:53:18PM -0700, Marc J. Driftmeyer wrote:

Yet, in Debian we get this:

python3-pyqt5 depends on qtbase-abi-5-5-1
qtbase-abi-5-5-1 does not appear to be available
python3-pyqt5 suggests python3-pyqt5-dbg

I hope this is an oversight. As of now its useless against Qt 5.6.0 which being 
in Sid.

I have uploaded a PyQt version built against Qt 5.6 to experimental.

--
Dmitry Shachnev


--

Marc J. Driftmeyer

main: m...@reanimality.com 
book: m...@holoworlds.net 
main:www.reanimastudios.com 
book:www.holoworlds.net 

Bug#823480: Error: no "view" mailcap rules found for type "inode/directory"

[積丹尼 Dan Jacobson]

Package: mime-support
Version: 3.60

# su - nobody
No directory, logging in with HOME=/
nobody@jidanni3:/$ xdg-open /tmp
Error: no "view" mailcap rules found for type "inode/directory"
(then iceweasel is called).

Bug#820538: Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/%{ <-- HERE (.*?)}/ at /usr/bin/run-mailcap line 528.

[積丹尼 Dan Jacobson]

> "CP" == Charles Plessy  writes:
>> Error: no "view" mailcap rules found for type "inode/directory"

CP> I can not reproduce this on my computer.  Please open a separate bug if 
needed.

OK I did.

Bug#823479: xul-ext-stylish: Please package upstream version 2.0.6

[Carl Suster]

Package: xul-ext-stylish
Version: 2.0.3-1
Severity: normal

Dear Maintainer,

Recently stylish hasn't been working at all for me, and looking at the upstream
changelog it seems that support for version 46 of firefox was added in version
2.0.5, with the subsequent release 2.0.6 fixing a regression introduced by that
version (see https://addons.mozilla.org/en-US/firefox/addon/stylish/versions/).


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

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

Versions of packages xul-ext-stylish depends on:
ii  firefox  46.0-1
ii  firefox-esr  45.1.0esr-1
ii  icedove  38.7.2-1

xul-ext-stylish recommends no packages.

xul-ext-stylish suggests no packages.

-- no debconf information

Bug#822726: dclock: blink/seconds issues

[J meritt]

Attached are patches for the changes described below.

Bugs fixed:

   1. Turning off blink or seconds with the other already off sets the
   update time to the second of the minute the change occurred. This makes it
   appear the clock is up to 1 minute slow after the change.  This is because
   the wakeup time is set to 1 minute from the toggle event instead of the
   start of the next minute.
   2. Dclock waits for child processes to finish playing audio, so the
   display doesn't update during that time.  This also causes update time to
   creep as above when seconds and blink are off because the wakeup time is
   set to 60 Sec. from the finish of the child process instead of  the first
   second of the next minute.
   3. Unless seconds are active, you can't turn on blink without waiting
   for the next minute timeout -- which may appear random due to (1).  The
   toggle function fails to reset the frame rate to 1 Sec until the next
   timeout -- up to a minute away.
   4. Toggling blink off, then on with seconds off -- also seconds with
   blink off -- in the minute of the alarm/bell causes the alarm/bell to sound
   again.  This is caused by the expectation dclock will wake only once during
   the minute of the alarm when the update rate is set to 60 Sec.  XEvents
   causing redisplay will set it off as will additional improperly controlled
   wakeups from the previous 1 Sec frame rate.  The fix is to compare against
   calendar  time, not time of day and to compute the next alarm/bell time
   when servicing the existing one.
   5. The alarm flashing goes on forever.  toggle_reverse_video() calls
   show_time() which then calls toggle_reverse_video() again the alarm is
   flashing.  Recursion can build on fast systems or on those with ulimit(1)
   for stack set low, until dclock crashes on stack overflow or SEGV.   A
   control to toggle reverse video once per frame until a counter expires
   fixes this.  Alarm flashing gets its own frame rate to control the flash
   rate instead of racing.
   6. Toggling reverse video repeatedly soon causes the reverse display to
   become corrupt and unreadable.   This is magically fixed by removing the
   recursion already causing other problems.
   7. When seconds or blinking are enabled, some updates get missed.
   Instrumentation shows 2 frames processed in the same second, then, none the
   next.  This appears to be a truncation of the wait time, so it is 1 TICK
   quicker than is desired.  It's fixed by waiting well more than a tick into
   the next second to wake -- 10mS or even 20mS are not noticeable but work
   well to avoid missed Seconds.
   8. If there is a failure in audio play, dclock begins using the X bell
   exclusively.  Dclock must be restarted to get audio back.  There is little
   penalty for continuing to try audio and falling back to X bell on each
   failed attempt, so that is the new behavior.

Features added:

   1. Ringing the bell  twice at the top of the hour is limiting.  A
   setting, "singleBell", when true, makes dclock chime just once at each bell
   event instead of the arbitrary two at the top of the hour, one at the
   bottom.  Scripting an audioPlay executable for advanced chimes is more
   convenient with this set TRUE.
   2. An "hourlyBells" resource defaulting to 2 has been created to allow
   quarter bells (when set to 4.)  This indicates the number of times per hour
   bells should play.  The right script in dclock*audioPlay could chime like
   Westminster or strike the hour like a cuckoo clock. (Yes, Westminster
   starts at 25 seconds before the hour, because the first stroke of the hour
   must be within 1 Sec of the start of the hour.  No, this change does not
   include that capability.  Precession parameters could be included in
   hourlyBells.)
   3. Man page edited to reflect changes above and correct formatting.


Dclock-2.2.2.1.tbz
Description: application/bzip-compressed-tar

Bug#823466: [pkg-go] Bug#823466: golang-github-docker-libnetwork: Please update to latest upstream release

[Dmitry Smirnov]

On Thursday, 5 May 2016 1:15:21 AM AEST Potter, Tim (HPE Linux Support) 
wrote:
> Please upload the latest snapshot of the golang-github-docker-libnetwork
> package, 0.7.0~rc.6+dfsg.  I've already packaged this in the repo on
> alioth.

Do we _really_ need ~RC version? I prefer to upload proper stable releases 
whenever possible...

-- 
Best wishes,
 Dmitry Smirnov.

---

I cannot believe in a God who wants to be praised all the time.
-- Friedrich Nietzsche


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

Bug#823478: RFS: python3-protobuf3/0.2.1-2 [ITP]

[Jonathon Love]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "python3-protobuf3"

 * Package name: python3-protobuf3
   Version : 0.2.1-2
   Upstream Author :Sergey Petrov 
 * URL : https://github.com/Pr0Ger/protobuf3
 * License : MIT
   Section : python

It builds the binary package:

  python3-protobuf3 - implementation of Google's Protocol Buffers for Python 3

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

https://mentors.debian.net/package/python3-protobuf3


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

dget -x 
https://mentors.debian.net/debian/pool/main/p/python3-protobuf3/python3-protobuf3_0.2.1-2.dsc

More information about hello can be obtained from 
https://github.com/Pr0Ger/protobuf3

with thanks
   Jonathon

Bug#823477: chromium: Chromium generates many kernel audit messages

[Jerry Quinn]

Package: chromium
Version: 50.0.2661.94-1
Severity: normal

Dear Maintainer,

chromium generates many security messages in the kernel log, like 1
per second whenever chromium is rurnning.  The following is an example:

May  4 23:22:57 cerberus kernel: [410461.001883] audit: type=1326
audit(1462418577.785:303305): auid=1000 uid=1000 gid=1000 ses=1
pid=2191 comm="chromium" exe="/usr/lib/chromium/chromium" sig=0
arch=c03e syscall=2 compat=0 ip=0x7fe56e79ef5f code=0x5




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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.0-1
ii  libatk1.0-0  2.20.0-1
ii  libavcodec57 7:3.0.1-3
ii  libavformat577:3.0.1-3
ii  libavutil55  7:3.0.1-3
ii  libc62.22-7
ii  libcairo21.14.6-1+b1
ii  libcups2 2.1.3-5
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.1.1-1
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:5.3.1-14
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.0-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.30-1.1
ii  libjpeg62-turbo  1:1.4.2-2
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.23-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpci3  1:3.3.1-1.1
ii  libspeechd2  0.8-7+b1
ii  libstdc++6   5.3.1-14
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.3+dfsg1-1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-2.1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

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

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#823344: bareos-storage: Automatic Volume Labeling not working after upgrade to 15.2.3

[Soren Stoutner]

That resolved the problem.  Thank you.

On Wednesday, May 04, 2016 11:18:18 PM Felix Geyer wrote:
> Could you please try if the problem goes away when you set RemovableMedia =
> no?
> 
> Felix

-- 
Soren Stoutner
Small Business Tech Solutions
623-262-6169
so...@smallbusinesstech.net
www.smallbusinesstech.net

Bug#823476: chromium: Chromium generates many kernel audit messages

[Jerry Quinn]

Package: chromium
Version: 50.0.2661.94-1
Severity: normal

Dear Maintainer,

[filing this a second time because I'm not sure the first filing went through]

chromium generates many security messages in the kernel log, like 1
per second whenever chromium is rurnning.  The following is an example:

May  4 23:22:57 cerberus kernel: [410461.001883] audit: type=1326
audit(1462418577.785:303305): auid=1000 uid=1000 gid=1000 ses=1
pid=2191 comm="chromium" exe="/usr/lib/chromium/chromium" sig=0
arch=c03e syscall=2 compat=0 ip=0x7fe56e79ef5f code=0x5

Filed as 609369 with upstream.



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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.0-1
ii  libatk1.0-0  2.20.0-1
ii  libavcodec57 7:3.0.1-3
ii  libavformat577:3.0.1-3
ii  libavutil55  7:3.0.1-3
ii  libc62.22-7
ii  libcairo21.14.6-1+b1
ii  libcups2 2.1.3-5
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.1.1-1
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:5.3.1-14
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.0-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.30-1.1
ii  libjpeg62-turbo  1:1.4.2-2
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.23-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpci3  1:3.3.1-1.1
ii  libspeechd2  0.8-7+b1
ii  libstdc++6   5.3.1-14
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.3+dfsg1-1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-2.1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

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

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#823322: please build "systemd-sysusers" binary

[Martin Pitt]

Hey Felipe,

Felipe Sateler [2016-05-03 10:06 -0300]:
> So, if we don't want to get in the business of defining users, just
> providing the binary would be sufficient for this purpose.

TBH, I see little reason to not just enable it wholesale [1]. There
are no new build or binary dependencies, it does not change the
default behaviour as the .service is ConditionNeedsUpdate=/etc (which
will practically never trigger -- we don't support empty /etc in
Debian yet), but this introduces useful functionality for moving the
adduser business to become declarative. The main downside is that it
increases the package size by ~ 380 kB (uncompressed).

If we do this, we should do it correctly though and patch
/usr/lib/sysusers.d/basic.conf to have Debian's static gids and remove
wheel.

Opinions/objections?

Martin

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

Bug#823369: adacontrol: FTBFS: t_representation_clauses vs. big-endian systems

[Aaron M. Ucko]

Jean-Pierre Rosen  writes:

> Could you try adding this line as the first line of
> t_representation_clauses.adb:
> pragma Ada_2005;

That's certainly a reasonable suggestion, but it just resulted in
different errors (observed on partch.d.o, a powerpc porterbox):

t_representation_clauses.adb:90:23: machine scalar rules not followed for "S"
t_representation_clauses.adb:90:23: last bit + 1 (81) exceeds maximum machine 
scalar size (64)
t_representation_clauses.adb:90:23: and is not a multiple of Storage_Unit (8) 
(RM 13.5.1(10))

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#823475: golang-google-cloud: Please update to latest upstream snapshot

[Potter, Tim (HPE Linux Support)]

Package: golang-google-cloud
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest snapshot of the golang-google-cloud package,
0.0~git20160413.  I've already packaged this in the repo on alioth.

I've added a new binary package to distribute the rest of the APIs that
aren't packaged in the compute-metadata package.  Misc other packaging
tweaks were also made.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#823474: RFS: btrfs-progs/4.5.2-0.1~exp1

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "btrfs-progs".  I've read
upstream reports of regressions in the 4.5.x series that were solved
by downgrading to 4.4.x, so I believe that it is most appropriate to
upload to experimental at this time.  When the reports of regressions
are solved in a future upstream version I will update this package and
request an upload to sid.

Package name: btrfs-progs
Version: 4.5.2-0.1~exp1
Section: admin

It builds these binary packages:

btrfs-progs - Checksumming Copy on Write Filesystem utilities
btrfs-progs-dbg - Checksumming Copy on Write Filesystem utilities (debug)
btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) (udeb)
btrfs-tools - transitional dummy package
btrfs-tools-dbg - transitional dummy package

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

https://mentors.debian.net/package/btrfs-progs

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

dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.5.2-0.1~exp1.dsc

Changes since the last upload:

  * Non-maintainer upload.
  * New upstream release.
  * Add upstream changelog.
  * Update standards version to 3.9.8 (no changes needed).
  * Add btrfs-convert support to initramfs (Closes: #801192).
  * Divert btrfs-convert to a wrapper script that warns against its use.

Thanks again!
Nicholas

Bug#823416: ITP: libjs-jquery-migrate -- Migrate older jQuery code to jQuery 1.9+

[Paul Wise]

On Wed, May 4, 2016 at 10:49 PM, Jean-Michel Vourgère wrote:

> That small javascript library is already used by a few packages:

Please let the security team know about these embedded code copies:

https://wiki.debian.org/EmbeddedCodeCopies

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#823473: golang-golang-x-oauth2

[Potter, Tim (HPE Linux Support)]

Package: golang-golang-x-oauth2
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest snapshot of the golang-golang-x-oauth2 package,
0.0~git20160416.0.7e9cd5d.  I've already packaged this in the repo on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#820538: Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/%{ <-- HERE (.*?)}/ at /usr/bin/run-mailcap line 528.

[Charles Plessy]

Control: forcemerge 810587 -1

Le Sun, Apr 10, 2016 at 12:19:31AM +0800, 積丹尼 Dan Jacobson a écrit :
> Package: mime-support
> Version: 3.59
> Severity: wishlist
> File: /usr/bin/run-mailcap
> 
> $ xdg-open /tmp
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/%{ <-- HERE (.*?)}/ at /usr/bin/run-mailcap line 528.

Hi,

thanks for the report.  The problem with the warning message was already
reported in #810587 and I closed it with the upload of version 3.60 a few days
ago.

> Error: no "view" mailcap rules found for type "inode/directory"

I can not reproduce this on my computer.  Please open a separate bug if needed.

Have a nice day,

Charles

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan

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

[Pierre Ynard]

severity 823465 critical
retitle 823465 New binaries won't run at all on i586 Pentium MMX due to
illegal instruction
stop

It seems like I was a bit quick to draw conclusions, and this bug
doesn't just affect the new dpkg packages with a lengthy changelog; it's
just that these were the first packages that I tried to upgrade and
immediately failed. Other packages like tar 1.28-2.1, which was only
rebuilt with a patch for Hurd/KFreeBSD, and openssl 1.0.2h-1, with just
a new upstream version, exhibit the same illegal instruction problem.
Apparently perl 5.22.2-1 was still fine. I didn't try upgrading more!

So it seems the archive is filling with new builds that won't run on my
hardware. Great! Sorry for the noise, please assist with triaging.

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

Bug#823472: system-config-printer-udev: Adding printer fails, logging "Unknown option: -"

[Matijs van Zuijlen]

Package: system-config-printer-udev
Version: 1.5.7-1
Severity: normal

Connecting a printer via USB does not make it available automatically,
and the following appears in the log:

May  4 10:31:19 walnut udev-configure-printer: URI match: 
usb://Canon/MG3200%20series?serial=823819=1
May  4 10:31:19 walnut udev-configure-printer: URI of detected printer: 
usb://Canon/MG3200%20series?serial=823819=1, normalized: canon mg3200 
series serial 823819 interface 1
May  4 10:31:19 walnut udev-configure-printer: About to add queue for 
usb://Canon/MG3200%20series?serial=823819=1
May  4 10:31:19 walnut udev-configure-printer[29497]: Unknown option: -
May  4 10:31:19 walnut udev-configure-printer[29497]: usage: /usr/bin/python3 
[option] ... [-c cmd | -m mod | file | -] [arg] ...
May  4 10:31:19 walnut udev-configure-printer[29497]: Try `python -h' for more 
information.

It seems this was fixed upstream but not released yet: 

https://github.com/twaugh/system-config-printer/commit/68f059e44942467ddeee4977d10f2b3a961c9f3a

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

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

Versions of packages system-config-printer-udev depends on:
ii  libc62.22-7
ii  libcups2 2.1.3-5
ii  libglib2.0-0 2.48.0-1
ii  libudev1 229-5
ii  libusb-1.0-0 2:1.0.20-1
ii  python3-cups 1.9.73-1
ii  python3-cupshelpers  1.5.7-1
ii  python3-dbus 1.2.4-1
pn  python3:any  

system-config-printer-udev recommends no packages.

system-config-printer-udev suggests no packages.

-- no debconf information

Bug#823471: golang-github-miekg-pkcs11: please update to latest upstream snapshot

[Potter, Tim (HPE Linux Support)]

Package: golang-github-miekg-pkcs11
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest snapshot of the golang-github-miekg-pkcs11 package,
0.0~git20160412.0.994d290.  I've already packaged this in the repo on alioth.


Tim.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#823470: RFS: sequitur-g2p/0.0.r1668.r3-1 -- Grapheme to Phoneme conversion tool

[Giulio Paci]

Package: sponsorship-requests
Severity: wishlist

Dear all,

I am looking for a sponsor for an updated version of my package "sequitur-g2p"

 * Package name: sequitur-g2p
   Version : 0.0.r1668.r3-1
   Upstream Author : Maximilian Bisani 
 * URL : 
http://www-i6.informatik.rwth-aachen.de/web/Software/g2p.html
 * License : GPL-2
   Section : science

It builds those binary packages:

   sequitur-g2p - Grapheme to Phoneme conversion tool


You can download the package with git using this command:

   git clone git://anonscm.debian.org/collab-maint/sequitur-g2p.git

More information about sequitur-g2p can be obtained from 
http://www-i6.informatik.rwth-aachen.de/web/Software/g2p.html.

A package review is very welcome as well.

Regards,
 Giulio

Bug#821043: wesnoth-1.13-core: fails to upgrade: update-alternatives: error: alternative link /usr/share/man/de/man6/wesnoth.6.gz is already managed by wesnoth.de.6.gz (slave of wesnoth)

[Vincent Cheng]

Control: tag -1 + moreinfo unreproducible

On Thu, Apr 14, 2016 at 3:10 PM, Axel Beckert  wrote:
> Package: wesnoth-1.13-core
> Version: 1:1.13.4-1
> Severity: serious
>
> Hi,
>
> trying to upgrade wesnoth-1.13-core from 1:1.13.2-1 to 1:1.13.4-1 fails
> as follows:
>
> Setting up wesnoth-1.13-core (1:1.13.4-1) ...
> update-alternatives: error: alternative link 
> /usr/share/man/de/man6/wesnoth.6.gz is already managed by wesnoth.de.6.gz 
> (slave of wesnoth)
> dpkg: error processing package wesnoth-1.13-core (--configure):
>  subprocess installed post-installation script returned error exit status 2
> Errors were encountered while processing:
>  wesnoth-1.13-core
>
> Accordingly all packages depending on wesnoth-1.13-core fail as well.
>
> Please note that wesnoth-1.12 is also installed. Current state of all
> wesnoth-related packages on this system:

I can't reproduce this error at all. I had no issues upgrading from
wesnoth-1.13 1.13.2-1 to 1.13.4-1 on my own system, with wesnoth-1.12
installed at the same time. I also can't reproduce this in a clean
pbuilder chroot, i.e.:

# pbuilder --create --distribution sid --mirror http://ftp.ca.debian.org/debian
# pbuilder login
# apt-get install wesnoth-1.12
# echo "deb http://snapshot.debian.org/archive/debian/20160331T221016Z/
experimental main" > /etc/apt/sources.list.d/exp.list
# apt-get -o Acquire::Check-Valid-Until=false update
# apt-get install wesnoth-1.13 # installs 1.13.2-1 from snapshot.d.o
# echo "deb http://ftp.ca.debian.org/debian experimental main" >
/etc/apt/sources.list.d/exp.list
# apt-get update
# apt-get dist-upgrade # installs 1.13.4-1 successfully

And piuparts doesn't report any installation errors either [1],
although I suppose the piuparts.d.o reports don't mean much since it's
just testing clean installs of 1.13.4-1, not upgrades from 1.13.2-1 to
1.13.4-1.

I didn't change anything in any of the maintscripts when I updated the
packaging for wesnoth-1.13 1.13.4-1, so I'm frankly stumped as to why
you're seeing this error. Rhonda, any ideas?

Regards,
Vincent

[1] 
https://piuparts.debian.org/experimental/maintainer/v/vch...@debian.org.html#wesnoth-1.13

Bug#823469: golang-github-fluent-fluent-logger-golang: Please update to latest upstream release

[Potter, Tim (HPE Linux Support)]

Package: golang-github-fluent-fluent-logger-golang
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest snapshot of the 
golang-github-fluent-fluent-logger-golang package,
1.1.0.  I've already packaged this in the repo on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#823468: xserver-xorg-input-synaptics: touchpad no longer accepting double-tap as input on Thinkpad T550

[Kyle Bentley]

Package: xserver-xorg-input-synaptics
Version: 1.8.3-1+b1
Severity: important

Dear Maintainer,

I'm using a Thinkpad T550.  Up until a few days ago, everything was working 
normally with both the touchpad, \
and the trackpoint.  Recently, the touchpad has ignored any double touch to act 
as a mouse click.  All other \
components are working normally; the bottom buttons that are part of the 
touchpad, the scrolling, and the three \
buttons that are at the top of the trackpad.

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

lrwxrwxrwx 1 root root 13 Oct 28  2015 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Apr  5 02:05 /usr/bin/Xorg

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

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

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 143 Apr 22 10:00 20-intel.conf

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

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

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 22424 May  4 19:56 /var/log/Xorg.0.log

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

[ 4.206] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[ 4.207] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 4.209] (--) PCI:*(0:0:2:0) 8086:1616:17aa:2223 rev 9, Mem @ 
0xe000/16777216, 0xc000/536870912, I/O @ 0x3000/64
[ 4.209] (II) LoadModule: "glx"
[ 4.210] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4.223] (II) Module glx: vendor="X.Org Foundation"
[ 4.223]compiled for 1.18.3, module version = 1.0.0
[ 4.223]ABI class: X.Org Server Extension, 

Bug#823467: RFS: flatbuffers/1.3.0-2 [ITP]

[Jonathon Love]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

  * Package name : flatbuffers
Version: 1.3.0-2
Upstream Author: Wouter van Oortmerssen
  * URL : http://google.github.io/flatbuffers/
  * License: Apache-V2
Section: libdevel

It builds the binary packages:

  flatbuffers-compiler - efficient cross platform serialization library
  libflatbuffers-dev - efficient cross platform serialization library
  libflatbuffers-java - efficient cross platform serialization library
  libjs-flatbuffers - efficient cross platform serialization library

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


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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/f/flatbuffers/flatbuffers_1.3.0-2.dsc


More information about flatbuffers can be obtained from 
http://google.github.io/flatbuffers/ and 
https://github.com/google/flatbuffers


with thanks

  Jonathon Love

Bug#823466: golang-github-docker-libnetwork: Please update to latest upstream release

[Potter, Tim (HPE Linux Support)]

Package: golang-github-docker-libnetwork
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest snapshot of the golang-github-docker-libnetwork 
package,
0.7.0~rc.6+dfsg.  I've already packaged this in the repo on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#809065:

[Tom Lee]

Thanks Artur! I'll land this when I get a few moments spare.

-- 
*Tom Lee */ http://tomlee.co / @tglee 

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

[Pierre Ynard]

Package: dpkg
Version: 1.18.6
Severity: important

After upgrading from version 1.18.4 to 1.18.6, dpkg binary executables
will not run on my system anymore. They will crash with an "illegal
instruction" error. In fact, apt-get aborts during the upgrade because
dpkg crashes after unpacking the new version of itself. Of course,
this leaves the system with a broken dpkg so I can't downgrade to the
previous version either (at least not without doing things by hand with
the help of a healthy system).

>From /var/log/dpkg.log:

2016-05-05 00:49:42 startup archives unpack
2016-05-05 00:49:44 upgrade dpkg:i386 1.18.4 1.18.6
2016-05-05 00:49:44 status half-configured dpkg:i386 1.18.4
2016-05-05 00:49:44 status unpacked dpkg:i386 1.18.4
2016-05-05 00:49:44 status half-installed dpkg:i386 1.18.4
2016-05-05 00:49:45 status triggers-pending man-db:i386 2.7.5-1
2016-05-05 00:49:50 status half-installed dpkg:i386 1.18.4
2016-05-05 00:49:50 status unpacked dpkg:i386 1.18.6
2016-05-05 00:49:50 status unpacked dpkg:i386 1.18.6
*apt-get aborts, system hosed*


>From /proc/cpuinfo:

model name  : Pentium MMX
flags   : fpu vme de pse tsc msr mce cx8 mmx


Filtered logs from dmesg as I try and manage to fix the problem by
replacing incompatible /usr/bin/dpkg, /usr/bin/dpkg-split, then
/usr/bin/dpkg-debinaries by healthy ones, obvious ASLR in action:

[3584780.023939] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
15f94f03 in /usr/bin/dpkg[dpkg:22878] uid/euid:0/0 gid/egid:0/0, parent 
/var/lib/dpkg/info/dpkg.postrm[dpkg.postrm:22877] uid/euid:0/0 gid/egid:0/0
[3584780.987573] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
12670f03 in /usr/bin/dpkg[dpkg:22880] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22840] uid/euid:0/0 gid/egid:0/0
[3584781.292243] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
15026f03 in /usr/bin/dpkg[dpkg:22881] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22840] uid/euid:0/0 gid/egid:0/0
[3584791.931143] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
177b0f03 in /usr/bin/dpkg[dpkg:22883] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22840] uid/euid:0/0 gid/egid:0/0
[3584858.241959] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
1113cf03 in /usr/bin/dpkg[dpkg:22887] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22886] uid/euid:0/0 gid/egid:0/0
[3584858.283520] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
16215f03 in /usr/bin/dpkg[dpkg:22888] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22886] uid/euid:0/0 gid/egid:0/0
[3584877.922106] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
1625ef03 in /usr/bin/dpkg[dpkg:22892] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22886] uid/euid:0/0 gid/egid:0/0
[3584877.956635] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
15f83f03 in /usr/bin/dpkg[dpkg:22893] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22886] uid/euid:0/0 gid/egid:0/0
[3584878.063734] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
13a89f03 in /usr/bin/dpkg[dpkg:22894] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22886] uid/euid:0/0 gid/egid:0/0
[3584901.392576] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
10798f03 in /usr/bin/dpkg[dpkg:22897] uid/euid:0/0 gid/egid:0/0, parent 
/bin/zsh5[zsh:22720] uid/euid:0/0 gid/egid:0/0
[3585028.250121] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
15d59f03 in /usr/bin/dpkg[dpkg:22901] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22900] uid/euid:0/0 gid/egid:0/0
[3585029.730413] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
15671f03 in /usr/bin/dpkg[dpkg:22910] uid/euid:117/117 gid/egid:65534/65534, 
parent /usr/bin/apt-config[apt-config:22909] uid/euid:117/117 
gid/egid:65534/65534
[3585029.860104] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
17c30f03 in /usr/bin/dpkg[dpkg:22912] uid/euid:117/117 gid/egid:65534/65534, 
parent /usr/bin/apt-config[apt-config:22911] uid/euid:117/117 
gid/egid:65534/65534
[3585143.137563] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
17d6bf03 in /usr/bin/dpkg[dpkg:23011] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22900] uid/euid:0/0 gid/egid:0/0
[3585208.920845] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
12e96f03 in /usr/bin/dpkg[dpkg:23012] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:22900] uid/euid:0/0 gid/egid:0/0
[3585220.543423] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
17903f03 in /usr/bin/dpkg[dpkg:23014] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:23013] uid/euid:0/0 gid/egid:0/0
[3585220.577152] grsec: From XXX.XXX.XXX.XXX: Illegal instruction occurred at 
15776f03 in /usr/bin/dpkg[dpkg:23015] uid/euid:0/0 gid/egid:0/0, parent 
/usr/bin/apt-get[apt-get:23013] uid/euid:0/0 

Bug#823464: golang-gocapability-dev: Please update to latest upstream snapshot

[Potter, Tim (HPE Linux Support)]

Package: golang-gocapability-dev
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest snapshot of the golang-gocapability-dev package,
0.0~git20150716.0.2c00dae.  I've already packaged this in the repo on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#823323: busybox: Side effect after disabling CONFIG_FEATURE_PREFER_APPLETS

[Ben Hutchings]

Control: reassign -1 src:klibc 2.0.4-8

On Wed, 2016-05-04 at 08:58 +0800, Steven Shiau wrote:
> On 5/4/2016 AM 04:26, Ben Hutchings wrote:
> > 
> > 
> > On 3 May 2016 15:27:07 CEST, Steven Shiau  wrote:
> > > 
> > > Package: busybox
> > > Version: 1:1.22.0-19
> > > Severity: important
> > > 
> > > Dear Maintainer,
> > > 
> > > To address the issue about kmod's modprobe in busybox (#821307), the
> > > CONFIG_FEATURE_PREFER_APPLETS is disabled in busybox 1:1.22.0-19.
> > > However, this causes some issues for live-boot. There are some commands
> > > in
> > > the shell script use the options that the commands from kmod do not
> > > support.
> > I guess you mean klibc-utils not kmod?
> Oh, YES. My bad. Thanks for correcting that.
> > 
> > 
> > > 
> > > E.g. now when "ls" is used, the one from kmod is used. However, it only
> > > supports option "-h":
> > > $ bin/ls -h
> > > Usage: ls [-h] [FILE ...]
> > [...]
> > 
> > /bin/ls should be a symlink to busybox. Why isn't it?
> No idea here. Is it due to the config of initramfs-tools? There are some 
> more files in initrd.img in the Debian live are from klibc-utils:
> # file * | grep klibc | awk -F":" '{print $1}'
> cat
> chroot
> cpio
> dd
[...]

I bet this is due to removing the busybox hook from initramfs-tools
itself.

The ordering of initramfs-tools hooks is firstly ordered by
dependencies, but secondly by name (not documented, but implicit in the
implementation).

We used to run hooks in this order:

1. busybox (initramfs-tools)
2. klibc (initramfs-tools)

busybox version 1:1.21.0-2exp changed the order to:

1. busybox (initramfs-tools)
2. klibc (initramfs-tools)
3. zz-busbyox (busybox)

initramfs-toools version 0.123 changed the order to:

1. klibc (klibc-utils)
2. zz-busybox (busybox)

Each of the hooks generally avoids overwriting anything in /bin, so
where both busybox and klibc-utils provide the same command we used to
favour busybox and now we favour klibc-utils.  This didn't make much
difference in practice until I made this config change in busybox.

Since initramfs-tools only allows hook A to declare a dependency on
(must run after) hook B, not to declare that it must run before hook B,
this has to be solved in klibc.

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of incompetence.

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

Bug#823463: golang-context: Please update to latest upstream snapshot

[Potter, Tim (HPE Linux Support)]

Package: golang-context
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest release of the golang-context package,
0.0~git20160226.0.1ea2538.  I've already packaged this in the repo on alioth.

I've transitioned the binary package name in this update also - I've double 
checked but
it would be great if someone double-checked my work here.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#823462: flint: FTBFS in testing with LaTeX error (i.e. please make an upload for unstable)

[Santiago Vila]

Package: src:flint
Version: 2.5.2-3
Severity: serious

Dear maintainer: This package FTBFS in stretch:

---
! Argument of \zap@to@space has an extra }.

\par
l.4164 \left
|\frac{a_1}{a_n}\right|^{\frac{1}{n-1}},
?
! Emergency stop.

\par
l.4164 \left
|\frac{a_1}{a_n}\right|^{\frac{1}{n-1}},
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on flint-manual.log.
---

Please make an upload for unstable to fix the bug in unstable
(as I see that it's already fixed in experimental).

This is one of the packages I check for "dpkg-buildpackage -A",
and I would like to help with "unreproducible" Bug #818990, but
this is currently impossible for me because I can't get past the
LaTeX error (I only build on testing and sometimes on unstable).

Thanks.

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

[Vincent Lefevre]

Control: tags -1 fixed-upstream

according to the upstream bug(s).

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

Bug#823448: autogen: Breaks if rebuilt using gcc-6 and glibc 2.23

[Bruce Korb]

That would be my first guess -- there is a problem in the dependencies.
So, where is the ditritus?  Is it a single thread build or multi thread?
Can you dump out the commands that were executed?  etc.
There is little I can do if I do not see any of this on my system
and I cannot fully understand exactly what is going on on yours.
Sorry. :( - Bruce

On 05/04/16 12:55, Daniel Schepler wrote:

Source: autogen
Version: 1:5.18.7-3
Severity: important

I'm running a test rebuild of the Debian archive against gcc-defaults
and glibc from experimental, using a bootstrapping process that "eats
its own dog food".  In gnutls28, I got this error:

...
make[6]: Entering directory '/build/gnutls28-3.4.11/src'
autogen srptool-args.def
fserr 2: cannot map data file options:  No such file or directory
Makefile:2232: recipe for target 'srptool-args.c' failed
make[6]: [srptool-args.c] Error 2 (ignored)
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H
[]
gcc: error: srptool-args.c: No such file or directory
gcc: fatal error: no input files
compilation terminated.

[...]

(It's possible that the actual problem is in one of the dependencies
such as guile-2.0.)

Bug#823461: mirrors: [debian.proxad.net] Corrupt Packages file

[Vincent Lefevre]

Package: mirrors
Severity: normal

# apt-get update
[...]
Fetched 2701 kB in 8s (326 kB/s)   
Encountered a section with no Package: header
Problem with MergeList 
/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_unstable_main_binary-amd64_Packages
The package lists or status file could not be parsed or opened.
Can't call method "policy" on an undefined value at /usr/bin/apt-show-versions 
line 56.
Reading package lists... Error!
E: Problem executing scripts APT::Update::Post-Invoke-Success 'test -x 
/usr/bin/apt-show-versions || exit 0 ; apt-show-versions -i'
E: Sub-process returned an error code
E: Encountered a section with no Package: header
E: Problem with MergeList 
/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_unstable_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

The end of
/var/lib/apt/lists/ftp.fr.debian.org_debian_dists_unstable_main_binary-amd64_Packages
contains:

[...]
Package: python3-zzzeeksphinx
Source: zzzeeksphinx
Version: 1.0.17-1
Installed-Size: 103
Maintainer: Debian Python Modules Team 

Architecture: all
Depends: python3-mako, python3-pyscss, python3:any (>= 3.3.2-2~)
Recommends: python3-pygments
Enhances: python3-sphinx
Description: Zzzeek's Sphinx layout and utilities
Homepage: https://bitbucket.org/zzzeek/zzzeeksphinx
Description-md5: 4f212bc11d1a3c5c6d0fa4b9761ac8d1
Section: python
Priority: optional
Filename: pool/main/z/zzzeeksphinx/python3-zzzeeksphinx_1.0.17-1_all.deb
Size: 22628
MD5sum: 4b0ed3c253c79e31ad72d61c2483b154
SHA256: 6dd74641729e991c6dcc8a697fb26a91c8e42249055018091c2333c350da

1.0.17-1
Installed-Size: 103
Maintainer: Debian Python Modules Team 

Architecture: all
Depends: python3-mako, python3-pyscss, python3:any (>= 3.3.2-2~)
Recommends: python3-pygments
Enhances: python3-sphinx
Description: Zzzeek's Sphinx layout and utilities
Homepage: https://bitbucket.org/zzzeek/zzzeeksphinx
Description-md5: 4f212bc11d1a3c5c6d0fa4b9761ac8d1
Section: python
Priority: optional
Filename: pool/main/z/zzzeeksphinx/python3-zzzeeksphinx_1.0.17-1_all.deb
Size: 22628
MD5sum: 4b0ed3c253c79e31ad72d61c2483b154
SHA256: 6dd74641729e991c6dcc8a697fb26a91c8e42249055018091c2333c350da

The 1.0.17-1 alone is clearly wrong.

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

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

Bug#821442: linux-image-4.6.0-rc3-amd64 fails as well but in a different way

[Norbert Kiesel]

Further update: I just booted into linux-image-4.6.0-rc5-amd64 and that
also works correctly with docker.

On Wed, Apr 27, 2016 at 1:08 PM, Norbert Kiesel  wrote:

> I just installed linux-image-4.6.0-rc3-amd64 from experimental.  With this
> kernel, I can run `docker start`, and I get a bash root prompt using
> `docker exec -it  bash`.  However, the shell then hangs: I can
> edit the line, but even w/o entering anything and just hitting  the
> shell locks up.
>
> /var/log/messages shows:
>
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.528976] [ cut here
> ]
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529019] WARNING: CPU: 3 PID: 468
> at /build/linux-aGlcVo/linux-4.6~rc3/net/wireless/sme.c:850
> wl_notify_roaming_status+0xb6/0x130 [wl]
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529021] Modules linked in:
> veth(E) fuse(E) xt_CHECKSUM(E) iptable_mangle(E) ipt_REJECT(E)
> nf_reject_ipv4(E) xt_tcpudp(E) tun(E) ebtable_filter(E) ebtables(E)
> ip6table_filter(E) ip6_tables(E) xt_conntrack(E) ipt_MASQUERADE(E)
> nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E)
> nf_defrag_ipv4(E) nf_nat_ipv4(E) xt_addrtype(E) iptable_filter(E)
> ip_tables(E) x_tables(E) br_netfilter(E) nf_nat(E) nf_conntrack(E)
> overlay(E) bridge(E) stp(E) llc(E) binfmt_misc(E) intel_rapl(E)
> x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm_intel(E) kvm(E)
> irqbypass(E) crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E)
> wl(POE) jitterentropy_rng(E) hmac(E) drbg(E) ansi_cprng(E) iTCO_wdt(E)
> iTCO_vendor_support(E) amdkfd(E) dcdbas(E) aesni_intel(E) aes_x86_64(E)
> lrw(E) gf128mul(E) glue_helper(E) ablk_helper(E) cryptd(E) radeon(E)
> dell_smm_hwmon(E) joydev(E) sg(E) evdev(E) cfg80211(E)
> snd_hda_codec_realtek(E) ttm(E) serio_raw(E) snd_hda_codec_generic(E)
> pcspkr(E) i915(E) i2c_i801(E) snd_hda_codec_hdmi(E) wmi(E) snd_hda_intel(E)
> battery(E) 8250_fintek(E) snd_hda_codec(E) elan_i2c(E) snd_hda_core(E)
> snd_hwdep(E) drm_kms_helper(E) dell_smo8800(E) snd_pcm(E) drm(E)
> snd_timer(E) dell_rbtn(E) dw_dmac(E) i2c_designware_platform(E) snd(E)
> dw_dmac_core(E) i2c_designware_core(E) soundcore(E) i2c_algo_bit(E)
> video(E) lpc_ich(E) rfkill(E) mei_me(E) shpchp(E) tpm_tis(E) mfd_core(E)
> ie31200_edac(E) ac(E) mei(E) tpm(E) edac_core(E) button(E) processor(E)
> parport_pc(E) ppdev(E) lp(E) parport(E) autofs4(E) ext4(E) crc16(E) jbd2(E)
> mbcache(E) btrfs(E) crc32c_generic(E) xor(E) raid6_pq(E) md_mod(E)
> sd_mod(E) hid_generic(E) usbhid(E) crc32c_intel(E) ahci(E) libahci(E)
> libata(E) psmouse(E) scsi_mod(E) xhci_pci(E) ehci_pci(E) sdhci_pci(E)
> xhci_hcd(E) ehci_hcd(E) e1000e(E) ptp(E) usbcore(E) pps_core(E)
> usb_common(E) thermal(E) sdhci_acpi(E) sdhci(E) mmc_core(E) i2c_hid(E)
> hid(E) fjes(E)
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529090] CPU: 3 PID: 468 Comm:
> wl_event_handle Tainted: P   OE   4.6.0-rc3-amd64 #1 Debian
> 4.6~rc3-1~exp1
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529091] Hardware name: Dell Inc.
> Precision M4800/0WJNC2, BIOS A14 05/19/2015
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529093]  0286
> 8ce2ddb2 81310e95 
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529095]  
> 8107a4ee 880805d54700 8807d8a61614
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529096]  880805d54f1a
> 88080925a000 880805d54af8 81ab21a0
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529098] Call Trace:
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529104]  [] ?
> dump_stack+0x5c/0x77
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529107]  [] ?
> __warn+0xbe/0xe0
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529134]  [] ?
> wl_notify_roaming_status+0xb6/0x130 [wl]
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529158]  [] ?
> wl_event_handler+0x58/0x1a0 [wl]
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529182]  [] ?
> wl_notify_scan_status+0x310/0x310 [wl]
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529184]  [] ?
> kthread+0xcd/0xf0
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529187]  [] ?
> ret_from_fork+0x22/0x40
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529189]  [] ?
> kthread_create_on_node+0x190/0x190
> Apr 27 12:09:48 lt-nkiesel kernel: [  214.529190] ---[ end trace
> f6e95ef4cd43b7be ]---
>
>
> However, I see similar problems when running the 4.4 kernel, so this might
> not be related to the "shell hanging" problem.
>

Bug#806043: gumbo-parser: FTBFS in testing

[Santiago Vila]

retitle 806043 gumbo-parser: FTBFS in testing
severity 806043 serious
fixed 806043 0.10.1+dfsg-2.1
thanks

> python3.5 python3.4 setup.py install 
> --root=/<>/gumbo-parser-0.10.1+dfsg/debian/python3-gumbo 
> --install-layout=deb
> python3.5: can't open file 'python3.4': [Errno 2] No such file or directory

This was really a duplicate of Bug #802075 (FTBFS with multiple
python3 versions) and it really had anything to do with
"dpkg-buildpackage -A".

Closing.

Bug#817806: please upload fresh bugfix (4.4.4)

[Yaroslav Halchenko]

On Wed, 04 May 2016, Nicholas D Steeves wrote:

> Hi Yaroslav,
> Is this bug for linux-image or btrfs-tools?  

let's see...  (I wouldn't know myself by now)

$> lynx --dump http://bugs.debian.org/817806 | head 
  Debian Bug report logs - [1]#817806
   please upload fresh bugfix (4.4.4)

   [2]version graph

   Package: [3]btrfs-tools; Maintainer for [4]btrfs-tools is [5]Dimitri
   John Ledkov ; Source for [6]btrfs-tools is
   [7]src:btrfs-progs.

so I guess it was indeed against btrfs-tools

>  Kernels based on
> linux-4.4.6 and linux-4.5.1 are available, and I've updated
> btrfs-progs to v4.4.1.  I'm planning to upload v4.5.2 soon, for
> completeness, but it will be to experimental, because I've read a
> couple of reports of problems that were solved by downgrading to
> btrfs-progs v4.4.x.

oh -- yeah, I would prefer a stable version ;)  but I guess having it in
unstable could also speed up detection of existing issues ;)

cheers!
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#247134: /var/cache vs. /var/lib

[Raphaël]

The bug itself does not seem that hard to solve:
> sed '/^Filename/s;/var/cache/debconf/;/var/lib/debconf/;' /etc/debconf.conf # 
> using -i
(in the package-provided default debconf.conf file)

Then the upgrade needs to move said directory automatically.
(should not be that hard either for experienced maintainers)

Bug#806114: tacacs+: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

tags 806114 + patch
thanks

On Tue, 24 Nov 2015, Santiago Vila wrote:

> install -m 644 debian/tacacs+.default 
> /build/tacacs+-QzZNjg/tacacs+-4.0.4.27a/debian/tacacs+/etc/default/tacacs+
> install: cannot create regular file 
> '/build/tacacs+-QzZNjg/tacacs+-4.0.4.27a/debian/tacacs+/etc/default/tacacs+': 
> No such file or directory
> debian/rules:16: recipe for target 'override_dh_auto_install' failed
> make[1]: *** [override_dh_auto_install] Error 1

Explanation: This happens because we are creating arch-independent packages 
only,
so debian/tacacs+/[...] does not exist because tacacs+ is arch-dependent.

The trivial fix is to move most of the current "override_dh_auto_install"
target to "override_dh_auto_install-arch".

Patch attached.

Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -12,9 +12,10 @@ include /usr/share/dpkg/buildflags.mk
 %:
dh $@ --with autotools-dev,quilt
 
-override_dh_auto_install:
-   dh_installdirs
+override_dh_installinit:
dh_installinit --name=tacacs_plus
+
+override_dh_auto_install-arch:
dh_auto_install
install -m 644 debian/tacacs+.default 
$(CURDIR)/debian/tacacs+/etc/default/tacacs+
install -m 600 debian/tac_plus.conf $(CURDIR)/debian/tacacs+/etc/tacacs+

Bug#823460: lightdm: SIGPIPE ignored in session

[Ian Jackson]

Package: lightdm
Version: 1.18.1-1
Severity: serious


I have just discovered that my entire X session is running with
SIGPIPE ignored.  I think this is the fault of lightdm - see below.

All Unix programs are entitled to assume that they start with
reasonable signal dispositions, which (with a few exceptions) means
everything set to SIG_DFL.  I have marked this bug "serious" on the
grounds that I think this is a release-critical bug.


More details:

In an xterm:

zealot:~> perl -e 'print $SIG{PIPE},"\n"'
IGNORE
zealot:~>


By grepping /proc I have discovered this:


* Several processes spawned directly from init (including secnet, a
  program of which I am the maintainer, which does not mess with
  SIGPIPE) do not have SIGPIPE ignored:

root(ian)@zealot:~> for f in `pidof secnet`; do grep SigIgn /proc/$f/status; 
done
SigIgn: 0002
SigIgn: 0002
root(ian)@zealot:~>

So I don't think init (sysvinit, in my case) is responsible.


* lightdm has SIGPIPE ignored:

root(ian)@zealot:~> for f in `pidof lightdm`; do grep SigIgn /proc/$f/status; 
done
SigIgn: 1000
SigIgn: 1000
root(ian)@zealot:~>

lightdm is of course entitled to run with whatever SIGPIPE disposition
it likes, but this is suggestive.



* My .xsession script has SIGPIPE ignored:

root  4144  3371  0 11:24 ?00:00:00 lightdm --session-child 13 
22
ian   4154  4144  0 11:24 ?00:00:00   /bin/bash 
/home/ian/.xsession

root(ian)@zealot:~> grep SigIgn /proc/4154/status 
SigIgn: 1004
root(ian)@zealot:~>

My .xsession script is fairly complicated but does not mention PIPE,
and hasn't changed since Decmeber; on another machine running jessie
and gdm it has SIGPIPE set to DFL.

So this isn't something my .xsession script has done.

I have a .dmrc containing this:

[Desktop]
Language=en_GB.utf8
Layout=gb
Session=lightdm-xsession



The bad SIGPIPE disposition is inherited by the primary xterm which my
xsession runs, and its children including my main session script, my
window manager, all my xterms, etc.


Thanks for your attention.

Ian.



-8<- ~/.xession -8<-
#!/bin/bash

exec >>.configs/xsession-errors 2>&1
echo xsession running

. .configs/setenvir

rm .configs/mini-desktop-window-id

eval `.configs/configure`

set

if [ -x .configs/xmodmap-kb=$kb ]
then
.configs/xmodmap-kb=$kb | xmodmap -
else
xmodmap .configs/xmodmap-kb=$kb
fi

xrdb -merge .configs/Xresources
xrdb -merge .configs/Xresources-colours=$colours
xrdb -merge .configs/Xresources-font=$font
xrdb -merge .configs/Xresources-size=$size

xset b off

${lxtermpath}xterm -C $lxtermopts -T "login" -e .configs/xprofile
echo xterm done logging out again
rm .configs/xsession-errors
.configs/eliforp
-8<-


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

Kernel: Linux 4.5.0-1-amd64 (SMP w/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: sysvinit (via /sbin/init)

Versions of packages lightdm depends on:
ii  adduser3.114
ii  dbus   1.10.8-1
ii  debconf [debconf-2.0]  1.5.59
ii  libaudit1  1:2.4.5-1+b1
ii  libc6  2.22-7
ii  libgcrypt201.7.0-2
ii  libglib2.0-0   2.48.0-1
ii  libpam-systemd 229-5
ii  libpam0g   1.1.8-3.2
ii  libxcb11.11.1-1
ii  libxdmcp6  1:1.1.2-1.1
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.1-2

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+15

Versions of packages lightdm suggests:
pn  accountsservice  
ii  upower   0.99.4-2

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
xserver-command=X -retro
[XDMCPServer]
[VNCServer]


-- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm

Bug#823272: [Pkg-samba-maint] Bug#823272: libsmbclient: [Regression] Perl Filesys::SmbClient fails after move from 2:3.6.6-6+deb7u7 to 2:3.6.6-6+deb7u9

[Jelmer Vernooij]

CC'ing in the bug.

On Wed, May 04, 2016 at 07:33:38PM +, Spencer Godfrey wrote:
> 
> Thanks for noticing the similarities to bug 822937.
> 
> Here are some server side details:
> 
> - FAILS: EMC VNX which presents as Windows share and backends against Windows 
> AD for authentication
> - WORKS: Debian wheezy samba 2:3.6.6-6+deb7 server
> - WORKS: Debian squeeze samba 2:3.5.6~dfsg-3squeeze13 server
> 
> Both Debian samba servers backend against an OpenLDAP authentication server - 
> no Kerberos involved. I will collect information about the windows versions 
> and configuration on the VNX and forward it to you.
> 
> As for context and error messages, my perl script fails when I attempt to 
> create a file descriptor to the smb share file:
> 
>  $fd = $smb->open(">$smbfile", 0660) or die("CRITICAL - Couldn't open 
> $smbfile: $!");
> 
> Which prints the error message:
> 
> CRITICAL - Couldn't open smb://path/to/file/smbfile: Permission denied at 
> ./script line 96.
> 
> I will make a basic perl script to isolate the issue and will send it your 
> way.
> 
> Thanks!
> 
> 
> From: Jelmer Vernooij 
> Sent: Monday, May 2, 2016 6:03 PM
> To: Spencer Godfrey; 823...@bugs.debian.org
> Cc: cont...@bugs.debian.org
> Subject: Re: [Pkg-samba-maint] Bug#823272: libsmbclient: [Regression] Perl 
> Filesys::SmbClient fails after move from 2:3.6.6-6+deb7u7 to 2:3.6.6-6+deb7u9
> 
> tags 823272 +moreinfo
> tags 823272 +jessie
> thanks
> 
> On Mon, May 02, 2016 at 02:15:42PM -0500, Spencer S Godfrey wrote:
> > After moving to the current Wheezy Oldstable version of libsmbclient,
> > 2:3.6.6-6+deb7u9, the use of the Perl module Filesys::SmbClient fails
> > to read/write to samba shares citing permissions errors. Rolling back
> > to the previously installed version, 2:3.6.6-6+deb7u7, allows the perl
> > module's read/write interactions to succeed.
> >
> >
> > To verify:
> > I used two systems running the same version of the Perl module,
> > libfilesys-smbclient-perl, version 3.1-3+b3, and its dependencies.
> > On one, I downgraded to libsmbclient version 2:3.6.6-6+deb7u7, and
> > the other remained at 2:3.6.6-6+deb7u9 (Oldstable).
> >
> > The machine with 7u7 installed worked, while the machine with 7u9 did not.
> > The libsmbclient package is the only package which differed between
> > the machine's perl module dependencies.
> 
> This is almost certainly a dupe, e.g. of 822937.
> 
> What were you running on the server side? Can you reproduce this in sid?


signature.asc
Description: PGP signature

Bug#823459: ldlinux.c32 module only loads default label

[Jamie Heilman]

Package: syslinux-common
Version: 3:6.03+dfsg-12
Severity: grave

Given a fairly simple config of:

SERIAL 0 115200
DISPLAY boot.txt
PROMPT 1
TIMEOUT 250

DEFAULT local
LABEL local
 LOCALBOOT -1

LABEL memtest
 KERNEL mt86plus

it's now impossible to load anything other than the default label.
Hitting tab at the boot: prompt still displays all available labels,
but entering any other label at the prompt always results in execution
of the default.  Reverting syslinux-common to 3:6.03+dfsg-11 resolves
the problem.  Platform in use is amd64.

-- 
Jamie Heilman http://audible.transient.net/~jamie/

Bug#805961: toilet: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

[Santiago Vila]

tags 805961 + patch
thanks

This bug could be fixed by switching to dh, but in the meantime, here
is a trivial patch.

Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -51,34 +51,39 @@ install: build
 
 # Build architecture-independent files here.
 binary-indep: build install
-# We have nothing to do by default.
+   dh_installdocs -i -A README TODO NEWS
+   dh_installmenu -i
+   dh_installcron -i
+   dh_installinfo -i
+   dh_installmime -i
+   dh_installchangelogs -i ChangeLog
+   dh_link -i
+   dh_strip -i
+   dh_compress -i
+   dh_fixperms -i
+   dh_installdeb -i
+   dh_shlibdeps -i
+   dh_gencontrol -i
+   dh_md5sums -i
+   dh_builddeb -i
 
 # Build architecture-dependent files here.
 binary-arch: build install
-#  dh_testversion
-   dh_testdir
-   dh_testroot
-#  dh_installdebconf   
-   dh_installdocs -A README TODO NEWS
-#  dh_installexamples
-   dh_installmenu
-#  dh_installemacsen
-#  dh_installpam
-#  dh_installinit
-   dh_installcron
-#  dh_installmanpages
-   dh_installinfo
-   dh_installmime
-   dh_installchangelogs ChangeLog
-   dh_link
-   dh_strip
-   dh_compress
-   dh_fixperms
-   dh_installdeb
-   dh_shlibdeps
-   dh_gencontrol
-   dh_md5sums
-   dh_builddeb
+   dh_installdocs -a -A README TODO NEWS
+   dh_installmenu -a
+   dh_installcron -a
+   dh_installinfo -a
+   dh_installmime -a
+   dh_installchangelogs -a ChangeLog
+   dh_link -a
+   dh_strip -a
+   dh_compress -a
+   dh_fixperms -a
+   dh_installdeb -a
+   dh_shlibdeps -a
+   dh_gencontrol -a
+   dh_md5sums -a
+   dh_builddeb -a
 
 binary: binary-indep binary-arch
 .PHONY: build clean binary-indep binary-arch binary install configure

Bug#821195: survex: FTBFS on hurd-i396

[Colin Watson]

On Wed, May 04, 2016 at 11:37:05PM +0100, Olly Betts wrote:
> On Wed, May 04, 2016 at 05:53:20PM +0100, Colin Watson wrote:
> > A more complete fix would be to make sure that structures are always
> > zero-filled when they are allocated, but that probably requires work
> > throughout the codebase.
> 
> The new settings are always initialised from the existing settings:
> 
>pcsNew = osnew(settings);
>*pcsNew = *pcs; /* copy contents */
> 
> So the root cause is that begin_survey is never actually initialised in
> the first place.

Ah yes, I managed to read past that.

> I suspect the compiler is doing that for us on some architectures (some
> fields are explicitly initialised to NULL or 0 so it probably decides a
> memset() of the whole structure is more efficient), but not on hurd-i386
> for some reason, and that's why valgrind doesn't pick this up on x86-64.

I actually encountered this on amd64 and valgrind picked it up there.
There may be differences between toolchain versions; this was on Ubuntu
yakkety, our current development series.  I only guessed that it might
be the same as this Hurd issue; unfortunately the log isn't detailed
enough for me to be sure of that.

valgrind's data flow analysis is probably managing to notice that the
original pcs structure that is being copied doesn't have an initialised
begin_survey, and indeed the code in src/cavern.c:main that allocates
the first structure in the list only initialises some fields, so as you
say a memset there would be a good idea.  Still, something like my patch
is likely still a good idea to make the behaviour clearer in error
cases, especially as it results in shorter code. :-)

> I'll push a fix upstream and let it flow back in the next release, but
> if the hurd-i386 issue is a problem for you, feel free to NMU (the patch
> as-is looks good to me for that).

Tobias, perhaps you could see if this patch fixes the Hurd issue?  If
not, apologies for dogpiling onto this bug.

Thanks,

-- 
Colin Watson   [cjwat...@ubuntu.com]

Bug#821195: survex: FTBFS on hurd-i396

[Olly Betts]

Control: tags -1 + patch pending

On Wed, May 04, 2016 at 05:53:20PM +0100, Colin Watson wrote:
> On Sat, Apr 16, 2016 at 05:16:54PM +0200, Tobias Frost wrote:
> > survex  FTBFS on hurd-i386 but built before.
> > Please take a look.
> > 
> > As this is preventing decrufting of wxwidgets3.0, I've filed an RM for this 
> > arch.
> > See #821191
> 
> The attached patch may help.  Please consider it.

Ah, so that's what's going on here.  Thanks for tracking this down.

> A more complete fix would be to make sure that structures are always
> zero-filled when they are allocated, but that probably requires work
> throughout the codebase.

The new settings are always initialised from the existing settings:

   pcsNew = osnew(settings);
   *pcsNew = *pcs; /* copy contents */

So the root cause is that begin_survey is never actually initialised in
the first place.  Usually that doesn't matter (as it won't be checked),
but in this error case that gets copied into the new settings, and then
used later.  So this shouldn't affect normal use.

Zero-initialising the first settings would help avoid any issues like
this.

I suspect the compiler is doing that for us on some architectures (some
fields are explicitly initialised to NULL or 0 so it probably decides a
memset() of the whole structure is more efficient), but not on hurd-i386
for some reason, and that's why valgrind doesn't pick this up on x86-64.

I'll push a fix upstream and let it flow back in the next release, but
if the hurd-i386 issue is a problem for you, feel free to NMU (the patch
as-is looks good to me for that).

Cheers,
Olly

Bug#823458: Allow a custom ntp config file

[Christian Ehrhardt]

Package: ntp
Version: 1:4.2.8p7+dfsg-3

Hi,
this is another bug I found while cleaning up and again I'd prefer to just
fix it in Debian instead working around it in Ubuntu (alone).
Also it is surely worth another opinion/review on it.

This is about providing a way to allow a user to specify a custom ntp
config file.
But only so if dhcp did not provide one to allow dhcp to overwrite.

The patch is a slightly extended version of what was reported to us on the
Ubuntu bug (plus actual config and a bit of a helper text).

BTW - I currently submit a lot of smaller fixes and I guess after
Discussion they will all fit in one upload. That is why I send individual
patches instead of a debdiff. But if you would prefer debdiffs let me know.
diff --git a/ntp-4.2.8p7+dfsg/debian/ntp.default b/ntp-4.2.8p7+dfsg/debian/ntp.default
index af78139..02562f7 100644
--- a/ntp-4.2.8p7+dfsg/debian/ntp.default
+++ b/ntp-4.2.8p7+dfsg/debian/ntp.default
@@ -1 +1,6 @@
 NTPD_OPTS='-g'
+
+# Can be set to a custom ntp config file that shall be provided to ntp.
+# If ntp options are provided via dhcp this custom config is ignored
+# in favor of the generated /var/lib/ntp/ntp.conf.dhcp config.
+NTPD_CONF=''
diff --git a/ntp-4.2.8p7+dfsg/debian/ntp.init b/ntp-4.2.8p7+dfsg/debian/ntp.init
index 7eb932e..d29a7ff 100644
--- a/ntp-4.2.8p7+dfsg/debian/ntp.init
+++ b/ntp-4.2.8p7+dfsg/debian/ntp.init
@@ -24,6 +24,8 @@ fi
 
 if [ -e /var/lib/ntp/ntp.conf.dhcp ]; then
 	NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp"
+elif [ -n "$NTPD_CONF" ]; then
+	NTPD_OPTS="$NTPD_OPTS -c $NTPD_CONF"
 fi
 
 

Bug#823457: RFS: webfs/1.21+ds1-12

[Mats Erik Andersson]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor of my package "webfs":

  Package name: webfs
  Version : 1.21+ds1-12
  Upstream Author : Gerd Knorr 
  URL : http://linux.bytesex.org/misc/webfs.html
  License : GPL-2+
  Section : httpd

It builds a single binary package:

  webfs - lightweight HTTP server for static content

Information about this package is available at

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

A package download is standard:

  dget -x 
https://mentors.debian.net/debian/pool/main/w/webfs/webfs_1.21+ds1-12.dsc

Changes since last upload are:

  * Step Standards-Version to 3.9.8, no changes.
  * debian/control: Remove obsolete build dependency on dpkg-dev.
Reorder dependency lists.
  * debian/copyright: Update the time span of my contribution.
  * debian/rules: Do not set compiler flags.  Activate all available
hardening, even though not all consumed libraries do this.
  * Update debconf translation:
+ Dutch (Frans Spiesschaert).  Closes: #821449


Regards,
 Mats Erik Andersson

Bug#820101: jessie-pu: package nam/1.15-3

[Adam D. Barratt]

Control: tags -1 -pending

On Wed, 2016-05-04 at 23:10 +0100, Adam D. Barratt wrote:
> Control: tags -1 + pending
> 
> On Wed, 2016-05-04 at 14:51 -0300, Herbert Fortes wrote:
> > Hi,
> > 
> > > > All in all, I'm still not entirely sure that the changes are completely
> > > > correct, but on the assumption that there have been no issues since they
> > > > were applied in unstable, please go ahead and we'll keep our fingers
> > > > crossed. :-|
> > > > 
> > > 
> > > Thanks for the aditional information.
> > > 
> > > I asked for a sponsor to do the upload.
> > > 
> > > Thanks again Adam.
> > > 
> > > 
> > 
> > the package was uploaded today. 
> 
> Flagged for acceptance.

Actually, no. Apologies for not noticing it before, but the version
number is broken - it should either be 1.15-3+deb8u1 or 1.15-3.1~deb8u1.
1.15-3.1+deb8u1 fails, as it is greater than the version of the package
in unstable.

Regards,

Adam

Bug#820101: jessie-pu: package nam/1.15-3

[Adam D. Barratt]

Control: tags -1 + pending

On Wed, 2016-05-04 at 14:51 -0300, Herbert Fortes wrote:
> Hi,
> 
> > > All in all, I'm still not entirely sure that the changes are completely
> > > correct, but on the assumption that there have been no issues since they
> > > were applied in unstable, please go ahead and we'll keep our fingers
> > > crossed. :-|
> > > 
> > 
> > Thanks for the aditional information.
> > 
> > I asked for a sponsor to do the upload.
> > 
> > Thanks again Adam.
> > 
> > 
> 
> the package was uploaded today. 

Flagged for acceptance.

Regards,

Adam

Bug#823430: jessie-pu: package icedove/38.7.0-1~deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Wed, 2016-05-04 at 19:39 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Wed, 2016-05-04 at 19:08 +0200, Julien Cristau wrote:
> > The icedove package currently on security.d.o and proposed-updates fails
> > to build on armhf because some files get built with -mfloat-abi=softfp.
> > This should hopefully fix that.
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

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

[David Hill]

Hello sir,

  If I send you the templates in a secure location would it help you ?

Thank you very much,

David Hill

-Original Message- 
From: Andreas Metzler

Sent: Wednesday, May 4, 2016 12:56 PM
To: David Hill ; 823...@bugs.debian.org
Subject: Re: Bug#823418: exim4: Since the last update, it seems like some 
messages are rejected after DATA


On 2016-05-04 David Hill  wrote:

Package: exim4
Version: 4.87-2
Severity: important



Dear Maintainer,


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



   * What led up to the situation?
  I updated
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I updated
   * What was the outcome of this action?
 Some messages are rejected after DATA
   * What outcome did you expect instead?
 It should not be rejected after DATA .   I'm not quite sure but it 
looks like the DKIM or TLS
 default behavior changed from not checking to checking unless 
dc_minimaldns is set?



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


Hello,

this a little bit too short on information. I assume you are running a
configuration with at least some local customizations. Can you reproduce
this, especially in -bh testing mode?

cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Bug#823404: RM: php5/5.6.20+dfsg-1

[Julien Cristau]

On Wed, May  4, 2016 at 23:59:34 +0200, Ondřej Surý wrote:

> And is there a way that doesn't involve filling a serious bugs on all of
> those reverse deps?  I have no problem bumping the severity on those I
> have already filled, but it seems to be excessive.
> 
No, bugs against reverse deps will need to happen.  Either that or have
php7.0-* provide php5-*, which I guess you don't want.

Cheers,
Julien

Bug#823404: RM: php5/5.6.20+dfsg-1

[Ondřej Surý]

And is there a way that doesn't involve filling a serious bugs on all of
those reverse deps?  I have no problem bumping the severity on those I
have already filled, but it seems to be excessive.

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

On Wed, May 4, 2016, at 19:37, Julien Cristau wrote:
> Control: tag -1 moreinfo
> 
> On Wed, May  4, 2016 at 13:59:09 +0200, Ondřej Surý wrote:
> 
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: rm
> > 
> > Hi,
> > 
> > as the PHP 7.0 transition goes forward I would like to remove php5
> > (and r-deps) from testing and keep it only in unstable.  Filling the
> > bug as php5 is on the "always-keep" list for auto-removals, so it
> > needs a manual kick from testing.
> > 
> There's way too many reverse deps left AFAICT.
> 
> Cheers,
> Julien
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

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

[David Hill]

Hello sir,

   I also forwarded myself an email I successfully received on hotmail 
to myself and even without DKIM it failed...  Perhaps there's something 
else happening here but I only have a meaningless error message :


2016-05-04 12:54:34 1ay04I-0005yV-EV H=localhost (binarystorm.net) 
[127.0.0.1] F= rejected after DATA


Thank you very much,

David Hill


On 05/04/2016 05:54 PM, David Hill wrote:

Hello sir,

  If I send you the templates in a secure location would it help you ?

Thank you very much,

David Hill

-Original Message- From: Andreas Metzler
Sent: Wednesday, May 4, 2016 12:56 PM
To: David Hill ; 823...@bugs.debian.org
Subject: Re: Bug#823418: exim4: Since the last update, it seems like 
some messages are rejected after DATA


On 2016-05-04 David Hill  wrote:

Package: exim4
Version: 4.87-2
Severity: important



Dear Maintainer,


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



   * What led up to the situation?
  I updated
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I updated
   * What was the outcome of this action?
 Some messages are rejected after DATA
   * What outcome did you expect instead?
 It should not be rejected after DATA .   I'm not quite sure but 
it looks like the DKIM or TLS
 default behavior changed from not checking to checking unless 
dc_minimaldns is set?



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


Hello,

this a little bit too short on information. I assume you are running a
configuration with at least some local customizations. Can you reproduce
this, especially in -bh testing mode?

cu Andreas



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Bug#617965: [ntpdate] ntpdate-debian ignore dhcp option

[Christian Ehrhardt]

Hi,
I just came over this long dormant bug in Ubuntu and I saw it was just as
that in Debian.
IMHO the patch still makes sense, it also still applies.
And I see no reason to not just fix this in Debian first.

It reads a bit weird as /var/lib/ntp/ntp.conf.dhcp could be checked twice
if NTPDATE_USE_NTP_CONF is set. But that could be solved by moving the new
section down after the check of local files.
This also allows for a default.dhcp that does not specify NTPSERVERS to
fall back to the local config.

A patch with these small modifications would look like this:
diff --git a/ntp-4.2.8p7+dfsg/debian/ntpdate-debian b/ntp-4.2.8p7+dfsg/debian/ntpdate-debian
index 4748b3a..4f5b17b 100644
--- a/ntp-4.2.8p7+dfsg/debian/ntpdate-debian
+++ b/ntp-4.2.8p7+dfsg/debian/ntpdate-debian
@@ -7,7 +7,7 @@ if [ -r /etc/default/ntpdate ]; then
 fi
 
 if [ "$NTPDATE_USE_NTP_CONF" = yes ]; then
-	for f in /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf /etc/openntpd/ntpd.conf; do
+	for f in /etc/ntp.conf /etc/openntpd/ntpd.conf; do
 		if [ -r "$f" ]; then
 			file=$f
 			break
@@ -16,7 +16,9 @@ if [ "$NTPDATE_USE_NTP_CONF" = yes ]; then
 	if [ -n "$file" ]; then
 		NTPSERVERS=$(sed -rne 's/^(servers?|peer)[[:space:]]+(-[46][[:space:]]+)?([-_.:[:alnum:]]+).*$/\3/p' "$file" | grep -v '^127\.127\.') || [ $? -le 1 ]
 	fi
-elif [ -r /var/lib/ntpdate/default.dhcp ]; then
+fi
+
+if [ -r /var/lib/ntpdate/default.dhcp ]; then
 	. /var/lib/ntpdate/default.dhcp
 fi
 

Bug#823146: linux-image-4.5.0-0.bpo.1-amd64: Kernel 4.5 fails to boot on AMD A6 APU

[Ben Hutchings]

On Wed, 2016-05-04 at 08:42 +0200, CJP wrote:
> > 
> > Of course.  It looks like we can do that by reverting the change that
> > caused this regression.  Please test whether the attached patch fixes
> > the problem, following the instructions at:
> > 
> > https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
> > 
> Yes, it fixes the problem, even without my modprobe.blacklist argument.
> 
> Some notes:
> 
> test-patches asked me for a flavour; I entered amd64.
> 
> When installing the linux-image package, I got this error:
> update-initramfs: Generating /boot/initrd.img-4.5.0-0.bpo.1-amd64
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for
> module r8169
> I ignored it, since I probably won't need WiFi during early start-up.

These are actually for Ethernet controllers not wifi.

> When fully booted with this kernel, I tested my WiFi and it still works.
> 
> lsmod shows now that the sp5100_tco module is loaded.
> 
> dmesg contains the following line:
> [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.5.0-0.bpo.1-amd64
> root=UUID=cab2c5d5-4664-4105-bcbd-fcb860cc035d ro quiet
> (so it is version 4.5, without the blacklist argument)
> 
> dmesg does not show the ACPI error lines that were generated by the
> faulty 4.5.
> 
> dmesg | grep sp5100_tco returns the following:
> [   31.700531] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
> [   31.700640] sp5100_tco: PCI Revision ID: 0x13
> [   31.700709] sp5100_tco: failed to find MMIO address, giving up.
> 
> I hope this is what you expected. To me, it looks like the problem is
> fixed.

That looks right - the driver is now failing in a harmless way.

Thanks for testing.

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of incompetence.

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

Bug#823397: vagrant-libvirt: backport to jessie

[Antonio Terceiro]

On Wed, May 04, 2016 at 09:43:14AM +, anonym wrote:
> Package: vagrant-libvirt
> Severity: wishlist
> 
> Dear Maintainer,
> 
> In Tails [0] we are in the process of migrating our Vagrant-based build
> system from the VirtualBox provider to the Libvirt one thanks to the
> newly uploaded vagrant-livirt package. Since we like Tails to remain
> buildable on Jessie, the vagrant-libvirt package would have to be
> backported to Jessie. In addition, due to its dependencies, the
> following packages would have to be backported to Jessie as well:
> 
> * vagrant
> * ruby-excon
> * ruby-fog-core
> * ruby-fog-libvirt
> * ruby-fog-xml
> 
> Luckily I expect all of these backports to be trivial rebuilds -- at the
> moment installing these packages from Stretch into Jessie works fine.
> 
> In addition to the above, bug #823395 must also be fixed since
> ruby-fog-libvirt requires a ruby-libvirt *with* rubygems integration. An
> alternative would be to also backport ruby-libvirt, since Stretch's
> version already is fixed (it is not installable in Jessie, though, so
> the backporting could be more complicated, YMMV).

I do not have plans to work on this.

Please go ahead, and feel free to ask on debian-ruby@l.d.o if you have
issues with the backports.  ruby-libvirt probably just needs to be built
on jessie (Depends: libvirt0 (>= 1.2.11~rc1) is not satisfiable in
jessie)


signature.asc
Description: PGP signature

Bug#823455: libpdl-io-matlab-perl: FTBFS in sid: 1.5.0 is not a valid version

[Samuel Thibault]

Control: reassign -1 dpkg
Control: forcemerge -1 823431

Niko Tyni, on Thu 05 May 2016 00:30:56 +0300, wrote:
> On Wed, May 04, 2016 at 11:23:36PM +0200, Samuel Thibault wrote:
> > Package: libpdl-io-matlab-perl
> > Version: 0.005-1
> > Severity: serious
> > Justification: FTBFS
> 
> > libpdl-io-matlab-perl currently FTBFS in sid:
> 
> > dpkg-checkbuilddeps: error: 1.5.0  is not a valid version
> 
> > I guess the space after 1.5.0 in the Build-Depends field of
> > debian/control is the culprit.
> 
> That's a dpkg regression, see #823431.

Aow, OK, thanks!

Samuel

Bug#823456: dnspython: python3 branch dropped, python2/3 compatible codebase

[Arthur Gautier]

Source: dnspython
Version: 1.12
Severity: normal

Dear Maintainers,

Just a gentle notification to let you know that
https://github.com/rthalley/dnspython/pull/148 has been merged upstream
and you could most probably drop source package dnspython3 to make a
python2/python3 build from the same source.

Bob is currently preparing 1.13 release for that, see
https://github.com/rthalley/dnspython/commit/9d9c9f520d4d15a8c2759dbeabad15e4dec9043e

Thanks!

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

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

Bug#823455: libpdl-io-matlab-perl: FTBFS in sid: 1.5.0 is not a valid version

[Niko Tyni]

On Wed, May 04, 2016 at 11:23:36PM +0200, Samuel Thibault wrote:
> Package: libpdl-io-matlab-perl
> Version: 0.005-1
> Severity: serious
> Justification: FTBFS

> libpdl-io-matlab-perl currently FTBFS in sid:

> dpkg-checkbuilddeps: error: 1.5.0  is not a valid version

> I guess the space after 1.5.0 in the Build-Depends field of
> debian/control is the culprit.

That's a dpkg regression, see #823431.
-- 
Niko Tyni   nt...@debian.org

Bug#823455: libpdl-io-matlab-perl: FTBFS in sid: 1.5.0 is not a valid version

[Samuel Thibault]

Package: libpdl-io-matlab-perl
Version: 0.005-1
Severity: serious
Justification: FTBFS

Hello,

libpdl-io-matlab-perl currently FTBFS in sid:

dpkg-buildpackage: info: source package libpdl-io-matlab-perl
dpkg-buildpackage: info: source version 0.005-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Dima Kogan 
 dpkg-source -i -I --before-build libpdl-io-matlab-perl-0.005
dpkg-buildpackage: info: host architecture amd64
dpkg-checkbuilddeps: error: 1.5.0  is not a valid version
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)

I guess the space after 1.5.0 in the Build-Depends field of
debian/control is the culprit.

Samuel

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

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

-- 
Samuel
 Cliquez sur le lien qui suit dans ce mail...vous n'avez plus qu'a vous
 inscrire pour gagner de l'argent en restant connecteet puis faites
 passer le message et vous gagnerez encore plus d'argent ...
 -+- AC in NPC : Neuneu a rencontré le Pere Noël -+-

Bug#804138: percona-xtradb-cluster-galera-2.x: FTBFS: ssl support required but asio/ssl.hpp not found or not usable

[Sebastian Andrzej Siewior]

On 2015-11-05 10:33:46 [+], Chris Lamb wrote:
> Dear Maintainer,
> 
> percona-xtradb-cluster-galera-2.x fails to build from source in
> unstable/amd64:

the patch attached would let it build again. Do we want this? From what
I read at the github page [0] is that the current series is the 3.x ones
while this seems to be an older 2.x.
So do we want this package fixed or rather a removal and 3.x packaged by
someone who needs / uses it?

[0] https://github.com/codership/galera/tree/3.x

Sebastian
diff -Nru percona-xtradb-cluster-galera-2.x-2.11.2675/debian/changelog percona-xtradb-cluster-galera-2.x-2.11.2675/debian/changelog
--- percona-xtradb-cluster-galera-2.x-2.11.2675/debian/changelog	2015-08-30 23:49:37.0 +0200
+++ percona-xtradb-cluster-galera-2.x-2.11.2675/debian/changelog	2016-05-04 23:09:16.0 +0200
@@ -1,3 +1,12 @@
+percona-xtradb-cluster-galera-2.x (1:2.11.2675-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Depend on libasio-dev to avoid build failure on internal asio copy
+(Closes: #804138).
+  * Replace _BSD_SOURCE with _DEFAULT_SOURCE to avoid a warning with -Werror
+
+ -- Sebastian Andrzej Siewior   Wed, 04 May 2016 23:02:27 +0200
+
 percona-xtradb-cluster-galera-2.x (1:2.11.2675-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru percona-xtradb-cluster-galera-2.x-2.11.2675/debian/control percona-xtradb-cluster-galera-2.x-2.11.2675/debian/control
--- percona-xtradb-cluster-galera-2.x-2.11.2675/debian/control	2015-08-30 23:37:25.0 +0200
+++ percona-xtradb-cluster-galera-2.x-2.11.2675/debian/control	2016-05-04 23:09:16.0 +0200
@@ -9,6 +9,7 @@
  libboost-dev (>= 1.41),
  libboost-program-options-dev (>= 1.41),
  libssl-dev,
+ libasio-dev,
  scons
 Standards-Version: 3.9.6
 Homepage: http://www.percona.com/software/percona-xtradb-cluster/
diff -Nru percona-xtradb-cluster-galera-2.x-2.11.2675/debian/patches/series percona-xtradb-cluster-galera-2.x-2.11.2675/debian/patches/series
--- percona-xtradb-cluster-galera-2.x-2.11.2675/debian/patches/series	2015-08-30 23:42:40.0 +0200
+++ percona-xtradb-cluster-galera-2.x-2.11.2675/debian/patches/series	2016-05-04 23:09:00.0 +0200
@@ -1,3 +1,4 @@
 detect-atomic.patch
 fix-atomic-and-align.patch
 gcc5.patch
+sslv3_fixup.patch
diff -Nru percona-xtradb-cluster-galera-2.x-2.11.2675/debian/patches/sslv3_fixup.patch percona-xtradb-cluster-galera-2.x-2.11.2675/debian/patches/sslv3_fixup.patch
--- percona-xtradb-cluster-galera-2.x-2.11.2675/debian/patches/sslv3_fixup.patch	1970-01-01 01:00:00.0 +0100
+++ percona-xtradb-cluster-galera-2.x-2.11.2675/debian/patches/sslv3_fixup.patch	2016-05-04 23:11:30.0 +0200
@@ -0,0 +1,31 @@
+From: Sebastian Andrzej Siewior 
+Subject: Fix build without SSLv3
+
+- use external libasio-dev isntead of the internal copy which seems to work
+- avoid using _BSD_SOURCE which triggers a warning (and fails to compile with
+  -Werror)
+Index: percona-xtradb-cluster-galera-2.x-2.11.2675/SConstruct
+===
+--- percona-xtradb-cluster-galera-2.x-2.11.2675.orig/SConstruct
 percona-xtradb-cluster-galera-2.x-2.11.2675/SConstruct
+@@ -186,7 +186,6 @@ if extra_sysroot != '':
+ 
+ # Include paths
+ env.Append(CPPPATH = Split('''#/common
+-  #/asio
+   #/galerautils/src
+   #/gcomm/src
+   #/gcomm/src/gcomm
+Index: percona-xtradb-cluster-galera-2.x-2.11.2675/galerautils/src/gu_fifo.c
+===
+--- percona-xtradb-cluster-galera-2.x-2.11.2675.orig/galerautils/src/gu_fifo.c
 percona-xtradb-cluster-galera-2.x-2.11.2675/galerautils/src/gu_fifo.c
+@@ -13,7 +13,7 @@
+  * minimum space when there are few items in the queue. 
+  */
+ 
+-#define _BSD_SOURCE
++#define _DEFAULT_SOURCE
+ 
+ #include 
+ #include 

Bug#823344: bareos-storage: Automatic Volume Labeling not working after upgrade to 15.2.3

[Felix Geyer]

Hi,

On Tue, 03 May 2016 12:16:55 -0700 Soren Stoutner  
wrote:
> Package: bareos-storage
> Version: 15.2.3-2
> Severity: normal
> 
> Dear Maintainer,
> 
> After upgrading from 14.2.6 to 15.2.3, automatic volume labeling no longer 
> works.
> 
> The relevant sections from bareos-sd.conf:
> 
> Device {
>   Name = Backup1
>   Media Type = File
>   Archive Device = /var/lib/bareos/storage/Backup1
>   LabelMedia = yes;   # lets Bareos label unlabeled media
>   Random Access = yes;
>   AutomaticMount = yes;   # when device opened, read it
>   RemovableMedia = yes;
>   AlwaysOpen = no;
> }
> 
> Device {
>   Name = Backup2
>   Media Type = File
>   Archive Device = /var/lib/bareos/storage/Backup2
>   LabelMedia = yes;   # lets Bareos label unlabeled media
>   Random Access = yes;
>   AutomaticMount = yes;   # when device opened, read it
>   RemovableMedia = yes;
>   AlwaysOpen = no;
> }

Could you please try if the problem goes away when you set RemovableMedia = no?

Felix

Bug#823444: linux-image-4.5.0-0.bpo.1-amd64: breaks kwin (abort with fatal error) on Thinkpad T560

[Ben Hutchings]

On Wed, 2016-05-04 at 21:38 +0200, Maria wrote:
> Package: src:linux
> Version: 4.5.1-1~bpo8+1
> Severity: important
> 
> Dear Ben,
> 
> I didn't find the error among the list of over 1500 packages shown to
> me, sorry. This is an addendum to error #823156 which I wrote
> initially on this topic. And the title of #819272 sounded similar.
> I actually reinstalled Debian on a USB 3 Harddisk to test wether the
> problem still occurs with the Firmware (firmware-misc-nonfree,
> firmware-intel-sound, firmware-iwlwifi).

The firmware-iwlwifi version is too old; you'll need the version in
jessie-backports.

>  But I still get stuck at the console. 
> Kwin still refuses to load and aborts with the same fatal error.

You didn't say what the error is.

Which version of xserver-xorg-video-intel do you have?  You may need
the version from jessie-backports.

>  I actually started with the install of the new header files and
> kernel. As I had the same effect I started with installing the
> firmware-misc-nonfree.
> Then I installed the other two. But there was no change. Just an
> error of failing to load some Kernel module, which was too fast to
> see. I hope it is in the logs below. 

I don't see it, unfortunately.

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of incompetence.

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

Bug#823134: calibre: Cannot edit books

[Tobias Brink]

Package: calibre
Version: 2.55.0+dfsg-1
Followup-For: Bug #823134

BTW, if you need a quick hack to fix this, run the following as root:

dpkg -L calibre | grep py$ | xargs sed -i 's/QUrl\.None/QUrl.None_/g'

Warning: This will edit the package's files (see debsums errors in the
information below). Still, this makes the program usable until the next update.



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

Kernel: Linux 4.5.0-1-amd64 (SMP w/8 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 calibre depends on:
ii  calibre-bin2.55.0+dfsg-1
ii  fonts-liberation   1.07.4-1
ii  imagemagick8:6.8.9.9-7+b2
ii  libjs-mathjax  2.6.1-1
ii  poppler-utils  0.38.0-3
ii  python-apsw3.8.11.1-r1-1+b2
ii  python-beautifulsoup   3.2.1-1
ii  python-chardet 2.3.0-2
ii  python-cherrypy3   3.5.0-2
ii  python-cssselect   0.9.1+git90c72b0-1
ii  python-cssutils1.0-4.1
ii  python-dateutil2.4.2-1
ii  python-dbus1.2.4-1
ii  python-feedparser  5.1.3-3
ii  python-imaging 3.2.0-1
ii  python-lxml3.6.0-1
ii  python-markdown2.6.6-1
ii  python-mechanize   1:0.2.5-3
ii  python-netifaces   0.10.4-0.1+b2
ii  python-pil 3.2.0-1
ii  python-pkg-resources   20.10.1-1
ii  python-pyparsing   2.0.3+dfsg1-1
ii  python-pyqt5   5.6+dfsg-1
ii  python-pyqt5.qtsvg 5.6+dfsg-1
ii  python-pyqt5.qtwebkit  5.6+dfsg-1
ii  python-routes  2.2-1
ii  python2.7  2.7.11-8
ii  xdg-utils  1.1.1-1

Versions of packages calibre recommends:
ii  python-dnspython  1.12.0-1

calibre suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/calibre/calibre/gui2/book_details.py (from 
calibre package)
debsums: changed file /usr/lib/calibre/calibre/gui2/comments_editor.py (from 
calibre package)
debsums: changed file /usr/lib/calibre/calibre/gui2/dialogs/book_info.py (from 
calibre package)
debsums: changed file /usr/lib/calibre/calibre/gui2/metadata/single_download.py 
(from calibre package)
debsums: changed file /usr/lib/calibre/calibre/gui2/store/web_control.py (from 
calibre package)
debsums: changed file /usr/lib/calibre/calibre/gui2/tweak_book/check.py (from 
calibre package)
debsums: changed file /usr/lib/calibre/calibre/gui2/tweak_book/preview.py (from 
calibre package)
debsums: changed file /usr/lib/calibre/calibre/gui2/viewer/image_popup.py (from 
calibre package)
debsums: changed file /usr/lib/calibre/calibre/web/jsbrowser/browser.py (from 
calibre package)

Bug#817806: please upload fresh bugfix (4.4.4)

[Nicholas D Steeves]

Hi Yaroslav,

Is this bug for linux-image or btrfs-tools?  Kernels based on
linux-4.4.6 and linux-4.5.1 are available, and I've updated
btrfs-progs to v4.4.1.  I'm planning to upload v4.5.2 soon, for
completeness, but it will be to experimental, because I've read a
couple of reports of problems that were solved by downgrading to
btrfs-progs v4.4.x.

Kind regards,
Nicholas

Bug#820479: patch

[Nicholas D Steeves]

Hi Steve,

I just wanted to follow-up, and mention that the btrfs-progs rename
and patched partman-btrfs are in the archive and have migrated to
testing.

Best regards,
Nicholas

Bug#823454: mutt-patched: soft-fill behaviour no longer working in sidebar after 1.5.24-1 -> 1.6.0-1

[nfb]

Package: mutt-patched
Version: 1.6.0-1
Severity: normal

Dear Maintainer,

after having updated mutt(-patched) today from 1.5.24-1 to 1.6.0-1,
i noticed that long mailbox names are no longer truncated, and as
consequence mailbox sizes are no longer visible for some mailboxes,
since the name takes the whole space.

I remember the default behaviour of the previous version(s) was to
truncate long mailbox names to leave space to mailbox sizes, like in
the soft-fill format. Now it's the opposite.
Particularly, i never had to use the sidebar_format option in my
.muttrc (i don't even know wheter it has been introduced now or was
already there, just to say).

At this point, i tried getting the good ol' behaviour setting the
sidebar_format option, but it doesn't seem to do what i want. You can
consider this simplified test version:

set sidebar_format = "%B%*  %S"

With this format string I'd expect the rightmost part (mailbox size)
to be always visible because of the soft-fill (e.g. " 219"), and have
the mailbox name truncated at some point if it is too long, or padded
with ' ' if it is too short.
Anyway as i said, this is not working as expected, but it behaves like
the regular right-alignment was used ('%> ') since the mailbox sizes
are right-aligned, but mailbox names take the precedence when they are
too long. So:

- Is soft-fill even supported by the sidebar_format option?
- Is there an equivalent way to obtain this behaviour in the sidebar?
- Am i misunderstanding something?

In the same way, also the default value of the sidebar_format option
specified in the man page (Default: “%B%?F? [%F]?%* %?N?%N/?%4S”) is
not doing its job.

Let me know if you need additional infos.
Thank you.



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

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

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

mutt-patched recommends no packages.

mutt-patched suggests no packages.

-- no debconf information

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

[Daniel Richard G.]

Hi David,

On Wed, 2016 May  4 10:06+0200, David Kalnischkies wrote:
>
> Please move this to a new (wishlist) bugreport – as I think we can do
> something about that (see below)…

Great to hear :)

> … to a certain extend. We can't change 'foo-' to mean 'foo:*-' as for
> libraries (M-A: same) it would mean that you always remove all of
> them, while you perhaps just want to remove one of the set. More
> importantly through it is just inconsistent as all the other modifiers
> do not apply to a 'group' of packages either, its always a single
> package with a specific architecture (native by default) by default.

While I favor Carsten's proposal (if two arch packages are installed and
I want to remove only one, I'd think it reasonable to add the arch
specifier then), I don't find myself removing packages often enough for
it to be a great concern.

(Though if I'm, say, removing "foo" and "foo:i386" will remain
installed, it would be nice for apt-get to point that out. In case I'm
under the mistaken impression that I'm getting rid of "foo" completely.)

> That said, the problem with bluez above is that xubuntu-desktop
> recommends bluez (not checked, inferred from your message) and given
> that bluez:amd64 isn't installable, apt tries to install bluez:i386
> because that is also satisfying bluez (as it is M-A: foreign).

"xubuntu-desktop" does recommend "bluez", but I think the issue is
hairier than that, as I have not observed this behavior in scenarios
involving fewer packages. As metapackages go, this one is gigantic,
and if I had ever encountered a simpler example I would have given
that instead.

> I think the resolver should realize that if bluez(:amd64) is
> forbidden from the installation everything which provides
> bluez(:amd64) [which is how M-A:foreign is implemented internally] is
> forbidden to step in for bluez(:amd64), too – but not forbidden on
> its own (which foo:*- does).
>
> That should capture the "common" case of M-A:foreign packages in "foo
> recommends bar", but would still allow picking off alternatives in
> cases like "foo recommends bar | bar:i386".

Hmm. If someone specifies "bluez:amd64-", they may intend for
"bluez:i386" to be installable. But the resolver should be able to
distinguish that from "bluez-", right?

> Anyway, please split it off (cloning feels a bit wrong as it isn't
> overly related to the other long messages in this report) to a new bug
> for record keeping.  Perhaps I even have some time later this week to
> look into implementing this…

I am happy to have direction from you on this, as just discovering this
report as relevant to the issue was non-trivial :]  I will prepare and
file a new wishlist bug report, then.

Bug#823134: calibre: Cannot edit books

[Tobias Brink]

Package: calibre
Version: 2.55.0+dfsg-1
Followup-For: Bug #823134

I also have this problem. It occurs not only when editing a book but also when
trying to view a book or do a bunch of other things. It makes this package
pretty much unusable for me right now.

The problem seems to be related to a recent python-pyqt5 update to version 5.6.
They seem to have helpfully broken the API: "PyQt5.Qt.QUrl.None" is now named
"PyQt5.Qt.QUrl.None_" as far as I can see. Great. Maybe there are other
problems after fixing this one, too, the upstream changelog for pyqt5 does not
mention this from what I can tell at a quick glance.

I think upstream doesn't know about this. It is not fixed in their github.com
repo and I can't find a bug report. They use Launchpad, though, where I would
need to create an account and I barely have time to report this here right now.
If somebody with connections to upstream could pass this along? Otherwise I'd
have to have a look next week or even later.



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

Kernel: Linux 4.5.0-1-amd64 (SMP w/8 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 calibre depends on:
ii  calibre-bin2.55.0+dfsg-1
ii  fonts-liberation   1.07.4-1
ii  imagemagick8:6.8.9.9-7+b2
ii  libjs-mathjax  2.6.1-1
ii  poppler-utils  0.38.0-3
ii  python-apsw3.8.11.1-r1-1+b2
ii  python-beautifulsoup   3.2.1-1
ii  python-chardet 2.3.0-2
ii  python-cherrypy3   3.5.0-2
ii  python-cssselect   0.9.1+git90c72b0-1
ii  python-cssutils1.0-4.1
ii  python-dateutil2.4.2-1
ii  python-dbus1.2.4-1
ii  python-feedparser  5.1.3-3
ii  python-imaging 3.2.0-1
ii  python-lxml3.6.0-1
ii  python-markdown2.6.6-1
ii  python-mechanize   1:0.2.5-3
ii  python-netifaces   0.10.4-0.1+b2
ii  python-pil 3.2.0-1
ii  python-pkg-resources   20.10.1-1
ii  python-pyparsing   2.0.3+dfsg1-1
ii  python-pyqt5   5.6+dfsg-1
ii  python-pyqt5.qtsvg 5.6+dfsg-1
ii  python-pyqt5.qtwebkit  5.6+dfsg-1
ii  python-routes  2.2-1
ii  python2.7  2.7.11-8
ii  xdg-utils  1.1.1-1

Versions of packages calibre recommends:
ii  python-dnspython  1.12.0-1

calibre suggests no packages.

-- no debconf information

Bug#823369: adacontrol: FTBFS: t_representation_clauses vs. big-endian systems

[Matthias Klose]

On 04.05.2016 22:36, Jean-Pierre Rosen wrote:

Le 04/05/2016 à 20:31, Matthias Klose a écrit :

OK, then type D (for diff) to see the reason. Please send the output so
I can see if there is something obviouse...


attached.


Well, for some reason linked to the target architecture, the source of
the test does not compile. It's not the test that fails, it's the test
itself that has a problem.

So, is it possible to ignore this "failure"? It would be a pity to block
a release due to a problem in the test, not in the program!


Probably, so how should that be disabled?

Bug#823453: khronos-opengl-man4: get-orig-source should use a peg revision

[Daniel Shahaf]

Source: khronos-opengl-man4
Version: 1.0~svn31251-1
Severity: minor
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Dear Maintainer,

I've noticed that the get-orig-source target is implemented in a way
that's susceptible to bitrot: the 'svn export' command it uses could
retrieve a different source tree in a year than it does today, due to
passing an implicit peg revision of "HEAD" (which is mutable).

The following patch fixes the issue:

[[[
Index: debian/get-orig-source
===
--- debian/get-orig-source  (revision 6506)
+++ debian/get-orig-source  (working copy)
@@ -20,7 +20,7 @@ fi
 FOLDER=${PACKAGE}-${VERSION}
 
 
URL=https://cvs.khronos.org/svn/repos/ogl/trunk/ecosystem/public/sdk/docs/man4/ 
-svn export --quiet --revision ${REVISION} ${URL} ${FOLDER}
+svn export --quiet ${URL}@${REVISION} ${FOLDER}
 
 # we will re-generate them anyway:
 rm ${FOLDER}/xhtml/*.xml
]]]

The reference documentation is
.

Cheers,

Daniel

Bug#823452: opengl-4-html-doc: please make the build reproducible (randomness)

[Daniel Shahaf]

Package: opengl-4-html-doc
Version: 1.0~svn31251-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that opengl-4-html-doc could not be built reproducibly [2].

Specifically, the incumbent index sorting emits the glMemoryBarrier and
memoryBarrier entries in random order, determined by readdir() and dict
iteration order.  The attached patch makes the index sorting
deterministic, such that those two entries are always emitted in the
same order.

Cheers,

Daniel
(thanks to boyska on #debian-reproducible for correcting an earlier
draft of the patch)

 [1]: https://wiki.debian.org/ReproducibleBuilds
 [2]: 
https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/khronos-opengl-man4.html
diff --git a/debian/patches/reproducible.patch b/debian/patches/reproducible.patch
new file mode 100644
index 000..0ab9dcf
--- /dev/null
+++ b/debian/patches/reproducible.patch
@@ -0,0 +1,20 @@
+Description: Make the build reproducible: make index order independent of dict keys iteration order
+Author: Daniel Shahaf 
+Forwarded: no
+Last-Update: 2016-05-03 
+Bug-Debian: https://bugs.debian.org/-1
+
+--- khronos-opengl-man4-1.0~svn31251.orig/html/makeindex.py
 khronos-opengl-man4-1.0~svn31251/html/makeindex.py
+@@ -238,7 +238,10 @@ def sortedKeys(dict, whichKeys):
+ (whichKeys == 'api' and dict[key].apiCommand) or
+ (whichKeys == 'glsl' and not dict[key].apiCommand)):
+ list.append(key)
+-list.sort(key=str.lower)
++# Sort case-insensitively; the second tuple element is a tie breaker,
++# making the order deterministic/reproducible.
++keyFunc = lambda dictkey: (str.lower(dictkey), dictkey)
++list.sort(key=keyFunc)
+ return list
+ 
+ # Generate accordion menu for this dictionary, titled as specified.
diff --git a/debian/patches/series b/debian/patches/series
index e686169..ff66dbf 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 addingmanpages.patch
 db5.patch
 use_local_mathjax.patch
+reproducible.patch

Bug#819719: override: apt:admin/required

[Cyril Brulebois]

Hi Ansgar,

And thanks for the prod/sorry for the lag.

Ansgar Burchardt  (2016-04-01):
> Package: ftp.debian.org
> Severity: normal
> 
> apt is currently at Priority: important, but debootstrap treats it
> like Priority: required by including it in every variant explicitly:
> 
> +---
> | if doing_variant - || doing_variant fakechroot; then
> | #required="$required $(get_debs Priority: important)"
> | #  ^^ should be getting debconf here somehow maybe
> | base="$(get_debs Priority: important)"
> | elif doing_variant buildd || doing_variant scratchbox; then
> | base="apt build-essential"
> | elif doing_variant minbase; then
> | base="apt"
> | fi
> +---[ file:///usr/share/debootstrap/scripts/sid ]
> 
> If apt was Priority: required, debootstrap wouldn't need to pretend it
> was. It also seems more honest ;)

We will likely need to keep it in there (debootstrap) for a while anyway
given scripts are used (through symlinks) for many distributions. But it
looks like a good idea to get overrides in line with reality anyway.

So ack from d-i rm; if anything breaks, things should be easy enough to
fix (famous last words).

[ Extra cc for debian-cd@ to cover all the bases. ]


KiBi.


signature.asc
Description: Digital signature

Bug#823451: libbitcoin fails to build on all archs except x86

[Matthias Klose]

Package: src:libbitcoin
Version: 2.11.0-1
Severity: serious
Tags: sid stretch

libbitcoin fails to build on all release archs except x86, where it built 
before.

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

Bug#823429: libreoffice: wrong package description for libreoffice-l10n-zh-tw (taiwanese, not Chinese_traditional)

[Rene Engelhard]

Hi,

On Wed, May 04, 2016 at 10:25:05PM +0200, Jonas Smedegaard wrote:
> > Almost everything in the world does it how is it now, why should we 
> > change it?
> 
> Is the content of the package truly traditional chinese locale data, not 
> taiwanese-flavored chinese locale data?

it's not locale data at all. It's UI locaalization. Nothing else.

> For these packages, the same suffix is described as "Taiwan":
> firefox-l10n-zh-tw firefox-esr-l10n-zh-tw iceowl-l10n-zh-tw 
> icedove-l10n-zh-tw iceweasel-l10n-zh-tw

I know, but that changed, I am sure it had it as simplified and traditional
long ago...

And there is still counter-examples:

kde-l10n-zhcn - Chinese Simplified (zh_CN) localization files for KDE
kde-l10n-zhtw - Chinese Traditional (zh_TW) localization files for KDE

> What is the logic of using suffix "tw" to denote "traditional"?

The logic is "everyone did it in the past as this", basically.
Yeah, I got that (almost) everything except KDE changed it..

Regards,

Rene

Bug#823429: libreoffice: wrong package description for libreoffice-l10n-zh-tw (taiwanese, not Chinese_traditional)

[Jonas Smedegaard]

Quoting Rene Engelhard (2016-05-04 21:48:12)
[not-essentially-this-bug comments snipped]
>> but the locale zh_TW which the package name quite likely is tied to 
>> is _not_ traditional chinese but instead taiwanese.
[more not-essentially-this-bug comments snipped]

> Almost everything in the world does it how is it now, why should we 
> change it?

Is the content of the package truly traditional chinese locale data, not 
taiwanese-flavored chinese locale data?

For these packages, the same suffix is described as "Taiwan":
firefox-l10n-zh-tw firefox-esr-l10n-zh-tw iceowl-l10n-zh-tw 
icedove-l10n-zh-tw iceweasel-l10n-zh-tw

What is the logic of using suffix "tw" to denote "traditional"?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#823450: cl-uuid: Typo in short description

[Thomas Vincent]

Package: cl-uuid
Severity: minor

Dear Maintainer,

I spotted a typo while translating the description of cl-uuid.

Indeed, in the short description, "Common Lisp librabry" should be replaced by 
"Common Lisp library".

Thanks for your work on cl-uuid,
Thomas


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

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

Bug#823429: libreoffice: wrong package description for libreoffice-l10n-zh-tw (taiwanese, not Chinese_traditional)

[Rene Engelhard]

Hi again,

On Wed, May 04, 2016 at 09:48:12PM +0200, Rene Engelhard wrote:
> On Wed, May 04, 2016 at 07:01:34PM +0200, Jonas Smedegaard wrote:
> > One thing is that the underscore is wrong there (both short and long
> > description fields should contain prose, not computer-mangled strings),
> 
> No, those are computer-generated and the stuff can't handle spaces. That's
> also why we have English_british etc.
> See https://cgit.freedesktop.org/libreoffice/core/tree/bin/lo-xlate-lang
> 
> And given they are understandable I don't see a bug here...

OK, actually it *seems* for control it works with spaces.. Either it doesn't
work for some internal use or for some specific distro needs... Will try..

But that is - if at all - a different "bug".

> > but the locale zh_TW which the package name quite likely is tied to is
> > _not_ traditional chinese but instead taiwanese.
> > 
> > Similarly, the package libreoffice-l10n-zh-cn is described as being
> > "Chinese_simplified" where at least the underscore should be corrected.
> 
> Almost everything in the world does it how is it now, why should we change it?
> 
> Regards,
> 
> Rene
> 

Bug#820493: aptitude: does not install package from Build-Depends

[Manuel A. Fernandez Montecelo]

2016-04-10 03:09 Dmitry Smirnov:

On Saturday, 9 April 2016 2:40:45 PM AEST Manuel A. Fernandez Montecelo
wrote:

From "buildpackage" until it starts unpacking the package's source and
compiling.


Sorry, I'm unable to spot anything useful... Maybe you could try?
Simple "apt-get source civicrm" is enough to fetch the package suitable to
reproduce the problem.


I don't always have the time, as I didn't have much in the last few
weeks, and with my miserable "broadband" took me the best of an hour to
get the system to an up-to-date state today.  In the weeks in between,
perhaps things changed, so it's difficult to solve things in this way...


Anyway, the basic problem today seems to be that:

 The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Depends: php-mail-mimedecode which is a 
virtual package and is not provided by any available package

This is because the package has been removed:

 https://packages.qa.debian.org/p/php-mail-mimedecode/news/20160502T014605Z.html

When trying to compile the package in cowbuilder, the output of this bit
looks like it's truncated (the last-but-one line):

=
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
pbuilder-satisfydepends-dummy depends on debhelper (>= 9); however:
 Package debhelper is not installed.
pbuilder-satisfydepends-dummy depends on pkg-php-tools (>= 1.14~); however:
 Package pkg-php-tools is not installed.
pbuilder-satisfydepends-dummy depends on dh-linktree; however:
 Package dh-linktree is not installed.
pbuilder-satisfydepends-dummy depends on fonts-font-awesome; however:
 Package fonts-font-awesome is not installed.
pbuilder-satisfydepends-dummy depends on libjs-angularjs; however:
 Package libjs-angularjs is not installed.
pbuilder-satisfydepends-dummy depends on libjs-backbone; however:
 Package libjs-backbone is not installed.
pbuilder-satisfydepends-dummy depends on libjs-d3; however:
 Package libjs-d3 is not installed.
pbuilder-satisfydepends-dummy depends on libjs-jquery (>= 1.11.3~); however:
 Package libjs-jquery is not installed.
pbuilder-satisfydepends-dummy depends on l
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
=
			 
I reported this informally to pbuilder and dpkg, I am not sure about

what's going on, but looks suspicious.

Probably if this was complete there would be a clue about why
php-gettext doesn't get pulled.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#823429: libreoffice: wrong package description for libreoffice-l10n-zh-tw (taiwanese, not Chinese_traditional)

[Rene Engelhard]

reassign 823429 libreoffice-l10n-zh-cn,libreoffice-l10n-zh-tw
retitle 823429 Subject: Re: Bug#823429: libreoffice: wrong package description 
for libreoffice-l10n-zh-*
tag 823429 - wontfix
thanks

Hi,

On Wed, May 04, 2016 at 09:48:12PM +0200, Rene Engelhard wrote:
> On Wed, May 04, 2016 at 07:01:34PM +0200, Jonas Smedegaard wrote:
> > One thing is that the underscore is wrong there (both short and long
> > description fields should contain prose, not computer-mangled strings),
> 
> No, those are computer-generated and the stuff can't handle spaces. That's
> also why we have English_british etc.
> See https://cgit.freedesktop.org/libreoffice/core/tree/bin/lo-xlate-lang
> 
> And given they are understandable I don't see a bug here...
> 
> > but the locale zh_TW which the package name quite likely is tied to is
> > _not_ traditional chinese but instead taiwanese.
> > 
> > Similarly, the package libreoffice-l10n-zh-cn is described as being
> > "Chinese_simplified" where at least the underscore should be corrected.
> 
> Almost everything in the world does it how is it now, why should we change it?

OK; I see almost the world changed to what you propose:

$ apt-cache search zh-tw  
chromium-l10n - web browser - language packs
icedove-l10n-zh-tw - Chinese (Taiwan) language package for Icedove
iceowl-l10n-zh-tw - Chinese (Taiwan) language package for iceowl-extension
iceweasel-l10n-zh-tw - Chinese (Taiwan) language package for Iceweasel
libreoffice-help-zh-tw - office productivity suite -- Chinese_traditional help
libreoffice-l10n-zh-tw - office productivity suite -- Chinese_traditional 
language package
openvanilla-imgeneric-data-zh-tw - libraries of openvanilla input method - 
Chinese (Traditional) data files

If we did it correctly we would use Republic of China for Taiwan, but that's
an other story.

Regards,

Rene

Bug#823449: freefem++ fails to build on nearly all architectures

[Matthias Klose]

Source: src:freefem++
Version: 3.46+dfsg1-1
Severity: serious
Tags: sid stretch

freefem++ fails to build on nearly all architectures, where it built before.
see https://buildd.debian.org/status/package.php?p=freefem%2B%2B

Looks like the tests are timing out.

Bug#823448: autogen: Breaks if rebuilt using gcc-6 and glibc 2.23

[Daniel Schepler]

Source: autogen
Version: 1:5.18.7-3
Severity: important

I'm running a test rebuild of the Debian archive against gcc-defaults
and glibc from experimental, using a bootstrapping process that "eats
its own dog food".  In gnutls28, I got this error:

...
make[6]: Entering directory '/build/gnutls28-3.4.11/src'
autogen srptool-args.def
fserr 2: cannot map data file options:  No such file or directory
Makefile:2232: recipe for target 'srptool-args.c' failed
make[6]: [srptool-args.c] Error 2 (ignored)
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H
-I. -I..  -I./gl -I./gl -I./../lib/includes -I./../lib/includes
-I./../libdane/includes -I./../extra/includes   -Wdate-time
-D_FORTIFY_SOURCE=2 -W -Wabi -Waddress -Waggressive-loop-optimizations
-Wall -W
attributes -Wbad-function-cast -Wbool-compare
-Wbuiltin-macro-redefined -Wcast-align -Wchar-subscripts -Wchkp
-Wclobbered -Wcomment -Wcomments -Wcoverage-mismatch -Wcpp -Wdate-time
-Wdeprecated -Wdeprecated-declarations -Wdesignated-init
-Wdisabled-optimization -Wdiscard
ed-array-qualifiers -Wdiscarded-qualifiers -Wdiv-by-zero
-Wdouble-promotion -Wempty-body -Wendif-labels -Wenum-compare -Wextra
-Wformat-contains-nul -Wformat-extra-args -Wformat-security
-Wformat-zero-length -Wfree-nonheap-object -Wignored-qualifiers
-Wimplicit -Wimplici
t-function-declaration -Wimplicit-int -Wincompatible-pointer-types
-Winit-self -Wint-conversion -Wint-to-pointer-cast
-Winvalid-memory-model -Winvalid-pch -Wjump-misses-init
-Wlogical-not-parentheses -Wlogical-op -Wmain -Wmaybe-uninitialized
-Wmemset-transposed-args -Wmi
ssing-braces -Wmissing-declarations -Wmissing-field-initializers
-Wmissing-include-dirs -Wmissing-parameter-type -Wmissing-prototypes
-Wmultichar -Wnarrowing -Wnested-externs -Wnonnull -Wodr
-Wold-style-declaration -Wold-style-definition -Wopenmp-simd
-Woverflow -Woverri
de-init -Wpacked -Wpacked-bitfield-compat -Wparentheses
-Wpointer-arith -Wpointer-sign -Wpointer-to-int-cast -Wpragmas
-Wreturn-local-addr -Wreturn-type -Wsequence-point -Wshadow
-Wshift-count-negative -Wshift-count-overflow -Wsizeof-array-argument
-Wsizeof-pointer-memac
cess -Wstrict-aliasing -Wstrict-prototypes -Wsuggest-attribute=format
-Wsuggest-final-methods -Wsuggest-final-types -Wswitch -Wswitch-bool
-Wsync-nand -Wtrampolines -Wtrigraphs -Wtype-limits -Wuninitialized
-Wunknown-pragmas -Wunsafe-loop-optimizations -Wunused -Wunused-
but-set-parameter -Wunused-but-set-variable -Wunused-function
-Wunused-label -Wunused-local-typedefs -Wunused-macros
-Wunused-parameter -Wunused-result -Wunused-value -Wunused-variable
-Wvarargs -Wvariadic-macros -Wvector-operation-performance
-Wvolatile-register-var -Ww
rite-strings -Warray-bounds=2 -Wnormalized=nfc
-Wno-missing-field-initializers -Wno-missing-field-initializers
-Wno-format-y2k -Wno-unused-value -Wno-unused-result
-Wno-unused-parameter -Wno-stack-protector -Wno-int-to-pointer-cast
-fdiagnostics-show-option  -g -O2 -fsta
ck-protector-strong -Wformat -Werror=format-security -Wall -c -o
srptool-args.lo srptool-args.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I./gl -I./gl
-I./../lib/includes -I./../lib/includes -I./../libdane/includes
-I./../extra/includes -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wabi
-Waddress -Waggressive-loop-optimizations -Wall -Wattributes
-Wbad-function-cast -
Wbool-compare -Wbuiltin-macro-redefined -Wcast-align -Wchar-subscripts
-Wchkp -Wclobbered -Wcomment -Wcomments -Wcoverage-mismatch -Wcpp
-Wdate-time -Wdeprecated -Wdeprecated-declarations -Wdesignated-init
-Wdisabled-optimization -Wdiscarded-array-qualifiers -Wdiscarded-
qualifiers -Wdiv-by-zero -Wdouble-promotion -Wempty-body
-Wendif-labels -Wenum-compare -Wextra -Wformat-contains-nul
-Wformat-extra-args -Wformat-security -Wformat-zero-length
-Wfree-nonheap-object -Wignored-qualifiers -Wimplicit
-Wimplicit-function-declaration -Wimplici
t-int -Wincompatible-pointer-types -Winit-self -Wint-conversion
-Wint-to-pointer-cast -Winvalid-memory-model -Winvalid-pch
-Wjump-misses-init -Wlogical-not-parentheses -Wlogical-op -Wmain
-Wmaybe-uninitialized -Wmemset-transposed-args -Wmissing-braces
-Wmissing-declarati
ons -Wmissing-field-initializers -Wmissing-include-dirs
-Wmissing-parameter-type -Wmissing-prototypes -Wmultichar -Wnarrowing
-Wnested-externs -Wnonnull -Wodr -Wold-style-declaration
-Wold-style-definition -Wopenmp-simd -Woverflow -Woverride-init
-Wpacked -Wpacked-bitfie
ld-compat -Wparentheses -Wpointer-arith -Wpointer-sign
-Wpointer-to-int-cast -Wpragmas -Wreturn-local-addr -Wreturn-type
-Wsequence-point -Wshadow -Wshift-count-negative
-Wshift-count-overflow -Wsizeof-array-argument
-Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstrict-
prototypes -Wsuggest-attribute=format -Wsuggest-final-methods
-Wsuggest-final-types -Wswitch -Wswitch-bool -Wsync-nand -Wtrampolines
-Wtrigraphs -Wtype-limits -Wuninitialized -Wunknown-pragmas
-Wunsafe-loop-optimizations -Wunused -Wunused-but-set-parameter
-Wunused-but-s
et-variable -Wunused-function -Wunused-label 

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

[Sebastian Andrzej Siewior]

On 2016-04-05 10:43:13 [+0200], Christian Pernegger wrote:
> Hi,
Hi,

> no error e-mail this week, yay!
> 
> It looks like this is/was a duplicate of #788652 in the end (at least
> the clamav-freshclam part of it). If you agree, please close & merge
> as appropriate.

indeed. This did not yet migrate into stable. What is your change that
you made to make it go away?
But you are right. The reload fails if it is started from cron. Not sure
if the error message is the same :)

> Thank you,
> Christian

Sebastian

Bug#823074: clamav: Fix LSB init output

[Sebastian Andrzej Siewior]

control: tags -1 pending

On 2016-05-04 02:00:22 [+0200], Guillem Jover wrote:
> Hi!
Hi,

> I checked those when fixing freshclam, and they looked fine, but it's
> true that they might also miss --quiet for start-stop-daemon itself.

Oki. Added to your patch:
https://anonscm.debian.org/cgit/pkg-clamav/clamav.git/commit/?id=8f6bb8f02a7c6fbfb0fdbdf3ae40c3e83dad00f0

> Thanks,
> Guillem

Sebastian

Bug#823447: gtest: FTBFS with g++-6 and glibc 2.23: Test failure

[Daniel Schepler]

Source: gtest
Version: 1.7.0-4
Severity: important

>From my pbuilder build log, using a chroot with gcc-defaults and glibc
from experimental:

...
31/41 Test #30: gtest_catch_exceptions_test ***Failed0.82 sec
.FF.
==
FAIL: testCatchesCxxExceptionsInSetUp (__main__.CatchCxxExceptionsTest)
--
Traceback (most recent call last):
 File "/build/gtest-1.7.0/test/gtest_catch_exceptions_test.py", line
176, in testCatchesCxxExceptionsInSetUp
   in EX_BINARY_OUTPUT)
AssertionError: False is not true

==
FAIL: testCatchesCxxExceptionsInSetUpTestCase (__main__.CatchCxxExceptionsTest)
--
Traceback (most recent call last):
 File "/build/gtest-1.7.0/test/gtest_catch_exceptions_test.py", line
148, in testCatchesCxxExceptionsInSetUpTestCase
   in EX_BINARY_OUTPUT)
AssertionError: False is not true

==
FAIL: testCatchesCxxExceptionsInTearDown (__main__.CatchCxxExceptionsTest)
--
Traceback (most recent call last):
 File "/build/gtest-1.7.0/test/gtest_catch_exceptions_test.py", line
194, in testCatchesCxxExceptionsInTearDown
   in EX_BINARY_OUTPUT)
AssertionError: False is not true

==
FAIL: testCatchesCxxExceptionsInTearDownTestCase
(__main__.CatchCxxExceptionsTest)
--
Traceback (most recent call last):
 File "/build/gtest-1.7.0/test/gtest_catch_exceptions_test.py", line
171, in testCatchesCxxExceptionsInTearDownTestCase
   in EX_BINARY_OUTPUT)
AssertionError: False is not true

==
FAIL: testCatchesCxxExceptionsInTestBody (__main__.CatchCxxExceptionsTest)
--
Traceback (most recent call last):
 File "/build/gtest-1.7.0/test/gtest_catch_exceptions_test.py", line
205, in testCatchesCxxExceptionsInTestBody
   in EX_BINARY_OUTPUT)
AssertionError: False is not true

==
FAIL: testCatchesNonStdCxxExceptions (__main__.CatchCxxExceptionsTest)
--
Traceback (most recent call last):
 File "/build/gtest-1.7.0/test/gtest_catch_exceptions_test.py", line
218, in testCatchesNonStdCxxExceptions
   in EX_BINARY_OUTPUT)
AssertionError: False is not true

--
Ran 8 tests in 0.004s

FAILED (failures=6)

32/41 Test #34: gtest_help_test    Passed0.51 sec
33/41 Test #35: gtest_list_tests_unittest ..   Passed0.51 sec
34/41 Test #37: gtest_shuffle_test .   Passed0.07 sec
35/41 Test #36: gtest_output_test ..   Passed0.17 sec
36/41 Test #38: gtest_throw_on_failure_test    Passed0.17 sec
37/41 Test #33: gtest_filter_unittest ..   Passed0.68 sec
 Start 39: gtest_uninitialized_test
 Start 40: gtest_xml_outfiles_test
 Start 41: gtest_xml_output_unittest
38/41 Test #40: gtest_xml_outfiles_test    Passed0.14 sec
39/41 Test #39: gtest_uninitialized_test ...   Passed0.24 sec
40/41 Test #41: gtest_xml_output_unittest ..   Passed0.24 sec
41/41 Test #11: gtest-port_test    Passed2.03 sec

98% tests passed, 1 tests failed out of 41

Total Test time (real) =   2.21 sec

The following tests FAILED:
30 - gtest_catch_exceptions_test (Failed)
Errors while running CTest
Makefile:64: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory '/build/gtest-1.7.0/obj-x86_64-linux-gnu'
dh_auto_test: make -j8 test ARGS+=-j8 returned exit code 2
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#823429: libreoffice: wrong package description for libreoffice-l10n-zh-tw (taiwanese, not Chinese_traditional)

[Rene Engelhard]

severity 823429 wishlist
tag 823429 + wontfix
thanks

Hi,

On Wed, May 04, 2016 at 07:01:34PM +0200, Jonas Smedegaard wrote:
> One thing is that the underscore is wrong there (both short and long
> description fields should contain prose, not computer-mangled strings),

No, those are computer-generated and the stuff can't handle spaces. That's
also why we have English_british etc.
See https://cgit.freedesktop.org/libreoffice/core/tree/bin/lo-xlate-lang

And given they are understandable I don't see a bug here...

> but the locale zh_TW which the package name quite likely is tied to is
> _not_ traditional chinese but instead taiwanese.
> 
> Similarly, the package libreoffice-l10n-zh-cn is described as being
> "Chinese_simplified" where at least the underscore should be corrected.

Almost everything in the world does it how is it now, why should we change it?

Regards,

Rene

Bug#823446: cowpoke fails on symlinkedd .orig.tar.gz

[Antoine Beaupré]

Package: devscripts
Version: 2.15.3
Severity: normal

It seems to me like fairly common practice to have symlinked
.orig.tar.gz files. Yet cowpoke seems incapable of managing those
files. I see this:

$ cowpoke --buildd=marcos.anarc.at --dist=wheezy --arch=amd64 
../xen_4.1.6.1-1+deb7u1.dsc
cowssh_it
  4,845 100%0.00kB/s0:00:00 (xfr#1, to-chk=4/5)
skipping non-regular file "xen_4.1.6.1.orig-qemu.tar.gz"
skipping non-regular file "xen_4.1.6.1.orig.tar.gz"
xen_4.1.6.1-1+deb7u1.debian.tar.xz
150,728 100%   23.96MB/s0:00:00 (xfr#2, to-chk=3/5)
xen_4.1.6.1-1+deb7u1.dsc
  2,372 100%  289.55kB/s0:00:00 (xfr#3, to-chk=2/5)

sent 158,271 bytes  received 190 bytes  63,384.40 bytes/sec
total size is 157,983  speedup is 1.00
 --- Begin build for amd64 wheezy ---
[...]
cp: cannot stat 
'/home/anarcat/cowbuilder-incoming/xen_4.1.6.1.orig-qemu.tar.gz': No such file 
or directory
I: unmounting /home filesystem
I: unmounting dev/pts filesystem
I: unmounting proc filesystem
 -> Cleaning COW directory
  forking: rm -rf /var/cache/pbuilder/build/cow.23114
Connection to marcos.anarc.at closed.

Can we support those files please?

-- Package-specific info:

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

--- ~/.devscripts ---
RMADISON_DEFAULT_URL=debian,ubuntu
DSCVERIFY_KEYRINGS=~/.gnupg/pubring.gpg

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev 1.17.27
ii  libc62.19-18+deb8u4
ii  perl 5.20.2-3+deb8u4
ii  python3  3.4.2-2
pn  python3:any  

Versions of packages devscripts recommends:
pn  at  
ii  curl7.38.0-4+deb8u3
ii  dctrl-tools 2.23
ii  debian-keyring  2015.04.10
ii  dput0.9.6.4
ii  equivs  2.0.9
ii  fakeroot1.20.2-1
ii  file1:5.22+15-2+deb8u1
ii  gnupg   1.4.18-7+deb8u1
ii  libdistro-info-perl 0.14
ii  libencode-locale-perl   1.03-1
ii  libjson-perl2.61-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libparse-debcontrol-perl2.005-4
ii  libsoap-lite-perl   1.11-1
ii  liburi-perl 1.64-1
ii  libwww-perl 6.08-1
ii  lintian 2.5.44~bpo8+1
ii  man-db  2.7.0.2-5
ii  patch   2.7.5-1
ii  patchutils  0.3.3-1
ii  python3-debian  0.1.27
ii  python3-magic   1:5.22+15-2+deb8u1
ii  sensible-utils  0.0.9
ii  strace  4.9-2
ii  unzip   6.0-16+deb8u2
ii  wdiff   1.2.2-1
ii  wget1.16-1
ii  xz-utils5.1.1alpha+20120614-2+b3

Versions of packages devscripts suggests:
ii  bsd-mailx [mailx]8.1.2-0.20141216cvs-2
ii  build-essential  11.7
pn  cvs-buildpackage 
pn  debbindiff   
ii  devscripts-el35.12
ii  gnuplot  4.6.6-2
ii  gpgv 1.4.18-7+deb8u1
ii  libauthen-sasl-perl  2.1600-1
pn  libfile-desktopentry-perl
ii  libnet-smtp-ssl-perl 1.01-3
ii  libterm-size-perl0.207-1+b2
ii  libtimedate-perl 2.3000-2
ii  libyaml-syck-perl1.27-2+b2
ii  mutt 1.5.23-3
ii  openssh-client [ssh-client]  1:6.7p1-5+deb8u2
ii  svn-buildpackage 0.8.5+nmu1
ii  w3m  0.5.3-19

-- no debconf information

Bug#823445: congress: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: congress 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the Dutch translation of congress debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#822444: Solved

[Sebastian Andrzej Siewior]

control: tags -1 patch pending
control: forwarded -1 https://bugzilla.clamav.net/show_bug.cgi?id=11557 
control: found -1 0.98.5~beta1+dfsg-1

On 2016-05-01 17:33:02 [+0200], Xavier Quost wrote:
> Hello Sebastian
Hi Xavier,

> Basically I was cloning configuration for mail server from wheezy to Jessie  
> and could not understand my mistake. Confronting configuration files between 
> wheezy and Jessie seeing nothing relevant lead me to look at init process.

yeah and I don't think this should happen.

> A simple comment in clamd configuration files like "clamd started with 
> systemd is enforcing strongly this options whereas started with sysinit it 
> might not" would have been enough for not bothering you.
maybe but people still need to read this and connect the dots. And when I
upgrade from oldstable to stable I am very glad about things I don't
have to deal with :)
Anyway. I removed the config option and it does not look that upstream
is insisting on it. So I will push this change in the next unstable upload
and hope that we won't carry that patch for long.

> Best regards and thanks for your kind explanations.
you are welcome.

> XQ

Sebastian

Bug#823440: senlin: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: senlin 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of senlin debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#823444: linux-image-4.5.0-0.bpo.1-amd64: breaks kwin (abort with fatal error) on Thinkpad T560

[Maria]

Package: src:linux
Version: 4.5.1-1~bpo8+1
Severity: important

Dear Ben,

I didn't find the error among the list of over 1500 packages shown to me, 
sorry. This is an addendum to error #823156 which I wrote initially on this 
topic. And the title of #819272 sounded similar.
I actually reinstalled Debian on a USB 3 Harddisk to test wether the problem 
still occurs with the Firmware (firmware-misc-nonfree, firmware-intel-sound, 
firmware-iwlwifi). But I still get stuck at the console. 
Kwin still refuses to load and aborts with the same fatal error. I actually 
started with the install of the new header files and kernel. As I had the same 
effect I started with installing the firmware-misc-nonfree.
Then I installed the other two. But there was no change. Just an error of 
failing to load some Kernel module, which was too fast to see. I hope it is in 
the logs below. 

Thanks for your work.
Maria



-- Package-specific info:
** Version:
Linux version 4.5.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.5.1-1~bpo8+1 (2016-04-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.5.0-0.bpo.1-amd64 
root=UUID=4fdaf978-e312-4fbc-b8e9-858f4a4934c0 ro quiet

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   10.939238] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input13
[   10.939319] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input14
[   10.939398] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input15
[   11.014402] iTCO_vendor_support: vendor-support=0
[   11.281309] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   11.281453] iTCO_wdt: Found a Intel PCH TCO device (Version=4, 
TCOBASE=0x0400)
[   11.281682] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   11.431640] usbcore: registered new interface driver btusb
[   11.433059] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   11.440063] Bluetooth: hci0: Device revision is 5
[   11.440073] Bluetooth: hci0: Secure boot is enabled
[   11.440078] Bluetooth: hci0: OTP lock is enabled
[   11.440083] Bluetooth: hci0: API lock is enabled
[   11.440087] Bluetooth: hci0: Debug lock is disabled
[   11.440093] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.440925] AVX2 version of gcm_enc/dec engaged.
[   11.440933] AES CTR mode by8 optimization enabled
[   11.490734] bluetooth hci0: firmware: failed to load intel/ibt-11-5.sfi (-2)
[   11.490765] bluetooth hci0: Direct firmware load for intel/ibt-11-5.sfi 
failed with error -2
[   11.490768] Bluetooth: hci0: Failed to load Intel firmware file (-2)
[   11.654093] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   11.661198] Bluetooth: hci0: Device revision is 5
[   11.661203] Bluetooth: hci0: Secure boot is enabled
[   11.661205] Bluetooth: hci0: OTP lock is enabled
[   11.661207] Bluetooth: hci0: API lock is enabled
[   11.661208] Bluetooth: hci0: Debug lock is disabled
[   11.661211] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.661228] bluetooth hci0: firmware: failed to load intel/ibt-11-5.sfi (-2)
[   11.661284] bluetooth hci0: Direct firmware load for intel/ibt-11-5.sfi 
failed with error -2
[   11.661288] Bluetooth: hci0: Failed to load Intel firmware file (-2)
[   11.751913] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   11.774531] Intel(R) Wireless WiFi driver for Linux
[   11.774535] Copyright(c) 2003- 2015 Intel Corporation
[   11.774893] iwlwifi :04:00.0: enabling device ( -> 0002)
[   11.777258] iwlwifi :04:00.0: firmware: failed to load 
iwlwifi-8000C-20.ucode (-2)
[   11.777336] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-20.ucode failed with error -2
[   11.777359] iwlwifi :04:00.0: firmware: failed to load 
iwlwifi-8000C-19.ucode (-2)
[   11.777439] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-19.ucode failed with error -2
[   11.777460] iwlwifi :04:00.0: firmware: failed to load 
iwlwifi-8000C-18.ucode (-2)
[   11.777536] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-18.ucode failed with error -2
[   11.777556] iwlwifi :04:00.0: firmware: failed to load 
iwlwifi-8000C-17.ucode (-2)
[   11.777631] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-17.ucode failed with error -2
[   11.777651] iwlwifi :04:00.0: firmware: failed to load 
iwlwifi-8000C-16.ucode (-2)
[   11.35] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-16.ucode failed with error -2
[   11.54] iwlwifi :04:00.0: firmware: failed to load 
iwlwifi-8000C-15.ucode (-2)
[   11.777829] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-15.ucode failed with error -2
[   11.777848] iwlwifi :04:00.0: firmware: failed to load 
iwlwifi-8000C-14.ucode (-2)
[   11.777921] iwlwifi :04:00.0: Direct firmware load for 

Bug#804944: dtach seems broken on arm64

[Stefan Völkel]

On Thu, 17 Dec 2015 16:18:17 -0800 "Ned T. Crigler" 
 wrote:

Something like the following could be an improvement to the error
message, though I can't think of a portable way to determine if forkpty
is looking for /dev/pts and a devpts filesystem, so that a hint could
also be added to the error message.

Did mounting devpts on /dev/pts fix the problem?


I can reproduce the problem inside a chroot without /dev/pts mounted. 
Once I mount /dev/pts the error is gone.


I'd say lets go with the patch.

Stefan

Bug#823443: usrmerge: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: usrmerge 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of usrmerge debconf 
messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#823442: tzdata: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: tzdata 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of tzdata debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#823441: zaqar: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: zaqar 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of zaqar debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#823439: gnocchi: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: gnocchi 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of gnocchi debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#397728: aptitude should purge deleted packages at the end

[Manuel A. Fernandez Montecelo]

Control: tags -1 + wontfix
Control: close -1


Hi,

2006-11-09 01:33 Vincent Lefevre:

Package: aptitude
Version: 0.4.3-1
Severity: normal

One may want to mark deleted packages as purge to get rid of obsolete
configuration files. But some configuration files may be common to a
package to be purged and a package to installed (this is the case when
a package is renamed). To avoid losing the contents of these files
(when the user has modified them), the actual purge should occur after
installing all the packages.


aptitude passes the information from a high-level point of view from
(lib)apt to dpkg, and they decide what to do between them depending on
complex sets of rules of who-depends-on-what.

aptitude doesn't intervine directly in that process, so it cannot do
much, sorry.  Closing as +wontfix.

I think that the cases that you mention has to be handled specially by
the package being renamed, to preserve the information from before.  If
old and new packages share config files, probably this is handled
specially by dpkg.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#820013: general: Touchpad not working on Lenovo IdeaPad Yoga 13 after updating from 8.3 to 8.4

[Juho]

Any news?

--
Juho