Bug#806879: xsp: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails)

[tony mancill]

Package: src:xsp
Followup-For: Bug #806879

Hi Debian Mono Group,

The workaround patch works fine.  Is there anything preventing an
upload?  Would the team be okay with an NMU?

Thanks,
tony


signature.asc
Description: PGP signature

Bug#858756: sqlite3: debian/* files are licensed under GPLv2+

[Mohammed Sadiq]

Source: sqlite3
Severity: serious

Dear Maintainer,

  The license file[0] of src:sqlite3 states that the debian/* files
are licensed under GPLv2+. Which means that the debian specific patches
are applied as GPLv2+, which in turn may convert the whole package into 
GNU GPLv2+.

This may make the libraries (libsqlite3, and so on) too to be licensed under
GNU GPLv2+, and thus every library and package linked to it to be too
licensed under GNU GPLv2+ (or even GNU GPLv3+).

Right now, the patches are so small to have any legal issues with it (I hope),
but it would be better to let the patches have the same license as the file
to which it is applied.

It is okay to have debian/* to GPLv2+ license (I myself am happy to see more GNU
GPL packages), but debian/patches/* should follow the package license.

This may cause unintended harms to people who are giving commercial support
to their own application AND the Debian (or Derivatives) installation.

I didn't find such a suggestion in debian policy. Or am I wrong?


Thanks

[0] 
http://metadata.ftp-master.debian.org/changelogs/main/s/sqlite3/unstable_copyright

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

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

-- no debconf information

Bug#854873: marked as done (mosh FTBFS: FAIL local.test)

[Debian Bug Tracking System]

Your message dated Sat, 25 Mar 2017 19:42:30 -0700
with message-id 

Bug#858556: In case the code is not anywhere...

[Santiago Garcia Mantinan]

> Maybe it was just that the original code had to be at the 
> upgrade|install-upgrade
> block of the case?
> 
> But why is the -d /etc/squid3 checked?

I followed this two questions doing some tests on my system and it looks to
me as we should be happy with this patch:

--- /tmp/squid.preinst  2017-03-26 01:27:31.201012140 +0100
+++ debian/squid.preinst2017-03-26 00:59:34.433577481 +0100
@@ -26,6 +26,8 @@
/etc/squid3/errorpage.css /etc/squid/errorpage.css 3.5.4-1~ 
squid3 -- "$@"
 fi
 
+case "$1" in
+   upgrade|install-upgrade)
 #
 # If the squid (2.7) package was being used previously protect
 # the squid.conf file, which was not tracked as a conffile.
@@ -34,12 +36,9 @@
 # Except when a squid3 package was used, since we do want the
 # debconf questions to appear as the packages get merged.
 #
-if dpkg --compare-versions "$2" lt '2.8' && test -d /etc/squid3; then
+if dpkg --compare-versions "$2" lt '2.8'; then
mv /etc/squid/squid.conf /etc/squid/squid.conf.pre3.5_upgrade
 fi
-
-case "$1" in
-   upgrade|install-upgrade)
;;
abort-upgrade)
exit 0

Which basically means to move the check to the upgrade|install-upgrade
section and remove the check for the squid3 dir.

My tests of both an upgrade from 2.7 and from jessie's squid3 work ok.

Amos, I don't know what your idea with this code was, so I'd like to talk
about it a bit before uploading a new version.

Regards.
-- 
Manty/BestiaTester -> http://manty.net

Bug#858503: diff NMU for libinfinity_0.6.7-1.1

[Anton Gladky]

tags 858503 +pending +patch
thanks

Dear maintainer,

I have prepared an NMU (versioned as 0.6.7-1.1) and
uploaded to DELAYED/5.

Please fell free to tell me if I should delay it longer, cancel
or reschedule.

Diff is attached.

Best regards

Anton


nmu.debdiff
Description: Binary data

Processed: diff NMU for libinfinity_0.6.7-1.1

[Debian Bug Tracking System]

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

> tags 858503 +pending +patch
Bug #858503 [libinfinity-0.6-dev] libinfinity-0.6-dev: missing Depends: 
infinoted (= ${binary:Version})
Added tag(s) pending.
Bug #858503 [libinfinity-0.6-dev] libinfinity-0.6-dev: missing Depends: 
infinoted (= ${binary:Version})
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#858730: marked as done (mudlet FTBFS on !amd64: /usr/lib/x86_64-linux-gnu/qt5/bin/qmake: Command not found)

[Debian Bug Tracking System]

Your message dated Sat, 25 Mar 2017 21:51:14 +
with message-id 
and subject line Bug#858730: fixed in mudlet 1:3.0.0-2
has caused the Debian Bug report #858730,
regarding mudlet FTBFS on !amd64: /usr/lib/x86_64-linux-gnu/qt5/bin/qmake: 
Command not found
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.)


-- 
858730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mudlet
Version: 1:3.0.0-1
Severity: serious

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

...
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/«PKGBUILDDIR»'
[ ! -f src/Makefile ] || /usr/bin/make -C src distclean
make[2]: Entering directory '/«PKGBUILDDIR»/src'
/usr/lib/x86_64-linux-gnu/qt5/bin/qmake -o Makefile src.pro
make[2]: /usr/lib/x86_64-linux-gnu/qt5/bin/qmake: Command not found
Makefile:627: recipe for target 'Makefile' failed
make[2]: *** [Makefile] Error 127


x86_64-linux-gnu is not part of paths that are expected to exist
on !amd64, the generated src/Makefile should not be used.
--- End Message ---
--- Begin Message ---
Source: mudlet
Source-Version: 1:3.0.0-2

We believe that the bug you reported is fixed in the latest version of
mudlet, 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 858...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated mudlet 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: SHA512

Format: 1.8
Date: Sun, 26 Mar 2017 08:15:59 +1100
Source: mudlet
Binary: mudlet
Architecture: source amd64
Version: 1:3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 mudlet - Graphical MUD client with fast lua scripting support
Closes: 858730
Changes:
 mudlet (1:3.0.0-2) unstable; urgency=medium
 .
   * Remove upstream Makefile Closes: #858730
Checksums-Sha1:
 6b96a0f73abdcf17e6d506fbb611cd0beebfeb5a 2220 mudlet_3.0.0-2.dsc
 923e7ba03f037148e5cfdcca4cd61dba48bc2348 21244 mudlet_3.0.0-2.debian.tar.xz
 e1e591ccc259e0eb50c380e85b9882bbdeba89fb 20627284 
mudlet-dbgsym_3.0.0-2_amd64.deb
 1a2a856fc5d7929cd3d66585f84a6cfcb3baa950 11314 mudlet_3.0.0-2_amd64.buildinfo
 e422e11c6b19b2ad5274e0dba64d9c3f02a58cda 2630186 mudlet_3.0.0-2_amd64.deb
Checksums-Sha256:
 83883ff22fe7c409679435cfd18aec3a0c9427fb1058e27ea67d7c182e4db51e 2220 
mudlet_3.0.0-2.dsc
 25a001dad78bdb978890b5bbb5cddf7c2b974bc3a86d58e3b8e68d1da38c41b0 21244 
mudlet_3.0.0-2.debian.tar.xz
 77c8252493a0d5a1bdd262335b4a9caacce6b52fd07713f7e9b2ca6bd9cba982 20627284 
mudlet-dbgsym_3.0.0-2_amd64.deb
 ff5ac16a29da25e9c098eee63c618d19e0fd4e70fb836a9957d5bd532ccabc77 11314 
mudlet_3.0.0-2_amd64.buildinfo
 bc57f5804532c4325e34f6ab27ff0d4ac292e6403b996040071d677f96c45ec4 2630186 
mudlet_3.0.0-2_amd64.deb
Files:
 99a315ac3ba76f0e768d0080d4051d38 2220 games extra mudlet_3.0.0-2.dsc
 de84404334353a777b15c28e8cd70e58 21244 games extra mudlet_3.0.0-2.debian.tar.xz
 2aa026f2fcde63f7734cdbae386b4fbf 20627284 debug extra 
mudlet-dbgsym_3.0.0-2_amd64.deb
 bbb5031d3cb166bc22d50dc1423a19c2 11314 games extra 
mudlet_3.0.0-2_amd64.buildinfo
 3a4c61aab79083eccafc136981913ec5 2630186 games extra mudlet_3.0.0-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAljW4QUACgkQAiFmwP88
hOMh6g/+Lsx7VPU7PanN2o6LH+CUSzfqhajeK7wwamd6uwYCSUBgXwz/FkmXtTv6
0xVOnG9UcXA2YdG8NNav9x2IU0VS0X08df0K4zd6D4CxqsAYe52ZjR+rla/Scs7+
ZqwBpFMDThQiWv8hWfZgotbQ/DHqwRpus87HGl5X4qNxkSDymAQZXZXo627TQWe7
AHEyVHyfzxXueC0SLqh3U5JVdaxavm0JsJr3XWoANVIFsXP06bHXJkvSoGQVHdT/
2fgxptF+Oi2BaiWt8QEPd8MgiAUl18QPVTAhgL++RHRgSCt5yPMy5guDB5vQdn7u
NtwmESB27jMi9SqG16A2e1jFZHxg9XKS+bkl46njszJWnAghlF0MHxvfUQbK8hWo
ppycYCNiLW313lwk+t+2fcIhAKS+jUIDet+XSLEFfN5IPdrDdm2VrjN4F2J06HgJ
5tHn5eUvURjS8J/rqz/53NjDxrfFcx2BSzKjjz7ssmZ7YPosP/HYzhAZ2pG8HgKC
VibiaJwObWXoiEkxFK232cLdiNwFvgNLYebmYsk+3os2PIJXCFA7INir9crVQT02
yvrnV1no/SrIFHP0E1afWQ2Qwz/pkzHii9WJMWgUhvJ7IfbIR8Nc40X0o6QNRYxU
qo3QrCVVdrNkVGKehE7qBf+1XWgnmuKpkYgczIQ59X92QNKv9qA=
=PN+7
-END PGP 

Bug#858729: plasma-discover: too many bugs for the next stable

[Matthias Klumpp]

2017-03-25 22:27 GMT+01:00 Rene Engelhard :
> [ I am NOT the plasma-discover maintainer ]
>
> On Sat, Mar 25, 2017 at 12:53:20PM -0400, Leand wrote:
>>There are basic functions that are bugged. For example, the search
>>function returns wrong and unrelated results too many times. If I
>>search for "office" or "writer" it doesn't show LibreOffice packages
>>or LibreOffice Writer at all. Furthermore in some cases it doesn't
>
> Looks it looks at Name and/or GenericName in the .desktop files. Here:
>
> # cat /usr/share/applications/libreoffice-writer.desktop | grep -E 
> '(.*Name=|.*Name\[en.*\]=)'
> Name=LibreOffice Writer
> GenericName=Word Processor
> GenericName[en]=Word Processor
> GenericName[en_GB]=Word Processor
> GenericName[en_ZA]=Word Processor
> [...]
>
> So if it takes GenericName before Name it of course doesn't see "LibreOffice 
> Writer" but
> "Word Processor". And also note "office" and "writer" don't even appear in 
> Name (not the
> case), no idea whether the search is case-sensitive, though.

The explanation is even easier here: LO Writer is not in the metadata,
because it symlinks files in /usr/share/applications, which the
metadata generator doesn't support.
See 
https://appstream.debian.org/sid/main/issues/index.html#debian_libreoffice_maintainers_%3cdebian-openoff...@lists.debian.org%3E
for the issue information.
So, this is not a bug in Discover. Also, all of the issues outlined in
this bug report are minor annoyances which do not at all justify the
severity of "grave" for this bug report.
I am even tempted to close it:
 * The search results are not Discover's fault, or are intended (see below)
 * Discover will not show dependencies or packages - it is not a
package manager. If you want a package manager, use Apper or Muon.
 * Displaying unrelated stuff to be removed when removing Gimp is
definitely a bug, but creating a clean, new one with normal priority
is a better idea here. Also, immediately reporting this upstream will
help.

>>even display the exact name of the packages in any way, for example
>>the package "file-roller" (Gnome's File Roller) is displayed as
>>"Archive manager".
>
> # cat /usr/share/applications/org.gnome.FileRoller.desktop | grep -E 
> '(.*Name=|.*Name\[en.*\]=)'
> Name=Archive Manager
> Name[en@shaw]=ѸђѲѝ ѥѨѯѩѡѼ
> Name[en_CA]=Archive Manager
> Name[en_GB]=Archive Manager
>
> So at least the second one is expected.

Jup, that's the reason. Nothing we can do here - complain to GNOME for
using very generic names.

Cheers,
Matthias

-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/

Bug#858626: marked as done (libllvm-3.8-ocaml-dev: Package is empty)

[Debian Bug Tracking System]

Your message dated Sat, 25 Mar 2017 21:50:28 +
with message-id 
and subject line Bug#858626: fixed in llvm-toolchain-3.8 1:3.8.1-19~exp2
has caused the Debian Bug report #858626,
regarding libllvm-3.8-ocaml-dev: Package is empty
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.)


-- 
858626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libllvm-3.8-ocaml-dev
Version: 1:3.8.1-18
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The package `libllvm-3.8-ocaml-dev` does not ship any library. It only
contains the following files:

/usr/share/doc/libllvm-3.8-ocaml-dev/NEWS.Debian.gz
/usr/share/doc/libllvm-3.8-ocaml-dev/changelog.Debian.gz
/usr/share/doc/libllvm-3.8-ocaml-dev/copyright
/usr/share/lintian/overrides/libllvm-3.8-ocaml-dev
/var/lib/ocaml/lintian/libllvm-3.8-ocaml-dev.info
/var/lib/ocaml/md5sums/libllvm-3.8-ocaml-dev.md5sums

It misses the `/usr/lib/ocaml/llvm-3.8` folder, which should contain the
libraries, making the package totally unusable.

It looks like this folder is missing since `libllvm-3.6-ocaml-dev`, and
is still missing in `libllvm-3.9-ocaml-dev`. Last version containing it
was `libllvm-3.5-ocaml-dev`, but it is not installable on `stretch`.

The change log mentions that OCaml bindings were disabled in November
2014, because `libctypes-ocaml` 0.3.3 was needed, but not available.
Would it work with a current version of that library? (0.7.0 is
installed on my system)

Thanks in advance for your help.

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

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

Versions of packages libllvm-3.8-ocaml-dev depends on:
ii  llvm-3.8-dev  1:3.8.1-18

libllvm-3.8-ocaml-dev recommends no packages.

Versions of packages libllvm-3.8-ocaml-dev suggests:
pn  llvm-3.8-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-3.8
Source-Version: 1:3.8.1-19~exp2

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-3.8, 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 858...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-3.8 
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: Sat, 25 Mar 2017 16:37:44 +0100
Source: llvm-toolchain-3.8
Binary: clang-3.8 clang-format-3.8 clang-tidy-3.8 clang-3.8-doc libclang1-3.8 
libclang1-3.8-dbg libclang-3.8-dev libclang-common-3.8-dev libfuzzer-3.8-dev 
python-clang-3.8 clang-3.8-examples libllvm3.8 libllvm3.8-dbg llvm-3.8 
llvm-3.8-runtime llvm-3.8-dev llvm-3.8-tools llvm-3.8-doc llvm-3.8-examples 
lldb-3.8 liblldb-3.8 liblldb-3.8-dbg python-lldb-3.8 liblldb-3.8-dev 
lldb-3.8-dev
Architecture: source amd64 all
Version: 1:3.8.1-19~exp2
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-3.8  - C, C++ and Objective-C compiler (LLVM based)
 clang-3.8-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-3.8-examples - Clang examples
 clang-format-3.8 - Tool to format C/C++/Obj-C code
 clang-tidy-3.8 - clang-based C++ linter tool
 libclang-3.8-dev - clang library - Development package
 libclang-common-3.8-dev - clang library - Common development package
 libclang1-3.8 - C interface to the clang library
 libclang1-3.8-dbg - clang library
 libfuzzer-3.8-dev - Library for coverage-guided fuzz testing
 liblldb-3.8 - Next generation, high-performance debugger, library
 liblldb-3.8-dbg - Next generation, high-performance debugger, debugging 
libraries
 liblldb-3.8-dev - Next generation, high-performance debugger - Header files
 

Bug#858729: plasma-discover: too many bugs for the next stable

[Rene Engelhard]

[ I am NOT the plasma-discover maintainer ]

On Sat, Mar 25, 2017 at 12:53:20PM -0400, Leand wrote:
>There are basic functions that are bugged. For example, the search
>function returns wrong and unrelated results too many times. If I
>search for "office" or "writer" it doesn't show LibreOffice packages
>or LibreOffice Writer at all. Furthermore in some cases it doesn't

Looks it looks at Name and/or GenericName in the .desktop files. Here:

# cat /usr/share/applications/libreoffice-writer.desktop | grep -E 
'(.*Name=|.*Name\[en.*\]=)'
Name=LibreOffice Writer
GenericName=Word Processor
GenericName[en]=Word Processor
GenericName[en_GB]=Word Processor
GenericName[en_ZA]=Word Processor
[...]

So if it takes GenericName before Name it of course doesn't see "LibreOffice 
Writer" but
"Word Processor". And also note "office" and "writer" don't even appear in Name 
(not the
case), no idea whether the search is case-sensitive, though.

>even display the exact name of the packages in any way, for example
>the package "file-roller" (Gnome's File Roller) is displayed as
>"Archive manager".

# cat /usr/share/applications/org.gnome.FileRoller.desktop | grep -E 
'(.*Name=|.*Name\[en.*\]=)'
Name=Archive Manager
Name[en@shaw]=ѸђѲѝ ѥѨѯѩѡѼ
Name[en_CA]=Archive Manager
Name[en_GB]=Archive Manager

So at least the second one is expected.

Regards,

Rene

Bug#857522: libbind-export-dev: broken symlinks: /usr/lib/x86_64-linux-gnu/liblwres-export.so -> /lib/x86_64-linux-gnu/liblwres-export.so.141, /usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.

[Michael Gilbert]

control: severity -1 important

On Sun, Mar 12, 2017 at 1:26 AM, Andreas Beckmann wrote:
>   /usr/lib/x86_64-linux-gnu/liblwres-export.so -> 
> /lib/x86_64-linux-gnu/liblwres-export.so.141
>   /usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.0.10

These are mistakenly included in libbind-export-dev, but they do no
harm being there.  This is a bug, not an RC bug.

Best wishes,
Mike

Processed: Re: Bug#857522: libbind-export-dev: broken symlinks: /usr/lib/x86_64-linux-gnu/liblwres-export.so -> /lib/x86_64-linux-gnu/liblwres-export.so.141, /usr/lib/x86_64-linux-gnu/libbind9.so -> l

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #857522 [libbind-export-dev] libbind-export-dev: broken symlinks: 
/usr/lib/x86_64-linux-gnu/liblwres-export.so -> 
/lib/x86_64-linux-gnu/liblwres-export.so.141, 
/usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.0.10
Severity set to 'important' from 'serious'

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

Bug#858730: mudlet FTBFS on !amd64: /usr/lib/x86_64-linux-gnu/qt5/bin/qmake: Command not found

[Craig Small]

On Sun, Mar 26, 2017 at 4:30 AM Adrian Bunk  wrote:

> x86_64-linux-gnu is not part of paths that are expected to exist
> on !amd64, the generated src/Makefile should not be used.
>
That makefile is generally not shipped with the upstream rebuilt package.
I'm not sure why it is there now.

 - Craig

-- 
Craig Small (@smallsees)   http://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

Bug#858633: libreoffice-dmaths: DMath isn't installed in Libreoffice 5.2

[Innocent De Marchi]

Hi TheSuperGeek,

Yes, I know this issue. Apparently, it is due to changes in the management
of LibreOffice plug-ins.
I have to investigate how to install the package with the changes.

Regards!

I. De Marchi

2017-03-24 18:20 GMT+01:00 TheSuperGeek :

> Package: libreoffice-dmaths
> Version: 3.7.0.0+dfsg1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
> I've got a problem with libreoffice 5.2.5.1 and DMath 3.7 : DMath isn't
> installed. I cannot find it into Libreoffice's extention manager too.
> I installed libreoffice-dmath, purged it and re-installed it but it even
> don't
> work.
> The upstream version looks to be in 4.xx but for paying users only.
> So for the moment the package don't work on debian stretch.
> Best regards,
> TheSuperGeek
>
>
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libreoffice-dmaths depends on:
> ii  libreoffice-draw1:5.2.5-2
> ii  libreoffice-writer  1:5.2.5-2
> ii  zenity  3.22.0-1+b1
>
> libreoffice-dmaths recommends no packages.
>
> Versions of packages libreoffice-dmaths suggests:
> pn  dia
> pn  drgeo  
>
> -- no debconf information
>

Processed: Also seems to affect stretch

[Debian Bug Tracking System]

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

> found 858725 8.13.11+dfsg-2
Bug #858725 [src:gitlab] [src:gitlab] FTBFS for 
/vendor/assets/javascripts/fuzzaldrin-plus.js and incomplete copyright
Marked as found in versions gitlab/8.13.11+dfsg-2.
> thanks
Stopping processing here.

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

Bug#848813: marked as done (blacs-mpi: FTBFS: make[3]: *** No rule to make target '/usr/lib/openmpi/include/mpif.h', needed by 'mpif.h'. Stop.)

[Debian Bug Tracking System]

Your message dated Sat, 25 Mar 2017 17:33:52 +
with message-id 
and subject line Bug#848813: fixed in blacs-mpi 1.1-38
has caused the Debian Bug report #848813,
regarding blacs-mpi: FTBFS: make[3]: *** No rule to make target 
'/usr/lib/openmpi/include/mpif.h', needed by 'mpif.h'.  Stop.
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.)


-- 
848813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blacs-mpi
Version: 1.1-37
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[3]: Entering directory '/<>/SRC/MPI/INTERNAL'
> rm -f Bdef.h
> ln -s ../Bdef.h Bdef.h
> rm -f Bconfig.h
> ln -s ../Bconfig.h Bconfig.h
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_HypBS.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_HypBR.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_IdringBS.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_IdringBR.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_MpathBS.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_MpathBR.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_SringBS.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_SringBR.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_TreeBS.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_TreeBR.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_Ssend.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_Rsend.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_Srecv.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_Asend.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_Arecv.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_TreeComb.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_BeComb.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_MringComb.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_ArgCheck.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_TransDist.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_GetBuff.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_UpdateBuffs.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_EmergencyBuff.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_BlacsErr.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_BlacsWarn.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_BlacsAbort.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_BuffIsFree.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_imvcopy.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_smvcopy.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_dmvcopy.c
> mpicc.openmpi -c  -O4 -DSYSINC -I/usr/lib/openmpi/include -DAdd_   
> -DBlacsDebugLvl=0   -DUseMpi2   BI_ivmcopy.c
> mpicc.openmpi 

Bug#858730: mudlet FTBFS on !amd64: /usr/lib/x86_64-linux-gnu/qt5/bin/qmake: Command not found

[Adrian Bunk]

Source: mudlet
Version: 1:3.0.0-1
Severity: serious

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

...
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/«PKGBUILDDIR»'
[ ! -f src/Makefile ] || /usr/bin/make -C src distclean
make[2]: Entering directory '/«PKGBUILDDIR»/src'
/usr/lib/x86_64-linux-gnu/qt5/bin/qmake -o Makefile src.pro
make[2]: /usr/lib/x86_64-linux-gnu/qt5/bin/qmake: Command not found
Makefile:627: recipe for target 'Makefile' failed
make[2]: *** [Makefile] Error 127


x86_64-linux-gnu is not part of paths that are expected to exist
on !amd64, the generated src/Makefile should not be used.

Bug#854228: Libraries not linked with their deps

[Muammar El Khatib]

Dear all,

On Mon, Mar 20, 2017 at 11:03 PM, Drew Parsons  wrote:
> Probably the solution we want is to update our scalapack to 2.0.2, and
> remove this blacs package, at least as a separate source package. That
> won't happen for stretch, obviously.

I am sorry for the delay in replying to this report. I am right now
preparing to upload a Debian revision that adds the patch in #848813
for fixing the FTBFS.

Lately, I have had limited time to take care of ScaLAPACK, and I think
it is time to move it to team maintenance. I was thinking of
Debian-science. I have already sent an email to the mailing list.

Regards,
-- 
Muammar El Khatib.
Linux user: 403107.
GPG Key = 71246E4A.
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Bug#858729: plasma-discover: too many bugs for the next stable

[Leand]

Package: plasma-discover
Version: 5.8.5-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The version of Discover provided in Stretch is too bugged and
immature, it is not suitable for a stable release. Please remove it or
provide a newer version.

There are basic functions that are bugged. For example, the search
function returns wrong and unrelated results too many times. If I
search for "office" or "writer" it doesn't show LibreOffice packages
or LibreOffice Writer at all. Furthermore in some cases it doesn't
even display the exact name of the packages in any way, for example
the package "file-roller" (Gnome's File Roller) is displayed as
"Archive manager".

Other issues: Discover doesn't display the dependencies of a package
and don't ask for confirmation when installing one; when removing an
application the confirmation dialog may display wrong info (search for
gimp, ask to remove it and the dialog will display xsane, bleachbit
and unrelated packages).

There are also issues with the interface but, simply, this application
is still immature and unreliable. It cannot be used for package
management.

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
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 plasma-discover depends on:
ii appstream 0.10.6-1
ii kio 5.28.0-1
ii libappstreamqt2 0.10.6-1
ii libc6 2.24-9
ii libkf5archive5 5.28.0-1+b2
ii libkf5attica5 5.28.0-1
ii libkf5configcore5 5.28.0-1+b2
ii libkf5configgui5 5.28.0-1+b2
ii libkf5configwidgets5 5.28.0-1
ii libkf5coreaddons5 5.28.0-1+b2
ii libkf5crash5 5.28.0-1
ii libkf5dbusaddons5 5.28.0-1
ii libkf5declarative5 5.28.0-1
ii libkf5i18n5 5.28.0-1+b2
ii libkf5kiocore5 5.28.0-1
ii libkf5kiowidgets5 5.28.0-1
ii libkf5newstuff5 5.28.0-1
ii libkf5notifications5 5.28.0-1
ii libkf5service-bin 5.28.0-1
ii libkf5service5 5.28.0-1
ii libkf5widgetsaddons5 5.28.0-1
ii libkf5xmlgui5 5.28.0-1
ii libpackagekitqt5-0 0.9.6-1
ii libqt5core5a 5.7.1+dfsg-3+b1
ii libqt5dbus5 5.7.1+dfsg-3+b1
ii libqt5gui5 5.7.1+dfsg-3+b1
ii libqt5qml5 5.7.1-2+b2
ii libqt5quick5 5.7.1-2+b2
ii libqt5widgets5 5.7.1+dfsg-3+b1
ii libqt5xml5 5.7.1+dfsg-3+b1
ii libstdc++6 6.3.0-10
ii packagekit 1.1.5-2
ii plasma-discover-common 5.8.5-3
ii qml-module-org-kde-kirigami 1.1.0-1

Versions of packages plasma-discover recommends:
ii software-properties-kde 0.96.20.2-1

plasma-discover suggests no packages.

-- no debconf information

Bug#858644: [pkg-firebird-general] Bug#858644: CVE-2017-6369: authenticated remote execution in firebird 2.5 before version 3.0.2

[Damyan Ivanov]

-=| Damyan Ivanov, 24.03.2017 19:22:53 + |=-
> Relevant upstream commits for 3.0:
>  - 
> https://github.com/FirebirdSQL/firebird/commit/8b2a9cb44bf6055e15f016d70a6842b8ada60375

Correction: the commit for 3.0 (branch B3_0_Release) is 
https://github.com/FirebirdSQL/firebird/commit/56e9a73c16803c3544076edb2d6c4ca25815e541

8b2a9cb4 is the commit in the master branch.


-- dam


signature.asc
Description: Digital signature

Bug#856133: shiboken FTBFS on i386/armel/armhf: other_collector_external_operator test failed

[Gilles Filippini]

On Sat, 4 Mar 2017 20:06:36 +0100 gregor herrmann  wrote:
> On Sat, 25 Feb 2017 16:07:03 +0200, Adrian Bunk wrote:
> 
> > Source: shiboken
> > Version: 1.2.2-3
> > Severity: serious
> > 
> > https://buildd.debian.org/status/package.php?p=shiboken=sid
> > 
> 
> FWIW, the package currently builds fine for me in an i386 sid
> cowbuilder chroot (and an amd64 machine).

Strangely it builds fine in an i386 sbuild chroot, but it fails
reproducibly on porter box barriere.debian.org.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Bug#850464: marked as done (nfs-blkmap.service fails to start at boot)

[Debian Bug Tracking System]

Your message dated Sat, 25 Mar 2017 16:03:42 +
with message-id 
and subject line Bug#850464: fixed in nfs-utils 1:1.3.4-2.1
has caused the Debian Bug report #850464,
regarding nfs-blkmap.service fails to start at boot
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.)


-- 
850464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: nfs-kernel-server
version: 1:1.3.4-2
severity: serious


The blkmapd process looks for /run/rpc_pipefs/nfs/blocklayout

It fails to find it and the system boot doesn't complete, it asks for an
emergency login on the text console.

I don't see anything under /run/rpc_pipefs/nfs

Other NFS services appear to be running fine.

The ArchLinux NFS wiki recommends masking the blkmapd service:

systemctl mask nfs-blkmap.service

https://wiki.archlinux.org/index.php/NFS

Perhaps blkmapd could be split into a separate package so it is only
installed for people who want it.



blkmapd[278]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No
such file or directory



blkmapd[278]: exit on signal(15)


systemd[1]: Failed to start pNFS block layout mapping daemon.
-- Subject: Unit nfs-blkmap.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nfs-blkmap.service has failed.
-- 
-- The result is failed.
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:1.3.4-2.1

We believe that the bug you reported is fixed in the latest version of
nfs-utils, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated nfs-utils 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: SHA512

Format: 1.8
Date: Mon, 20 Mar 2017 16:07:55 +0100
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source
Version: 1:1.3.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Andreas Henriksson 
Description:
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 850464
Changes:
 nfs-utils (1:1.3.4-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix patch to also change pidfile path in service file (Closes: #850464)
Checksums-Sha1:
 15e8dff425eb3bc009520116870e5572476d17e1 2360 nfs-utils_1.3.4-2.1.dsc
 3bcbe2f83f18577befbc6ca40f40b4a9bf0ee3e3 40882 
nfs-utils_1.3.4-2.1.debian.tar.bz2
Checksums-Sha256:
 d533fb1a6bda9986b0f7e323af9493dc912131d655885d5c94388eb211193d4e 2360 
nfs-utils_1.3.4-2.1.dsc
 63b0fdead8e46cd4e3576ae0e557a3ba27f3d41367b61beead9659c3cdeca11f 40882 
nfs-utils_1.3.4-2.1.debian.tar.bz2
Files:
 0d6d899a75bdf8155c02ecc3ca17d5f9 2360 net standard nfs-utils_1.3.4-2.1.dsc
 e17b1f3b74324ce888bd4b98fd053954 40882 net standard 
nfs-utils_1.3.4-2.1.debian.tar.bz2

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAljP9WQACgkQC8R9xk0T
Uwbb6RAAo6xnIrpdSWhV53oablwfvvjVjyNPDGTqKtZFvoSVb+0Gamftmad0kok/
+EA2Dl1umkLYsmYDPglT300EPp/Pc/VBJF4iDkY+rayZgWCPOQlwpBUUJcxMwz6K
DmIauq7b/444jrejUv2GHaCPexzscTT3h5PUl780dBCbUbUp4cGoYAVLhk2GwxlP
HU2wyM9aes6nEo6gH/pG7Jhg3T+umZ6jMWFXv6SjLrz/uejG9BB9PJuJPtGKuXt6
v3LpHIZ/eAJwa1EfTfKIfyIpMd9ZcAWeXx6EeMLO8aLsCSlpoKSG5yVVHlushP1D
GzkQ8IVJRJ1M3BkJylrmDuyfuG9Aph8ZIXZwWVY1U6I8GoaBP3qJiWBMd3GubK76
xECw0PDCmNTjIkrjwyuc5vJXlrPNvLdSC2cxUhYXEL4MPNgJFokq/PzQ2CXqZEmc
FGXm1Ku90OgHnjPmcYFxtaFgE1r4cwRTdS09K7qFEmxcPsjD1dxm1Jr2MJsdPXYR
OBPAA3Y/y0BaIS68k4JKqtK7v76tGM+4ly1yPaJSa4fsenTqbR5Di21McmpM1Tmb
Wcul5BfODMYAYa5AN1uKcsEv3WvZbHqF/0MllISsBL547e9DPiWKAbW18PT229FB
joWzj7XEABgSwX4UFo/i9YddLzJ6u4THIFgPfH/WQOKKvPd47bE=
=Jvcv
-END PGP SIGNATURE End Message ---

Bug#858626: libllvm-3.8-ocaml-dev: Package is empty

[Sylvestre Ledru]

Le 24/03/2017 à 17:04, Cyril Soldani a écrit :
> It looks like this folder is missing since `libllvm-3.6-ocaml-dev`, and
> is still missing in `libllvm-3.9-ocaml-dev`. Last version containing it
> was `libllvm-3.5-ocaml-dev`, but it is not installable on `stretch`.
>
Thanks!
As it has been in this state for a while and nobody complained about,
I will probably just remove it from the packaging...

S

Bug#858725: [src:gitlab] FTBFS for /vendor/assets/javascripts/fuzzaldrin-plus.js and incomplete copyright

[Bastien ROUCARIÈS]

Package: src:gitlab
Version: 8.13.11+dfsg-8
Severity: serious

/vendor/assets/javascripts/fuzzaldrin-plus.js  is a concatenation of few files.

Moreover copyright file lack some part of copyright of this file.

I suppose moreover that some concatenation has lost some part of license and 
author

Searching indentical code on codesearch give a few hit

Bastien

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

Bug#857396: Pending fixes for bugs in the open-font-design-toolkit package

[pkg-fonts-devel]

tag 857396 + pending
thanks

Some bugs in the open-font-design-toolkit package are closed in
revision c18a050331ccee4e989e9c163a8a2ada4354a2da in branch 'master'
by Ivo De Decker

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-fonts/open-font-design-toolkit.git;a=commitdiff;h=c18a050

Commit message:

Import Debian version 1.6+nmu1

open-font-design-toolkit (1.6+nmu1) unstable; urgency=medium

  * Non-maintainer upload.
  * Merge changes from 1.5.1 upload, which got dropped accidentally in the 
1.6
upload (Closes: #857396)

Processed: Pending fixes for bugs in the open-font-design-toolkit package

[Debian Bug Tracking System]

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

> tag 857396 + pending
Bug #857396 {Done: Ivo De Decker } [open-font-design-toolkit] 
open-font-design-toolkit: Depends on RC buggy fontmatrix, which is not in 
testing
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#809625: Upload and maintainer address change

[Tobias Frost]

Hallo Drake,

I've checked with FTP Masters on #debian-ftp and appearantly the GPG
signature was wrong. For example:

Dec 19 09:55:39 GnuPG signature check failed on empire-
hub_1.0.2.2_amd64.changes
Dec 19 09:55:39 (Exit status 2)
Dec 19 09:55:39 /empire-hub_1.0.2.2_amd64.changes has bad PGP/GnuPG
signature!

Maybe check if you used the right key?

--
tobi

Processed: Re: dafny: FTBFS

[Debian Bug Tracking System]

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

> retitle 852645 dafny: FTBFS: The type or namespace name `IToken' could not be 
> found. Are you missing an assembly reference?
Bug #852645 [src:dafny] dafny: FTBFS
Changed Bug title to 'dafny: FTBFS: The type or namespace name `IToken' could 
not be found. Are you missing an assembly reference?' from 'dafny: FTBFS'.
> thanks
Stopping processing here.

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

Processed: Re: /usr/bin/leo: throws HTTP 404

[Debian Bug Tracking System]

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

> retitle 857238 /usr/bin/leo: throws HTTP 404 (needs update to new remote API)
Bug #857238 [libwww-dict-leo-org-perl] /usr/bin/leo: throws HTTP 404
Changed Bug title to '/usr/bin/leo: throws HTTP 404 (needs update to new remote 
API)' from '/usr/bin/leo: throws HTTP 404'.
> thanks
Stopping processing here.

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

Bug#858502: diff NMU for openmama_2.2.2.1-11.1

[Anton Gladky]

tags 858502 +pending +patch
thanks

Dear maintainer,

I have prepared an NMU (versioned as 2.2.2.1-11.1) and
uploaded to DELAYED/5.

Please fell free to tell me if I should delay it longer, cancel
or reschedule.

Diff is attached.

Best regards

Anton


nmu.debdiff
Description: Binary data

Processed: diff NMU for openmama_2.2.2.1-11.1

[Debian Bug Tracking System]

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

> tags 858502 +pending +patch
Bug #858502 [libmama-dev] libmama-dev: missing Depends: libwombatcommoncpp0, 
libmamaavis0, libmamacpp0
Added tag(s) pending.
Bug #858502 [libmama-dev] libmama-dev: missing Depends: libwombatcommoncpp0, 
libmamaavis0, libmamacpp0
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: diff NMU for sanlock_3.3.0-2.1

[Debian Bug Tracking System]

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

> tags 858500 +pending +patch
Bug #858500 [libsanlock-dev] libsanlock-dev: missing Depends: libsanlock1 (= 
${binary:Version})
Added tag(s) pending.
Bug #858500 [libsanlock-dev] libsanlock-dev: missing Depends: libsanlock1 (= 
${binary:Version})
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#858500: diff NMU for sanlock_3.3.0-2.1

[Anton Gladky]

tags 858500 +pending +patch
thanks

Dear maintainer,

I have prepared an NMU (versioned as 3.3.0-2.1) and
uploaded to DELAYED/5.

Please fell free to tell me if I should delay it longer, cancel
or reschedule.

Diff is attached.

Best regards


nmu.debdiff
Description: Binary data