Bug#789619: NMU for Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred!

[Axel Beckert]

Control: tag -1 + pending

Hi,

Axel Beckert wrote:
> Will do the NMU soon.

I've uploaded it to DELAYED/1 (see
https://ftp-master.debian.org/deferred.html soon) to allow me to do
some more testing (mostly with GDL, etc.).

Except for the changelog there were IIRC no more changes compared to
the debdiff I posted earlier. Details and full history at
https://anonscm.debian.org/cgit/users/abe/nmu/plplot.git/ and
initially imported with "gbp import-dscs --debsnap plplot".

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


signature.asc
Description: Digital signature

Bug#801702: marked as done ([plasma-desktop] Recent Sid Upgrades Including Numerous KF5... Break Plasma-desktop)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2015 17:38:09 +0200
with message-id <11960545.29maxch...@whitebase.usersys.redhat.com>
and subject line Fixed kservice/kbuildsycoca loop
has caused the Debian Bug report #801702,
regarding [plasma-desktop] Recent Sid Upgrades Including Numerous KF5... Break 
Plasma-desktop
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
801702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-desktop
Version: 4:5.4.2-1
Severity: grave

--- Please enter the report below this line. ---
Recent upgrade from Sid breaks plasma-desktop. All apps can be run from a 
command line (i.e 
Yakuake starts and works!) but there is no desktop.

Plasmashell is running using few resources. If I kill it and restart it (what I 
too often must do to 
get the desktop!), then is loops with:
* * *
Reusing existing ksycoca
Recreating ksycoca file 
("/home/david/.cache/ksycoca5_en_3F1fXXDsrvdw3By1XvCKEDww3hA=", version 303)
Still in the time dict (i.e. deleted files) ("apps")
Saving
Reusing existing ksycoca
Recreating ksycoca file 
("/home/david/.cache/ksycoca5_en_3F1fXXDsrvdw3By1XvCKEDww3hA=", version 303)
Still in the time dict (i.e. deleted files) ("apps")
Saving
Reusing existing ksycoca ...

Reboots, trying new .kde, nothing helps.


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

Debian Release: Kali Linux 2.0
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 kali-currentsecurity.kali.org 
  500 kali-currenthttp.kali.org 
  500 jessie  linux.dropbox.com 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
kde-wallpapers-default  | 4:15.04.2-1
plasma-widgets-workspace(= 4:4.11.11-1) | 4:4.11.22-2
kde-runtime (>> 4:4.10) | 4:15.08.1-1
libc6 (>= 2.14) | 
libkactivities6 (>= 4:4.11) | 
libkcmutils4(>= 4:4.11) | 
libkdecore5 (>= 4:4.11) | 
libkdeui5   (>= 4:4.11) | 
libkephal4abi1  (= 4:4.11.11-1) | 
libkfile4   (>= 4:4.11) | 
libkidletime4   (>= 4:4.11) | 
libkio5 (>= 4:4.11) | 
libknewstuff3-4 (>= 4:4.11) | 
libktexteditor4 (>= 4:4.11) | 
libkworkspace4abi2  (= 4:4.11.11-1) | 
libplasma3  (>= 4:4.11) | 
libplasmagenericshell4  (= 4:4.11.11-1) | 
libqt4-dbus(>= 4:4.6.1) | 
libqt4-declarative (>= 4:4.7.0~rc1) | 
libqt4-xml (>= 4:4.5.3) | 
libqtcore4   (>= 4:4.7.0~beta1) | 
libqtgui4  (>= 4:4.8.0) | 
libsolid4   (>= 4:4.11) | 
libstdc++6   (>= 4.1.1) | 
libtaskmanager4abi4 (= 4:4.11.11-1) | 
libx11-6| 
libxext6| 


Recommends (Version) | Installed
-+-===
kde-workspace| 


Package's Suggests field is empty.



--- End Message ---
--- Begin Message ---
The bug showed in the initial rc tarball of kservice 5.15 and it was fixed in 
the final tarball:

https://git.reviewboard.kde.org/r/125537/

kservice 5.15.0+1 contains the final tarball.

Ciao
-- 
Luigi--- End Message ---

Processed: NMU for Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred!

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #789619 [src:plplot] plplot: FTBFS: CMake Error at 
cmake/modules/pkg-config.cmake:97 (_pkg_check_modules_internal): 
_pkg_check_modules_internal Macro invoked with incorrect arguments
Added tag(s) pending.

-- 
789619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: kbuildsycoca-releated breakages are now fixed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 801702 5.15.0+-1
Bug #801702 {Done: Luigi Toscano } 
[libkf5service-bin] [plasma-desktop] Recent Sid Upgrades Including Numerous 
KF5... Break Plasma-desktop
Marked as fixed in versions kservice/5.15.0+-1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
801702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801702: kbuildsycoca-releated breakages are now fixed

[Luigi Toscano]

fixed 801702 5.15.0+-1

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred! (debdiff so far)

[Axel Beckert]

Hi Ole,

Ole Streicher wrote:
> Am 14.10.2015 um 16:37 schrieb Axel Beckert:
> > Yes, but not inside a clean chroot (pbuilder here). But I'm working on
> > this.
>
> I used a clean chroot (pbuilder with cowbuild), and I didn't get any
> unresolved deps (after a "cowbuilder --update").

Hrm, interesting. On which architecture? amd64 here. Other (probably
less relevant) facts: Running pbuilder from Sid and the host is
running Sid, too under kernel 4.2.

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

Processed (with 1 error): kbuildsycoca-releated breakages are now fixed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassing 801702 libkf5service-bin 5.15.0-1
Unknown command or malformed arguments to command.
> notfound 801702 5.15.0+-1
Bug #801702 [plasma-desktop] [plasma-desktop] Recent Sid Upgrades Including 
Numerous KF5... Break Plasma-desktop
There is no source info for the package 'plasma-desktop' at version '5.15.0+-1' 
with architecture ''
Unable to make a source version for version '5.15.0+-1'
Ignoring request to alter found versions of bug #801702 to the same values 
previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
801702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801702: kbuildsycoca-releated breakages are now fixed

[Luigi Toscano]

reassing 801702 libkf5service-bin 5.15.0-1
notfound 801702 5.15.0+-1

Processed: affects 765157, user debian...@lists.debian.org, usertagging 765157

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 765157 + crystalspace-glshader-cg
Bug #765157 [src:crystalspace] crystalspace: FTBFS: make[2]: *** No rule to 
make target 'install_lib'.  Stop.
Added indication that 765157 affects crystalspace-glshader-cg
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 765157 piuparts
Usertags were: qa-ftbfs qa-ftbfs-20141012.
Usertags are now: qa-ftbfs piuparts qa-ftbfs-20141012.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
765157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801784: gitk de_DE.UTF-8: Error in startup script: bad menu entry index "Ansicht bearbeiten ..."

[Christoph Berg]

Package: gitk
Version: 1:2.6.1-1
Severity: grave

Hi,

running in a German locale, gitk is broken:

$ gitk
Error in startup script: bad menu entry index "Ansicht bearbeiten ..."
while executing
".bar.view entryconf [mca "Edit view..."] -state normal"
invoked from within
"if {$cmdline_files ne {} || $revtreeargs ne {} || $revtreeargscmd ne {}} {
# create a view for the files/dirs specified on the command line
se..."
(file "/usr/bin/gitk" line 12442)

The experimental version 1:2.6.1+next.20151009-1 has the same problem.

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

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

Versions of packages gitk depends on:
ii  git  1:2.6.1-1
ii  tk   8.6.0+8

gitk recommends no packages.

Versions of packages gitk suggests:
pn  git-doc  

-- no debconf information

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred! (debdiff so far)

[Ole Streicher]

amd64, host is "testing" (with the latest cowbuilder that was there
before it got removed), and the build is done on a sid chroot, no local
package repo (everything was fetched from a mirror). Kernel is 4.2 as well.

Best

Ole

Am 14.10.2015 um 16:42 schrieb Axel Beckert:
> Hi Ole,
>
> Ole Streicher wrote:
>> Am 14.10.2015 um 16:37 schrieb Axel Beckert:
>>> Yes, but not inside a clean chroot (pbuilder here). But I'm working on
>>> this.
>> I used a clean chroot (pbuilder with cowbuild), and I didn't get any
>> unresolved deps (after a "cowbuilder --update").
> Hrm, interesting. On which architecture? amd64 here. Other (probably
> less relevant) facts: Running pbuilder from Sid and the host is
> running Sid, too under kernel 4.2.
>
>   Regards, Axel

Bug#800348: marked as done (empathy crash at startup (segmentation violation))

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2015 15:19:50 +
with message-id 
and subject line Bug#800348: fixed in empathy 3.12.11-1
has caused the Debian Bug report #800348,
regarding empathy crash at startup (segmentation violation)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
800348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: empathy
Version: 3.12.10-1

I'm using Debian/sid and the crash is due to a recent upgrade on the
system. This very same version was working last Friday (3 days ago).

Here is the last strace log:

futex(0x1721268, FUTEX_WAKE_PRIVATE, 1) = 1
recvmsg(7, 0x7ffd9c6348d0, 0)   = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=7,
events=POLLIN}, {fd=17, events=POLLIN}, {fd=21, events=POLLIN}], 5, 0)
= 1 ([{fd=6, revents=POLLIN}])
read(6, "\1\0\0\0\0\0\0\0", 16) = 8
sendmsg(17, {msg_name(0)=NULL,
msg_iov(2)=[{"l\2\1\1\330\2\0\0A\0\0\0\37\0\0\0\6\1s\0\5\0\0\0:1.17\0\0\0"...,
48}, {"\6aa{sv}\0\314\2\0\0\250\0\0\0-\0\0\0org.freedesk"..., 728}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 776
write(2, "\n(empathy:16832): GLib-GIO-CRITI"..., 110
(empathy:16832): GLib-GIO-CRITICAL **: g_task_propagate_boolean:
assertion 'task->result_set == TRUE' failed
) = 110
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x8} ---
+++ killed by SIGSEGV +++
Segmentation fault

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://v2p.fr.eu.org
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B
--- End Message ---
--- Begin Message ---
Source: empathy
Source-Version: 3.12.11-1

We believe that the bug you reported is fixed in the latest version of
empathy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated empathy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Oct 2015 15:53:35 +0200
Source: empathy
Binary: empathy empathy-dbg empathy-common
Architecture: source all amd64
Version: 3.12.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Telepathy maintainers 

Changed-By: Laurent Bigonville 
Description:
 empathy- GNOME multi-protocol chat and call client
 empathy-common - GNOME multi-protocol chat and call client (common files)
 empathy-dbg - GNOME multi-protocol chat and call client (debug symbols)
Closes: 800348
Changes:
 empathy (3.12.11-1) unstable; urgency=medium
 .
   * New upstream release
 - Fix segfault at start (Closes: #800348)
Checksums-Sha1:
 c815d9806ee2e169502b9140749d057dad62f71a 2898 empathy_3.12.11-1.dsc
 64646b9929cefdb94152e9982f4cc6497bdad511 5149768 empathy_3.12.11.orig.tar.xz
 b78729d5ccc6219e212fa969637eba7e3c856aa2 20292 empathy_3.12.11-1.debian.tar.xz
 b7b1c90735a69d56bbb6006446c53eb756ee2149 3927500 
empathy-common_3.12.11-1_all.deb
 3f5ff312338c5a9490e8c8642e0644d28bd92808 2523904 
empathy-dbg_3.12.11-1_amd64.deb
 3b8ce3d41ef745ef03829cb8513a1909e72ac1e3 1563324 empathy_3.12.11-1_amd64.deb
Checksums-Sha256:
 764c8d24faa277e00709a7608d5f36910ab0285fbf24486906c705aae27e9ab9 2898 
empathy_3.12.11-1.dsc
 d1e4ff4e5f502b7f4ca2c6140462bad2a712b82f019aea4e0a2700e77545d487 5149768 
empathy_3.12.11.orig.tar.xz
 bb9b84c406cade92747dde45f200df80354cd9293cf8d92b4c47946d8223c5fe 20292 
empathy_3.12.11-1.debian.tar.xz
 5c8c2084d0f0b802c7aac856d92d25ef3f11ccd29c94b3184018a324ff6a1d53 3927500 
empathy-common_3.12.11-1_all.deb
 5cbebe2b22809d2a2bdfd616fd567465d044f7b8b8310bbca0b5f4e4c46866e7 2523904 
empathy-dbg_3.12.11-1_amd64.deb
 7e72143b91567a953905c794dcbb8fb07cc3c09927ba0448cafb86a7c6f8fdb3 1563324 
empathy_3.12.11-1_amd64.deb
Files:
 6528bb169bb1fcb4b7a12bdf019614fc 2898 gnome optional empathy_3.12.11-1.dsc
 08636d1f04b94282f384ca5ed8482eab 5149768 gnome optional 
empathy_3.12.11.orig.tar.xz
 

Processed: kbuildsycoca-releated breakages are now fixed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 801702 libkf5service-bin 5.15.0-1
Bug #801702 [plasma-desktop] [plasma-desktop] Recent Sid Upgrades Including 
Numerous KF5... Break Plasma-desktop
Bug reassigned from package 'plasma-desktop' to 'libkf5service-bin'.
No longer marked as found in versions plasma-desktop/4:5.4.2-1.
Ignoring request to alter fixed versions of bug #801702 to the same values 
previously set
Bug #801702 [libkf5service-bin] [plasma-desktop] Recent Sid Upgrades Including 
Numerous KF5... Break Plasma-desktop
Marked as found in versions kservice/5.15.0-1.
> notfound 801702 5.15.0+-1
Bug #801702 [libkf5service-bin] [plasma-desktop] Recent Sid Upgrades Including 
Numerous KF5... Break Plasma-desktop
Ignoring request to alter found versions of bug #801702 to the same values 
previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
801702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801702: kbuildsycoca-releated breakages are now fixed

[Luigi Toscano]

reassign 801702 libkf5service-bin 5.15.0-1
notfound 801702 5.15.0+-1

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred! (debdiff so far)

[Axel Beckert]

Hi,

Axel Beckert wrote:
> Ole Streicher wrote:
> > Am 14.10.2015 um 16:37 schrieb Axel Beckert:
> > > Yes, but not inside a clean chroot (pbuilder here). But I'm working on
> > > this.
> >
> > I used a clean chroot (pbuilder with cowbuild), and I didn't get any
> > unresolved deps (after a "cowbuilder --update").
> 
> Hrm, interesting.

I finally found the culprit: My build space was too small. I captured
this while the test suite failed inside a "pbuilder login":

→ df -h /var/cache/pbuilder/build
Filesystem   Type  Size  Used  Avail  Use%  Mounted on
/dev/mapper/vgcc-pb  ext4  6.8G  6.8G  0  100%  /var/cache/pbuilder

There was no "no space left on device" in any of the build logs nor in
the output of the manually run test suite. I just became aware of it
bceause of other commands I entered after the test suite has been run.

It seems the LV was full only exactly at the point when the test suite
was run and I can imagine that maybe some internal, compiled
dependencies for the test suite weren't properly built due to this,
but it was only noticed when the tests itself failed.

With 1 GB more on that LV, the pdebuild-based build worked fine. Will
do the NMU soon.

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

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred! (debdiff so far)

[Axel Beckert]

Hi Ole,

deb...@liska.ath.cx wrote:
> I just tried to compile plplot: All ocaml requirements for plplot
> work now; and the package builds fine with Axels debdiff.

Yes, but not inside a clean chroot (pbuilder here). But I'm working on
this.

> Axel, when you have time, would you upload a NMU then?

As soon as I find the last missing build-dep, yes. :-)

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

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred! (debdiff so far)

[Ole Streicher]

I used a clean chroot (pbuilder with cowbuild), and I didn't get any
unresolved deps (after a "cowbuilder --update").

Cheers

Ole

Am 14.10.2015 um 16:37 schrieb Axel Beckert:
> Hi Ole,
> 
> deb...@liska.ath.cx wrote:
>> I just tried to compile plplot: All ocaml requirements for plplot
>> work now; and the package builds fine with Axels debdiff.
> 
> Yes, but not inside a clean chroot (pbuilder here). But I'm working on
> this.
> 
>> Axel, when you have time, would you upload a NMU then?
> 
> As soon as I find the last missing build-dep, yes. :-)
> 
>   Regards, Axel
> 

Bug#801786: python3-nacl: must depend on python3-cffi

[Ximin Luo]

Package: python3-nacl
Version: 0.3.0-1+b1
Severity: grave
Tags: patch
Justification: renders package unusable

This package needs to depend on python3-cffi, otherwise ImportError is raised.

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

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

Versions of packages python3-nacl depends on:
ii  libc6  2.19-22
ii  libsodium131.0.3-1
ii  python33.4.3-6
pn  python3-cffi-backend-api-9729  
ii  python3-six1.9.0-5

python3-nacl recommends no packages.

Versions of packages python3-nacl suggests:
pn  python-nacl-doc  

-- no debconf information

Bug#799322: pocl: With 0.11 some test are failing

[Gert Wollny]

Hi, I had a look into the package, but I for me with 0.11 an llvm-3.6
two tests are failing - this has also already been reported upstream:

https://github.com/pocl/pocl/issues/181

Bug#801802: openvdb: FTBFS on 32-bit systems (size_t != unsigned long)

[Aaron M. Ucko]

Source: openvdb
Version: 2.3.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of openvdb for 32-bit architectures such as i386 have been
failing, with a number of errors of the form

  unittest/TestUtil.cc:147:9: error: no matching function for call to 
'assertEquals(long unsigned int, size_t, CppUnit::SourceLine, const char [1])'
   CPPUNIT_ASSERT_EQUAL(0UL, d.size());
   ^
  /usr/include/cppunit/TestAssert.h:109:6: note: candidate: template 
void CppUnit::assertEquals(const T&, const T&, CppUnit::SourceLine, const 
string&)
   void assertEquals( const T& expected,
^
  /usr/include/cppunit/TestAssert.h:109:6: note:   template argument 
deduction/substitution failed:

because size_t is formally unsigned int rather than unsigned long on
those platforms, even though the two types are equivalent in practice
there.  Meanwhile, 64-bit platforms do still need unsigned long, so my
recommendation would be to replace the UL suffixes with casts to size_t.

Could you please take a look?

Thanks!

Processed: fixed 798806 in 2.0.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 798806 2.0.1-1
Bug #798806 {Done: Carl Suster } [src:plowshare4] 
plowshare4: FTBFS: Incompatible with bash-completion 1:2.1-4.2
The source 'plowshare4' and version '2.0.1-1' do not appear to match any binary 
packages
Marked as fixed in versions plowshare4/2.0.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
798806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#798900: Source files

[Ole Streicher]

Am 13.10.2015 um 22:23 schrieb Walter Landry:
> Ole Streicher  wrote:
>> Walter Landry  writes:
>>> Ole Streicher  wrote:
 What are the general guidelines here? Somewhere in written form? The
 DFSG does not contain a hint here.
>>> The rule of thumb that I have seen applied is that 'source' is the
>>> preferred form of modification for the people making modifications.
>>> If a person really prefers editing 1400 character lines, then that is
>>> the source.  However, you can not just state that you prefer that.
>> I'd prefer just to ignore the line: it is a comment line that is not
>> needed for the functionality, so I see no reason to touch it at all. The
>> only reason to touch it for me would be to delete it.
> Sorry, I had not noticed that it was a comment.  I am confused as to
> why it is there.  Do you know why?  Could you get upstream to delete
> this seemingly useless line?  That would solve your immediate problem
> and clean up the code.

Upstream included the code on my request as an external source. I think
it would be not a good idea to ask them for the removal of the line,
since then their version would deviate from the original source.

I am not a specialist at all for Javascript, and all I try is just to
keep a Python package (with a very responsive upstream!) in a good
shape. Unfortunately, nobody with Javascript experience and also nobody
from the Lintian team (who wrote the heuristics to identify this file as
non-source, and also underlined that they still claim the file to be
non-source) took part in the discussion here so far. It looks a bit
weird for me that they create a Lintian "error" and seem not to have a
(even preliminary and discussable) "source" definition. So, I think that
the lintian tag in question is more a "wild guess" and should be marked
as such.

Best regards

Ole

Processed: Re: Bug#801585: python-debianbts: get_bugs interface is broken

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #801585 {Done: Bastian Venthur } [python-debianbts] 
python-debianbts: get_bugs interface is broken
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-debianbts/2.5.2.

-- 
801585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801585: python-debianbts: get_bugs interface is broken

[Ritesh Raj Sarraf]

Control: reopen -1

On Tue, 2015-10-13 at 14:47 +0200, Gaetano Guerriero wrote:
> 
> Hello, and thank you for the logs.
> 
> With --threads 1 I get no errors, can you confirm this ?
> 
> If it is a thread issue maybe we could lower severity.

THis bug was closed by the last upload. Was it intentionally closed ?
Because, the bug is still reproducible with more than 1 thread.

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


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

Bug#800810: openslide-python: Missing Build-Depends on python3-pil and libopenslide-dev

[Benjamin Gilbert]

A reasonable fix might be to just tell pybuild not to run tests.  
OpenSlide Python doesn't have a test suite, and probably won't any time 
soon.

Bug#798900: [Debian-med-packaging] Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

[Sascha Steinbiss]

Hi all,

I have prepared a package for datatables [1] building directly from the
GitHub sources, creating the JS and CSS files and associated images.
I have kept the JS policy [2] in mind, storing minified and non-minified
versions of the .js files in /usr/share/javascript/datatables, stripping
away the package descriptors and examples (also looked at some of the
other .js packages in the archive to see how they did it). Embedded
copies of JQuery etc. in the upstream source are removed via
Files-Excluded during repacking.

However, even this package triggers the lintian error we are discussing
here as the source input JS file from upstream contains the overly long
line [3] that lintian complains about, raising the missing-source error
as well. I suppose it is finally OK to write this off as a false
positive in this case?

I will also look for a sponsor for this package from the Debian Med team
to also get it into collab-maint.

Cheers,
Sascha

[1] https://anonscm.debian.org/cgit/users/sascha-guest/datatables.js.git/
[2] https://wiki.debian.org/Javascript/Policy
[3]
https://github.com/DataTables/DataTablesSrc/blob/master/js/DataTables.js#L25

On 12/10/2015 09:01, Paul Wise wrote:
> On Sun, 2015-10-11 at 13:38 +0100, Sascha Steinbiss wrote:
> 
>> It looks like JSHint is not a hard requirement but will just not be used if 
>> it’s
>> not there:
>> https://github.com/DataTables/DataTablesSrc/blob/master/build/make.sh#L58
>> Otherwise I wouldn't mind patching the build script to not use it.
> 
> Aha, great!
> 
>> In principle I agree here.
> 
> Good to hear :)
> 
>> Sure. Could you probably give me access to collab-maint then? As a DM I only 
>> have a
>> guest account on Alioth and someone has to approve me. I have sent a request 
>> via
>> the Alioth web interface quite some time ago but received no response.
> 
> I don't have admin access to collab-maint. 
> 
> As per the policy, you should have your sponsor or potential sponsor
> advocate you in order to get access. Probably someone from debian-med.
> 
> https://lists.debian.org/debian-devel-announce/2012/01/msg6.html
> 


-- 
 The Wellcome Trust Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE. 

Bug#798900: [Debian-med-packaging] Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

[Paul Wise]

On Wed, 2015-10-14 at 10:11 +0100, Sascha Steinbiss wrote:

> I have prepared a package for datatables [1] building directly from the
> GitHub sources, creating the JS and CSS files and associated images.
> I have kept the JS policy [2] in mind...

All great! Looks good to me. :)

> However, even this package triggers the lintian error we are discussing
> here as the source input JS file from upstream contains the overly long
> line [3] that lintian complains about, raising the missing-source error
> as well. I suppose it is finally OK to write this off as a false
> positive in this case?

Agreed. I'm still curious about the line length though.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Processed: cqrlog: prompting due to modified conffiles which were not modified by the user: /etc/apparmor.d/usr.sbin.mysqld

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.8.2-1.1
Bug #801755 [cqrlog] cqrlog: prompting due to modified conffiles which were not 
modified by the user: /etc/apparmor.d/usr.sbin.mysqld
Marked as found in versions cqrlog/1.8.2-1.1.

-- 
801755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 775385 in 1.16.2-1, found 771085 in 3.18.0-2, found 799258 in muon/4:5.4.2-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 775385 1.16.2-1
Bug #775385 [lightdm] lightdm: unowned symlink after purge (policy 6.8, 10.8): 
/etc/systemd/system/display-manager.service
Marked as found in versions lightdm/1.16.2-1.
> found 771085 3.18.0-2
Bug #771085 [gdm3] gdm3: unowned symlink after purge (policy 6.8, 10.8): 
/etc/systemd/system/display-manager.service
Marked as found in versions gdm3/3.18.0-2.
> found 799258 muon/4:5.4.2-1
Bug #799258 [apt-xapian-index] apt-xapian-index: unowned files after purge 
(policy 6.8, 10.8): /var/cache/apt-xapian-index/*
Marked as found in versions muon/4:5.4.2-1.
> found 770251 ruby-devise-lastseenable/0.0.6-1
Bug #770251 [ruby-jbuilder,ruby-responders] ruby-jbuilder,ruby-responders: 
error when trying to install together
Marked as found in versions ruby-devise-lastseenable/0.0.6-1.
> affects 801561 + libsunpinyin-dev python-sunpinyin
Bug #801561 [libsunpinyin3v5] libsunpinyin3v5: fails to upgrade from 'testing' 
- trying to overwrite /usr/lib/x86_64-linux-gnu/libsunpinyin.so.3.0
Added indication that 801561 affects libsunpinyin-dev and python-sunpinyin
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
770251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770251
771085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771085
775385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775385
799258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799258
801561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801755: cqrlog: prompting due to modified conffiles which were not modified by the user: /etc/apparmor.d/usr.sbin.mysqld

[Andreas Beckmann]

Package: cqrlog
Version: 1.9.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.8.2-1.1

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

While installing cqrlog/jessie (with --install-recommends):

  Setting up cqrlog (1.8.2-1.1) ...
  
  File /etc/apparmor.d/usr.sbin.mysqld was modified, now restarting apparmor ...
  
  /usr/share/cqrlog/cqrlog-apparmor-fix: line 21: /etc/init.d/apparmor: No such 
file or directory

While upgrading to stretch:

  Setting up mysql-server-5.6 (5.6.25-4) ...
  
  Configuration file '/etc/apparmor.d/usr.sbin.mysqld'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** usr.sbin.mysqld (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package mysql-server-5.6 (--configure):
   EOF on stdin at conffile prompt
  dpkg: dependency problems prevent configuration of mysql-server:
   mysql-server depends on mysql-server-5.6; however:
Package mysql-server-5.6 is not configured yet.
  
  dpkg: error processing package mysql-server (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.19-18+deb8u1) ...
  Errors were encountered while processing:
   mysql-server-5.6
   mysql-server


cheers,

Andreas


cqrlog_1.9.0-4.log.gz
Description: application/gzip

Bug#798900: Source files

[Ole Streicher]

On 14.10.2015 10:35, Bastien Roucaries wrote:

Le 14 octobre 2015 08:51:16 GMT+02:00, Ole Streicher  a 
écrit :

I am not a specialist at all for Javascript, and all I try is just
to keep a Python package (with a very responsive upstream!) in a
good shape. Unfortunately, nobody with Javascript experience and
also nobody from the Lintian team (who wrote the heuristics to
identify this file as non-source, and also underlined that they
still claim the file to be non-source) took part in the discussion
here so far. It looks a bit weird for me that they create a Lintian
"error" and seem not to have a (even preliminary and discussable)
"source" definition. So, I think that the lintian tag in question
is more a "wild guess" and should be marked as such.


Next Lintian version will count ; and ne more clever.

However line > 512 will be tagged due to regex récursion problèm and
it is totally insane.


What I meant here is that you should explain a bit what you consider a 
source and what not -- here for the discussion, and in the lintian tag 
documentation for the help of the users. Just experimenting some random 
heuristics without a proper definition (at least a working one) is not 
enough to qualify the tag for something other than "experimental", IMO.


Best regards

Ole

Bug#801739: plasma-workspace: plasmashell crashes after login through display manager

[Diederik de Haas]

On Wednesday 14 October 2015 15:38:34 Robi Malik wrote:
> > See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948
> 
> Confirmed: I can fix the problem by adding myself (and
> presumably all users that want to login) to the video group.

That's not exactly the solution/workaround that was mentioned there.
You should not add yourself, but the display manager user to the video group.

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

Bug#801739: plasma-workspace: plasmashell crashes after login through display manager

[Robi Malik]

On 14/10/2015 10:19 p.m., Diederik de Haas wrote:

On Wednesday 14 October 2015 15:38:34 Robi Malik wrote:

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948


Confirmed: I can fix the problem by adding myself (and
presumably all users that want to login) to the video group.


That's not exactly the solution/workaround that was mentioned there.
You should not add yourself, but the display manager user to the video group.


I understand that. But in my case the crash appears in
plasmashell after login from kdm. Apparently that is run
in the context of the user. Adding kdm to video does
not help, but adding the user does.

Bug#798806: marked as done (plowshare4: FTBFS: Incompatible with bash-completion 1:2.1-4.2)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2015 10:00:47 +
with message-id 
and subject line Bug#798806: fixed in plowshare 2.0.1-1
has caused the Debian Bug report #798806,
regarding plowshare4: FTBFS: Incompatible with bash-completion 1:2.1-4.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
798806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plowshare4
Version: 1.0.5-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

plowshare4 fails to build from source in unstable/amd64 as the paths
have changed in bash-completion 1:2.1-4.2:

  [..]

 debian/rules override_dh_bash-completion
  make[1]: Entering directory '/tmp/buildd/plowshare4-1.0.5'
  dh_bash-completion
  sed -i -e '/cut/ s,/usr/local,/usr,' \
debian/plowshare4/etc/bash_completion.d/plowshare
  sed: can't read debian/plowshare4/etc/bash_completion.d/plowshare: No
  such file or directory
  debian/rules:14: recipe for target 'override_dh_bash-completion'
  failed
  make[1]: *** [override_dh_bash-completion] Error 2
  make[1]: Leaving directory '/tmp/buildd/plowshare4-1.0.5'
  debian/rules:7: recipe for target 'binary' failed
  make: *** [binary] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/plowshare4_1.0.5-2.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Sep 12 07:38:10 GMT+12 2015
I: pbuilder-time-stamp: 1442086690
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), bash-completion
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20260 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on bash-completion; however:
  Package bash-completion is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  bash-completion{a} 
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 179 kB of archives. After unpacking 1252 kB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main bash-completion all 
1:2.1-4.2 [179 kB]
Fetched 179 kB in 0s (9892 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package bash-completion.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 

Bug#798900: Source files

[Bastien Roucaries]

Le 14 octobre 2015 08:51:16 GMT+02:00, Ole Streicher  a 
écrit :
>
>
>Am 13.10.2015 um 22:23 schrieb Walter Landry:
>> Ole Streicher  wrote:
>>> Walter Landry  writes:
 Ole Streicher  wrote:
> What are the general guidelines here? Somewhere in written form?
>The
> DFSG does not contain a hint here.
 The rule of thumb that I have seen applied is that 'source' is the
 preferred form of modification for the people making modifications.
 If a person really prefers editing 1400 character lines, then that
>is
 the source.  However, you can not just state that you prefer that.
>>> I'd prefer just to ignore the line: it is a comment line that is not
>>> needed for the functionality, so I see no reason to touch it at all.
>The
>>> only reason to touch it for me would be to delete it.
>> Sorry, I had not noticed that it was a comment.  I am confused as to
>> why it is there.  Do you know why?  Could you get upstream to delete
>> this seemingly useless line?  That would solve your immediate problem
>> and clean up the code.
>
>Upstream included the code on my request as an external source. I think
>it would be not a good idea to ask them for the removal of the line,
>since then their version would deviate from the original source.
>
>I am not a specialist at all for Javascript, and all I try is just to
>keep a Python package (with a very responsive upstream!) in a good
>shape. Unfortunately, nobody with Javascript experience and also nobody
>from the Lintian team (who wrote the heuristics to identify this file
>as
>non-source, and also underlined that they still claim the file to be
>non-source) took part in the discussion here so far. It looks a bit
>weird for me that they create a Lintian "error" and seem not to have a
>(even preliminary and discussable) "source" definition. So, I think
>that
>the lintian tag in question is more a "wild guess" and should be marked
>as such.

Next Lintian version will count ; and ne more clever.

However line > 512 will be tagged due to regex récursion problèm and  it is 
totally insane.


>
>Best regards
>
>Ole

-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Bug#801585: python-debianbts: get_bugs interface is broken

[Bastian Venthur]

control: severity -1 normal
control: retitle -1 python-debianbts is not thread safe

Sorry that was a mistake. I assumed the bug was about the
base64-decoding problem which was also in your stack traces.



Am 14.10.2015 um 08:21 schrieb Ritesh Raj Sarraf:
> THis bug was closed by the last upload. Was it intentionally closed ?
> Because, the bug is still reproducible with more than 1 thread.



-- 
Dr. Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org

Bug#801585: python-debianbts: get_bugs interface is broken

[Gaetano Guerriero]

Version 2.5.2 fixes something but not the threading issue. For that I hope a 
patch is coming. Il 14/10/15 08:21 Ritesh Raj Sarraf ha scritto:
Control: reopen -1

On Tue, 2015-10-13 at 14:47 +0200, Gaetano Guerriero wrote:
>
> Hello, and thank you for the logs.
>
> With --threads 1 I get no errors, can you confirm this ?
>
> If it is a thread issue maybe we could lower severity.

THis bug was closed by the last upload. Was it intentionally closed ?
Because, the bug is still reproducible with more than 1 thread.

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

Processed: Re: Bug#801585: python-debianbts: get_bugs interface is broken

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #801585 [python-debianbts] python-debianbts: get_bugs interface is broken
Severity set to 'normal' from 'grave'
> retitle -1 python-debianbts is not thread safe
Bug #801585 [python-debianbts] python-debianbts: get_bugs interface is broken
Changed Bug title to 'python-debianbts is not thread safe' from 
'python-debianbts: get_bugs interface is broken'

-- 
801585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801753: libreoffice: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Source: libreoffice
Version: 1:5.0.3~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> sid
  jessie -> sid

This bug seems to occur in (nearly) all binary packages built from
src:libreoffice.

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

1m19.1s ERROR: WARN: Inadequate results from running adequate!
  libreoffice-style-galaxy: missing-copyright-file 
/usr/share/doc/libreoffice-style-galaxy/copyright
  
1m19.1s ERROR: WARN: Running adequate resulted in inadequate tags found:  
missing-copyright-file 

  MISSING COPYRIGHT FILE: /usr/share/doc/libreoffice-style-galaxy/copyright
  # ls -lad /usr/share/doc/libreoffice-style-galaxy
  drwxr-xr-x 2 root root 40 Oct 13 10:11 /usr/share/doc/libreoffice-style-galaxy
  # ls -la /usr/share/doc/libreoffice-style-galaxy/
  total 0
  drwxr-xr-x   2 root root   40 Oct 13 10:11 .
  drwxr-xr-x 110 root root 2320 Oct 13 10:11 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libreoffice-style-galaxy_1:5.0.3~rc1-1.log.gz
Description: application/gzip

Bug#801757: Pinentry displays password while typing

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: pinentry-gtk2
Version: 0.9.6-2
Severity: grave

In newest version, pinentry is displaying password when typing. (It is
displaying the last letter but a observer can easily read the password.)

That is a big security issue that renders pinentry completely unusable in
any environment where one is not alone sitting in a dark cabin. When
working in a big office, that is insane!

Please revert that recent change back to the secure way of just
displaying dots.

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

Kernel: Linux 4.0.7 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to 
de_DE)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pinentry-gtk2 depends on:
ii  libassuan0 2.3.0-1
ii  libc6  2.19-22
ii  libglib2.0-0   2.46.0-2
ii  libgpg-error0  1.20-1
ii  libgtk2.0-02.24.28-1
ii  libncursesw5   6.0+20150810-1
ii  libsecret-1-0  0.18.3-1
ii  libtinfo5  6.0+20150810-1

pinentry-gtk2 recommends no packages.

Versions of packages pinentry-gtk2 suggests:
ii  pinentry-doc  0.9.6-2

- -- no debconf information

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCgAGBQJWHhzaAAoJEKZ8CrGAGfasJo0L/jH9Uf5x+qUagHhM0noEAu7r
eOZbe6oEGiPZEIdnQW6F+ndCYW35V57dm0H/X5aHIbBzmJ7e2vR6LCnfmMjQnbT3
FW4WiBU1t2D/8yucUD+PdlbqdKJoCjfW23SRvlL1d0/wa/Qb++rdkJyZqIYgWEjH
7OzY1uLlMJo0bTCYRwq2U+0h3Nj024oSktxpi84L8FZjy8kpfbEDClkT4fRUeDKq
ly/O7DsEPB3jUBGD8uUvoQZvoDj4eyGe5lTfb0gFLhuq4WrJVKN+r0p0Ysd0FVsE
xqeiicvZDVxXtIDYWG7XbL9FQ8hTOAdXKkuAFyOWF/PTv9fkQ+fviSSruxS6Urck
oVYOGKYnDp83KxFBUR5iCV9NqtUW6WBXHQS47irvF7eR/i+eJE1NR3zj1lT5VY/z
1BrAbXT5KbUG1Lb1UAl7+fHiPh9mvOv1Mr5jPvL8EtpI5Lhx298bZMKxErqu5yMA
nj7gekhyrVG6n9cDBR0Dn3lcaTAWdDo6s5p1hTFaAA==
=w367
-END PGP SIGNATURE-

Bug#773029: groonga-server-common: purging deletes conffiles owned by other packages: /etc/groonga/{groonga.conf, synonyms.tsv}

[Aníbal Monsalve Salazar]

On Wed, 2014-12-31 19:54:11 +0900, HAYASHI Kentaro wrote:
> Hi,
>
> Thank you for reporting & pointing out issues,  Andreas!
>
> I've just uploaded fixed version of Groonga.
> (There are some minor problems, so I've also fixed it)
>
> Here is the dsc file.
>  http://mentors.debian.net/debian/pool/main/g/groonga/groonga_4.0.6.1-3.dsc
>
> I'm not a member of DM nor DD, so please upload it to Debian archive.
>
> groonga (4.0.6.1-3) unstable; urgency=low
>
>   * Team upload.
>   * debian/groonga-server-common.postrm
> debian/groonga-server-gqtp.postrm
> debian/groonga-httpd.postrm
> debian/groonga-server-common.dirs
> debian/groonga-server-gqtp.dirs
> debian/groonga-server-http.dirs
> debian/libgroonga0.dirs
> debian/libgroonga0.postrm
> - Fix not to delete conffiles which are owned by other packages
>   (Closes: #773029)
>   * debian/groonga-httpd.init
> - Fix invalid conf path to detect proper default pid file.
> - Ensure to create directory to store pid file.
>   * debian/patches/hardening-vendor-nginx.patch
> - Apply hardening to groonga-httpd.

Hello HAYASHI Kentaro,

The URL above returns a 404 error.

Where can I find groonga_4.0.6.1-3.dsc and groonga_4.0.6.1-3.debian*
with all the changes above?

Thank you,

Aníbal

Bug#799584: UnicodeDecodeError in postinst

[Enrico Rossi]

Package: debtags
Version: 2.0.1
Tags: unreproducible

Hi,

I'm trying to reproduce the bug upgrading from 2.0+nmu1 and 1.12.3
without succeeding.
Can you eventually try:

debtags update

and see if it works?

Thanks for reporting.
E.

-- 
GPG Key: 4096R/F2133176 2010-10-19 Enrico Rossi 

Bug#800810: openslide-python: Missing Build-Depends on python3-pil and libopenslide-dev

[Benjamin Gilbert]

If you decide to add the build-deps instead, note that OpenSlide Python 
has only a runtime dependency on OpenSlide (libopenslide0) and doesn't 
need the headers (libopenslide-dev).

Bug#801046: git: "Out of memory, malloc failed" cloning certain repos

[PICCORO McKAY Lenz]

the 2.X does not have that problem, but i not used 2.x
due i not have jeese or sid, i use only squeeze and wheeze-live

seems that commits u refer have the point of the problem
as i explain, the tech exact info its in
commit c80d96ca0c3cf948c5062bf6591a46c625620b6d (tags/v1.9-rc0~97^2)
but i also read its also a workaround like i send prevoiusly
but more elegancy..

right now i coulnd analize that code at that commit but can u
take over this or notify something on debian mantainers?

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com


2015-10-12 15:32 GMT-04:30 Jonathan Nieder :
> tags 801046 + moreinfo
> quit
>
> Hi Lenz,
>
> PICCORO McKAY Lenz wrote:
>
>> Version: 1:1.7.10.4-1+wheezy1
>> Severity: grave
>
> I am able to use git.  Are you sure the package is actually unusable?
> For example, do commands like "git init" work?
>
> [...]
>> Current version of git for wheeze and squeeze are unusable, does not
>> work as normal user for make it work user must know the root
>> password and swicht, sudo does not work!
>
> Thanks for reporting.  I'm having some trouble understanding the exact
> problem.
>
> Does version 2.x have this problem as well?  There was a change
> upstream mentioning http.pushbuffer but I am not sure if it is
> related.
>
> commit c80d96ca0c3cf948c5062bf6591a46c625620b6d (tags/v1.9-rc0~97^2)
> Author: Brian M. Carlson 
> Date:   Thu Oct 31 02:36:51 2013 -0400
>
> remote-curl: fix large pushes with GSSAPI
>
> Due to an interaction between the way libcurl handles GSSAPI
> authentication over HTTP and the way git uses libcurl, large
> pushes (those over http.postBuffer bytes) would fail due to
> an authentication failure requiring a rewind of the curl
> buffer.  Such a rewind was not possible because the data did
> not fit into the entire buffer.
>
> Enable the use of the Expect: 100-continue header for large
> requests where the server offers GSSAPI authentication to
> avoid this issue, since the request would otherwise fail.
> This allows git to get the authentication data right before
> sending the pack contents.  Existing cases where pushes
> would succeed, including small requests using GSSAPI, still
> disable the use of 100 Continue, as it causes problems for
> some remote HTTP implementations (servers and proxies).
>
> Signed-off-by: Brian M. Carlson 
> Signed-off-by: Jeff King 
>
> Thanks and hope that helps,
> Jonathan

Bug#797942: sentinella: build-depends on obsolete kdebase-workspace-dev

[Carlos Olmedo Escobar]

Hi.

I'm going to release a new version soon addressing all those issues.

Thanks for the heads up.


2015-10-11 17:29 GMT+02:00, Eriberto Mota :
> tags 797942 upstream
> thanks
>
>
> Hi Felix,
>
> Initially, sorry for my long delay.
>
> I think that the removal from testing is the best way at this time
> because the upstream is active. I added the upstream in Cc.
>
>
> Hi Carlos,
>
> Can you send us a light about this issue[1] and your future plans?
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797942
>
> Thanks a lot in advance.
>
> Regards,
>
> Eriberto
>
>
>
> 2015-10-02 12:52 GMT-03:00 Felix Geyer :
>> Control: severity -1 serious
>>
>> Raising severity to serious as kde-workspace is finally going away.
>>
>> sentinella doesn't seem to build without it so maybe removal is the right
>> option?
>> Unless it's being ported of course.
>>
>> Cheers,
>> Felix
>

Bug#801815: plowshare-modules and plowshare: error when trying to install together

[Ralf Treinen]

Package: plowshare,plowshare-modules
Version: plowshare/2.0.1-1
Version: plowshare-modules/0~git20150404.gfd038c5-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-10-14
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package libgcrypt20:amd64.
(Reading database ... 10896 files and directories currently installed.)
Preparing to unpack .../libgcrypt20_1.6.3-2_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.6.3-2) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-3_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-3) ...
Selecting previously unselected package libssh2-1:amd64.
Preparing to unpack .../libssh2-1_1.5.0-2+b1_amd64.deb ...
Unpacking libssh2-1:amd64 (1.5.0-2+b1) ...
Selecting previously unselected package libdb5.3:amd64.
Preparing to unpack .../libdb5.3_5.3.28-11_amd64.deb ...
Unpacking libdb5.3:amd64 (5.3.28-11) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-7_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.0.0+dfsg-7) ...
Selecting previously unselected package libnettle6:amd64.
Preparing to unpack .../libnettle6_3.1.1-4_amd64.deb ...
Unpacking libnettle6:amd64 (3.1.1-4) ...
Selecting previously unselected package libhogweed4:amd64.
Preparing to unpack .../libhogweed4_3.1.1-4_amd64.deb ...
Unpacking libhogweed4:amd64 (3.1.1-4) ...
Preparing to unpack .../libp11-kit0_0.23.1-3_amd64.deb ...
Unpacking libp11-kit0:amd64 (0.23.1-3) over (0.18.5-3) ...
Selecting previously unselected package libtasn1-6:amd64.
Preparing to unpack .../libtasn1-6_4.7-2_amd64.deb ...
Unpacking libtasn1-6:amd64 (4.7-2) ...
Selecting previously unselected package libgnutls-deb0-28:amd64.
Preparing to unpack .../libgnutls-deb0-28_3.3.18-1_amd64.deb ...
Unpacking libgnutls-deb0-28:amd64 (3.3.18-1) ...
Selecting previously unselected package libkeyutils1:amd64.
Preparing to unpack .../libkeyutils1_1.5.9-8_amd64.deb ...
Unpacking libkeyutils1:amd64 (1.5.9-8) ...
Selecting previously unselected package libkrb5support0:amd64.
Preparing to unpack .../libkrb5support0_1.13.2+dfsg-2_amd64.deb ...
Unpacking libkrb5support0:amd64 (1.13.2+dfsg-2) ...
Selecting previously unselected package libk5crypto3:amd64.
Preparing to unpack .../libk5crypto3_1.13.2+dfsg-2_amd64.deb ...
Unpacking libk5crypto3:amd64 (1.13.2+dfsg-2) ...
Selecting previously unselected package libkrb5-3:amd64.
Preparing to unpack .../libkrb5-3_1.13.2+dfsg-2_amd64.deb ...
Unpacking libkrb5-3:amd64 (1.13.2+dfsg-2) ...
Selecting previously unselected package libgssapi-krb5-2:amd64.
Preparing to unpack .../libgssapi-krb5-2_1.13.2+dfsg-2_amd64.deb ...
Unpacking libgssapi-krb5-2:amd64 (1.13.2+dfsg-2) ...
Selecting previously unselected package libsasl2-modules-db:amd64.
Preparing to unpack .../libsasl2-modules-db_2.1.26.dfsg1-14_amd64.deb ...
Unpacking libsasl2-modules-db:amd64 (2.1.26.dfsg1-14) ...
Selecting previously unselected package libsasl2-2:amd64.
Preparing to unpack .../libsasl2-2_2.1.26.dfsg1-14_amd64.deb ...
Unpacking libsasl2-2:amd64 (2.1.26.dfsg1-14) ...
Selecting previously unselected package libldap-2.4-2:amd64.
Preparing to unpack .../libldap-2.4-2_2.4.42+dfsg-2_amd64.deb ...
Unpacking libldap-2.4-2:amd64 (2.4.42+dfsg-2) ...
Selecting previously unselected package libnghttp2-14:amd64.
Preparing to unpack .../libnghttp2-14_1.3.2-0.1_amd64.deb ...
Unpacking libnghttp2-14:amd64 (1.3.2-0.1) ...
Selecting previously unselected package librtmp1:amd64.
Preparing to unpack .../librtmp1_2.4+20150115.gita107cef-1+b2_amd64.deb ...
Unpacking librtmp1:amd64 (2.4+20150115.gita107cef-1+b2) ...
Selecting previously unselected package libcurl3-gnutls:amd64.
Preparing to unpack .../libcurl3-gnutls_7.45.0-1_amd64.deb ...
Unpacking libcurl3-gnutls:amd64 (7.45.0-1) ...
Selecting previously unselected package curl.
Preparing to unpack .../curl_7.45.0-1_amd64.deb ...
Unpacking curl (7.45.0-1) ...
Selecting previously unselected package librecode0:amd64.
Preparing to unpack .../librecode0_3.6-22_amd64.deb ...
Unpacking librecode0:amd64 (3.6-22) ...
Selecting previously unselected package recode.
Preparing to unpack .../recode_3.6-22_amd64.deb ...
Unpacking recode (3.6-22) ...
Selecting previously unselected package plowshare.
Preparing to unpack .../plowshare_2.0.1-1_all.deb ...
Unpacking plowshare (2.0.1-1) ...
Selecting previously unselected package plowshare-modules.
Preparing to unpack .../plowshare-modules_0~git20150404.gfd038c5-1_all.deb ...
Unpacking plowshare-modules (0~git20150404.gfd038c5-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/plowshare-modules_0~git20150404.gfd038c5-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/plowshare/modules/config', which is also in 
package plowshare 2.0.1-1
dpkg-deb: error: 

Processed: vmtk: switch to vtk6

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798166 798168 798174 798963 798169 798165 798167 798172 
798170 798171
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 801820

-- 
798164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798164
801820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801820: vmtk: switch to vtk6

[Andreas Beckmann]

Source: vmtk
Version: 1.0.1-3
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

As written in #798164, stretch will not ship with vtk5, so please switch
to vtk6.


Andreas

Bug#801733: python-biopython: build-depends unsatisfiable in stretch

[peter green]

On 14/10/15 11:33, Andreas Tille wrote:

To make your package releasable either bug 801112 needs to be fixed so that


I guess you mean s/801112/775254/ here, right?


Yeah, must have copy/pasted the wrong bug number.

Bug#801598: nvidia device permissions in jessie

[Luca Boccassi]

On Wed, 2015-10-14 at 12:29 +0200, Andreas Beckmann wrote:
> On 2015-10-14 00:25, Luca Boccassi wrote:
> > loading the module. As you suspected, it's udev. More precisely, it's
> > this systemd unit at boot:
> > 
> > /lib/systemd/system/systemd-udev-trigger.service
> > 
> > And even more precisely, this udevadm call by that unit:
> > 
> > udevadm trigger --type=devices --action=add
> 
> Thanks for verifying.
> 
> Can you check whether the behavior is the same if the system runs under
> sysv instead of systemd?

It is. The equivalent when booting with sysv is the /etc/init.d/udev
script. By commenting out the "udevadm trigger --action=add" call (line
206) the exact same happens as with systemd, the module is loaded and
the devices have permissions 660 root:video.

Kind regards,
Luca Boccassi

Bug#754803: healpy: out-of-date binaries

[Steven Chamberlain]

Hi,

On kfreebsd-amd64 healpy still FTBFS, but I suspect it just needs a
Dep-Wait on python3-matplotlib (>= 1.5.0~)?

https://buildd.debian.org/status/fetch.php?pkg=healpy=kfreebsd-amd64=1.8.1-1.1=1444690648
| __ ERROR collecting .pybuild/pythonX.Y_3.5/build/healpy/test/test_visufunc.py 
__
| healpy/test/test_visufunc.py:5: in 
| from ..visufunc import *
| healpy/visufunc.py:54: in 
| from . import projaxes as PA
| healpy/projaxes.py:24: in 
| from matplotlib import axes,ticker,colors,cm,lines,cbook,figure
| /usr/lib/python3/dist-packages/matplotlib/axes/__init__.py:4: in 
| from ._subplots import *
| /usr/lib/python3/dist-packages/matplotlib/axes/_subplots.py:7: in 
| from matplotlib.gridspec import GridSpec, SubplotSpec
| /usr/lib/python3/dist-packages/matplotlib/gridspec.py:26: in 
| import matplotlib.transforms as mtransforms
| /usr/lib/python3/dist-packages/matplotlib/transforms.py:39: in 
| from matplotlib._path import (affine_transform, 
count_bboxes_overlapping_bbox,
| E   ImportError: No module named 'matplotlib._path'

Newer matplotlib, in turn, is waiting on the glib2.0 FTBFS
(https://bugs.debian.org/712848) but that may be fixed in a few days.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Processed: Re: aptitude: segfault maybe casued by package dependency loop aptitudeDepCache::internal_mark_delete loop here

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #801430 [aptitude] aptitude: segfault when mark remove marked pkgs as 
purge, aptitudeDepCache::internal_mark_delete loop here
Added tag(s) pending.

-- 
801430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801430: aptitude: segfault maybe casued by package dependency loop aptitudeDepCache::internal_mark_delete loop here

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


2015-10-13 1:06 GMT+01:00 Nick Black :
> if you want me to pull something and test it, i ought be able to within a
> day or so.

OK, if you can confirm it would be great, thanks.

Other than that, I already commited it to git, because I am pretty
confident that this is the issue behind it, so marking as +pending.


Cheers.
-- 
Manuel A. Fernandez Montecelo 
From d6b67aba318ab83752f10adabf1b0490d2c88b39 Mon Sep 17 00:00:00 2001
From: "Manuel A. Fernandez Montecelo" 
Date: Wed, 14 Oct 2015 23:53:44 +0100
Subject: [PATCH 1/2] Fix for circular dependencies in internal_mark_delete()
 (Closes: #801430)

Under some circumstances, when following reverse dependencies of packages to
be deleted to see if they are automatically installed and unused (so they
can be pro-actively marked for deletion as well), the function calls itself
recursively.  In this case, it uses this version with an extra parameter to
detect when packages were already visited, to avoid infinite loops in the
case of circular dependencies (bug #801430).
---
 NEWS|  9 +
 src/generic/apt/aptcache.cc | 28 ++--
 src/generic/apt/aptcache.h  | 15 +++
 3 files changed, 50 insertions(+), 2 deletions(-)

diff --git a/NEWS b/NEWS
index c8f49b1..7187b05 100644
--- a/NEWS
+++ b/NEWS
@@ -19,6 +19,15 @@ Version 0.7.4 UNRELEASED
 errors, but didn't retrieve long descriptions anymore (it did for short
 ones).
 
+  * Fix for circular dependencies in internal_mark_delete() (Closes: #801430)
+
+Under some circumstances, when following reverse dependencies of packages to
+be deleted to see if they are automatically installed and unused (so they
+can be pro-actively marked for deletion as well), the function calls itself
+recursively.  In this case, it uses this version with an extra parameter to
+detect when packages were already visited, to avoid infinite loops in the
+case of circular dependencies (bug #801430).
+
 - User visible changes:
 
   * [cmdline] In versioned provides, include '=' symbol (Closes: #767393)
diff --git a/src/generic/apt/aptcache.cc b/src/generic/apt/aptcache.cc
index 838c1da..7cec034 100644
--- a/src/generic/apt/aptcache.cc
+++ b/src/generic/apt/aptcache.cc
@@ -1231,6 +1231,15 @@ void aptitudeDepCache::internal_mark_delete(const PkgIterator ,
 	bool Purge,
 	bool unused_delete)
 {
+  std::vector unused_already_visited;
+  internal_mark_delete(Pkg, Purge, unused_delete, unused_already_visited);
+}
+
+void aptitudeDepCache::internal_mark_delete(const PkgIterator ,
+	bool Purge,
+	bool unused_delete,
+	std::vector& unused_already_visited)
+{
   // honour ::Purge-Unused in the main entry point for removing packages, it
   // should catch cases of automatically installed and unused packages not
   // purged (#724034 and others)
@@ -1275,6 +1284,21 @@ void aptitudeDepCache::internal_mark_delete(const PkgIterator ,
   if (Pkg.CurrentVer().end())
 return;
 
+  // to avoid endless recursion/crashes, check if this package has already been
+  // visited for this purpose (the container has to be empty at the start of
+  // each run)
+  auto it = std::find(unused_already_visited.begin(), unused_already_visited.end(), Pkg->ID);
+  if (it == std::end(unused_already_visited))
+{
+  // not previously visited, register
+  unused_already_visited.push_back(Pkg->ID);
+}
+  else
+{
+  // already visited
+  return;
+}
+
   // from now and for the remaining of this function, these are "unused
   // deletes", so set variable accordingly
   unused_delete = true;
@@ -1326,7 +1350,7 @@ void aptitudeDepCache::internal_mark_delete(const PkgIterator ,
 
 	  // if we reach here, can delete the real package providing the
 	  // dependency
-	  internal_mark_delete(dep_prv.OwnerPkg(), Purge, unused_delete);
+	  internal_mark_delete(dep_prv.OwnerPkg(), Purge, unused_delete, unused_already_visited);
 	}
 
 	  // it was a virtual package -- so stop processing the considered
@@ -1356,7 +1380,7 @@ void aptitudeDepCache::internal_mark_delete(const PkgIterator ,
 	continue;
 	  }
 
-	  internal_mark_delete(dep_pkg, Purge, unused_delete);
+	  internal_mark_delete(dep_pkg, Purge, unused_delete, unused_already_visited);
 	}
 }
 }
diff --git a/src/generic/apt/aptcache.h b/src/generic/apt/aptcache.h
index 51a0990..a7d716c 100644
--- a/src/generic/apt/aptcache.h
+++ b/src/generic/apt/aptcache.h
@@ -330,7 +330,22 @@ private:
* package's auto flag is set properly.
*/
   void internal_mark_install(const PkgIterator , bool AutoInst, bool ReInstall);
+
+  /** Internally marking packages for deletion -- main entry point
+   */
   void internal_mark_delete(const PkgIterator , bool Purge, bool unused_delete);
+  /** Internally marking packages for deletion -- recursive
+   *
+   

Bug#801733: python-biopython: build-depends unsatisfiable in stretch

[Andreas Tille]

On Wed, Oct 14, 2015 at 12:27:31AM +0100, peter green wrote:
> Package: python-biopython
> Severity: serious
> Tags: stretch
> 
> The release policy says that "packages must be buildable within the same
> release". Your package build-depends on python3-mysqldb which is not in
> testing.
> 
> To make your package releasable either bug 801112 needs to be fixed so that

I guess you mean s/801112/775254/ here, right?

> python3-mysqldb can migrate to testing or the build-dependency of your
> package on python3-mysqldb needs to be eliminated.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#801598: nvidia device permissions in jessie

[Andreas Beckmann]

On 2015-10-14 00:25, Luca Boccassi wrote:
> loading the module. As you suspected, it's udev. More precisely, it's
> this systemd unit at boot:
> 
> /lib/systemd/system/systemd-udev-trigger.service
> 
> And even more precisely, this udevadm call by that unit:
> 
> udevadm trigger --type=devices --action=add

Thanks for verifying.

Can you check whether the behavior is the same if the system runs under
sysv instead of systemd?


Andreas

Bug#800617: Fails to provide secrets

[Andreas Kurth]

Package: gnome-keyring
Version: 3.18.0-4
Followup-For: Bug #800617

Hi,

for me this bug is not fixed.

I use gnome-keyring to store SVN credentials. When calling "svn up" or
other server related commands, svn waits endlessly without returning.

This behaviour was introduced with 3.18.0-1 and can be "fixed" by
downgrading to 3.16.0-4.

Please advise how I can help debugging the issue.


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

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

Versions of packages gnome-keyring depends on:
ii  dbus-x11 1.10.0-3
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gcr  3.18.0-1
ii  libc62.19-22
ii  libcap-ng0   0.7.7-1
ii  libcap2-bin  1:2.24-12
ii  libgck-1-0   3.18.0-1
ii  libgcr-base-3-1  3.18.0-1
ii  libgcrypt20  1.6.3-2
ii  libglib2.0-0 2.46.0-2
ii  p11-kit  0.23.1-3
ii  pinentry-gnome3  0.9.6-2

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.18.0-4

gnome-keyring suggests no packages.

-- no debconf information

Bug#801598: nvidia device permissions in jessie

[Luca Boccassi]

On 14 October 2015 at 11:29, Andreas Beckmann  wrote:
> On 2015-10-14 00:25, Luca Boccassi wrote:
>> loading the module. As you suspected, it's udev. More precisely, it's
>> this systemd unit at boot:
>>
>> /lib/systemd/system/systemd-udev-trigger.service
>>
>> And even more precisely, this udevadm call by that unit:
>>
>> udevadm trigger --type=devices --action=add
>
> Thanks for verifying.
>
> Can you check whether the behavior is the same if the system runs under
> sysv instead of systemd?

Ok, I'll give it a shot later tonight.

Kind regards,
Luca Boccassi

Bug#789402: marked as done (FTBFS with OCaml 4.02.2: Some fatal warnings were triggered)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2015 11:19:52 + (UTC)
with message-id <1487596688.298673.1444821592797.javamail.ya...@mail.yahoo.com>
and subject line closing, llvm-toolchain-3.5 uploaded in unstable.
has caused the Debian Bug report #789402,
regarding FTBFS with OCaml 4.02.2: Some fatal warnings were triggered
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
789402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-3.5
Version: 3.5.2-1
Severity: important
Tags: patch

Dear Maintainer,

Your package FTBFS with OCaml 4.02.2:
> [...]
> Command Output (stderr):
> --
> File 
> "/tmp/pbuilder/llvm-toolchain-3.5-3.5.2/build-llvm/test/Bindings/Ocaml/Output/bitwriter.ml.tmp.builddir/bitwriter.ml",
>  line 20, characters 12-25:
> Warning 3: deprecated: String.create
> Use Bytes.create instead.
> File 
> "/tmp/pbuilder/llvm-toolchain-3.5-3.5.2/build-llvm/test/Bindings/Ocaml/Output/bitwriter.ml.tmp.builddir/bitwriter.ml",
>  line 1:
> Error: Some fatal warnings were triggered (1 occurrences)
> [...]

I suggest to not use the -warn-error option. With the attached patch,
the package builds. It should as well build with the version of OCaml
currently in unstable, so I suggest you to upload it as soon as
possible, and not wait for the transition to start.

Cheers,

-- 
Stéphane

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru llvm-toolchain-3.5-3.5.2/debian/changelog llvm-toolchain-3.5-3.5.2/debian/changelog
--- llvm-toolchain-3.5-3.5.2/debian/changelog	2015-04-27 19:00:56.0 +0200
+++ llvm-toolchain-3.5-3.5.2/debian/changelog	2015-06-20 10:43:54.0 +0200
@@ -1,3 +1,10 @@
+llvm-toolchain-3.5 (1:3.5.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix compilation with OCaml 4.02
+
+ -- Stéphane Glondu   Sat, 20 Jun 2015 08:43:54 +
+
 llvm-toolchain-3.5 (1:3.5.2-1) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru llvm-toolchain-3.5-3.5.2/debian/patches/fix-ftbfs-ocaml-4.02 llvm-toolchain-3.5-3.5.2/debian/patches/fix-ftbfs-ocaml-4.02
--- llvm-toolchain-3.5-3.5.2/debian/patches/fix-ftbfs-ocaml-4.02	1970-01-01 01:00:00.0 +0100
+++ llvm-toolchain-3.5-3.5.2/debian/patches/fix-ftbfs-ocaml-4.02	2015-06-20 10:45:02.0 +0200
@@ -0,0 +1,146 @@
+Description: Fix compilation with OCaml 4.02
+Author: Stéphane Glondu 
+
+--- llvm-toolchain-3.5-3.5.2.orig/test/Bindings/Ocaml/analysis.ml
 llvm-toolchain-3.5-3.5.2/test/Bindings/Ocaml/analysis.ml
+@@ -1,7 +1,7 @@
+ (* RUN: rm -rf %t.builddir
+  * RUN: mkdir -p %t.builddir
+  * RUN: cp %s %t.builddir
+- * RUN: %ocamlopt -warn-error A llvm.cmxa llvm_analysis.cmxa %t.builddir/analysis.ml -o %t
++ * RUN: %ocamlopt  llvm.cmxa llvm_analysis.cmxa %t.builddir/analysis.ml -o %t
+  * RUN: %t
+  * XFAIL: vg_leak
+  *)
+--- llvm-toolchain-3.5-3.5.2.orig/test/Bindings/Ocaml/bitreader.ml
 llvm-toolchain-3.5-3.5.2/test/Bindings/Ocaml/bitreader.ml
+@@ -1,7 +1,7 @@
+ (* RUN: rm -rf %t.builddir
+  * RUN: mkdir -p %t.builddir
+  * RUN: cp %s %t.builddir
+- * RUN: %ocamlopt -warn-error A llvm.cmxa llvm_bitreader.cmxa llvm_bitwriter.cmxa %t.builddir/bitreader.ml -o %t
++ * RUN: %ocamlopt  llvm.cmxa llvm_bitreader.cmxa llvm_bitwriter.cmxa %t.builddir/bitreader.ml -o %t
+  * RUN: %t %t.bc
+  * RUN: llvm-dis < %t.bc
+  * XFAIL: vg_leak
+--- llvm-toolchain-3.5-3.5.2.orig/test/Bindings/Ocaml/bitwriter.ml
 llvm-toolchain-3.5-3.5.2/test/Bindings/Ocaml/bitwriter.ml
+@@ -1,7 +1,7 @@
+ (* RUN: rm -rf %t.builddir
+  * RUN: mkdir -p %t.builddir
+  * RUN: cp %s %t.builddir
+- * RUN: %ocamlopt -warn-error A unix.cmxa llvm.cmxa llvm_bitwriter.cmxa %t.builddir/bitwriter.ml -o %t
++ * RUN: %ocamlopt  unix.cmxa llvm.cmxa llvm_bitwriter.cmxa %t.builddir/bitwriter.ml -o %t
+  * RUN: %t %t.bc
+  * RUN: llvm-dis < %t.bc
+  * XFAIL: vg_leak
+--- llvm-toolchain-3.5-3.5.2.orig/test/Bindings/Ocaml/executionengine.ml
 llvm-toolchain-3.5-3.5.2/test/Bindings/Ocaml/executionengine.ml
+@@ -1,7 +1,7 @@
+ (* RUN: rm -rf %t.builddir
+  * RUN: mkdir -p %t.builddir
+  * RUN: cp %s %t.builddir
+- * RUN: %ocamlopt -warn-error A llvm.cmxa llvm_target.cmxa llvm_executionengine.cmxa 

Bug#801833: desmume: Desmume crashes when starting

[Alejandro Carrazzoni]

Package: desmume
Version: 0.9.10-2+b2
Severity: grave
Justification: renders package unusable

When I run desmume, it crashes right after starting, with the following error:

(desmume:6776): Gdk-CRITICAL **: IA__gdk_cairo_create: assertion
'GDK_IS_DRAWABLE (drawable)' failed
Violación de segmento



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

Versions of packages desmume depends on:
ii  libasound21.0.29-1
ii  libc6 2.19-22
ii  libcairo2 1.14.2-2
ii  libgcc1   1:5.2.1-16
ii  libgdk-pixbuf2.0-02.32.0-1
ii  libgl1-mesa-glx [libgl1]  10.6.8-1
ii  libglade2-0   1:2.6.4-2
ii  libglib2.0-0  2.46.0-2
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgtk2.0-0   2.24.28-1
ii  libgtkglext1  1.2.0-3.2
ii  libosmesa610.6.8-1
ii  libpango-1.0-01.38.0-3
ii  libsdl1.2debian   1.2.15-11
ii  libsoundtouch11.9.2-2
ii  libstdc++65.2.1-16
ii  libtinyxml2.6.2v5 2.6.2-3
ii  zlib1g1:1.2.8.dfsg-2+b1

desmume recommends no packages.

desmume suggests no packages.

-- no debconf information

Bug#799562: marked as done (kdbus-dkms: ignores KVER and always tries to build a module for the running kernel)

[Debian Bug Tracking System]

Your message dated Thu, 15 Oct 2015 01:18:44 +
with message-id 
and subject line Bug#799562: fixed in kdbus-dkms 0.20150901t074837.245fe93-1
has caused the Debian Bug report #799562,
regarding kdbus-dkms: ignores KVER and always tries to build a module for the 
running kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
799562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdbus-dkms
Version: 0.20150824t110616.0c05fbd-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

kdbus-dkms fails to install since it cannot build a module
for the current sid kernel. This is a test on a stretch host (3.16.0-4)
in a sid chroot with linux-headers-amd64 (4.1.0-2) installed:


[...]
Selecting previously unselected package kdbus-dkms.
Preparing to unpack .../kdbus-dkms_0.20150824t110616.0c05fbd-1_all.deb ...
Unpacking kdbus-dkms (0.20150824t110616.0c05fbd-1) ...
Setting up libkmod2:amd64 (21-1) ...
Setting up kmod (21-1) ...
Setting up dkms (2.2.0.3-2) ...
Setting up kdbus-dkms (0.20150824t110616.0c05fbd-1) ...
Loading new kdbus-20150824t110616.0c05fbd DKMS files...
First Installation: checking all kernels...
dpkg: warning: version '*-*' has bad syntax: version number does not start with 
digit
It is likely that 3.16.0-4-amd64 belongs to a chroot's host
Building initial module for 4.1.0-2-amd64
Error! Bad return status for module build on kernel: 4.1.0-2-amd64 (x86_64)
Consult /var/lib/dkms/kdbus/20150824t110616.0c05fbd/build/make.log for more 
information.
Processing triggers for libc-bin (2.19-20) ...


Let's do it manually:


# dkms build -m kdbus/20150824t110616.0c05fbd -k 4.1.0-2-amd64

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area
make KERNELRELEASE=4.1.0-2-amd64 KVER=4.1.0-2-amd64(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.1.0-2-amd64 (x86_64)
Consult /var/lib/dkms/kdbus/20150824t110616.0c05fbd/build/make.log for more 
information.


and from make.log:


DKMS make.log for kdbus-20150824t110616.0c05fbd for kernel 4.1.0-2-amd64 
(x86_64)
Sun Sep 20 11:46:25 UTC 2015
make -C /lib/modules/3.16.0-4-amd64/build 
M=/var/lib/dkms/kdbus/20150824t110616.0c05fbd/build 
EXTRA_CFLAGS="-I/var/lib/dkms/kdbus/20150824t110616.0c05fbd/build/include 
-DKDBUS_SUPER_MAGIC=0x4442757" \

HOST_EXTRACFLAGS="-I/var/lib/dkms/kdbus/20150824t110616.0c05fbd/build/usr/include"
 KDBUS_EXT= \
CONFIG_KDBUS=m CONFIG_SAMPLES=y CONFIG_SAMPLE_KDBUS=y
make[1]: *** /lib/modules/3.16.0-4-amd64/build: No such file or directory.  
Stop.
Makefile:50: recipe for target 'module' failed
make: *** [module] Error 2


Andreas
--- End Message ---
--- Begin Message ---
Source: kdbus-dkms
Source-Version: 0.20150901t074837.245fe93-1

We believe that the bug you reported is fixed in the latest version of
kdbus-dkms, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 799...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated kdbus-dkms package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Oct 2015 03:12:42 +0200
Source: kdbus-dkms
Binary: kdbus-dkms
Architecture: source
Version: 0.20150901t074837.245fe93-1
Distribution: experimental
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 kdbus-dkms - DKMS source for the kdbus module
Closes: 799562
Changes:
 kdbus-dkms (0.20150901t074837.245fe93-1) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * debian/copyright: Drop obsolete copyright for Junio C Hamano, not present
 any more in current upstream version.
 .
   [ Michael Biebl ]
   * Pull from the upstream v4.2 branch for now as it contains quite a few
 important fixes.
   * Pass the correct kernel version to the build system. This makes it
 possible to build the module for a kernel other then the currently running
 one. (Closes: 

Bug#801768: blktap-dkms: module FTBFS for Linux 4.2: error: too many arguments to function 'mempool_resize'

[Andreas Beckmann]

Package: blktap-dkms
Version: 2.0.93-0.3
Severity: serious
Tags: sid stretch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to build a
kernel module for the current sid kernel:

Setting up blktap-dkms (2.0.93-0.3) ...
Loading new blktap-2.0.93 DKMS files...
First Installation: checking all kernels...
dpkg: warning: version '*-*' has bad syntax: version number does not start with 
digit
It is likely that 3.16.0-4-amd64 belongs to a chroot's host
Building initial module for 4.2.0-1-amd64
Error! Bad return status for module build on kernel: 4.2.0-1-amd64 (x86_64)
Consult /var/lib/dkms/blktap/2.0.93/build/make.log for more information.


DKMS make.log for blktap-2.0.93 for kernel 4.2.0-1-amd64 (x86_64)
Wed Oct 14 11:51:33 UTC 2015
make: Entering directory '/usr/src/linux-headers-4.2.0-1-amd64'
Makefile:10: *** mixed implicit and normal rules: deprecated syntax
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/control.o
In file included from /var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:66:0,
 from /var/lib/dkms/blktap/2.0.93/build/blktap.h:33,
 from /var/lib/dkms/blktap/2.0.93/build/control.c:30:
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:119:24: warning: variably 
modified 'pending' at file scope
sizeof(((struct blktap_sring *)0)->ring[0])))
^
/usr/src/linux-headers-4.2.0-1-common/include/xen/interface/io/ring.h:15:59: 
note: in definition of macro '__RD2'
 #define __RD2(_x)  (((_x) & 0x0002) ? 0x2 : ((_x) & 0x1))
   ^
/usr/src/linux-headers-4.2.0-1-common/include/xen/interface/io/ring.h:17:66: 
note: in expansion of macro '__RD4'
 #define __RD8(_x)  (((_x) & 0x00f0) ? __RD4((_x)>>4)<<4: __RD4(_x))
  ^
/usr/src/linux-headers-4.2.0-1-common/include/xen/interface/io/ring.h:18:66: 
note: in expansion of macro '__RD8'
 #define __RD16(_x) (((_x) & 0xff00) ? __RD8((_x)>>8)<<8: __RD8(_x))
  ^
/usr/src/linux-headers-4.2.0-1-common/include/xen/interface/io/ring.h:19:66: 
note: in expansion of macro '__RD16'
 #define __RD32(_x) (((_x) & 0x) ? __RD16((_x)>>16)<<16 : __RD16(_x))
  ^
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:117:8: note: in expansion of 
macro '__RD32'
  ((int)__RD32((BLKTAP_PAGE_SIZE -\
^
/var/lib/dkms/blktap/2.0.93/build/blktap.h:77:41: note: in expansion of macro 
'BLKTAP_RING_SIZE'
  struct blktap_request *pending[BLKTAP_RING_SIZE];
 ^
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/ring.o
In file included from /var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:66:0,
 from /var/lib/dkms/blktap/2.0.93/build/blktap.h:33,
 from /var/lib/dkms/blktap/2.0.93/build/ring.c:38:
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:119:24: warning: variably 
modified 'pending' at file scope
sizeof(((struct blktap_sring *)0)->ring[0])))
^
/usr/src/linux-headers-4.2.0-1-common/include/xen/interface/io/ring.h:15:59: 
note: in definition of macro '__RD2'
 #define __RD2(_x)  (((_x) & 0x0002) ? 0x2 : ((_x) & 0x1))
   ^
/usr/src/linux-headers-4.2.0-1-common/include/xen/interface/io/ring.h:17:66: 
note: in expansion of macro '__RD4'
 #define __RD8(_x)  (((_x) & 0x00f0) ? __RD4((_x)>>4)<<4: __RD4(_x))
  ^
/usr/src/linux-headers-4.2.0-1-common/include/xen/interface/io/ring.h:18:66: 
note: in expansion of macro '__RD8'
 #define __RD16(_x) (((_x) & 0xff00) ? __RD8((_x)>>8)<<8: __RD8(_x))
  ^
/usr/src/linux-headers-4.2.0-1-common/include/xen/interface/io/ring.h:19:66: 
note: in expansion of macro '__RD16'
 #define __RD32(_x) (((_x) & 0x) ? __RD16((_x)>>16)<<16 : __RD16(_x))
  ^
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:117:8: note: in expansion of 
macro '__RD32'
  ((int)__RD32((BLKTAP_PAGE_SIZE -\
^
/var/lib/dkms/blktap/2.0.93/build/blktap.h:77:41: note: in expansion of macro 
'BLKTAP_RING_SIZE'
  struct blktap_request *pending[BLKTAP_RING_SIZE];
 ^
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/device.o
In file included from /var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:66:0,
 from /var/lib/dkms/blktap/2.0.93/build/blktap.h:33,
 from /var/lib/dkms/blktap/2.0.93/build/device.c:31:
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:119:24: warning: variably 
modified 'pending' at file scope
sizeof(((struct 

Bug#798079: utopia-documents: diff for NMU version 2.4.4-2.1

[Sebastian Ramacher]

On 2015-10-13 16:42:13, James Marsh wrote:
> On 12 October 2015 at 20:16, Sebastian Ramacher 
> wrote:
> 
> > Dear maintainer,
> >
> > I've prepared an NMU for utopia-documents (versioned as 2.4.4-2.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it longer.
> 
> 
> Dear Sebastian and Steve,
> 
> That's great — thanks Sebastian for preparing the NMU and Steve for the
> patches to make Qt and the newer boost play nicely.
> 
> We will have a new major release of utopia-documents within the next few
> weeks which will have some reasonably big changes including moving over to
> Qt5, though there is no reason to delay your NMU package in the meantime.
> 
> One extra change we could include in your NMU is to disable the built in
> update checker which checks for new releases on startup. If a new upstream
> release is available on Linux it will pop up a message that says: "An
> update of this software is available. Install using your system package
> manager."

I have included your patch in the NMU and uploaded without delay. New NMU patch
attached.

> I'll disable this check by default in future Debian releases but is this
> going to be enough of an annoyance/source of confusion for these users to
> warrant an update for them? A patch that disables the check is attached if
> you wish to include it.

An update for jessie? I'd think so. But that's something you need to discuss
with the release team: reportbug release.debian.org and select jessie-pu and
include a source debdiff with the proposed changes. See dev-ref 5.5.1 for some
pointers
(https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable).

Cheers
-- 
Sebastian Ramacher
diff -Nru utopia-documents-2.4.4/debian/changelog 
utopia-documents-2.4.4/debian/changelog
--- utopia-documents-2.4.4/debian/changelog 2014-10-24 14:39:17.0 
+0200
+++ utopia-documents-2.4.4/debian/changelog 2015-10-14 13:49:40.0 
+0200
@@ -1,3 +1,18 @@
+utopia-documents (2.4.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Steve Langasek ]
+  * debian/patches/boost1.58-qt4moc-compatibility.patch: compatibility
+with boost 1.58.
+  * Add missing build-dependency on libqt4-opengl-dev. (Closes: #798079)
+
+  [ James Marsh ]
+  * debian/patches/remove-utopia-update-check.diff: Disable check for new
+upstream releases on startup.
+
+ -- Sebastian Ramacher   Wed, 14 Oct 2015 13:49:39 +0200
+
 utopia-documents (2.4.4-2) unstable; urgency=medium
 
   * Updated copyright file to include additional licenses.
diff -Nru utopia-documents-2.4.4/debian/control 
utopia-documents-2.4.4/debian/control
--- utopia-documents-2.4.4/debian/control   2014-10-23 12:34:54.0 
+0200
+++ utopia-documents-2.4.4/debian/control   2015-10-12 21:08:51.0 
+0200
@@ -18,6 +18,7 @@
libqglviewer-dev | libqglviewer-qt4-dev,
libqjson-dev,
libqt4-dev,
+   libqt4-opengl-dev,
libqtwebkit-dev | libqt4-dev (<< 4:4.7),
libraptor-dev,
libssl-dev,
diff -Nru 
utopia-documents-2.4.4/debian/patches/boost1.58-qt4moc-compatibility.patch 
utopia-documents-2.4.4/debian/patches/boost1.58-qt4moc-compatibility.patch
--- utopia-documents-2.4.4/debian/patches/boost1.58-qt4moc-compatibility.patch  
1970-01-01 01:00:00.0 +0100
+++ utopia-documents-2.4.4/debian/patches/boost1.58-qt4moc-compatibility.patch  
2015-10-12 20:44:31.0 +0200
@@ -0,0 +1,527 @@
+Author: Steve Langasek 
+Description: compatibility with boost 1.58
+ Newer versions of boost break compatibility with previous workarounds for
+ qt4 moc's inability to parse boost headers.  Add a new workaround here.
+Index: utopia-documents-2.4.4/libutopia2/utopia2/extension.h
+===
+--- utopia-documents-2.4.4.orig/libutopia2/utopia2/extension.h
 utopia-documents-2.4.4/libutopia2/utopia2/extension.h
+@@ -34,7 +34,9 @@
+ 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ #include 
+ #include 
+ #include 
+Index: utopia-documents-2.4.4/libpapyro/papyro/annotationprocessoraction.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/annotationprocessoraction.h
 utopia-documents-2.4.4/libpapyro/papyro/annotationprocessoraction.h
+@@ -35,7 +35,9 @@
+ #include 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ 
+ #include 
+ #include 
+Index: utopia-documents-2.4.4/libpapyro/papyro/annotatorrunnable.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/annotatorrunnable.h
 utopia-documents-2.4.4/libpapyro/papyro/annotatorrunnable.h
+@@ -34,7 +34,9 @@
+ 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ 
+ #include 
+ #include 
+Index: 

Processed: Re: Bug#801770: devscripts: rmadison does not run properly but instead has a mishmash of rubbish

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo unreproducible
Bug #801770 [devscripts] devscripts: rmadison does not run properly but instead 
has a mishmash of rubbish
Added tag(s) unreproducible and moreinfo.
> severity -1 important
Bug #801770 [devscripts] devscripts: rmadison does not run properly but instead 
has a mishmash of rubbish
Severity set to 'important' from 'grave'

-- 
801770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#801770: devscripts: rmadison does not run properly but instead has a mishmash of rubbish

[Adam D. Barratt]

Control: tags -1 + moreinfo unreproducible
Control: severity -1 important

On 2015-10-14 13:12, Sharon Kimble wrote:

Package: devscripts
Version: 2.15.9
Severity: grave
Justification: renders package unusable


An issue with a single script in the package does not render the whole 
package unusable (even for an "important" script).



rmadison emacs24
<��0
E��l9[)���fՀ���֌؇�{OK)��t7���}"�S�8�ە���1�ʹ�E��GA2�4z�p���׹E��q�J���Qa4
�uq(��J��0�Q(�+.IL�IE�9,�b#������f����TC0��X�
   �@Ri0O��OAA��
H�%�����"����Bv������B7�h���%��%�y�4������";

This is on a fresh install of jessie yesterday, 64bit. I've tried 
upgrading to
the version of devscripts in testing, but it makes no difference, still 
the

same mishmash.

I was hoping to see the output showing what version of emacs24 in all 
debian

repos.


I'm unable to reproduce this:

adam@mowgli:~$ rmadison emacs24
debian:
 emacs24 | 24.4+1-4.1~bpo70+1 | wheezy-backports | source, amd64, i386, 
ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, 
sparc

 emacs24 | 24.4+1-4.1 | sid  | source, hurd-i386
 emacs24 | 24.4+1-5   | jessie-kfreebsd  | source, 
kfreebsd-amd64, kfreebsd-i386
 emacs24 | 24.4+1-5   | jessie   | source, amd64, arm64, 
armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
 emacs24 | 24.5+1-2   | stretch  | source, amd64, arm64, 
armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
 emacs24 | 24.5+1-2   | sid  | source, amd64, arm64, 
armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, 
mipsel, powerpc, ppc64el, s390x

new:
adam@mowgli:~$

(2.15.3, on jessie amd64)

Please provide the output of:

- grep -i rmadison /etc/devscripts.conf
- env | grep -i proxy
- which rmadison
- type rmadison

Regards,

Adam

Processed: Re: Bug#800617: Fails to provide secrets

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #800617 {Done: Dmitry Shachnev } [gnome-keyring] Fails 
to provide secrets
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gnome-keyring/3.18.0-3.
> notfixed -1 gnome-keyring/3.18.0-3
Bug #800617 [gnome-keyring] Fails to provide secrets
Ignoring request to alter fixed versions of bug #800617 to the same values 
previously set

-- 
800617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#800617: Fails to provide secrets

[Dmitry Shachnev]

Control: reopen -1
Control: notfixed -1 gnome-keyring/3.18.0-3

Hi Andreas,

On Wed, Oct 14, 2015 at 12:29:57PM +0200, Andreas Kurth wrote:
> Hi,
> 
> for me this bug is not fixed.
> 
> I use gnome-keyring to store SVN credentials. When calling "svn up" or
> other server related commands, svn waits endlessly without returning.
> 
> This behaviour was introduced with 3.18.0-1 and can be "fixed" by
> downgrading to 3.16.0-4.
> 
> Please advise how I can help debugging the issue.

Thanks for the confirmation. I have notified the upstream developers that
the new patch still does not fix the bug.

I am trying to do my best to get it fixed, but please try to stick to
the testing version if the unstable one is broken for you.

--
Dmitry Shachnev

Processed: Re: Bug#801550: ocamlnet: FTBFS on hppa -- unterminated string literal

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #801550 [src:ocamlnet] ocamlnet: FTBFS on hppa -- unterminated string 
literal
Severity set to 'serious' from 'normal'

-- 
801550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#798079: marked as done (FTBFS: QGLWidget: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 14 Oct 2015 12:19:33 +
with message-id 
and subject line Bug#798079: fixed in utopia-documents 2.4.4-2.1
has caused the Debian Bug report #798079,
regarding FTBFS: QGLWidget: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
798079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: utopia-documents
Version: 2.4.4-2
Severity: serious
Tags: stretch sid
Justification: FTBFS, but did so in the past

During a binary-only rebuild for the pcre3 transition, your package failed
to build from source:

| In file included from 
/«PKGBUILDDIR»/libutopia2_qt/utopia2/qt/flowbrowser.cpp:32:0:
| /«PKGBUILDDIR»/libutopia2_qt/utopia2/qt/flowbrowser.h:37:21: fatal error: 
QGLWidget: No such file or directory
| compilation terminated.
| make[3]: *** 
[libutopia2_qt/utopia2/qt/CMakeFiles/utopia2_qt.dir/flowbrowser.cpp.o] Error 1


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

Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: utopia-documents
Source-Version: 2.4.4-2.1

We believe that the bug you reported is fixed in the latest version of
utopia-documents, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 798...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated utopia-documents 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Oct 2015 13:49:39 +0200
Source: utopia-documents
Binary: utopia-documents utopia-documents-dbg
Architecture: source
Version: 2.4.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: The Utopia Project 
Changed-By: Sebastian Ramacher 
Description:
 utopia-documents - PDF reader that displays interactive annotations on 
scientific ar
 utopia-documents-dbg - debugging symbols for utopia-documents
Closes: 798079
Changes:
 utopia-documents (2.4.4-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Steve Langasek ]
   * debian/patches/boost1.58-qt4moc-compatibility.patch: compatibility
 with boost 1.58.
   * Add missing build-dependency on libqt4-opengl-dev. (Closes: #798079)
 .
   [ James Marsh ]
   * debian/patches/remove-utopia-update-check.diff: Disable check for new
 upstream releases on startup.
Checksums-Sha1:
 96d0719df192774241040e0e332333d1a32c8a53 2487 utopia-documents_2.4.4-2.1.dsc
 052250f498fa345a89d76fb8708555c787333104 32652 
utopia-documents_2.4.4-2.1.debian.tar.xz
Checksums-Sha256:
 7ce8f16f56c05d48c10bbbde9b0376d1202fdd9d3cc89bfe619be6d710eb450f 2487 
utopia-documents_2.4.4-2.1.dsc
 fba6e75be1c4919b3eb3ad5113bc7891356d310f6bd148ff2ab9e7d753c3b5f4 32652 
utopia-documents_2.4.4-2.1.debian.tar.xz
Files:
 0f560fd07e3daecc8a795aa4b95d21d2 2487 science optional 
utopia-documents_2.4.4-2.1.dsc
 7e3b301c37eb396707a36b19e76b00c1 32652 science optional 
utopia-documents_2.4.4-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWHkbkAAoJEGny/FFupxmTexYP/jnZdMDgTu3+Sl04xQe+utP3
QpDei+85eXVb6QOnlgdzFDVDBkkdf8B1JCjtGvf7ZlIxxUy/JHMjjLqvpO/an0kW
VleEN4PRq34O68xPTxG1ZSY2DAUucFzF2b4zJFsITaOUXZozW1Idq98HUrgXr/r0
J/ZTogRNwPP69KSxg2aFlTclJ0arUPzzvbI4Z/lDI4SPQim2x6qcq9xfldGWTmpd
9nV+ugd1/YyfrxSQHKMsSC/PJmu2iwpTfoxMBt2qGj0U3c1mUFfyzCi8Jh9WLIRC
u4zB7/h0096LnNGIqvND7CUpvD5n4BqHxwbCypVXgFN20a2AqYi87tdeLl7PNn4I
JC99eYsSEK+BVCApOJp7pIcS8741jYVQMY+nMu0tjVI/5XyF8d5/L1yh4Q9C2AKj
SSLP+kt+wH6MHBKwQX9ZBh0/qluiwAbLA3Pzx9sbBhAnlgdZKlHzoERI7s/kGZCd
nxvGEpQti+MfhEDTZQY1kBhIRtCA1j1HGdre/f8//3q/Sv7gJIkX5f86+aaAriJ3
vMo/ZIMPVaL29cTNx5NacnMJOuAPFH50+pVF8Msej7ufoR8pDbYUqc4lQpq0Bjvh

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred! (debdiff so far)

[Stéphane Glondu]

Le 09/10/2015 21:41, Ole Streicher a écrit :
> I tried it, but in the moment on unstable there is a dependency problem with
> ocaml:
> 
> libcairo-ocaml-dev : Depends: ocaml-nox-4.01.0 which is a virtual package
> and is not provided by any available package.
> [...]
> 
> This happened since ocaml-4.02.3-2 was uploaded to unstable just two days
> ago and cairo-ocaml was not updated yet [1]. Transitions are a bit of
> nightmare in the moment.
> 
> I would guess that we just need to wait a few more days.
> 
> @debian-ocaml-maint: can you estimate when the packages required by plplot
> (camlidl, cairo-ocaml, lablgtk2) fit together in unstable again? Plplot has
> quite a couple of dependencies in astronomy (the whole gdl ecosystem, psfex,
> scamp etc.).

libcairo-ocaml-dev is installable on all (release) architectures, now.


Cheers,

-- 
Stéphane

Bug#801770: devscripts: rmadison does not run properly but instead has a mishmash of rubbish

[Sharon Kimble]

Package: devscripts
Version: 2.15.9
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When trying to use "rmadison emacs24" I get this -

rmadison emacs24
<��0
E��l9[)���fՀ���֌؇�{OK)��t7���}"�S�8�ە���1�ʹ�E��GA2�4z�p���׹E��q�J���Qa4
�uq(��J��0�Q(�+.IL�IE�9,�b#������f����TC0��X�
   �@Ri0O��OAA��
H�%�����"����Bv������B7�h���%��%�y�4������";

This is on a fresh install of jessie yesterday, 64bit. I've tried upgrading to
the version of devscripts in testing, but it makes no difference, still the
same mishmash.

I was hoping to see the output showing what version of emacs24 in all debian
repos.

Thanks
Sharon.




-- Package-specific info:

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

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

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

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

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

Versions of packages devscripts recommends:
ii  at  3.1.16-1
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
ii  gnupg   1.4.18-7
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  libsoap-lite-perl   1.11-1
ii  liburi-perl 1.64-1
ii  libwww-perl 6.08-1
ii  lintian 2.5.30+deb8u4
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
ii  sensible-utils  0.0.9
ii  strace  4.9-2
ii  unzip   6.0-16
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   
pn  devscripts-el
pn  gnuplot  
ii  gpgv 1.4.18-7
ii  libauthen-sasl-perl  2.1600-1
ii  libfile-desktopentry-perl0.07-1
ii  libnet-smtp-ssl-perl 1.01-3
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
ii  mutt 1.5.23-3
ii  openssh-client [ssh-client]  1:6.7p1-5
pn  svn-buildpackage 
ii  w3m  0.5.3-19

-- no debconf information

Bug#801773: FTBFS with OCaml 4.02.3

[Stéphane Glondu]

Package: src:dose3
Version: 4.0.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

dose3 fails to build on all architectures:

  https://buildd.debian.org/status/package.php?p=dose3=sid

Cheers,

-- 
Stéphane

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

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

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred! (debdiff so far)

[Axel Beckert]

Hi Stéphane,

Stéphane Glondu wrote:
> > @debian-ocaml-maint: can you estimate when the packages required by plplot
> > (camlidl, cairo-ocaml, lablgtk2) fit together in unstable again? Plplot has
> > quite a couple of dependencies in astronomy (the whole gdl ecosystem, psfex,
> > scamp etc.).
> 
> libcairo-ocaml-dev is installable on all (release) architectures, now.

Thanks for notice. Will give it another try this evening or so.

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

Bug#789619: plplot: FTBFS: Configuring incomplete, errors occurred! (debdiff so far)

[debian]

Hi Stephane, Axel,

I just tried to compile plplot: All ocaml requirements for plplot work 
now; and the package builds fine with Axels debdiff. Thank you very much 
for your support, Stephane! Axel, when you have time, would you upload a 
NMU then?


Best regards,

Ole

On 14.10.2015 15:00, Axel Beckert wrote:

Hi Stéphane,

Stéphane Glondu wrote:

@debian-ocaml-maint: can you estimate when the packages required by plplot
(camlidl, cairo-ocaml, lablgtk2) fit together in unstable again? Plplot has
quite a couple of dependencies in astronomy (the whole gdl ecosystem, psfex,
scamp etc.).


libcairo-ocaml-dev is installable on all (release) architectures, now.


Thanks for notice. Will give it another try this evening or so.

Regards, Axel

Bug#801781: kate: Error in `kate': free(): invalid pointer

[Salvo Tomaselli]

Package: kate
Version: 4:15.08.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
after the last round of kde updates, kate krashes all the time

> *** Error in `kate': free(): invalid pointer: 0x7fbd0e50 ***

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

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

Versions of packages kate depends on:
ii  kate5-data   4:15.08.1-1
ii  ktexteditor-katepart 5.15.0-1
ii  libc62.19-22
ii  libgit2-23   0.23.1-1
ii  libkf5activities55.15.0-1
ii  libkf5bookmarks5 5.15.0-1
ii  libkf5completion55.15.0-1
ii  libkf5configcore55.15.0-1
ii  libkf5configgui5 5.15.0-1
ii  libkf5configwidgets5 5.15.0-1
ii  libkf5coreaddons55.15.0-1
ii  libkf5dbusaddons55.15.0-1
ii  libkf5guiaddons5 5.15.0-1
ii  libkf5i18n5  5.15.0-1
ii  libkf5iconthemes55.15.0-1
ii  libkf5itemmodels55.15.0-1
ii  libkf5jobwidgets55.15.0-1
ii  libkf5kiocore5   5.15.0-1
ii  libkf5kiofilewidgets55.15.0-1
ii  libkf5kiowidgets55.15.0-1
ii  libkf5newstuff5  5.15.0-1
ii  libkf5notifications5 5.15.0-1
ii  libkf5parts5 5.15.0-1
ii  libkf5plasma55.15.0-1
ii  libkf5service5   5.15.0+-1
ii  libkf5texteditor55.15.0-1
ii  libkf5textwidgets5   5.15.0-1
ii  libkf5threadweaver5  5.15.0-1
ii  libkf5wallet-bin 5.15.0-1
ii  libkf5wallet55.15.0-1
ii  libkf5widgetsaddons5 5.15.0-1
ii  libkf5windowsystem5  5.15.0-1
ii  libkf5xmlgui55.15.0-1
ii  libqt5core5a 5.4.2+dfsg-9
ii  libqt5dbus5  5.4.2+dfsg-9
ii  libqt5gui5   5.4.2+dfsg-9
ii  libqt5sql5   5.4.2+dfsg-9
ii  libqt5widgets5   5.4.2+dfsg-9
ii  libqt5xml5   5.4.2+dfsg-9
ii  libstdc++6   5.2.1-22
ii  plasma-framework 5.15.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.15.0-1
ii  qml-module-qtquick-layouts   5.4.2-2+b1
ii  qml-module-qtquick2  5.4.2-6

kate recommends no packages.

Versions of packages kate suggests:
ii  aspell 0.60.7~20110707-3
pn  khelpcenter
ii  konsole-kpart  4:15.08.1-1

-- no debconf information

Bug#754803: healpy: out-of-date binaries

[Scott Kitterman]

On October 14, 2015 6:50:34 PM EDT, Steven Chamberlain  
wrote:
>Hi,
>
>On kfreebsd-amd64 healpy still FTBFS, but I suspect it just needs a
>Dep-Wait on python3-matplotlib (>= 1.5.0~)?
>
>https://buildd.debian.org/status/fetch.php?pkg=healpy=kfreebsd-amd64=1.8.1-1.1=1444690648
>| __ ERROR collecting
>.pybuild/pythonX.Y_3.5/build/healpy/test/test_visufunc.py __
>| healpy/test/test_visufunc.py:5: in 
>| from ..visufunc import *
>| healpy/visufunc.py:54: in 
>| from . import projaxes as PA
>| healpy/projaxes.py:24: in 
>| from matplotlib import axes,ticker,colors,cm,lines,cbook,figure
>| /usr/lib/python3/dist-packages/matplotlib/axes/__init__.py:4: in
>
>| from ._subplots import *
>| /usr/lib/python3/dist-packages/matplotlib/axes/_subplots.py:7: in
>
>| from matplotlib.gridspec import GridSpec, SubplotSpec
>| /usr/lib/python3/dist-packages/matplotlib/gridspec.py:26: in 
>| import matplotlib.transforms as mtransforms
>| /usr/lib/python3/dist-packages/matplotlib/transforms.py:39: in
>
>| from matplotlib._path import (affine_transform,
>count_bboxes_overlapping_bbox,
>| E   ImportError: No module named 'matplotlib._path'
>
>Newer matplotlib, in turn, is waiting on the glib2.0 FTBFS
>(https://bugs.debian.org/712848) but that may be fixed in a few days.
>
>Regards,

Yes.  I believe that is correct.

Scott K