Bug#891819: dovecot: CVE-2017-14461: rfc822_parse_domain information leak vulnerability

[Salvatore Bonaccorso]

Source: dovecot
Version: 1:2.2.13-11
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for dovecot.

CVE-2017-14461[0]:
rfc822_parse_domain information leak vulnerability

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14461
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14461

Regards,
Salvatore

Processed: severity of 891786 is grave

[Debian Bug Tracking System]

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

> severity 891786 grave
Bug #891786 [src:isc-dhcp] isc-dhcp: CVE-2018-5732: A specially constructed 
response from a malicious server can cause a buffer overflow in dhclient
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#889608: Continuing to get core dumps with man-db

[John Sivak]

We have a winner. That build works on my system as well.

Let me know if you need any other assistance and thanks for tracking
down the issue.

John

On 02/28/2018 08:13 AM, Colin Watson wrote:
> On Sun, Feb 25, 2018 at 07:13:52PM -0500, John Sivak wrote:
>> On 02/25/2018 07:06 AM, Colin Watson wrote:
>>> Ah, right, no explicit path there. Can you try git master again
>>> (https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=122802046452c5d900a3d74b643d2089c4df58d2)?
>> Still not working. :(
>>
>> Stack trace attached for: strace -f -o man.trace -s 1024 man man
> OK, I finally cracked and installed a trial setup in a VM so that I
> could iterate more quickly.
> https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=eb88d394e8c3bed3953bbeb106f0dc5996c18621
> now works for me - please confirm.
>
> Thanks,
>

Processed: libmstoolkit82: symbols file generates dependencies that cannot be fulfilled

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:comet-ms
Bug #891805 [libmstoolkit82] libmstoolkit82: symbols file generates 
dependencies that cannot be fulfilled
Added indication that 891805 affects src:comet-ms

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

Bug#891805: libmstoolkit82: symbols file generates dependencies that cannot be fulfilled

[Adrian Bunk]

Package: libmstoolkit82
Version: 82-2
Severity: serious
Control: affects -1 src:comet-ms

The following packages have unmet dependencies:
 comet-ms : Depends: libmstoolkit82 (>= 82.0.0) but it is not going to be 
installed


libmstoolkit dropped the .0.0 from the version,
but the symbols file generates 82.0.0 dependencies.

Bug#871229: /usr/sbin/update-grub: running update-grub segment faults

[Sven Hartge]

On Wed, 28 Feb 2018 22:37:41 +0100 Martin Zobel-Helas 
wrote:

> I get segfaults when running update-grub on my Lenovo Thinkpad x270
> running Debian unstable from today.

I see the same on my Dell Precision 7520.

> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/usr/sbin/grub-probe --device /dev/nvme0n1p1 
> --target=hints_string'.
> Program terminated with signal SIGSEGV, Segmentation fault.

Interesting thing is: we both use a NVME-SSD on an AMD64 system.

My other systems, one 32bit-on-AMD64 on normal SATA disks and one pure
AMD64 on normal SATA disks works without segfault, only the NVME one
shows problems.

Grüße,
Sven.





signature.asc
Description: OpenPGP digital signature

Bug#891798: CVE-2017-3158

[Moritz Muehlenhoff]

Source: guacamole-client
Severity: grave
Tags: security

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3158

Cheers,
Moritz

Processed: Re: Bug#866731: gnss-sdr: Bogus build dependency on libc6

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #866731 {Done: Adrian Bunk } [src:gnss-sdr] gnss-sdr: 
Bogus build dependency on libc6
Severity set to 'important' from 'serious'

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

Bug#866731: gnss-sdr: Bogus build dependency on libc6

[Adrian Bunk]

Control: severity -1 important

On Sat, Jul 01, 2017 at 11:37:11AM +0200, John Paul Adrian Glaubitz wrote:
> Source: gnss-sdr
> Version: 0.0.8-1
> Severity: serious
> Justification: breaks build dependencies
> 
> Hello!
> 
> src:gnss-sdr has a bogus build dependency on libc6 which is not
> allowed for two reasons:
> 
>  a) libc6 is not the correct package required for building
> gnss-sdr, libc6-dev would be.
>  b) libc6-dev is also pulled in through "build-essential"
> which is always present during build.
> 
> Please remove "libc6" from Build-Depends completely. It blocks
> the build on multiple architectures like alpha, kfreebsd-* and
> hurd-*.
> 
> Please refer to Debian Policy, section 7.7 [1].

I am lowering the severity of this bug:

This was clearly a bug (and already fixed in unstable),
but it is not a release critical issue that would cause
problems on any release architectures and where the fix
should be backported to stretch.

> Thanks,
> Adrian
>...

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#891517: marked as done (ros-ros-comm FTBFS: error: 'logError' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 20:56:48 +
with message-id 
and subject line Bug#891517: fixed in ros-ros-comm 1.13.5+ds1-2
has caused the Debian Bug report #891517,
regarding ros-ros-comm FTBFS: error: 'logError' was not declared in this scope
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.)


-- 
891517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-ros-comm
Version: 1.13.5+ds1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=ros-ros-comm=sid

...
/<>/ros-ros-comm-1.13.5+ds1/tools/rosbag_storage/src/bz2_stream.cpp: 
In member function 'virtual void rosbag::BZ2Stream::read(void*, size_t)':
/<>/ros-ros-comm-1.13.5+ds1/tools/rosbag_storage/src/bz2_stream.cpp:130:13:
 error: 'logError' was not declared in this scope
 logError("unused data already available");
 ^~~~
/<>/ros-ros-comm-1.13.5+ds1/tools/rosbag_storage/src/bz2_stream.cpp:130:13:
 note: suggested alternative: 'strerror'
 logError("unused data already available");
 ^~~~
 strerror
make[3]: *** 
[tools/rosbag_storage/CMakeFiles/rosbag_storage.dir/build.make:138: 
tools/rosbag_storage/CMakeFiles/rosbag_storage.dir/src/bz2_stream.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: ros-ros-comm
Source-Version: 1.13.5+ds1-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-ros-comm 
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: Wed, 28 Feb 2018 20:23:08 +0100
Source: ros-ros-comm
Binary: libroscpp-dev libroscpp1d ros-roscpp-msgs libroscpp-msgs-dev 
python-roscpp-msgs cl-roscpp-msgs python-rospy librosbag-dev librosbag3d 
python-rosbag librosbag-storage-dev librosbag-storage2d librosconsole-dev 
librosconsole2d python-rosgraph python-roslaunch python-rosmaster python-rosmsg 
python-rosnode rosout python-rosparam python-rosservice python-rostest 
librostest-dev python-rostopic ros-topic-tools-srvs libtopic-tools-dev 
libtopic-tools1d topic-tools python-topic-tools cl-topic-tools 
libmessage-filters-dev libmessage-filters1d python-message-filters 
python-roswtf libroslz4-dev libroslz4-1d python-roslz4 libxmlrpcpp-dev 
libxmlrpcpp1d
Architecture: source
Version: 1.13.5+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 cl-roscpp-msgs - Header for roscpp messages, LISP
 cl-topic-tools - LISP library for working with Robot OS topics
 libmessage-filters-dev - Development files for Robot OS message-filters
 libmessage-filters1d - Library for Robot OS message-filters
 librosbag-dev - Tools for recording from and playing back to Robot OS topics
 librosbag-storage-dev - Development files for librosbag_storage
 librosbag-storage2d - Robot OS library for rosbag_storage
 librosbag3d - Library for recording from and playing back to Robot OS topics
 librosconsole-dev - Development files for librosconsole
 librosconsole2d - library for librosconsole
 libroscpp-dev - Robot OS development files for libroscpp
 libroscpp-msgs-dev - Robot OS header for roscpp messages
 libroscpp1d - Robot OS client library
 libroslz4-1d - library implementing lz4 for Robot OS
 libroslz4-dev - development files for libroslz4
 librostest-dev - Development files for rostest (Robot OS)
 libtopic-tools-dev - development files for libtopic-tools (Robot OS)
 libtopic-tools1d - library for messing with Robot OS topics
 libxmlrpcpp-dev - development files for Robot OS libxmlrpcpp
 libxmlrpcpp1d - Robot OS version of xml-rpc protocol library
 python-message-filters - Python library for Robot OS message-filters
 python-rosbag - Python tools for recording from and playing back to Robot OS 
topi
 python-roscpp-msgs - Header for 

Bug#891516: marked as done (ros-geometric-shapes FTBFS: error: 'logError' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 20:53:54 +
with message-id 
and subject line Bug#891516: fixed in ros-geometric-shapes 0.5.3-2
has caused the Debian Bug report #891516,
regarding ros-geometric-shapes FTBFS: error: 'logError' was not declared in 
this scope
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.)


-- 
891516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-geometric-shapes
Version: 0.5.3-1
Severity: serious

https://buildd.debian.org/status/package.php?p=ros-geometric-shapes=sid

...
/<>/src/body_operations.cpp: In function 'bodies::Body* 
bodies::createBodyFromShape(const shapes::Shape*)':
/<>/src/body_operations.cpp:62:7: error: 'logError' was not 
declared in this scope
   logError("Creating body from shape: Unknown shape type %d", 
(int)shape->type);
   ^~~~
--- End Message ---
--- Begin Message ---
Source: ros-geometric-shapes
Source-Version: 0.5.3-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated 
ros-geometric-shapes 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: Wed, 28 Feb 2018 20:27:35 +0100
Source: ros-geometric-shapes
Binary: libgeometric-shapes-dev libgeometric-shapes2d
Architecture: source
Version: 0.5.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 libgeometric-shapes-dev - Robot OS geometric_shapes package - development files
 libgeometric-shapes2d - Robot OS geometric_shapes package
Closes: 891516
Changes:
 ros-geometric-shapes (0.5.3-2) unstable; urgency=medium
 .
   [ Jochen Sprickerhof ]
   * Update Vcs URLs to salsa.d.o
 .
   [ Jose Luis Rivero ]
   * Added patch to solve problems with console-bridge 0.4 (Closes: #891516)
Checksums-Sha1:
 39ec476f11fbf13e10c4ee559d819d198f185794 2541 ros-geometric-shapes_0.5.3-2.dsc
 fa41c7c09e5284bf1959439625449789fad09bd6 5516 
ros-geometric-shapes_0.5.3-2.debian.tar.xz
 def13cd2f243ae331440ef8f51f39dbf47f641a0 7525 
ros-geometric-shapes_0.5.3-2_source.buildinfo
Checksums-Sha256:
 65ef58c01fd1b4dac5912b3971ebc5add27119e70d4cfa49ea7027ed8a33a400 2541 
ros-geometric-shapes_0.5.3-2.dsc
 b81987d06a9cb794d5ca7c22467dc2930c880bea54779a7366c843a4d40361b7 5516 
ros-geometric-shapes_0.5.3-2.debian.tar.xz
 87ebc1821656c4cd7b886d8693e24e450cd15b2b50f5b491b705f54a1064027b 7525 
ros-geometric-shapes_0.5.3-2_source.buildinfo
Files:
 c4ab76b674b28ef7452efee6ed1e1498 2541 libs optional 
ros-geometric-shapes_0.5.3-2.dsc
 e1d813eb38d28a4f9384ccaf05df270c 5516 libs optional 
ros-geometric-shapes_0.5.3-2.debian.tar.xz
 6c480db46fd2c8ea252fcb03a020a53f 7525 libs optional 
ros-geometric-shapes_0.5.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlqXCJMUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDOoaxAAgOpSHTMttmtQMBngh2PAHRAxn//G
1TzBLJlom/duqA+nm3cgB9pKiCzehx7jE2luS8gZm/+mZqePyl/LbGE4NIQxr7Hc
3+bkib/VFmnH6faB86JhqXX0OFzw2yWRTU6/t+idiJ5kEhQgzwfw2pTaZfz+5OjF
q4RxGm63EKVmlebyuJTz0uzVoLOEoyLbyDY5Tp8aduYtL6Q5gzgjiRRrzaF182mW
jDYy5Fy+nWsmpVCyl3jTdz6+bjvdJ+ycoITdTyb/7IeL00ggckQPIwpemZC8n+uY
2OxFqYbwFRC0FSLIWznqxduMTf5uOlt9ltCZ3STfIy5Pz5HAcK8hhlJx6VoR9Xwp
x8lpAsXdS7zf4lMNaPhSp9WMh8AIsEYg0z9bw7lrsibLux1VPCYLiuCQR9Q1mSMA
OF2cDSobRmk4B/B7fseZU1+CITrXderbgiYmq4dhYFOEHDj9OhS6Ebffj1EchnV7
XXvKaP4PqRMR+11IFq3G/glcjjWEycTOyL7zkXzMkKacMIuVRNA/AeUYXVlXoRpC
mmcfW3b56xW0sGqp+Eul+0sKwsVJztJCaNILjplxGn1FnVscJMKKSx7rZg6OTWbV
2dsmB5IJhMsTqYJsuk6f1wBSPxCYgQ8Etwz424SVOwesrZPcq2tYH4nKFkxkBBIj
/ORaOnnQF3ULcJY=
=SIk1
-END PGP SIGNATURE End Message ---

Bug#891518: marked as done (ros-geometry2 FTBFS: error: 'logWarn' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 19:50:31 +
with message-id 
and subject line Bug#891518: fixed in ros-geometry2 0.5.16-2
has caused the Debian Bug report #891518,
regarding ros-geometry2 FTBFS: error: 'logWarn' was not declared in this scope
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.)


-- 
891518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-geometry2
Version: 0.5.16-1
Severity: serious

https://buildd.debian.org/status/package.php?p=ros-geometry2=sid

...
/<>/tf2/src/buffer_core.cpp: In member function 'bool 
tf2::BufferCore::warnFrameId(const char*, const string&) const':
/<>/tf2/src/buffer_core.cpp:126:5: error: 'logWarn' was not 
declared in this scope
 logWarn("%s",ss.str().c_str());
 ^~~
/<>/tf2/src/buffer_core.cpp:134:5: error: 'logWarn' was not 
declared in this scope
 logWarn("%s",ss.str().c_str());
 ^~~
--- End Message ---
--- Begin Message ---
Source: ros-geometry2
Source-Version: 0.5.16-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-geometry2 
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: Wed, 28 Feb 2018 20:26:06 +0100
Source: ros-geometry2
Binary: libtf2-0d libtf2-dev python-tf2 libtf2-ros0d libtf2-ros-dev 
python-tf2-ros ros-tf2-msgs libtf2-msgs-dev python-tf2-msgs cl-tf2-msgs 
cl-tf2-srvs libtf2-sensor-msgs-dev python-tf2-sensor-msgs libtf2-bullet-dev 
libtf2-eigen-dev libtf2-geometry-msgs-dev python-tf2-geometry-msgs 
libtf2-kdl-dev python-tf2-kdl tf2-tools
Architecture: source
Version: 0.5.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 cl-tf2-msgs - Robot OS tf2 transform library messages - LISP
 cl-tf2-srvs - Robot OS tf2 transform library services - LISP
 libtf2-0d  - Robot OS tf2 transform library
 libtf2-bullet-dev - Robot OS tf2 transform library for Bullet - dev files
 libtf2-dev - Robot OS tf2 transform library - development files
 libtf2-eigen-dev - Robot OS tf2 transform library for Eigen - dev files
 libtf2-geometry-msgs-dev - Robot OS geometry messages for tf2 transform 
library - dev files
 libtf2-kdl-dev - Robot OS tf2 transform library using Orocos-KDL - dev files
 libtf2-msgs-dev - Robot OS messages for tf2 transform library - dev files
 libtf2-ros-dev - Robot OS binding for tf2 transform library - dev files
 libtf2-ros0d - Robot OS binding for tf2 transform library
 libtf2-sensor-msgs-dev - Small lib for ROS to transform sensor_msgs with tf2 - 
dev files
 python-tf2 - Robot OS tf2 transform library - Python
 python-tf2-geometry-msgs - Robot OS tf2 transform library for Bullet - Python
 python-tf2-kdl - Robot OS tf2 transform library using Orocos-KDL - Python
 python-tf2-msgs - Robot OS messages for tf2 transform library - Python
 python-tf2-ros - Robot OS binding for tf2 transform library - Python
 python-tf2-sensor-msgs - Robot OS sensor messages for tf2 transform library - 
Python
 ros-tf2-msgs - Robot OS messages for tf2 transform library - definitions
 tf2-tools  - Robot OS tool for tf2 transform library second generation
Closes: 891518
Changes:
 ros-geometry2 (0.5.16-2) unstable; urgency=medium
 .
   [ Jochen Sprickerhof ]
   * Update Vcs URLs to salsa.d.o
 .
   [ Jose Luis Rivero ]
   * Added patch to solve problems with console-bridge 0.4 (Closes: #891518)
Checksums-Sha1:
 13c285cab0adaee79ef6bc20dd022b6ab770774e 3859 ros-geometry2_0.5.16-2.dsc
 73826956392b204698f6c7f47820169535d21c86 7752 
ros-geometry2_0.5.16-2.debian.tar.xz
 a76396059c8a9d957d3ddf0c8d30fdf55866aa48 10617 
ros-geometry2_0.5.16-2_source.buildinfo
Checksums-Sha256:
 84c82b4656bee3c8b025fade9bb5dc26dbb1805e73c9433c41872f685d516faf 3859 
ros-geometry2_0.5.16-2.dsc
 

Bug#891662: marked as done (libcrypto++1: contains libcryptopp.so.6)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 19:49:59 +
with message-id 
and subject line Bug#891662: fixed in libcrypto++ 6.1.0-2
has caused the Debian Bug report #891662,
regarding libcrypto++1: contains libcryptopp.so.6
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.)


-- 
891662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcrypto++1
Version: 6.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libcrypto++1.
  Preparing to unpack .../libcrypto++1_6.1.0-1_amd64.deb ...
  Unpacking libcrypto++1 (6.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcrypto++1_6.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libcryptopp.so.6', which is 
also in package libcrypto++6 5.6.4-8
  Errors were encountered while processing:
   /var/cache/apt/archives/libcrypto++1_6.1.0-1_amd64.deb

libcryptopp.so.6 does not belong into this package!

Is the SOVERSION 6 => 1 change really a wise idea?
What happens after the next 5 SOVERSION bumps?


cheers,

Andreas


libcrypto++6=5.6.4-8_libcrypto++1=6.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libcrypto++
Source-Version: 6.1.0-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated libcrypto++ 
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: Tue, 27 Feb 2018 21:31:37 +
Source: libcrypto++
Binary: libcrypto++1 libcrypto++-dev libcrypto++-utils libcrypto++-doc
Architecture: source amd64 all
Version: 6.1.0-2
Distribution: experimental
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libcrypto++-dev - General purpose cryptographic library - C++ development
 libcrypto++-doc - General purpose cryptographic library - documentation
 libcrypto++-utils - General purpose cryptographic library - utilities and data 
files
 libcrypto++1 - General purpose cryptographic library - shared library
Closes: 879822 880637 891662
Changes:
 libcrypto++ (6.1.0-2) experimental; urgency=medium
 .
   * Update library compatibility symlink (closes: #891662).
   * Remove debug_info from libcrypto++.a library (closes: #880637).
   * Make the package multiarch (closes: #879822).
Checksums-Sha1:
 518d4ccdd15d7e1168135fb43ab9b8515cc1909e 1992 libcrypto++_6.1.0-2.dsc
 3c610a9ee53b0d5d8803a90cf9fa844920c2798f 21876 
libcrypto++_6.1.0-2.debian.tar.xz
 1a65253b6d37818a1c204346e516a0d475a5aa9a 1660936 
libcrypto++-dev_6.1.0-2_amd64.deb
 b3efeeed57ff2f248cb01132535f43adb945f647 4801032 
libcrypto++-doc_6.1.0-2_all.deb
 cff52dd9f53d4346b37b5bb5244e88c6eadde103 5154332 
libcrypto++-utils-dbgsym_6.1.0-2_amd64.deb
 b7d1765e5c0bedb87cfca5ee41a4a38253badece 5453912 
libcrypto++-utils_6.1.0-2_amd64.deb
 ef6527bb6672d440e6cbf468f69bfac59fe17327 9005308 
libcrypto++1-dbgsym_6.1.0-2_amd64.deb
 bdca6ee8db6055783fdcf82f8ee0282ec42b3d50 1030140 libcrypto++1_6.1.0-2_amd64.deb
 b24a61e06fac5901166124b6bcf58143d0e5f27e 7898 
libcrypto++_6.1.0-2_amd64.buildinfo
Checksums-Sha256:
 9f764e25e46646e8699f1060f62e1f3741b9dd86c1fe5347a95dc3b20f874c08 1992 
libcrypto++_6.1.0-2.dsc
 67ed2164741cc92561f89f20cf9694f7b4772675fbf562329af0dec381397d24 21876 
libcrypto++_6.1.0-2.debian.tar.xz
 9989a1d6c57075009971b53ec2367346337f52aa9ab5993b3264fccb7e38f776 

Bug#871229:

[Beren Minor]

Hello,

I have the same issue, with a NVME drive as well.

It looks like the segmentation fault comes from grub-probe, when
called with --target=hints_string. Attached grub-probe.log is the
output of the command that leads to a segfault.

Trying with gdb doesn't give much more information, the call stack is:

Program received signal SIGSEGV, Segmentation fault.
__strcat_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strcat-sse2-unaligned.S:46
46../sysdeps/x86_64/multiarch/strcat-sse2-unaligned.S: No such
file or directory.
(gdb) bt
#0  __strcat_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strcat-sse2-unaligned.S:46
#1  0xdd38 in ?? ()
#2  0xca89 in ?? ()
#3  0xbe76 in ?? ()
#4  0x777d7f2a in __libc_start_main (main=0xbd10,
argc=5, argv=0x7fffdf88, init=, fini=, rtld_fini=, stack_end=0x7fffdf78) at
../csu/libc-start.c:310
#5  0xbfea in ?? ()

I'm not sure how critical it is either but as a workaround, it's
possible to roll back to testing versions of the grub-efi-amd64-bin,
grub-efi-amd64, grub2-common packages.

Cheers,
--
Beren Minor
$ sudo /usr/sbin/grub-probe --device /dev/nvme0n1p2 --target=hints_string --verbose
/usr/sbin/grub-probe: info: cannot open `/boot/grub/device.map': No such file or directory.
/usr/sbin/grub-probe: info: /dev/nvme0n1p2 is not present.
/usr/sbin/grub-probe: info: Looking for /dev/nvme0n1p2.
/usr/sbin/grub-probe: info: /dev/nvme0n1 is a parent of /dev/nvme0n1p2.
/usr/sbin/grub-probe: info: /dev/nvme0n1p2 starts from 1050624.
/usr/sbin/grub-probe: info: opening the device hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: drive = 0.
/usr/sbin/grub-probe: info: the size of hostdisk//dev/nvme0n1 is 2000409264.
/usr/sbin/grub-probe: info: drive = 0.
/usr/sbin/grub-probe: info: the size of hostdisk//dev/nvme0n1 is 2000409264.
/usr/sbin/grub-probe: info: Scanning for DISKFILTER devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid1x devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid09 devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid09_be devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for dmraid_nv devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for ldm devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: scanning hostdisk//dev/nvme0n1 for LDM.
/usr/sbin/grub-probe: info: no LDM signature found.
/usr/sbin/grub-probe: info: Scanning for lvm devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: Scanning for DISKFILTER devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid1x devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid09 devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid09_be devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for dmraid_nv devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for ldm devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: scanning hostdisk//dev/nvme0n1 for LDM.
/usr/sbin/grub-probe: info: no LDM signature found.
/usr/sbin/grub-probe: info: Scanning for lvm devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: Scanning for DISKFILTER devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid1x devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid09 devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid09_be devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for dmraid_nv devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for ldm devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: scanning hostdisk//dev/nvme0n1 for LDM.
/usr/sbin/grub-probe: info: no LDM signature found.
/usr/sbin/grub-probe: info: Scanning for lvm devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: Scanning for DISKFILTER devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid1x devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid09 devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for mdraid09_be devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for dmraid_nv devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: Scanning for ldm devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: info: scanning hostdisk//dev/nvme0n1 for LDM.
/usr/sbin/grub-probe: info: no LDM signature found.
/usr/sbin/grub-probe: info: Scanning for lvm devices on disk hostdisk//dev/nvme0n1.
/usr/sbin/grub-probe: 

Bug#891778: zatacka crashes on map selection

[Adrian Bunk]

Package: zatacka
Version: 0.1.8-5
Severity: serious

Start the game and press m

Backtrace:
#0  0x76da8a52 in __readdir (dirp=dirp@entry=0x0)
at ../sysdeps/posix/readdir.c:44
#1  0x7084 in menu (screen=0x557a02e0) at fx.cpp:425
#2  0x5628 in main (argc=, argv=)
at main.cpp:40

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[John Kozak]

Andreas Beckmann writes:

> On 2018-02-28 14:39, John Kozak wrote:
>> Thanks - one more thing: on a reboot (yes, I should have checked this
>> before filing an all-clear!) X didn't start but was fixed by
>> `update-glx` (changing from 0 to 2):
>>
>>   $ sudo update-glx --config nvidia
>>   There are 2 choices for the alternative nvidia (providing 
>> /usr/lib/nvidia/nvidia).
>>
>> SelectionPath  Priority   Status
>>   
>> 0/usr/lib/nvidia/current384   auto mode
>> 1/usr/lib/nvidia/current384   manual mode
>>   * 2/usr/lib/nvidia/legacy-340xx   340   manual mode
>>
>> /usr/lib/nvidia/current is an empty directory.
>
> If that directory and the alternative still exist, some packages from
> the current driver must still be installed. Or you found another bug.
>
> Please send the output of
>
> dpkg -l | grep nvidia

ii  glx-alternative-nvidia0.8.3 
   amd64allows the selection of NVIDIA as GLX provider
ii  libegl-nvidia0:amd64  384.111-4 
   amd64NVIDIA binary EGL library
ii  libegl-nvidia0:i386   384.111-4 
   i386 NVIDIA binary EGL library
ic  libegl1-nvidia:amd64  340.96-1  
   amd64NVIDIA binary EGL libraries
ii  libegl1-nvidia-legacy-340xx:amd64 340.106-2 
   amd64NVIDIA binary EGL library (340xx legacy version)
ii  libegl1-nvidia-legacy-340xx:i386  340.106-2 
   i386 NVIDIA binary EGL library (340xx legacy version)
ii  libgl1-nvidia-glvnd-glx:i386  384.111-4 
   i386 NVIDIA binary OpenGL/GLX library (GLVND variant)
ic  libgl1-nvidia-glx:amd64   340.96-1  
   amd64NVIDIA binary OpenGL libraries
ii  libgl1-nvidia-legacy-340xx-glx:amd64  340.106-2 
   amd64NVIDIA binary OpenGL/GLX library (340xx legacy 
version)
ii  libgl1-nvidia-legacy-340xx-glx:i386   340.106-2 
   i386 NVIDIA binary OpenGL/GLX library (340xx legacy 
version)
ii  libgles-nvidia2:i386  384.111-4 
   i386 NVIDIA binary OpenGL|ES 2.x library
ic  libgles1-nvidia:amd64 340.96-1  
   amd64NVIDIA binary OpenGL|ES 1.x libraries
ii  libgles1-nvidia-legacy-340xx:amd64340.106-2 
   amd64NVIDIA binary OpenGL|ES 1.x library (340xx legacy 
version)
ii  libgles1-nvidia-legacy-340xx:i386 340.106-2 
   i386 NVIDIA binary OpenGL|ES 1.x library (340xx legacy 
version)
ic  libgles2-nvidia:amd64 340.96-1  
   amd64NVIDIA binary OpenGL|ES 2.x libraries
ii  libgles2-nvidia-legacy-340xx:amd64340.106-2 
   amd64NVIDIA binary OpenGL|ES 2.x library (340xx legacy 
version)
ii  libgles2-nvidia-legacy-340xx:i386 340.106-2 
   i386 NVIDIA binary OpenGL|ES 2.x library (340xx legacy 
version)
ii  libglx-nvidia0:amd64  384.111-4 
   amd64NVIDIA binary GLX library
ii  libglx-nvidia0:i386   384.111-4 
   i386 NVIDIA binary GLX library
ii  libnvidia-cfg1:i386   384.111-4 
   i386 NVIDIA binary OpenGL/GLX configuration library
ic  libnvidia-compiler:amd64  340.96-1  
   amd64NVIDIA runtime compiler library
ii  libnvidia-egl-wayland1:amd64  384.111-4 
   amd64NVIDIA binary Wayland EGL external platform library
ii  libnvidia-egl-wayland1:i386   384.111-4 
   i386 NVIDIA binary Wayland EGL external platform library
ii  libnvidia-eglcore:amd64   384.111-4 
   amd64NVIDIA binary EGL core libraries
ii  libnvidia-eglcore:i386384.111-4 
   i386 NVIDIA binary EGL core libraries
ii  libnvidia-glcore:amd64384.111-4 
   amd64NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-glcore:i386 384.111-4 

Bug#891693: marked as done (rakudo: fails to upgrade from 'testing' - trying to overwrite /usr/lib/perl6/runtime/dynext/libperl6_ops_moar.so)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 18:04:48 +
with message-id 
and subject line Bug#891693: fixed in rakudo 2018.02.1-2
has caused the Debian Bug report #891693,
regarding rakudo: fails to upgrade from 'testing' - trying to overwrite 
/usr/lib/perl6/runtime/dynext/libperl6_ops_moar.so
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.)


-- 
891693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rakudo
Version: 2018.02.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../rakudo_2018.02.1-1_amd64.deb ...
  Unpacking rakudo (2018.02.1-1) over (2017.06-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/rakudo_2018.02.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/perl6/runtime/dynext/libperl6_ops_moar.so', 
which is also in package rakudo-lib 2017.06-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/rakudo_2018.02.1-1_amd64.deb


cheers,

Andreas


rakudo_2018.02.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rakudo
Source-Version: 2018.02.1-2

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

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated rakudo 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: Wed, 28 Feb 2018 17:17:12 +0100
Source: rakudo
Binary: rakudo
Architecture: source
Version: 2018.02.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Description:
 rakudo - Perl 6 implementation on top of Moar virtual machine
Closes: 891693
Changes:
 rakudo (2018.02.1-2) unstable; urgency=medium
 .
   * control: breaks and replaces rakudo-lib (Closes: #891693)
Checksums-Sha1:
 5c1d1b6d57a394d87f6cd1e43a245ce0bec99d81 2366 rakudo_2018.02.1-2.dsc
 8254f97372e44635f6e93ee176dd99ba74de1ad1 13076 rakudo_2018.02.1-2.debian.tar.xz
 e78c5ae4a740556c1b324ecf3d1764bcbcd1037a 5732 
rakudo_2018.02.1-2_source.buildinfo
Checksums-Sha256:
 1c3740f24a05b5792bdaee8fc7f6b3dc9716fcd7f034f8492f0985e62f2f3d62 2366 
rakudo_2018.02.1-2.dsc
 727699da662a257ff6e11d46f9f693dba55014cdd87c33c4607aae1360d4eab8 13076 
rakudo_2018.02.1-2.debian.tar.xz
 cc6d09d723077b0013987f9a649385f2b1c2dffa6d79449b3ffada44f1aba8f3 5732 
rakudo_2018.02.1-2_source.buildinfo
Files:
 0a64d856303bd12761c72ee35865bd0a 2366 interpreters optional 
rakudo_2018.02.1-2.dsc
 385e756ea7f99ef83f625d79e2b126f2 13076 interpreters optional 
rakudo_2018.02.1-2.debian.tar.xz
 d40a5da29f8636b5ae06836649a88092 5732 interpreters optional 
rakudo_2018.02.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAlqW6noACgkQwx9P2Umr
K2w46Q/8CytS+AkJgYd068TOi+FvYQOwgUMuv+8fWfQ2fRr303Sro6ODG5Atwl0d
08wz1MaDxri5alDF52AShHK96RyH8ahW4VOwzJzOrk7lxKyI970uTVRJO7pKlbxl
RBLXzBnyVfLB+fej39AVm56fTXMBg1g911WD0cFSn89RsPVjNPPtT9NFLV0GWRHN
1DXI6RuXZFtyg3O5uQra10q4dXh+DiTfIpAdxbe3L0A9jk+JSUsfQLmXwsd9oDLd
4J7Ctbeyu+oh46cGcpuXi4UOkzUJnyls+CuSVOVNoD3tlPD6tEC+W1EZDp1EOuH1
Sof1Q+y5W42zMiqyyldjGGo0SkTjIpjBXMAOaA+o65vqJtjvI2eNbns3xrA0vnKD
vH2xCXZVJvOp8twT4K2Iy79RJyN60cYR0k9twU/qD7Oyb7UH2fBGMqIiSQIkmc4v
IcqSnK7YTD3PEYqwCtKMFHXLixpgAlT0UD/eZ4RmznN/NNSQYO1iYuGjJtZxhlYD
fAMqJVw4boR0vp8bOE9lu8bU0L3gptHcFb41Vc6cyVcNfFLN3uvtS2K8Yptp5jYE

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[Andreas Beckmann]

On 2018-02-28 14:39, John Kozak wrote:
> Thanks - one more thing: on a reboot (yes, I should have checked this
> before filing an all-clear!) X didn't start but was fixed by
> `update-glx` (changing from 0 to 2):
> 
>   $ sudo update-glx --config nvidia
>   There are 2 choices for the alternative nvidia (providing 
> /usr/lib/nvidia/nvidia).
> 
> SelectionPath  Priority   Status
>   
> 0/usr/lib/nvidia/current384   auto mode
> 1/usr/lib/nvidia/current384   manual mode
>   * 2/usr/lib/nvidia/legacy-340xx   340   manual mode
> 
> /usr/lib/nvidia/current is an empty directory.

If that directory and the alternative still exist, some packages from
the current driver must still be installed. Or you found another bug.

Please send the output of

dpkg -l | grep nvidia

dpkg -S /usr/lib/nvidia/current

I suspect the nvidia-alternative package to be still installed (not the
-legacy-340xx one, that of course needs to be there), but that shouldn't
be possible after you purged nvidia-legacy-check.


Andreas

Bug#891298: marked as done (fis-gtm: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 16:19:29 +
with message-id 
and subject line Bug#891298: fixed in fis-gtm 6.3-003A-2
has caused the Debian Bug report #891298,
regarding fis-gtm: Incomplete debian/copyright?
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.)


-- 
891298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fis-gtm
Version: 6.3-003A-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Amul Shah 

Hi,

I just ACCEPTed fis-gtm from NEW but noticed it was missing 
attribution in debian/copyright for at least md5hash.c. Please
clarify the situation in debian/copyright.

This is not exhaustive so please check over the entire package 
carefully - especially that directory for code copies - and address
these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: fis-gtm
Source-Version: 6.3-003A-2

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

Debian distribution maintenance software
pp.
Amul Shah  (supplier of updated fis-gtm 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: Mon, 26 Feb 2018 04:57:51 -0500
Source: fis-gtm
Binary: fis-gtm fis-gtm-6.3-003a
Architecture: source
Version: 6.3-003A-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Amul Shah 
Description:
 fis-gtm- metapackage for the latest version of FIS-GT.M database
 fis-gtm-6.3-003a - package for FIS-GT.M database
Closes: 891298
Changes:
 fis-gtm (6.3-003A-2) unstable; urgency=medium
 .
   [ Amul Shah ]
   * Update debian/copyright to acknowledge the public domain status of
 sr_port/md5hash.c
 Closes: #891298
 .
   [ Andreas Tille ]
   * Drop some unneeded lintian overrides
Checksums-Sha1:
 68d6c43ac27586ffaa8acdc5a8008d1ecee26328 2418 fis-gtm_6.3-003A-2.dsc
 35a1d5550b1358606060d20777d52fc6e3b2fd9d 23340 fis-gtm_6.3-003A-2.debian.tar.xz
 e5b339ca795a55f61a0889c8535eab445f5fc899 14688 
fis-gtm_6.3-003A-2_source.buildinfo
Checksums-Sha256:
 5e2c50541308c29fe9435251b0b4bc4257c69d65440093bf3d210aef14379631 2418 
fis-gtm_6.3-003A-2.dsc
 35cfc3b54d698f1f7b6c967ee39b269f907bb335373b9595327ba1eaed30 23340 
fis-gtm_6.3-003A-2.debian.tar.xz
 85fb43da97e931ff0516055bfa1b09a2c1692516daf854d7a7cc8dccb052b5fc 14688 
fis-gtm_6.3-003A-2_source.buildinfo
Files:
 3ae470080274755c19d56192213d56ac 2418 database optional fis-gtm_6.3-003A-2.dsc
 e91546dd73174538581cbb53d5acd2d3 23340 database optional 
fis-gtm_6.3-003A-2.debian.tar.xz
 26cf94f77780c9144e99d37dd8a5c25b 14688 database optional 
fis-gtm_6.3-003A-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlqW0NEOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHaYQ//UWiQIA2lwZ5vL/+ik3jgJ/ua1lHh2UfHPufh
9EbVLMtG19YqK7rOT5Uzv8kJq7+fX0iNFMbPs0kb76+7houg7gWA2xmS61ZmrgZj
nLNZSVuM/7lHZMk+uZ8Vk6prb+0V5Jqinl4vOIUUteFGO78NCqEea613toyhQabm
jq7MwZFX1SaUI+uXMEVnHgJXF/7ZTjmo5xB6FYaN0zlqE6jXC2Ja2R5wSB2+W3Up
tXGIipUTMklqhPjmA+9MB9+x8KEWES3DHQ3YzXBTL8qZHvWiFACV57L9Wf+bO+Eu
uKDZtj1co0TF3AqZfFDs0Zk0sdj2JCZKHRQMYjmggKy4Zqlq7TACQc4G7CmJ8I5W
ELeW7kbu2EJNuZqFu+9wEcb6ST1y5nDp7iUM0LoANo4+d8lW9zUV1jvYrVhhKQHT
KygRQA/qrGCU6WEvge9IVMN8AqdVkvdF2Qgc1TaQZmKFiYrIOfs9KqO3cZTmrsgZ
wxcqSuKH6tCZJ6p2CPHNvDqleXKWP92w04tXLqrsSTji8HJMwMfLSRcH/0SKbK8H
KOUnYEH3HwmZihl5WuEZkHiI7qAwVfTNjXN6sOsyygxPK+BykwR+RY3f+SfXmF7b
gXDbt3N3iupWQVxaobd9n4bztiJcUmSsv5UOqeWt6sJUtpFoE5S1Xg3APZKU1aXR
ZBLpY4s=
=Bfvn
-END PGP SIGNATURE End Message ---

Bug#891766: marked as done (nfsv4: Unknown symbol __x86_indirect_thunk_r*)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 17:13:09 +0100
with message-id <20180228161309.6obxpnhqrnx4e...@shell.thinkmo.de>
and subject line Re: Bug#891766: nfsv4: Unknown symbol __x86_indirect_thunk_r*
has caused the Debian Bug report #891766,
regarding nfsv4: Unknown symbol __x86_indirect_thunk_r*
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.)


-- 
891766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.3.4-2.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since upgrading testing today ( 1:1.3.4-2.2 ) mount.nfs fails to mount
at least two other filesystems on other debian machines, also running
testing, and also upgraded today.

dmesg reports many unknown symbols:

[12995.092576] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[12995.093725] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[12995.094258] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[12995.098091] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[12995.098789] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[12995.099563] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[12995.106045] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[12995.106814] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[12995.123108] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[12995.129793] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[12995.130336] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[12995.131534] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[12995.135815] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[12995.136606] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[12995.137113] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[12995.137865] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[12995.144654] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[12995.145588] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[12995.152488] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[12995.153577] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[12995.154159] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[12995.158831] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[12995.161160] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[12995.161841] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[12996.548940] nfsv3: Unknown symbol __x86_indirect_thunk_rax (err 0)
-- [snip] --
[13062.548743] nfsd: last server has exited, flushing export cache
[13063.900550] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery 
directory
[13063.921390] NFSD: starting 90-second grace period (net b38d4b80)
[13089.924328] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[13089.925123] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[13089.925452] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[13089.926327] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[13089.926788] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[13089.927319] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[13089.927670] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[13089.928425] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[13089.934883] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[13089.935672] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[13089.936046] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[13089.937190] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[13089.937722] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[13089.938280] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[13089.938632] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[13089.939176] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[13089.945661] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
-- [snip] --

A typical mount failure:-

# mount.nfs -v shelf: /mnt/shelf/
mount.nfs: timeout set for Wed Feb 28 15:55:38 2018
mount.nfs: trying text-based options 
'vers=4.2,addr=192.168.0.8,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 
'vers=4.1,addr=192.168.0.8,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 
'vers=4.0,addr=192.168.0.8,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.0.8'
mount.nfs: prog 13, 

Bug#891693: rakudo: fails to upgrade from 'testing' - trying to overwrite /usr/lib/perl6/runtime/dynext/libperl6_ops_moar.so

[Dominique Dumont]

On Wed, 28 Feb 2018 03:22:29 +0100 Andreas Beckmann  wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

Indeed... I'll fix this asap.

Thanks for the report.

All the best

Dod

Bug#871229: /usr/sbin/update-grub: running update-grub segment faults

[IOhannes m zmoelnig]

Package: grub-common
Version: 2.02+dfsg1-2
Followup-For: Bug #871229

Dear Maintainer,

today, when running a regular unstable->unstable upgrade i also experienced a
segmentation fault.
i do these updates regularly, e.g. the last update of grub-common (2.02-2 ->
2.02+dfsg1-1) happened on "Sun, Feb 18 2018 22:55:00 +0100".
The last update related to the boot manager would be linux-image-amd64 (4.14+89
-> 4.15+90) on "Mon, Feb 26 2018 14:24:15 +0100".

I didn't notice any problems with prior upgrades.
Note that I haven't rebooted my machine after the linux-image upgrade 3 days
ago.

I'll attach the output of
   # sh -x /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg 2>&1 | tee 
/tmp/update-grub.log

i'm slightly afraid of having bricked my machine on the next reboot and would be
grateful if you could fix the problem asap.


-- Package-specific info:

*** BEGIN /proc/mounts
/dev/nvme0n1p2 / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/nvme0n1p1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  6bb42702-8f67-4600-806e-69c9309532af
else
  search --no-floppy --fs-uuid --set=root 6bb42702-8f67-4600-806e-69c9309532af
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=C
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  6bb42702-8f67-4600-806e-69c9309532af
else
  search --no-floppy --fs-uuid --set=root 6bb42702-8f67-4600-806e-69c9309532af
fi
insmod png
if background_image /usr/share/desktop-base/softwaves-theme/grub/grub-16x9.png; 
then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-6bb42702-8f67-4600-806e-69c9309532af' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  
6bb42702-8f67-4600-806e-69c9309532af
else
  search --no-floppy --fs-uuid --set=root 
6bb42702-8f67-4600-806e-69c9309532af
fi
echo'Loading Linux 4.15.0-1-amd64 ...'
linux   /boot/vmlinuz-4.15.0-1-amd64 
root=UUID=6bb42702-8f67-4600-806e-69c9309532af ro  quiet
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-4.15.0-1-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-6bb42702-8f67-4600-806e-69c9309532af' {
menuentry 'Debian GNU/Linux, with Linux 4.15.0-1-amd64' --class debian 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-4.15.0-1-amd64-advanced-6bb42702-8f67-4600-806e-69c9309532af' {

Bug#891766: nfsv4: Unknown symbol __x86_indirect_thunk_r*

[ael]

Package: nfs-common
Version: 1:1.3.4-2.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since upgrading testing today ( 1:1.3.4-2.2 ) mount.nfs fails to mount
at least two other filesystems on other debian machines, also running
testing, and also upgraded today.

dmesg reports many unknown symbols:

[12995.092576] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[12995.093725] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[12995.094258] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[12995.098091] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[12995.098789] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[12995.099563] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[12995.106045] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[12995.106814] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[12995.123108] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[12995.129793] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[12995.130336] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[12995.131534] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[12995.135815] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[12995.136606] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[12995.137113] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[12995.137865] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[12995.144654] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[12995.145588] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[12995.152488] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[12995.153577] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[12995.154159] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[12995.158831] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[12995.161160] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[12995.161841] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[12996.548940] nfsv3: Unknown symbol __x86_indirect_thunk_rax (err 0)
-- [snip] --
[13062.548743] nfsd: last server has exited, flushing export cache
[13063.900550] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery 
directory
[13063.921390] NFSD: starting 90-second grace period (net b38d4b80)
[13089.924328] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[13089.925123] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[13089.925452] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[13089.926327] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[13089.926788] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[13089.927319] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[13089.927670] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[13089.928425] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[13089.934883] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
[13089.935672] nfsv4: Unknown symbol __x86_indirect_thunk_r11 (err 0)
[13089.936046] nfsv4: Unknown symbol __x86_indirect_thunk_rax (err 0)
[13089.937190] nfsv4: Unknown symbol __x86_indirect_thunk_r13 (err 0)
[13089.937722] nfsv4: Unknown symbol __x86_indirect_thunk_r10 (err 0)
[13089.938280] nfsv4: Unknown symbol __x86_indirect_thunk_rcx (err 0)
[13089.938632] nfsv4: Unknown symbol __x86_indirect_thunk_r9 (err 0)
[13089.939176] nfsv4: Unknown symbol __x86_indirect_thunk_r8 (err 0)
[13089.945661] nfsv4: Unknown symbol __x86_indirect_thunk_r15 (err 0)
-- [snip] --

A typical mount failure:-

# mount.nfs -v shelf: /mnt/shelf/
mount.nfs: timeout set for Wed Feb 28 15:55:38 2018
mount.nfs: trying text-based options 
'vers=4.2,addr=192.168.0.8,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 
'vers=4.1,addr=192.168.0.8,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 
'vers=4.0,addr=192.168.0.8,clientaddr=192.168.0.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.0.8'
mount.nfs: prog 13, trying vers=3, prot=6
mount.nfs: trying 192.168.0.8 prog 13 vers 3 prot TCP port 2049
mount.nfs: prog 15, trying vers=3, prot=17
mount.nfs: trying 192.168.0.8 prog 15 vers 3 prot UDP port 34299
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
3910022   tcp836  sgi_fam
1000241   udp  47937  status
1000241   tcp  39807  status
133   tcp   2049  nfs
134   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
1002273   udp   2049

Bug#889811: gosa-encrypt-password is broken since PHP7.2's php-mcrypt removal

[Benjamin Zapiec]

Hello,


there are two new commits that should keep the goto plugin alive.

https://github.com/gosa-project/gosa-plugins-goto/commit/e7f4515574e7f76612470b0a398252db81dd1501

Therefore the DaemonEvent classes remain available and
I reworked the patch for the systems plugin.

https://github.com/gosa-project/gosa-plugins-systems/commit/cf34737977a97e0090e09390b209078dabdc77af




Best regards

-- 
Benjamin Zapiec  (System Engineer)
* GONICUS GmbH * Moehnestrasse 55 (Kaiserhaus) * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 245
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 55 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968





signature.asc
Description: OpenPGP digital signature

Bug#889811: gosa-encrypt-password is broken since PHP7.2's php-mcrypt removal

[Wolfgang Schweer]

On Wed, Feb 28, 2018 at 02:24:59PM +0100, Benjamin Zapiec wrote:
> the plugin uses gosaSupportDaemon for communication.
> This class uses mcrypt extension. That is the reason why
> it was removed.
> 
> Using an incompatible openssl implementation is useless
> so the only other option is to provide further support
> for the Daemon. But this is most likely not to happen.
> 
> Another way, I want to mention, is that it looks like
> the communication to the daemon can be unencrypted.
> This would allow the communication classes without
> mcrypt dependencies.
> 
> But even if I wouldn't strongly recommend not
> to use unencrypted network traffic, the daemon
> remains unsupported.
> 
> I don't know if there is a benefit in using this
> plugin without gosaSupportDaemon.
> 
> If you do think so, tell me and I may revert the commit.
> Do you have a running setup with gosa-si?
 
Thanks for the feedback.

Debian Edu doesn't use gosa-si. AFAIK there's no need for the 
gosaSupportDaemon as there's no communication happening; only the LDAP 
related goto plugin features are needed.

It would be nice if the goto plugin could live on, stripped down like 
that.

Wolfgang


signature.asc
Description: PGP signature

Bug#891741: marked as done (node-vue-resource FTBFS: webpack: Command not found)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 14:51:46 +
with message-id 
and subject line Bug#891741: fixed in node-vue-resource 1.3.4+dfsg-1
has caused the Debian Bug report #891741,
regarding node-vue-resource FTBFS: webpack: 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.)


-- 
891741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-vue-resource
Version: 1.3.4-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-vue-resource.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-vue-resource-1.3.4'
webpack --config debian/webpack.config.js src/index.js 
dist/vue-resource.common.js --target=web --output-library=VueResource 
--output-library-target=commonjs --module-bind 'js=babel-loader'
make[1]: webpack: Command not found
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 127
--- End Message ---
--- Begin Message ---
Source: node-vue-resource
Source-Version: 1.3.4+dfsg-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-vue-resource 
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, 28 Feb 2018 19:04:56 +0530
Source: node-vue-resource
Binary: node-vue-resource
Architecture: source
Version: 1.3.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-vue-resource - HTTP client for Vue.js
Closes: 891741
Changes:
 node-vue-resource (1.3.4+dfsg-1) unstable; urgency=medium
 .
   * Build using webpack
   * Update build deps (Closes: #891741)
   * Remove dist from source tarball
   * Bump debhelper compat to 11 and standards version to 4.1.3
Checksums-Sha1:
 3fd40397d1b55d742e166e3943b554b6e271592d 2204 
node-vue-resource_1.3.4+dfsg-1.dsc
 115b78b2b5342ffbfac3a1ae88579270c245f5de 42024 
node-vue-resource_1.3.4+dfsg.orig.tar.xz
 c69a2d6db7d56beb0f322125ba1705a30463aad1 2744 
node-vue-resource_1.3.4+dfsg-1.debian.tar.xz
 460103ec9d049552549ade9a514b23e4a34441d1 15621 
node-vue-resource_1.3.4+dfsg-1_source.buildinfo
Checksums-Sha256:
 34b58a5ac3637a57fb132f2e8af6af1593d5104c8aa9827ac884e1d6dd71a7e9 2204 
node-vue-resource_1.3.4+dfsg-1.dsc
 93e82a7e58e3fc74c67137feef7c24c8d34d3efdb191cc6d196b8acf576c070d 42024 
node-vue-resource_1.3.4+dfsg.orig.tar.xz
 422db57d1a0affdf11ff1b747eae4ac3c53dbb8ea66a964cfbe57a5d70b42c88 2744 
node-vue-resource_1.3.4+dfsg-1.debian.tar.xz
 cfc6f9eb7cc1241c39d59e38f4a1162ce41df51de4615994d8b025d24d363172 15621 
node-vue-resource_1.3.4+dfsg-1_source.buildinfo
Files:
 587e016bc4f961d911ace17185b05fdb 2204 javascript optional 
node-vue-resource_1.3.4+dfsg-1.dsc
 e19e046ae99b44f92af208810cc84fe6 42024 javascript optional 
node-vue-resource_1.3.4+dfsg.orig.tar.xz
 1714767778fc197f3ced5fac3f85be74 2744 javascript optional 
node-vue-resource_1.3.4+dfsg-1.debian.tar.xz
 45746cbfb7981e2d11559567ef9767b0 15621 javascript optional 
node-vue-resource_1.3.4+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlqWtRAACgkQzh+cZ0US
wio4Lw//WO48ez5QkalHBu4uRgP++K2UZP0Ay+yieby5irbP8Fm6BdhwqspeyLBg
RwGnPtspv5zrbpSQ6Hk5GRXWAWO2scVJ2aHqinZiv6v2Rf2SKhEn6BftsKSjMbkz
ttOECH0gbztyP9uMWBH8YH2ViQI75rB8c54Z5cYACalDDc/aFxClSTAonTI+Yhc+
3iBHMXyHr+SNb/WTcvVUb5Dz2V16c4ENFsQiIvoZ78/kyUVRlOGf30uMwM41POWM
zhJ2+DFjT16rALlYJcHzCCEXKyTVQWVKGxcUxbZAyVjy2OU0Peb+/WS6HlGbXqja
Dy5ovw5b4VbRqIWc1G8YQsEIWuyYgpz45r++4XVeW7lYPdUXuosY5Lj5tG9fX8rR
DSMAxAIyM5jDV5T+o2kFi4eMT8nPpsW2DFzDcNM8SVtdRBeQj5fCStFIhfMb2K0f
X24BAcgpwTYgwAol9o2AVUwOt5ZZNhP09Id9vBdTbGVI3xCfKmOmJw511zSYnHV0
6fnJhYB+iJfwDURv2UlPmiGasdclfMu7rkWenfZpbczfnHPVfoOU1ZUaBOSZWBJf
/a2Fjm9jF37aUY+cz0MMd6PoOc5ocKvgOC4PNVwmSWWJqdy/286/XTL79nJLwXst

Processed: This isn't actually grave, though

[Debian Bug Tracking System]

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

> severity 862531 serious
Bug #862531 {Done: Wouter Verhelst } [nbd-client] 
nbd-client: provide a systemd service to allow proper shutdown of NBD mounts
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Bug#891755: ruby-html-pipeline FTBFS with ruby 2.5: test failures

[Adrian Bunk]

Source: ruby-html-pipeline
Version: 1.11.0-1
Severity: serious

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

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/ruby-html-pipeline-1.11.0/debian/ruby-html-pipeline/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-html-pipeline/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
Run options: --seed 62382

# Running:

..F.F...

Finished in 0.099830s, 1081.8441 runs/s, 1763.0052 assertions/s.

  1) Failure:
HTML::Pipeline::TableOfContentsFilterTest#test_anchors_with_utf8_characters 
[/build/1st/ruby-html-pipeline-1.11.0/test/html/pipeline/toc_filter_test.rb:112]:
--- expected
+++ actual
@@ -1,3 +1,3 @@
 # encoding: UTF-8
 "
-\u0420\u0443\u0441\u0441\u043A\u0438\u0439"
+\u0420\u0443\u0441\u0441\u043A\u0438\u0439"


  2) Failure:
HTML::Pipeline::TableOfContentsFilterTest#test_toc_with_utf8_characters 
[/build/1st/ruby-html-pipeline-1.11.0/test/html/pipeline/toc_filter_test.rb:124]:
--- expected
+++ actual
@@ -1,5 +1,5 @@
 # encoding: UTF-8
 "
 \u65E5\u672C\u8A9E
-\u0420\u0443\u0441\u0441\u043A\u0438\u0439
+\u0420\u0443\u0441\u0441\u043A\u0438\u0439
 "


108 runs, 176 assertions, 2 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1)

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-html-pipeline-1.11.0/debian/ruby-html-pipeline returned exit 
code 1
make: *** [debian/rules:18: binary] Error 1

Processed: Re: Bug#862531: stretch update for nbd

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:3.15.2-3
Bug #862531 {Done: Wouter Verhelst } [nbd-client] 
nbd-client: provide a systemd service to allow proper shutdown of NBD mounts
Marked as found in versions nbd/1:3.15.2-3.

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

Processed: python-django FTBFS: ERROR: test_load_empty_dir (migrations.test_loader.LoaderTests)

[Debian Bug Tracking System]

Processing control commands:

> found -1 2:2.0.2-1
Bug #891753 [src:python-django] python-django FTBFS: ERROR: test_load_empty_dir 
(migrations.test_loader.LoaderTests)
Marked as found in versions python-django/2:2.0.2-1.

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

Bug#891752: cwltool FTBFS: error running tests

[Adrian Bunk]

Source: cwltool
Version: 1.0.20180225105849-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=cwltool=all=1.0.20180225105849-1=1519823880=0

...
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild pybuild:219: python2.7 /<>/setup.py develop
running develop
error: can't create or remove files in install directory

The following error occurred while trying to add or remove files in the
installation directory:

[Errno 13] Permission denied: 
'/usr/local/lib/python2.7/dist-packages/test-easy-install-6769.write-test'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/usr/local/lib/python2.7/dist-packages/

Perhaps your account does not have write access to this directory?  If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account.  If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.

For information on other options, you may wish to consult the
documentation at:

  https://setuptools.readthedocs.io/en/latest/easy_install.html

Please make the appropriate changes for your system and try again.

E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 /<>/setup.py develop
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:11: build-indep] Error 25

Bug#891753: python-django FTBFS: ERROR: test_load_empty_dir (migrations.test_loader.LoaderTests)

[Adrian Bunk]

Source: python-django
Version: 1:1.11.10-1
Severity: serious
Control: found -1 2:2.0.2-1

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-django.html

...
==
ERROR: test_load_empty_dir (migrations.test_loader.LoaderTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
testMethod()
  File "/build/1st/python-django-1.11.10/tests/migrations/test_loader.py", line 
178, in test_load_empty_dir
loader = MigrationLoader(connection)
  File "/build/1st/python-django-1.11.10/django/db/migrations/loader.py", line 
52, in __init__
self.build_graph()
  File "/build/1st/python-django-1.11.10/django/db/migrations/loader.py", line 
203, in build_graph
self.load_disk()
  File "/build/1st/python-django-1.11.10/django/db/migrations/loader.py", line 
104, in load_disk
directory = os.path.dirname(module.__file__)
  File "/usr/lib/python3.6/posixpath.py", line 156, in dirname
p = os.fspath(p)
TypeError: expected str, bytes or os.PathLike object, not NoneType

--
Ran 11584 tests in 171.304s

Bug#862531: stretch update for nbd

[Wouter Verhelst]

Control: found -1 1:3.15.2-3
thanks

Hi Adrian,

On Tue, Feb 27, 2018 at 10:20:55PM +0200, Adrian Bunk wrote:
> On Wed, Sep 13, 2017 at 03:12:07PM +, Debian Bug Tracking System wrote:
> >...
> >  nbd (1:3.16.2-1) unstable; urgency=medium
> >...
> >* Add missing After=network-online.target to nbd@ systemd unit.
> >  Closes: #862531.
> >...
> 
> Thanks a lot for fixing this bug for unstable.
> 
> It is still present in stretch, could you also fix it there?
> Alternatively, I can fix it for stretch if you don't object.

Thanks for reminding me. I had intended to let the patches simmer in
unstable for a while before asking for an update to stable, but forgot
to do that, and it got off my radar because it's now marked as "closed"
and doesn't have the correct version information to know that it's still
in stable...

Annotated this bug now so it is marked as still present in stable (I
hope). I'll try to fix it in stable ASAP, then.

-- 
Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
 Hacklab

Bug#891751: gtimelog FTBFS: dh_installman: Cannot find (any matches for) "debian/gtimelogrc.5"

[Adrian Bunk]

Source: gtimelog
Version: 0.11-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gtimelog=all=0.11-3=1519816177=0

...
   dh_installman -i -O--buildsystem=pybuild
dh_installman: Cannot find (any matches for) "debian/gtimelogrc.5" (tried in ., 
debian/tmp)

dh_installman: Aborting due to earlier error
make: *** [debian/rules:4: binary-indep] Error 25

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[John Kozak]

Andreas Beckmann writes:

> Control: tag -1 - moreinfo
> Control: close -1
>
> On 2018-02-28 12:35, John Kozak wrote:
>> I explicitly installed just nvidia-legacy-check, took the "yes" option,
>> then purged it and ran full-upgrade again which this time ran normally.
>> I checked and nvidia-driver was not installed ;-)
>
>> Some, from my PoV, the problem has gone away.
>
> OK, closing the report since I don't see a bug here.

Thanks - one more thing: on a reboot (yes, I should have checked this
before filing an all-clear!) X didn't start but was fixed by
`update-glx` (changing from 0 to 2):

  $ sudo update-glx --config nvidia
  There are 2 choices for the alternative nvidia (providing 
/usr/lib/nvidia/nvidia).

SelectionPath  Priority   Status
  
0/usr/lib/nvidia/current384   auto mode
1/usr/lib/nvidia/current384   manual mode
  * 2/usr/lib/nvidia/legacy-340xx   340   manual mode

/usr/lib/nvidia/current is an empty directory.

--
John

Processed: libseqlib-dev: /usr/include/SeqLib/BamWalker.h includes file locations no longer provided by libhts-dev

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:freebayes
Bug #891745 [libseqlib-dev] libseqlib-dev: /usr/include/SeqLib/BamWalker.h 
includes file locations no longer provided by libhts-dev
Added indication that 891745 affects src:freebayes

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

Bug#891745: libseqlib-dev: /usr/include/SeqLib/BamWalker.h includes file locations no longer provided by libhts-dev

[Adrian Bunk]

Package: libseqlib-dev
Version: 1.1.1+dfsg-3
Severity: serious
Control: affects -1 src:freebayes

freebayes FTBFS:

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

...
g++ -O3 -D_FILE_OFFSET_BITS=64 -g -std=gnu++11 -I../ttmath  
-I/usr/include/bamtools `pkg-config --cflags libvcflib` `pkg-config --cflags 
libseqlib` `pkg-config --cflags htslib` `pkg-config --cflags jsoncpp` -c 
DataLikelihood.cpp
In file included from /usr/include/SeqLib/BamReader.h:6:0,
 from LeftAlign.h:99,
 from AlleleParser.h:30,
 from DataLikelihood.h:20,
 from DataLikelihood.cpp:1:
/usr/include/SeqLib/BamWalker.h:15:10: fatal error: htslib/cram/cram.h: No such 
file or directory
 #include "htslib/cram/cram.h"
  ^~~~
compilation terminated.
make[2]: *** [Makefile:127: DataLikelihood.o] Error 1

Processed: update

[Debian Bug Tracking System]

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

> forwarded 891570 https://github.com/openssl/openssl/issues/5359
Bug #891570 [libssl1.1] SSL connect attempt failed error:141A90B5:SSL 
routines:ssl_cipher_list_to_bytes:no ciphers available
Changed Bug forwarded-to-address to 
'https://github.com/openssl/openssl/issues/5359' from 
'https://github.com/openssl/openssl/issues/5474'.
>
End of message, stopping processing here.

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

Bug#876695: marked as done (leocad FTBFS on armel/armhf: only OpenGL ES is available)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 13:20:27 +
with message-id 
and subject line Bug#876695: fixed in leocad 18.01-1
has caused the Debian Bug report #876695,
regarding leocad FTBFS on armel/armhf: only OpenGL ES is available
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.)


-- 
876695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leocad
Version: 17.07-2
Severity: serious

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

...
In file included from common/lc_context.cpp:3:0:
common/lc_glextensions.h:19:8: error: 'PFNGLBINDBUFFERARBPROC' does not name a 
type; did you mean 'PFNGLBINDBUFFERBASEPROC'?
 extern PFNGLBINDBUFFERARBPROC lcBindBufferARB;
^~
PFNGLBINDBUFFERBASEPROC
common/lc_glextensions.h:20:8: error: 'PFNGLDELETEBUFFERSARBPROC' does not name 
a type; did you mean 'PFNGLDELETEBUFFERSPROC'?
 extern PFNGLDELETEBUFFERSARBPROC lcDeleteBuffersARB;
^
PFNGLDELETEBUFFERSPROC
common/lc_glextensions.h:21:8: error: 'PFNGLGENBUFFERSARBPROC' does not name a 
type; did you mean 'PFNGLGENBUFFERSPROC'?
 extern PFNGLGENBUFFERSARBPROC lcGenBuffersARB;
^~
PFNGLGENBUFFERSPROC
common/lc_glextensions.h:22:8: error: 'PFNGLISBUFFERARBPROC' does not name a 
type; did you mean 'PFNGLISBUFFERPROC'?
 extern PFNGLISBUFFERARBPROC lcIsBufferARB;
^~~~
PFNGLISBUFFERPROC
...


On armel and armhf, Qt uses OpenGL ES intead of full OpenGL.

leocad does contain some OpenGL ES code, but I didn't manage
to get that building easily (is this still supported and
maintained upstream?).

If it isn't easily possible to use OpenGL ES on armel and armhf,
then removal of the old armel and armhf binaries
(reportbug ftp.debian.org) would be a possible solution.
--- End Message ---
--- Begin Message ---
Source: leocad
Source-Version: 18.01-1

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

Debian distribution maintenance software
pp.
Nicolas Guilbert  (supplier of updated leocad 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: Sun, 28 Jan 2018 22:21:34 +0100
Source: leocad
Binary: leocad
Architecture: source
Version: 18.01-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LEGO Team 
Changed-By: Nicolas Guilbert 
Description:
 leocad - virtual brick CAD software
Closes: 876695
Changes:
 leocad (18.01-1) unstable; urgency=medium
 .
   * Update to latest upstream version.
   * Fix compile for OpenGL ES (Closes: #876695).
   * Update VCS urls to point to salsa.debian.org.
   * Fix test bed - run program in xvfb.
Checksums-Sha1:
 79e19919c968c587da58a4b0a3c034889ee6a0b9 2071 leocad_18.01-1.dsc
 800e02a6c91ff3caace928e09025e859e3286b40 5301708 leocad_18.01.orig.tar.gz
 a45b957be85c81796404d423a8b8811882d8110a 11920 leocad_18.01-1.debian.tar.xz
 4bbe4408a30215ce5b8d11d59f1d08b14416916b 11423 leocad_18.01-1_source.buildinfo
Checksums-Sha256:
 b477652238224cfd652038deb55277acd5fc6f6965a8ab99d961a49ea1152735 2071 
leocad_18.01-1.dsc
 9f10b66e8c05a8b559e11d05506d592e7c6eaad222cd6cfeb8a18aa33ee2999c 5301708 
leocad_18.01.orig.tar.gz
 cf09fa174a83b9135814a721787adeac6ff3c6da5d9f63298bb835b84d30f28f 11920 
leocad_18.01-1.debian.tar.xz
 b2f20f8732bb9b8fbffe01d8aaec5e99aaf3ba99f81d0c0b11cead5ee4b962cf 11423 
leocad_18.01-1_source.buildinfo
Files:
 341923846dc8b4337b93b840c4598578 2071 utils optional leocad_18.01-1.dsc
 a138c313055d4d3fc9cf59a75f8e6744 5301708 utils optional 
leocad_18.01.orig.tar.gz
 101a992fc4348eb73187d16c89f94d53 11920 utils optional 
leocad_18.01-1.debian.tar.xz
 63887c32e267c9a27c99a6962268525c 11423 utils optional 
leocad_18.01-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAlqWqSUACgkQgSgKoIe6

Bug#891743: ruby-influxdb: FTBFS with ruby2.5: Failed examples: rspec ./spec/influxdb/client_spec.rb:47 # InfluxDB::Client#full_url escapes params

[Andreas Beckmann]

Source: ruby-influxdb
Version: 0.3.16-1
Severity: serious
Justification: fails to build from source

Hi,

ruby-influxdb/experimental FTBFS with ruby2.5 as the default ruby:

Failures:

  1) InfluxDB::Client#full_url escapes params
 Failure/Error: expect(url).to 
include("value=+%21%40%23%24%25%5E%26%2A%28%29%2F%5C_%2B-%3D%3F%7C%60%7E")
   expected 
"/unknown?value=+%21%40%23%24%25%5E%26%2A%28%29%2F%5C_%2B-%3D%3F%7C%60~=username=password"
 to include "value=+%21%40%23%24%25%5E%26%2A%28%29%2F%5C_%2B-%3D%3F%7C%60%7E"
 # ./spec/influxdb/client_spec.rb:49:in `block (3 levels) in '

Full buildlog attached.


Andreas


ruby-influxdb_0.3.16-1.log.gz
Description: application/gzip

Bug#889608: Continuing to get core dumps with man-db

[Colin Watson]

On Sun, Feb 25, 2018 at 07:13:52PM -0500, John Sivak wrote:
> On 02/25/2018 07:06 AM, Colin Watson wrote:
> > Ah, right, no explicit path there. Can you try git master again
> > (https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=122802046452c5d900a3d74b643d2089c4df58d2)?
> 
> Still not working. :(
> 
> Stack trace attached for: strace -f -o man.trace -s 1024 man man

OK, I finally cracked and installed a trial setup in a VM so that I
could iterate more quickly.
https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=eb88d394e8c3bed3953bbeb106f0dc5996c18621
now works for me - please confirm.

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#891742: ceph-deploy requires internet access during the build

[Adrian Bunk]

Source: ceph-deploy
Version: 2.0.0+dfsg1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ceph-deploy.html

...
   dh_auto_build -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py build --force
[vendoring] Running command: git clone git://git.ceph.com/remoto


This library depends on sources fetched when packaging that failed to be
retrieved.

This means that it will *not* work as expected. Errors encountered:

Cloning into 'remoto'...

fatal: Unable to look up git.ceph.com (port 9418) (Temporary failure in name 
resolution)


vendor.py: git clone failed using ceph.com url with rc 128, trying github.com
[vendoring] Running command: git clone https://github.com/ceph/remoto.git


This library depends on sources fetched when packaging that failed to be
retrieved.

This means that it will *not* work as expected. Errors encountered:

Cloning into 'remoto'...

fatal: unable to access 'https://github.com/ceph/remoto.git/': Could not 
resolve host: github.com


Traceback (most recent call last):
  File "setup.py", line 27, in 
('remoto', '0.0.29', ['python', 'vendor.py']),
  File "/build/1st/ceph-deploy-2.0.0+dfsg1/vendor.py", line 112, in vendorize
vendor_library(name, version, cmd)
  File "/build/1st/ceph-deploy-2.0.0+dfsg1/vendor.py", line 75, in 
vendor_library
os.chdir(vendor_src)
OSError: [Errno 2] No such file or directory: 
'/build/1st/ceph-deploy-2.0.0+dfsg1/remoto'
dh_auto_build: python setup.py build --force returned exit code 1
make: *** [debian/rules:7: build] Error 1

Processed: affects 889151

[Debian Bug Tracking System]

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

> affects 889151 src:aplpy
Bug #889151 [python3-matplotlib] python3-matplotlib: 
backports.functools_lru_cache, subprocess32 are not Python 3 dependencies
Added indication that 889151 affects src:aplpy
> thanks
Stopping processing here.

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

Bug#891741: node-vue-resource FTBFS: webpack: Command not found

[Adrian Bunk]

Source: node-vue-resource
Version: 1.3.4-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-vue-resource.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-vue-resource-1.3.4'
webpack --config debian/webpack.config.js src/index.js 
dist/vue-resource.common.js --target=web --output-library=VueResource 
--output-library-target=commonjs --module-bind 'js=babel-loader'
make[1]: webpack: Command not found
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 127

Bug#891738: marked as done (libgda5 FTBFS with valac 0.39.92-1)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 13:05:24 +
with message-id 
and subject line Bug#891738: fixed in libgda5 5.2.4-8
has caused the Debian Bug report #891738,
regarding libgda5 FTBFS with valac 0.39.92-1
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.)


-- 
891738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgda5
Version: 5.2.4-7
Severity: serious

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

...
checking for valac... /usr/bin/valac
checking whether /usr/bin/valac is at least version 0.38.0... yes
checking for vapigen vapigen-0.38... no
configure: Searching for vapigen-0.38 program...
checking for vapigen-0.38... no
configure: error: Can't locate vapigen-0.38 >= 0.38.0 program
--- End Message ---
--- Begin Message ---
Source: libgda5
Source-Version: 5.2.4-8

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated libgda5 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: Wed, 28 Feb 2018 07:47:12 -0500
Source: libgda5
Binary: libgda-5.0-4 libgda-5.0-bin libgda-5.0-common libgda-5.0-dev 
libgda-5.0-doc libgda-5.0-mysql libgda-5.0-postgres gir1.2-gda-5.0
Architecture: source
Version: 5.2.4-8
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gir1.2-gda-5.0 - data abstraction library based on GLib -- GObject 
Introspection
 libgda-5.0-4 - data abstraction library based on GLib
 libgda-5.0-bin - data abstraction library based on GLib -- binary files
 libgda-5.0-common - data abstraction library based on GLib -- common files
 libgda-5.0-dev - data abstraction library based on GLib -- development files
 libgda-5.0-doc - data abstraction library based on GLib -- documentation files
 libgda-5.0-mysql - MySQL provider for libgda database abstraction library
 libgda-5.0-postgres - PostgreSQL provider for libgda database abstraction 
library
Closes: 891738
Changes:
 libgda5 (5.2.4-8) unstable; urgency=medium
 .
   * Update vala_version.patch for vala 0.40 (Closes: #891738)
Checksums-Sha1:
 72bd3f713f6c2254ecde06d0d464f385250d3ba7 3033 libgda5_5.2.4-8.dsc
 e80c6d7b9c900f133016204d3db08dec70d5ff5b 70116 libgda5_5.2.4-8.debian.tar.xz
 d50bb6461c2ed351578c22a1dae16e3b9b175124 12235 libgda5_5.2.4-8_source.buildinfo
Checksums-Sha256:
 96f2cc31df3846e8342903f7c3ce6aefe8a5d55ae1a62569600b723b6910ad9d 3033 
libgda5_5.2.4-8.dsc
 0b99594ffd570b66b46e41abf1cb1bd4b840d32d479f691bb387977c806cbb22 70116 
libgda5_5.2.4-8.debian.tar.xz
 4dc94dcb609535e2da34ec908851a5e0bb7c7fe9d7813d1b11e0b7b24cd0b3ca 12235 
libgda5_5.2.4-8_source.buildinfo
Files:
 4e9117f8b4ae2a79adab5a56d3e25598 3033 libs optional libgda5_5.2.4-8.dsc
 e2ab751bb7c6954b82e4cdd2d6d85d40 70116 libs optional 
libgda5_5.2.4-8.debian.tar.xz
 70c4cea5931eba1b1928e2c6fc861a6f 12235 libs optional 
libgda5_5.2.4-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlqWpQEACgkQ5mx3Wuv+
bH1hpQ/7BvZN6MAhNkBWei2Fx/Uz6oN0NlWAjZgECR/C6H+5SD6eS1OPedb11qBE
zClaK0f9ddU8GETjsvLQFWT/ZfIZdyQMj43k7xp18pkQ/o5t8JTa4UzKMHnB4kE5
EZ/KQEvYoIee5e0zzEDiULeQhs+0n2GKWMYTgx3KptoAQtZkdIPgb51def/jehPD
UdiOOH0k1LTk3FbFvHuaR2GIKmFvNDlZvlfDdIec8f03IfQ7ieplfeLS4tVatNLy
xeqxaV8rGhRZxhGjUG4jgY4BOlx8sz7d12SaA7W6ofgOWVh+Yz1xITp2ehEpSdny
jsFwZ+ZooiobRBztrJpjfW4zmZIFu+Z2mJnuUlbBS6SOus8XMTY9TcafoGDyLzgF
Dm4v+IizGq/uizgH1LrhT1MaDE7MxsVkryZmqISJUdqDnFzVts5Vm8j/YmNfcrw6
/a0TMAk3FjRJt2CEqqBBtGie31GWVeNnK7qoYHzCS5d8G9O/yzn1seYo+Z2OJscL
2J3nc/cTmzpDAhkgvfrMFYB7rZB88KQVk84HT1mjTqzt26Uswu+h9FZCy+HmCY93
1w6DfWoCdh38U/dj2h1dpK3GKaVGMVOzGRyL3wXFljjKHPSC7poYkSY69HjJZj0b
xb3LsDvDD1GSQrNrZuCl77Egxa3MTsxkkRsHC4jC6z2WZ5eNab4=
=ySXu
-END PGP SIGNATURE End Message ---

Bug#891740: pyvo FTBFS: ModuleNotFoundError: No module named 'requests'

[Adrian Bunk]

Source: pyvo
Version: 0.6.1+dfsg-1
Severity: serious

Some recent change in unstable makes pyvo FTBFS:

https://tests.reproducible-builds.org/debian/history/pyvo.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyvo.html

...
==
ERROR: pyvo (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: pyvo
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.6/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/__init__.py", 
line 41, in 
from . import registry
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/registry/__init__.py",
 line 7, in 
from . import regtap
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/registry/regtap.py",
 line 21, in 
from ..dal import scs, sia, ssa, sla, tap, query as dalq
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/dal/__init__.py", 
line 2, in 
from .sia import search as imagesearch
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/dal/sia.py", line 
39, in 
from .query import DALResults, DALQuery, DALService, Record, mime2extension
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/dal/query.py", 
line 35, in 
import requests
ModuleNotFoundError: No module named 'requests'


--
Ran 1 test in 0.001s

FAILED (errors=1)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build; python3.6 -m unittest 
discover -v 
dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
make: *** [debian/rules:7: build] Error 25

Bug#891739: gitlab-ci-multi-runner FTBFS: r.EncodeArrayStart undefined (type codec.genHelperEncDriver has no field or method EncodeArrayStart)

[Adrian Bunk]

Source: gitlab-ci-multi-runner
Version: 1.11.4+dfsg-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gitlab-ci-multi-runner.html

...
gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/client/unversioned/clientcmd/api/latest
gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/runtime/serializer
gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api
# gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:115:6:
 r.EncodeArrayStart undefined (type codec.genHelperEncDriver has no field or 
method EncodeArrayStart)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:123:6:
 r.EncodeMapStart undefined (type codec.genHelperEncDriver has no field or 
method EncodeMapStart)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:127:6:
 z.EncSendContainerState undefined (type codec.genHelperEncoder has no field or 
method EncSendContainerState)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:140:7:
 z.EncSendContainerState undefined (type codec.genHelperEncoder has no field or 
method EncSendContainerState)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:142:7:
 z.EncSendContainerState undefined (type codec.genHelperEncoder has no field or 
method EncSendContainerState)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:152:6:
 z.EncSendContainerState undefined (type codec.genHelperEncoder has no field or 
method EncSendContainerState)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:165:7:
 z.EncSendContainerState undefined (type codec.genHelperEncoder has no field or 
method EncSendContainerState)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:167:7:
 z.EncSendContainerState undefined (type codec.genHelperEncoder has no field or 
method EncSendContainerState)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:177:6:
 z.EncSendContainerState undefined (type codec.genHelperEncoder has no field or 
method EncSendContainerState)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:190:7:
 z.EncSendContainerState undefined (type codec.genHelperEncoder has no field or 
method EncSendContainerState)
src/gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/api/types.generated.go:190:7:
 too many errors
dh_auto_build: cd _build && go install 
-gcflags=\"-trimpath=/build/1st/gitlab-ci-multi-runner-1.11.4\+dfsg/_build/src\"
 
-asmflags=\"-trimpath=/build/1st/gitlab-ci-multi-runner-1.11.4\+dfsg/_build/src\"
 -v -p 16 -ldflags "-X 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/common.NAME=gitlab-ci-multi-runner 
-X gitlab.com/gitlab-org/gitlab-ci-multi-runner/common.REVISION=1.11.4" 
gitlab.com/gitlab-org/gitlab-ci-multi-runner 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/apps/gitlab-runner-helper 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/commands 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/commands/helpers 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/common 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/docker 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/docker/machine 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/kubernetes 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/parallels 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/shell 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/ssh 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/virtualbox 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/archives 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/cli 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/docker 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/formatter 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/parallels 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/prometheus 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/sentry 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/service 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/service/mocks 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/ssh 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/timeperiod 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/url 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/virtualbox 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/network 
gitlab.com/gitlab-org/gitlab-ci-multi-runner/shells returned 

Bug#891738: libgda5 FTBFS with valac 0.39.92-1

[Adrian Bunk]

Source: libgda5
Version: 5.2.4-7
Severity: serious

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

...
checking for valac... /usr/bin/valac
checking whether /usr/bin/valac is at least version 0.38.0... yes
checking for vapigen vapigen-0.38... no
configure: Searching for vapigen-0.38 program...
checking for vapigen-0.38... no
configure: error: Can't locate vapigen-0.38 >= 0.38.0 program

Processed: Re: Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo
Bug #891731 [nvidia-legacy-check] nvidia-legacy-check: check fails preventing 
apt full-upgrade
Removed tag(s) moreinfo.
> close -1
Bug #891731 [nvidia-legacy-check] nvidia-legacy-check: check fails preventing 
apt full-upgrade
Marked Bug as done

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

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[Andreas Beckmann]

Control: tag -1 - moreinfo
Control: close -1

On 2018-02-28 12:35, John Kozak wrote:
> I explicitly installed just nvidia-legacy-check, took the "yes" option,
> then purged it and ran full-upgrade again which this time ran normally.
> I checked and nvidia-driver was not installed ;-)

> Some, from my PoV, the problem has gone away.

OK, closing the report since I don't see a bug here.


Andreas

Processed: affects 890939

[Debian Bug Tracking System]

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

> affects 890939 src:docker.io
Bug #890939 [src:etcd] etcd FTBFS
Added indication that 890939 affects src:docker.io
> thanks
Stopping processing here.

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

Bug#891615: python3-zeitgeist: python3 invalid syntax error during installation

[Petter Reinholdtsen]

[Boyuan Yang]
> I can confirm the problem.
> 
> Jeremy, could you please fix this problem soon?

I see the problem too.

The code in question is obviously only going to work on Python 2, not Python 3.
Is upstream testing the code on Python 3?  Is it intended to work on Python 3?

If not, perhaps it is a bad idea for Debian to try to support the code with
Python 3?

-- 
Happy hacking
Petter Reinholdtsen

Bug#891736: node-marked-man FTBFS: test failure

[Adrian Bunk]

Source: node-marked-man
Version: 0.3.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-marked-man.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-marked-man-0.3.0'
nodejs test/compare.js
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/blockquotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/definition_list_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/dots_at_line_start_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/ellipses.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/entity_encoding_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/graves.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/links.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/markdown_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/nested_list_with_code.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/pre_block_with_quotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/table.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/underline_spacing_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/links.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/graves.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/entity_encoding_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/ellipses.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/dots_at_line_start_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/definition_list_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/blockquotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/nested_list_with_code.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/markdown_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/pre_block_with_quotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/underline_spacing_test.err
:173: warning [p 1, 2.0i, div `3tbd17,3', 0.0i]: cannot adjust 
line
:272: warning [p 1, 2.0i, div `3tbd28,3', 0.2i]: cannot adjust 
line
:671: warning [p 1, 2.0i, div `3tbd73,0', 0.0i]: cannot adjust 
line
warning: file `', around line 18:
  table wider than line width
warning: file `', around line 13:
  table squeezed horizontally to fit line length

Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/table.err
Failed tests:  12
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1

Bug#891735: xorg-gtest FTBFS with glibc 2.26

[Adrian Bunk]

Source: xorg-gtest
Version: 0.7.1-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xorg-gtest.html

...
../src/xorg-gtest_main.cpp: In function 'void setup_signal_handlers()':
../src/xorg-gtest_main.cpp:94:5: error: 'SIGUNUSED' was not declared in this 
scope
 SIGUNUSED,
 ^

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[John Kozak]

Andreas Beckmann writes:

> Control: found -1 384.111-4
> Control: tag -1 moreinfo
>
> On 2018-02-28 11:02, John Kozak wrote:
>> Attempting to do `apt full-upgrade` fails with a message with banner
>> "Configuring nvidia-legacy-check" and this body:
>
>> I am already using `nvidia-legacy-340xx-driver` for the two graphics cards
>> on this system and `nvidia-driver` is not installed.
>
> Do you have an old version of nvidia-legacy-check installed?
> Remove it, you don't need it.
> Otherwise something seems to pull in the new driver ... the complete
> output from apt may be helpful to analyze this.

I explicitly installed just nvidia-legacy-check, took the "yes" option,
then purged it and ran full-upgrade again which this time ran normally.
I checked and nvidia-driver was not installed ;-)

Some, from my PoV, the problem has gone away.

Thanks for a speedy reply, anyway!

>
>> console messages after clicking "no" are:
>
> It's intentional to fail in this case.
>
>
> Andreas


--
John

Bug#891647: marked as done (ikiwiki: FTBFS with new ImageMagick)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 12:06:02 +
with message-id 
and subject line Bug#891647: fixed in ikiwiki 3.20180228-1
has caused the Debian Bug report #891647,
regarding ikiwiki: FTBFS with new ImageMagick
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.)


-- 
891647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ikiwiki
Version: 3.20180105-1
Severity: serious

https://ci.debian.net/packages/i/ikiwiki/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ikiwiki.html

...
Test Summary Report
---
t/img.t  (Wstat: 2304 Tests: 70 Failed: 9)
  Failed tests:  21, 27-28, 30-35
  Non-zero exit status: 9
t/relativity.t   (Wstat: 0 Tests: 136 Failed: 0)
  TODO passed:   71
Files=67, Tests=3092, 507 wallclock secs ( 1.60 usr  0.64 sys + 122.15 cusr 
52.17 csys = 176.56 CPU)
Result: FAIL
Failed 1/67 test programs. 9/3092 subtests failed.
make[1]: *** [Makefile:972: test_dynamic] Error 255
--- End Message ---
--- Begin Message ---
Source: ikiwiki
Source-Version: 3.20180228-1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated ikiwiki 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, 28 Feb 2018 10:48:32 +
Source: ikiwiki
Binary: ikiwiki
Architecture: source
Version: 3.20180228-1
Distribution: unstable
Urgency: medium
Maintainer: Simon McVittie 
Changed-By: Simon McVittie 
Description:
 ikiwiki- wiki compiler
Closes: 888055 891647
Changes:
 ikiwiki (3.20180228-1) unstable; urgency=medium
 .
   * New upstream release
 - core: Don't send relative redirect URLs when behind a reverse proxy
 - core: Escape backticks etc. in directive error messages as HTML
   entities so that the error message is not subsequently parsed as
   Markdown
 - mdwn: Enable fenced code blocks, PHP Markdown Extra-style definition
   lists and GitHub-style extensions to HTML tag syntax when used with
   Discount >= 2.2.0 (Closes: #888055)
 - img: Fix auto-detection of image format (if enabled, which is
   strongly discouraged) with ImageMagick >= 6.9.8-3
 - rst: Use Python 3 instead of Python 2
 - build: `set -e` before each `for` loop, so that errors are reliably
   trapped
 - build: Use if/then instead of `||` so that the `-e` flag works
 - build: Ensure that pm_to_blib finishes before rewriting shebang lines
 - t: Make the img test pass with ImageMagick >= 6.9.8-3
   (Closes: #891647)
   * Stop rewriting shebang lines of Python 3 scripts
Checksums-Sha1:
 28c123d86915022d51965e8519c2b3ce72ca4320 2497 ikiwiki_3.20180228-1.dsc
 736abf42a48007ac379bb1243ba120e7ec44a5a3 2637180 ikiwiki_3.20180228.orig.tar.xz
 49e512246fbf87cca29839ac4fc7fac34bb32413 86248 
ikiwiki_3.20180228-1.debian.tar.xz
 7bb390144aef7894a6ec9ab32fc907b807f10983 5093 
ikiwiki_3.20180228-1_source.buildinfo
Checksums-Sha256:
 acfc5187e42baa93c2b51d942f017b9c49867ef3bb156b0b5f739f3eb36e97b5 2497 
ikiwiki_3.20180228-1.dsc
 c39fc3c46131193419fa690ff35b6d54097b0a6c46f54c3464b6d8cedd5e6411 2637180 
ikiwiki_3.20180228.orig.tar.xz
 2d592b0c155fd689137856720bc86ca955e029e2bf92337f475d1af423115e3b 86248 
ikiwiki_3.20180228-1.debian.tar.xz
 67cab1151ed05b0a1abbaa091867047e8bee0bcbfbdae683ea235b7742a046b7 5093 
ikiwiki_3.20180228-1_source.buildinfo
Files:
 05a66a7d820332d66fec1a61c54bb855 2497 web optional ikiwiki_3.20180228-1.dsc
 60ea05cc6d401c83bb09a47bb2e7f385 2637180 web optional 
ikiwiki_3.20180228.orig.tar.xz
 879d8f2e2d5b5e0dcb3ac999af4d8981 86248 web optional 
ikiwiki_3.20180228-1.debian.tar.xz
 e8d5a60ada7e8574e43747e52893b210 5093 web optional 
ikiwiki_3.20180228-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAlqWloEACgkQ4FrhR4+B

Bug#889811: gosa-encrypt-password is broken since PHP7.2's php-mcrypt removal

[Wolfgang Schweer]

Hi Benjamin,

thanks for your work.

On Tue, Feb 27, 2018 at 03:18:18PM +0100, Benjamin Zapiec wrote:
> Since the password hashing script wasn't the only part of the GOsa² 
> code that was using the php mcrypt extension i needed to clean up some 
> more code.
[..]
> https://github.com/gosa-project/gosa-plugins-goto/commit/1a29481e8eef32f980f61ecb4b83a7981e6913b3
[..]
> These commits basically remove their plugin. I don't think the plugins 
> do something useful without the possibility to communicate with the so 
> called "gosa support infrastructure daemon". (gosa-si)

With the goto plugin removed, Debian Edu would loose some machine
management functionality. ATM it is possible to add systems of type
workstations, terminals and printers (besides servers and devices)
allowing one to have a better overview. To get an impression about 
the details, see the related manual chapter:
https://wiki.debian.org/DebianEdu/Documentation/Stretch/GettingStarted#Machine_Management_with_GOsa.2BALI-

While the related instructions could be adjusted for new installations,
existing installations would be badly hit upon upgrades. I figure all
systems other than servers and devices would disappear from the GOsa² 
system overview. These systems would still work o.k., but admins 
are expected to be confused.

Wolfgang


signature.asc
Description: PGP signature

Bug#889701: marked as done (comet-ms: unsatisfiable build dependency)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 12:29:37 +0100
with message-id <787c20c8-7576-10a1-6066-7e27aa619...@debian.org>
and subject line Re: Bug#889701: comet-ms: unsatisfiable build dependency
has caused the Debian Bug report #889701,
regarding comet-ms: unsatisfiable build dependency
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.)


-- 
889701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: comet-ms
Version: 2017012-1
Severity: serious

Hi Filippo,

The comet-ms package in Debian unstable is unbuildable on all architectures,
because it build-depends on libmstoolkit-dev (>= 82) but the most recent
version of libmstoolkit which has been uploaded to the archive is
77.0.0-1.1.  If this newer version is required, please upload it to Debian
(I see you are the maintainer of both packages); otherwise, please relax the
build-dependency.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Thu, 15 Feb 2018 20:46:31 +0100 Filippo Rusconi  wrote:
> As a follow-up, I just got a mail from upstream as a response to my enquiry of
> today. Upstream is OK to fix the autorship/license problems soon, to I'm
> optimistic about the resolution of this bug.
> 

I think we can close it now :)

G.

> Filippo
> 
> -- 
> ⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
> ⣾⠁⢠⠒⠀⣿⡁  Debian Developer
> ⢿⡄⠘⠷⠚⠋⠀  http://msxpertsuite.org
> ⠈⠳⣄  http://www.debian.org
> 
> 



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#740160: Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais

[Egidijus Stanaitis]

Sveiki,

 

Ar Jums reikia bendrijų bazės?

 

Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais

 

Bazėje nurodomi šie duomenys

 

Bendrijos pavadinimas

Bendrijos kodas

SD kodas

Įregistravimo data

Darbuotojų skaičius

Elektroninio pašto adresas

Mobilus telefonas 

Bendrijos adresas 

Miestas

Pašto kodas

Bendrijos pirmininko vardas pavardė

 

Visos bendrijos veikiančios su pirmininkų kontaktais

 

Bendrijų bazę galima filtruoti pagal miestus, registracijos datą

 

Ši bazė gali būti naudinga ieškant klientų

 

Ar Jums atsiųsti bendrijų bazės pavyzdį su pasiūlymu?

 

Turime ir asociacijų, valstybinių institucijų, įmonių, ūkininkų bazių.

Kokių Jums dar reikia bazių?

 

Taip pat siunčiame naujienlaiškius

Išrašome sąskaitą faktūrą

 

 

Pagarbiai,

Egidijus Stanaitis

+370 603 160 22

teradi...@gmail.com

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[Andreas Beckmann]

Control: found -1 384.111-4
Control: tag -1 moreinfo

On 2018-02-28 11:02, John Kozak wrote:
> Attempting to do `apt full-upgrade` fails with a message with banner
> "Configuring nvidia-legacy-check" and this body:

> I am already using `nvidia-legacy-340xx-driver` for the two graphics cards
> on this system and `nvidia-driver` is not installed.

Do you have an old version of nvidia-legacy-check installed?
Remove it, you don't need it.
Otherwise something seems to pull in the new driver ... the complete
output from apt may be helpful to analyze this.

> console messages after clicking "no" are:

It's intentional to fail in this case.


Andreas

Processed: Re: Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[Debian Bug Tracking System]

Processing control commands:

> found -1 384.111-4
Bug #891731 [nvidia-legacy-check] nvidia-legacy-check: check fails preventing 
apt full-upgrade
Marked as found in versions nvidia-graphics-drivers/384.111-4.
> tag -1 moreinfo
Bug #891731 [nvidia-legacy-check] nvidia-legacy-check: check fails preventing 
apt full-upgrade
Added tag(s) moreinfo.

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

Bug#856086: Bug#885037: monster-masher: Please don't (Build-)Depend on gconfmm2.6

[Markus Koschany]

Am 28.02.2018 um 04:52 schrieb Jeremy Bicha:
> monster-masher is one of the last two packages in Debian unstable
> depending on esound. (And even if that were fixed, monster-masher
> depends on several other GNOME2 libraries that are being removed.)
> 
> monster-masher has been unmaintained usptream for 9 years.
> 
> https://git.gnome.org/browse/monster-masher/log/
> 
> Maybe it's time for monster-masher to be removed from Debian?

monster-masher is a complete game, so there was probably no interest to
continue working on it. We are aware of the removal of obsolete
libraries and intend to request their removal from Debian sometime
between now and the next Debian freeze. Personally I wanted to give
people more time to fix those bugs because they tend to notice such bugs
rather late and porting software to new libraries is a non-trivial task.
We could fix one game so far thanks to Juhanni (pegsolitaire).

I don't have any objections if you want to remove them right now but I
think you can achieve the removal of esound/Gnome2 libs anyway and you
don't have to wait for us. Just point the ftp team to this bug report.
This is true for all affected games maintained by the games team. They
will be broken in unstable but I think this might even raise more
awareness. Testing users won't be affected.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: tagging 891720

[Debian Bug Tracking System]

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

> tags 891720 + confirmed fixed-upstream
Bug #891720 [src:dumb-jump-el] dumb-jump-el FTBFS: test failures
Added tag(s) confirmed and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#891731: nvidia-legacy-check: check fails preventing apt full-upgrade

[John Kozak]

Package: nvidia-legacy-check
Severity: serious

Dear Maintainer,

Attempting to do `apt full-upgrade` fails with a message with banner
"Configuring nvidia-legacy-check" and this body:

 | This system has a graphics card which is no longer handled by the NVIDIA 
driver (package nvidia-driver). You   │
 │ may wish to keep the package installed - for instance to drive some other 
card - but the card with the │
 │ following chipset won't be usable:   
  │
 │  
  │
 │ 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98 [GeForce 
8400 GS Rev. 2] [10de:06e4] (rev │
 │ a1); 06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT200b 
[GeForce GTX 285] [10de:05e3] (rev│
 │ a1)  
  │
 │  
  │
 │ The above card requires either the non-free legacy NVIDIA driver (package 
nvidia-legacy-340xx-driver) or the   │
 │ free Nouveau driver (package xserver-xorg-video-nouveau).
  │
 │  
  │
 │ Use the update-glx command to switch between different installed drivers.
  │
 │  
  │
 │ Before the Nouveau driver can be used you must remove NVIDIA configuration 
from xorg.conf (and xorg.conf.d/).  │
 │  
  │
 │ Install NVIDIA driver despite unsupported graphics card?

I am already using `nvidia-legacy-340xx-driver` for the two graphics cards
on this system and `nvidia-driver` is not installed.

console messages after clicking "no" are:

  *** The following unsupported devices are present in the machine: 
  
  05:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98 [GeForce 
8400 GS Rev. 2] [10de:06e4] (rev a1)
  06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT200b [GeForce 
GTX 285] [10de:05e3] (rev a1)
  Aborting nvidia driver installation.
  dpkg: error processing archive 
/var/cache/apt/archives/nvidia-legacy-check_384.111-4_amd64.deb (--unpack):
   new nvidia-legacy-check package pre-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   /var/cache/apt/archives/nvidia-legacy-check_384.111-4_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#891719: marked as done (gtimelog FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 10:36:32 +
with message-id 
and subject line Bug#891719: fixed in gtimelog 0.11-3
has caused the Debian Bug report #891719,
regarding gtimelog FTBFS: test failure
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.)


-- 
891719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtimelog
Version: 0.11-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gtimelog=all=0.11-2=1519804492=0

...
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: python3.6 setup.py test 
running test
Searching for PyGObject

Note: Bypassing https://pypi.python.org/simple/PyGObject/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

Couldn't find index page for 'PyGObject' (maybe misspelled?)
Scanning index of all packages (this may take a while)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

No local packages or working download links found for PyGObject
error: Could not find suitable distribution for Requirement.parse('PyGObject')
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python3.6 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
make: *** [debian/rules:4: build-indep] Error 25
--- End Message ---
--- Begin Message ---
Source: gtimelog
Source-Version: 0.11-3

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated gtimelog 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, 28 Feb 2018 11:11:02 +0100
Source: gtimelog
Binary: gtimelog
Architecture: source
Version: 0.11-3
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Andrej Shadura 
Description:
 gtimelog   - time logging application
Closes: 891719
Changes:
 gtimelog (0.11-3) unstable; urgency=medium
 .
   * Update the build dependencies for tests (Closes: #891719).
Checksums-Sha1:
 653753fa142a7963064b1fb10ba152da501c4a9d 2144 gtimelog_0.11-3.dsc
 fbf674519c067b9fc9e799ecc023fb3d012010fc 6364 gtimelog_0.11-3.debian.tar.xz
Checksums-Sha256:
 97de1946a91f20ddbee743b86b4182631b0642756e43d020e689b67f4b0c5fad 2144 
gtimelog_0.11-3.dsc
 678818aa4db23801fc0c5e6462bec80f689cafa9c6568144c33039c086deb5ba 6364 
gtimelog_0.11-3.debian.tar.xz
Files:
 c2eecf936bedafe8324c770bc92ac9a5 2144 admin optional gtimelog_0.11-3.dsc
 d9838fd00f236e8eb04b49b8854c521e 6364 admin optional 
gtimelog_0.11-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEeCEwtMmUQkeXe4L9bqTSMRotJo0FAlqWgccUHGFuZHJld3No
QGRlYmlhbi5vcmcACgkQbqTSMRotJo329Q//QpYzRCD5sD0Twr8QNseddVfmvZSl
cvVQDYplEUz1RP5scAfaPSDkzlpufS06wXUvX8mE/T5w7AYBF2ic/wN+rP9X+eZ9
zfj9x4Pqevn8OIVYqu9ascXAP2CNI6+MaOd2yTA9m0PCnBB2m2ikwnSemzPV/UqC
EIudZGxNCGvO1GHcxvwATbP1Qy9stdAhUQy3xrlscnHqaPECZGIHOmbh1W5KqYRj
pcmeTBfrSOGqk/cIHDC/pwOAYvrN7RBlk9Ndjw1WIldk8bwiiL51rz56nDm2N4WC
sDMhK9pWi1les2r4pPS2fEGE+wsIjf+oH9UQ+E8V+hn+cucHGyWBgfsHRls7Fk1e
GO5SGABij74KLgUdYryrCPJTygOYsFpD28k/BUQs66MhQIKQCxII9yIAAVT57NDX
hDz/8KWibA9sk6288tijbg0Ij+twizUDJAQ+DBAMCOPxwDNuNGiSY3XDqW5EJI7M
oN+FMd/YezOR0bstb2mkDtroGsqd/RD9g7F0yjAIjg0Cvy6vJlC75fV0Q3UjgLaC
/IP7Sv5zDgfstRHVjL3rV9xpMYZMJG2/3qo4U6sfA+H1pz/DWJtL9YMtbw3uIdJX
MN2XsmO0EiJQgCAwdBCtNjYl3Pvi7O+/DfvFTf+YlW0PshPLVizZ0/mLLrj4GXFX
QWvEMX41ofRUFpI=
=Bifn
-END PGP SIGNATURE End Message ---

Bug#891529: marked as done (acedb FTBFS with flex 2.6.4-6)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 10:34:26 +
with message-id 
and subject line Bug#891529: fixed in acedb 4.9.39+dfsg.02-3
has caused the Debian Bug report #891529,
regarding acedb FTBFS with flex 2.6.4-6
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.)


-- 
891529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acedb
Version: 4.9.39+dfsg.02-2
Severity: serious
Tags: patch

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

...
gcc -g -Wl,-z,relro -Wl,-z,now -o metacheck metadata.o -L. -lace -lfree 
-L/usr/X11R6/lib `../w3rdparty/libs-config glib-2.0 gtk+-2.0` -lm -lreadline 
-lX11 -lfl 
./libfree.a(filsubs.o): In function `filTmpOpenWithSuffix':
acedb_4.9.39+dfsg.02-2/bin.LINUX_4/filsubs.c:588: warning: the use of `tempnam' 
is dangerous, better use `mkstemp'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libfl.so: undefined 
reference to `yylex'
collect2: error: ld returned 1 exit status
make[3]: *** [makefile:1271: metacheck] Error 1


Fix attached.
Description: With shared libfl needless linking causes FTBFS
 Due to libfl requiring yylex.
Author: Adrian Bunk 

--- acedb-4.9.39+dfsg.02.orig/wmake/truemake
+++ acedb-4.9.39+dfsg.02/wmake/truemake
@@ -1017,7 +1017,7 @@ acelibtest : libfree.a libace.a acelibte
 
 tagcount : libfree.a libace.a tagcount.c
$(CC) tagcount.c
-   $(LINKER) -o tagcount tagcount.o -L. -lace -lfree $(LIBS) $(LEX_LIBS)
+   $(LINKER) -o tagcount tagcount.o -L. -lace -lfree $(LIBS)
 
 
 ##
@@ -1268,7 +1268,7 @@ intron2 : libfree.a intron2.o
$(LINKER)  -o intron2 intron2.o -L. -lfree $(LIBS)
 
 metacheck : libfree.a libace.a metadata.o
- $(LINKER) -o metacheck metadata.o -L. -lace -lfree $(LIBS) 
$(LEX_LIBS) 
+ $(LINKER) -o metacheck metadata.o -L. -lace -lfree $(LIBS)
 
 makeUserPasswd: makeUserPasswd.c libfree.a libmd5.a 
$(CC) $@.c
--- End Message ---
--- Begin Message ---
Source: acedb
Source-Version: 4.9.39+dfsg.02-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated acedb 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, 28 Feb 2018 11:11:58 +0100
Source: acedb
Binary: acedb-other-dotter acedb-other-belvu acedb-other
Architecture: source
Version: 4.9.39+dfsg.02-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 acedb-other - retrieval of DNA or protein sequences
 acedb-other-belvu - transitional package for belvu
 acedb-other-dotter - transitional package for dotter
Closes: 891529
Changes:
 acedb (4.9.39+dfsg.02-3) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Fix with shared libfl needless linking
 Closes: #891529
 .
   [ Andreas Tille ]
   * Standards-Version: 4.1.3
   * Do not create empty directories
   * Drop outdated text from README.Debian
Checksums-Sha1:
 aaa9997c360464361809ea88232b981ba10a8078 2255 acedb_4.9.39+dfsg.02-3.dsc
 c86c0df440ca96e05a55cd224199bc638286b0c2 13440 
acedb_4.9.39+dfsg.02-3.debian.tar.xz
Checksums-Sha256:
 c71375e61fbffb559e770aa2da30c5e243f2cee7a2aff5d89ab04017d9b2b02c 2255 
acedb_4.9.39+dfsg.02-3.dsc
 10ccf8f002094ef0a9cf9c2300566f5d5fbadcd417566d3d76768807967260e5 13440 
acedb_4.9.39+dfsg.02-3.debian.tar.xz
Files:
 cd338651cb6bae6c06793e67cad0ae1f 2255 science optional 
acedb_4.9.39+dfsg.02-3.dsc
 acee54d0d88c3e4d77d0ed69f5cfe727 13440 science optional 
acedb_4.9.39+dfsg.02-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlqWgaoRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFMCg/5AXYELYnICwoW6HRipJVMLAOCvBoWUfTR
j9mnKrvGmVVEmaVBmEaPzYGyAOk/afsVcmvhHJKlzgPuWAqFv5pH+kSgoZzqUvRX

Bug#891640: marked as done (arctica-greeter: Fails to build with vala 0.40)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 10:04:22 +
with message-id 
and subject line Bug#891640: fixed in arctica-greeter 0.99.0.3-1
has caused the Debian Bug report #891640,
regarding arctica-greeter: Fails to build with vala 0.40
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.)


-- 
891640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arctica-greeter
Version:  1.7.0-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: vala-0.40
Tags: buster sid patch

arctica-greeter fails to build from source with vala 0.37.91 which is
currently in experimental and will be uploaded to unstable soon.

You can find a build log from Ubuntu 18.04 Alpha at
https://launchpad.net/~jbicha/+archive/ubuntu/vala40/+build/14327075

See my merge proposal at
https://github.com/ArcticaProject/arctica-greeter/pull/9

Also, could you please add debian/source/include-binaries
with this content:

debian/theme-debian-logo-v9.png
debian/theme-debian-logo-bare.png

(Its absence upset my build tools while I was testing this fix)

On behalf of the Debian GNOME Team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: arctica-greeter
Source-Version: 0.99.0.3-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated arctica-greeter 
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, 28 Feb 2018 10:34:08 +0100
Source: arctica-greeter
Binary: arctica-greeter arctica-greeter-guest-session 
arctica-greeter-remote-logon arctica-greeter-theme-debian
Architecture: source
Version: 0.99.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Description:
 arctica-greeter - LightDM Arctica Greeter
 arctica-greeter-guest-session - LightDM Arctica Greeter - Guest Session Support
 arctica-greeter-remote-logon - LightDM Arctica Greeter - Remote Login Support
 arctica-greeter-theme-debian - LightDM Arctica Greeter - Debian Theme
Closes: 891640
Changes:
 arctica-greeter (0.99.0.3-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #891640).
   * debian/control:
 + Bump Standards-Version: to 4.1.3. No changes needed.
   * debian/{control,compat}:
 + Bump DH compat level to 11.
   * debian/copyright:
 + Use secure URI for referencing copyright format.
   * debian/source/include-binaries:
 + Add file. Let's tolerate the PNG files for the debian theme.
   This file may have been part of previous upload, but was
   missing in the packaging Git.
   * debian/upstream/signing-key.asc:
   Add file. This file may have been part of previous upload, but was
   missing in the packaging Git.
Checksums-Sha1:
 4d6ff15f7a87d517ffdbb042804ef3a23560a87d 3082 arctica-greeter_0.99.0.3-1.dsc
 bbf09fc5572071f2df1da925a785218283ec8245 3527183 
arctica-greeter_0.99.0.3.orig.tar.gz
 698c7961996194782e4747ae9f7204c500640547 833 
arctica-greeter_0.99.0.3.orig.tar.gz.asc
 90a340dbd622c23f0fa9e43e9515e1d3c6f86fb7 42012 
arctica-greeter_0.99.0.3-1.debian.tar.xz
 900b3a96a0fdc0bd75a1b83f8c3b8a4a99a4521e 18462 
arctica-greeter_0.99.0.3-1_source.buildinfo
Checksums-Sha256:
 f58286c2d67b510195704240a13835c95159dd4bedd2e94f66a70de3ede067d3 3082 
arctica-greeter_0.99.0.3-1.dsc
 f6c1aa263d1c9eccd7f3b77054fe178b3f8f7d4a34274caf57a130f2fde805bc 3527183 
arctica-greeter_0.99.0.3.orig.tar.gz
 0c9792a4e9bfdffb203fad386da225aa7aee397c2e18848e9887a85e2e7f57e4 833 
arctica-greeter_0.99.0.3.orig.tar.gz.asc
 a736620fcdc5b61e6b3f82caef4c02083514ae858fbf697ef6b4c69a8f34aed6 42012 
arctica-greeter_0.99.0.3-1.debian.tar.xz
 99e7e56d0dd9b2dcc689fb6d48282314c2d0d111b586da1a41ee53c27a885a05 18462 
arctica-greeter_0.99.0.3-1_source.buildinfo
Files:
 57242a54be6fb1d084dd9b59b2b318b3 3082 x11 optional 

Bug#891728: ptlib FTBFS with glibc 2.26

[Adrian Bunk]

Source: ptlib
Version: 2.10.11~dfsg-2.1
Severity: serious
Tags: buster sid

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

...
ptlib/unix/channel.cxx: In member function 'virtual PBoolean 
PChannel::Read(const VectorOfSlice&)':
ptlib/unix/channel.cxx:239:40: error: '::readv' has not been declared
   if (ConvertOSError(lastReadCount = ::readv(os_handle, [0], 
slices.size()), LastReadError))
^
ptlib/unix/channel.cxx:239:40: note: suggested alternative: 'read'
   if (ConvertOSError(lastReadCount = ::readv(os_handle, [0], 
slices.size()), LastReadError))
^
read
ptlib/unix/channel.cxx: In member function 'virtual PBoolean 
PChannel::Write(const VectorOfSlice&)':
ptlib/unix/channel.cxx:258:22: error: '::writev' has not been declared
   while ((result = ::writev(os_handle, [0], slices.size())) < 0) {
  ^~
ptlib/unix/channel.cxx:258:22: note: suggested alternative: 'write'
   while ((result = ::writev(os_handle, [0], slices.size())) < 0) {
  ^~
  write

Processed: waiting for one bug fix before uploading gitlab 9.5 to unstable

[Debian Bug Tracking System]

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

> block 891630 by 891724
Bug #891630 [ruby-task-list] Missing dep making it unusable
891630 was not blocked by any bugs.
891630 was not blocking any bugs.
Added blocking bug(s) of 891630: 891724
>
End of message, stopping processing here.

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

Bug#891727: python-eventlet FTBFS: ERROR: tests.openssl_test.test_import

[Adrian Bunk]

Source: python-eventlet
Version: 0.20.0-4
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-eventlet.html

...
==
ERROR: tests.openssl_test.test_import
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/python-eventlet-0.20.0/.pybuild/pythonX.Y_2.7/build/tests/openssl_test.py",
 line 13, in test_import
import eventlet.green.OpenSSL.SSL
  File "eventlet/green/OpenSSL/__init__.py", line 3, in 
from . import SSL
  File "eventlet/green/OpenSSL/SSL.py", line 2, in 
from OpenSSL.SSL import *
  File "/usr/lib/python2.7/dist-packages/cryptography/utils.py", line 124, in 
__getattr__
obj = getattr(self._module, attr)
AttributeError: 'module' object has no attribute 'SSL_ST_INIT'

--
Ran 619 tests in 76.158s

FAILED (SKIP=95, errors=1)
Exception TypeError: "'NoneType' object is not callable" in  ignored
Exception TypeError: "'NoneType' object is not callable" in  ignored
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-eventlet-0.20.0/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 25

Bug#891725: python-scrapy FTBFS: test failures

[Adrian Bunk]

Source: python-scrapy
Version: 1.5.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scrapy.html

...
_ TextResponseTest.test_invalid_utf8_encoded_body_with_valid_utf8_BOM __

self = 

def test_invalid_utf8_encoded_body_with_valid_utf8_BOM(self):
r6 = self.response_class("http://www.example.com;,
 headers={"Content-type": ["text/html; 
charset=utf-8"]},
 body=b"\xef\xbb\xbfWORD\xe3\xab")
self.assertEqual(r6.encoding, 'utf-8')
>   self.assertEqual(r6.text, u'WORD\ufffd\ufffd')
E   AssertionError: u'WORD\ufffd' != u'WORD\ufffd\ufffd'
E   - WORD\ufffd
E   + WORD\ufffd\ufffd
E   ?  +

/build/1st/python-scrapy-1.5.0/.pybuild/pythonX.Y_2.7/build/tests/test_http_response.py:275:
 AssertionError
_ HtmlResponseTest.test_invalid_utf8_encoded_body_with_valid_utf8_BOM __

self = 

def test_invalid_utf8_encoded_body_with_valid_utf8_BOM(self):
r6 = self.response_class("http://www.example.com;,
 headers={"Content-type": ["text/html; 
charset=utf-8"]},
 body=b"\xef\xbb\xbfWORD\xe3\xab")
self.assertEqual(r6.encoding, 'utf-8')
>   self.assertEqual(r6.text, u'WORD\ufffd\ufffd')
E   AssertionError: u'WORD\ufffd' != u'WORD\ufffd\ufffd'
E   - WORD\ufffd
E   + WORD\ufffd\ufffd
E   ?  +

/build/1st/python-scrapy-1.5.0/.pybuild/pythonX.Y_2.7/build/tests/test_http_response.py:275:
 AssertionError
__ XmlResponseTest.test_invalid_utf8_encoded_body_with_valid_utf8_BOM __

self = 

def test_invalid_utf8_encoded_body_with_valid_utf8_BOM(self):
r6 = self.response_class("http://www.example.com;,
 headers={"Content-type": ["text/html; 
charset=utf-8"]},
 body=b"\xef\xbb\xbfWORD\xe3\xab")
self.assertEqual(r6.encoding, 'utf-8')
>   self.assertEqual(r6.text, u'WORD\ufffd\ufffd')
E   AssertionError: u'WORD\ufffd' != u'WORD\ufffd\ufffd'
E   - WORD\ufffd
E   + WORD\ufffd\ufffd
E   ?  +

Processed: Bug#891640 marked as pending

[Debian Bug Tracking System]

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

> tag 891640 pending
Bug #891640 [arctica-greeter] arctica-greeter: Fails to build with vala 0.40
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#891640: marked as pending

[Mike Gabriel]

tag 891640 pending
thanks

Hello,

Bug #891640 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/pkg-remote/arctica-greeter.git/commit/?id=ba94f5a

---
commit ba94f5a8ed907aaf4871b258ac910788a5017fed
Author: Mike Gabriel 
Date:   Wed Feb 28 10:48:48 2018 +0100

upload to unstable (debian/0.99.0.3-1)

diff --git a/debian/changelog b/debian/changelog
index df12aee..d20002a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,21 @@
-arctica-greeter (0.99.0.3-1) UNRELEASED; urgency=medium
-
-  * New upstream release.
-
- -- Mike Gabriel   Wed, 28 Feb 2018 10:18:27 +0100
+arctica-greeter (0.99.0.3-1) unstable; urgency=medium
+
+  * New upstream release. (Closes: #891640).
+  * debian/control:
++ Bump Standards-Version: to 4.1.3. No changes needed.
+  * debian/{control,compat}:
++ Bump DH compat level to 11.
+  * debian/copyright:
++ Use secure URI for referencing copyright format.
+  * debian/source/include-binaries:
++ Add file. Let's tolerate the PNG files for the debian theme.
+  This file may have been part of previous upload, but was
+  missing in the packaging Git.
+  * debian/upstream/signing-key.asc:
+  Add file. This file may have been part of previous upload, but was
+  missing in the packaging Git.
+
+ -- Mike Gabriel   Wed, 28 Feb 2018 10:34:08 +0100
 
 arctica-greeter (0.99.0.2-2) unstable; urgency=medium
 

Processed: rake assets:precompile fails with 'ExecJS::ProgramError: TypeError: UglifyJS.Compressor is not a function'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 help
Bug #891724 [gitlab] rake assets:precompile fails with 'ExecJS::ProgramError: 
TypeError: UglifyJS.Compressor is not a function'
Added tag(s) help.

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

Bug#891724: rake assets:precompile fails with 'ExecJS::ProgramError: TypeError: UglifyJS.Compressor is not a function'

[Pirate Praveen]

Package: gitlab
Version: 9.5.4+dfsg-6
Severity: grave
Control: tag -1 help

gitlab currently fails to install, it was working earlier so the issue
was likely introduced by a regression in one of the dependencies. But so
far I'm unable to track it down.

Precompiling assets...
I, [2018-02-28T09:39:09.279812 #22324]  INFO -- : Writing
/usr/share/gitlab/public/assets/print-87b4ace0db1f79d91e4fe6e74435b66b71d70fee57ffbb72d0fade17374fcc6b.css
I, [2018-02-28T09:39:09.281316 #22324]  INFO -- : Writing
/usr/share/gitlab/public/assets/print-87b4ace0db1f79d91e4fe6e74435b66b71d70fee57ffbb72d0fade17374fcc6b.css.gz
I, [2018-02-28T09:39:09.451061 #22324]  INFO -- : Writing
/usr/share/gitlab/public/assets/notify-abfe30822d82207505a29881cc27c46d0cf2f8bf68481bd421ba1ce23ca7c508.css
I, [2018-02-28T09:39:09.451349 #22324]  INFO -- : Writing
/usr/share/gitlab/public/assets/notify-abfe30822d82207505a29881cc27c46d0cf2f8bf68481bd421ba1ce23ca7c508.css.gz
I, [2018-02-28T09:39:10.417617 #22324]  INFO -- : Writing
/usr/share/gitlab/public/assets/katex-e46cafe9c3fa73920a7c2c063ee8bb0613e0cf85fd96a3aea25f8419c4bfcfba.css
I, [2018-02-28T09:39:10.417911 #22324]  INFO -- : Writing
/usr/share/gitlab/public/assets/katex-e46cafe9c3fa73920a7c2c063ee8bb0613e0cf85fd96a3aea25f8419c4bfcfba.css.gz
rake aborted!
ExecJS::ProgramError: TypeError: UglifyJS.Compressor is not a function
apply.source (eval at  ((execjs):4108:8), :23:35)
eval (eval at  ((execjs):4108:8), :63:2)
(execjs):4108:8
(execjs):4114:14
(execjs):1:102
Object. ((execjs):1:120)
Module._compile (module.js:635:30)
Object.Module._extensions..js (module.js:646:10)
Module.load (module.js:554:32)
tryModuleLoad (module.js:497:12)
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--install):
 installed gitlab package post-installation script subprocess returned
error exit status 1
Processing triggers for systemd (237-3) ...
Errors were encountered while processing:
 gitlab



signature.asc
Description: OpenPGP digital signature

Bug#891722: sqwebmail-de FTBFS: applying patches fails

[Adrian Bunk]

Source: sqwebmail-de
Version: 5.5.1-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sqwebmail-de.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/sqwebmail-de-5.5.1'
mkdir htmltree
cp -a /usr/lib/courier/sqwebmail/html/en-us/ htmltree
rm htmltree/en-us/ISPELLDICT
echo -n default > htmltree/en-us/ISPELLDICT
# patch files - except TIMEZONELIST
filterdiff -x */TIMEZONELIST < `ls *diff ` | (cd htmltree/en-us; patch -p1 )
patching file ISPELLDICT
patching file LANGUAGE
patching file LANGUAGE_PREF
patching file LOCALE
patching file abooklist.html
patching file acl.html
patching file attachments.html
patching file autoresponder.html
patching file calendarlogin.inc.html
patching file empty.html
patching file eventacl.html
patching file eventdaily.html
patching file eventdelete.html
patching file eventmonthly.html
patching file eventnotifydelete.txt
patching file eventnotifynew.txt
patching file eventnotifysubject.txt
patching file eventshow.html
patching file eventweekly.html
patching file expired.html
patching file filter.html
patching file folder.html
patching file folders.html
patching file gpg.html
Hunk #3 FAILED at 80.
Hunk #4 FAILED at 127.
Hunk #5 succeeded at 123 (offset -16 lines).
Hunk #6 succeeded at 132 (offset -16 lines).
Hunk #7 succeeded at 153 (offset -16 lines).
Hunk #8 FAILED at 181.
Hunk #9 succeeded at 183 (offset -16 lines).
Hunk #10 succeeded at 191 (offset -16 lines).
3 out of 10 hunks FAILED -- saving rejects to file gpg.html.rej
patching file gpgcreate.html
patching file gpgerr.html
patching file index.html
Hunk #2 succeeded at 18 with fuzz 2.
patching file invalid.html
patching file keyimport.html
patching file ldaplist.html
patching file ldapsearch.html
patching file login.html
patching file loginform.inc.html
patching file navbar.inc.html
patching file navbar2.inc.html
patching file navbar3.inc.html
patching file newevent.html
patching file newmsg.html
patching file preferences.html
patching file print.html
patching file printnocookie.html
patching file printredirect.html
patching file quickadd.html
patching file readmsg.html
patching file redirect.html
patching file spellchk.html
make[1]: *** [debian/rules:20: override_dh_auto_build] Error 1

Bug#891673: marked as done (collectd: build dependency intel-cmt-cat is only available on amd64+i386)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 09:34:21 +
with message-id 
and subject line Bug#891673: fixed in collectd 5.8.0-2
has caused the Debian Bug report #891673,
regarding collectd: build dependency intel-cmt-cat is only available on 
amd64+i386
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.)


-- 
891673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: collectd
Version: 5.8.0-1
Severity: serious

The new build dependency intel-cmt-cat is only available on amd64+i386,
and should therefore only be used on these architectures.
--- End Message ---
--- Begin Message ---
Source: collectd
Source-Version: 5.8.0-2

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

Debian distribution maintenance software
pp.
Marc Fournier  (supplier of updated collectd 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: Wed, 28 Feb 2018 10:06:58 +0100
Source: collectd
Binary: collectd-core collectd collectd-utils collectd-dbg collectd-dev 
libcollectdclient-dev libcollectdclient1
Architecture: source
Version: 5.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Harl 
Changed-By: Marc Fournier 
Description:
 collectd   - statistics collection and monitoring daemon
 collectd-core - statistics collection and monitoring daemon (core system)
 collectd-dbg - statistics collection and monitoring daemon (debugging symbols)
 collectd-dev - statistics collection and monitoring daemon (development files)
 collectd-utils - statistics collection and monitoring daemon (utilities)
 libcollectdclient-dev - client library for collectd's control interface 
(development file
 libcollectdclient1 - client library for collectd's control interface
Closes: 891673
Changes:
 collectd (5.8.0-2) unstable; urgency=medium
 .
   * debian/control: Limit intel-cmt-cat Build-depend to intel architectures;
 thanks to Adrian Bunk for reporting this. (Closes: #891673)
Checksums-Sha1:
 aa3240b807d135ea8ae132b567117a0930274d0c 4041 collectd_5.8.0-2.dsc
 7f1b91b2f74794d4c94b370d0e71e29c421cb4dc 76656 collectd_5.8.0-2.debian.tar.xz
 51031f7aedb08677b5d5e9fc4f5e41f904c98e76 20230 
collectd_5.8.0-2_source.buildinfo
Checksums-Sha256:
 3bddee61e2d5127737ab61bb41a437b6136330dbdcacaac90f894d239fa936a9 4041 
collectd_5.8.0-2.dsc
 afeafe0968439a5efe7b5c6c44abd9895192ad82274b50ccabb69b424301f2ea 76656 
collectd_5.8.0-2.debian.tar.xz
 6925e78138dce6ee4d703bc6107ab29281c2bb0f66e5be5a077606588636ec08 20230 
collectd_5.8.0-2_source.buildinfo
Files:
 341e00b980e68016e32829914138b42f 4041 utils optional collectd_5.8.0-2.dsc
 7d25e2c390c0e16ca001486eb7c36c43 76656 utils optional 
collectd_5.8.0-2.debian.tar.xz
 c6eb99fb6d92267a5fd73e6d91fa2905 20230 utils optional 
collectd_5.8.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0SB09zJN4Zng3RwbzAV+ci8f/McFAlqWcg0ACgkQzAV+ci8f
/MeCXA//YihkkYTjrljHPwMSvhcJZqcsBu9RzVBuV6B3936h16Eti+hSXcKUpfuk
P3SMf2MGRFFdnqrQlzlEMXgD3eKgTvYoAgPC4NYrzxgCMaFhLsAmCt+MWcllDvoM
mhg/MQniPjnQPTAmHdtg+63OCAqCHu4BFkEl93lMcbsWCBIIkM+rEB79vWnEOFmh
c668ijKwVeshTW0AM6y4pWBnOwBQRphwS3b1XsvKb5yo7T82nR7tx3E6aDqFkRZM
qhf5x+HUJWe+6Lyiqxvf0P9d3SHoNf2PJaWiw31YjTCeuAl6BzCpdluNGavREU/A
xfUKCNLyrn60JHz2jTxORv9Me1EljmT6sHaWSHgIiJ5UHq9hOLCxz1kB+X3xFa3X
e5VmMmR8TDRKQZCmaysWRwvcDsGljpHk7rUAe7KzT6+puzeZAMQfTh1plo9fyQjU
eEvVOQSoFvNircXIEJ7z6HNantEYKWVulfQkLdgnFjXORRbnC4Jo67i+rZjhdKS7
Gki4Y7KnAo2NKxWF5mEq+NAzhQ8VC1+ejAohNL0+JVEthoMEFhz4RI0FpbsaVIo/
+uaKevjjKoL8pvgfaGdi57dCmEd4oaI2VQceEYjybEfSX0N1lv3n316u/0mt4sfZ
D290kjoeioTUxF0ZAlHRPjoTtRAy8Yrrq6kQzYXFF/AWhY53WyU=
=8sdZ
-END PGP SIGNATURE End Message ---

Bug#891721: ubuntu-dev-tools FTBFS: test failure

[Adrian Bunk]

Source: ubuntu-dev-tools
Version: 0.161
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ubuntu-dev-tools.html

...
==
FAIL: test_pylint (ubuntutools.test.test_pylint.PylintTestCase)
Test: Run pylint on Python source code
--
Traceback (most recent call last):
  File "/build/1st/ubuntu-dev-tools-0.161/ubuntutools/test/test_pylint.py", 
line 47, in test_pylint
self.assertFalse(err, pylint_binary + ' crashed. Error output:\n' + 
err.decode())
AssertionError: pylint crashed. Error output:
Using config file /build/1st/ubuntu-dev-tools-0.161/ubuntutools/test/pylint.conf


==
FAIL: test_flake8 (ubuntutools.test.test_flake8.Flake8TestCase)
Test: Run flake8 on Python source code
--
Traceback (most recent call last):
  File "/build/1st/ubuntu-dev-tools-0.161/ubuntutools/test/test_flake8.py", 
line 44, in test_flake8
self.assertFalse(out, "flake8 found issues:\n" + out.decode())
AssertionError: flake8 found issues:
ubuntutools/test/test_logger.py:19:1: E722 do not use bare except'
ubuntutools/test/test_config.py:23:1: E722 do not use bare except'
ubuntutools/sponsor_patch/patch.py:76:72: E741 ambiguous variable name 'l'
ubuntutools/requestsync/mail.py:235:9: E722 do not use bare except'


--
Ran 81 tests in 248.085s

FAILED (failures=2, skipped=1)
Test failed: 
The old maintainer was: Ubuntu MOTU Developers 
Resetting as: Ubuntu Developers 
error: Test failed: 
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:6: build] Error 25

Bug#891720: dumb-jump-el FTBFS: test failures

[Adrian Bunk]

Source: dumb-jump-el
Version: 0.5.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dumb-jump-el.html

...
Ran 136 tests, 134 results as expected, 2 unexpected (2019-03-30 09:34:54-1200)

2 unexpected results:
   FAILED  dumb-jump-find-proj-root-test
   FAILED  dumb-jump-quick-look-test

dh_elpa_test: emacs -batch -Q -l package --eval "(add-to-list 
'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval 
"(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" 
-f package-initialize -L . -L test --eval "(load-file \"test/test-helper.el\")" 
-l test/dumb-jump-test.el --eval \(ert-run-tests-batch-and-exit\) returned exit 
code 1
make: *** [debian/rules:4: build] Error 2

Bug#891719: gtimelog FTBFS: test failure

[Adrian Bunk]

Source: gtimelog
Version: 0.11-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gtimelog=all=0.11-2=1519804492=0

...
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: python3.6 setup.py test 
running test
Searching for PyGObject

Note: Bypassing https://pypi.python.org/simple/PyGObject/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

Couldn't find index page for 'PyGObject' (maybe misspelled?)
Scanning index of all packages (this may take a while)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

No local packages or working download links found for PyGObject
error: Could not find suitable distribution for Requirement.parse('PyGObject')
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python3.6 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
make: *** [debian/rules:4: build-indep] Error 25

Bug#890591: marked as done (paml binary-all FTBFS: sed: can't read debian/paml//usr/lib/paml/data/*.ctl: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 28 Feb 2018 09:04:30 +
with message-id 
and subject line Bug#890591: fixed in paml 4.9g+dfsg-3
has caused the Debian Bug report #890591,
regarding paml binary-all FTBFS: sed: can't read 
debian/paml//usr/lib/paml/data/*.ctl: 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.)


-- 
890591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paml
Version: 4.9e+dfsg-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=paml=all=4.9g%2Bdfsg-1=1518781928=0

...
dh_install
set -x ; \
for datfile in debian/paml//usr/lib/paml/data/*.ctl ; do \
for item in seqfile treefile ; do \
sed -i -e "s?\(${item} =\).*[^a-z^A-Z^0-9^.^ 
]\+\([a-zA-Z0-9]\+\.[a-z]\+\)?\1 /usr/lib/paml/data/\2?" \
   -e "s?\(${item} =\) \([a-zA-Z0-9]\+\.[a-z]\+\)?\1 
/usr/lib/paml/data/\2?" \
   ${datfile} ; \
done ; \
done
+ sed -i -e s?\(seqfile =\).*[^a-z^A-Z^0-9^.^ ]\+\([a-zA-Z0-9]\+\.[a-z]\+\)?\1 
/usr/lib/paml/data/\2? -e s?\(seqfile =\) \([a-zA-Z0-9]\+\.[a-z]\+\)?\1 
/usr/lib/paml/data/\2? debian/paml//usr/lib/paml/data/*.ctl
sed: can't read debian/paml//usr/lib/paml/data/*.ctl: No such file or directory
+ sed -i -e s?\(treefile =\).*[^a-z^A-Z^0-9^.^ ]\+\([a-zA-Z0-9]\+\.[a-z]\+\)?\1 
/usr/lib/paml/data/\2? -e s?\(treefile =\) \([a-zA-Z0-9]\+\.[a-z]\+\)?\1 
/usr/lib/paml/data/\2? debian/paml//usr/lib/paml/data/*.ctl
sed: can't read debian/paml//usr/lib/paml/data/*.ctl: No such file or directory
make[1]: *** [debian/rules:23: override_dh_install] Error 2
--- End Message ---
--- Begin Message ---
Source: paml
Source-Version: 4.9g+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated paml 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, 28 Feb 2018 09:39:53 +0100
Source: paml
Binary: paml paml-doc
Architecture: source
Version: 4.9g+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 paml   - Phylogenetic Analysis by Maximum Likelihood (PAML)
 paml-doc   - Documentation for PAML
Closes: 890591
Changes:
 paml (4.9g+dfsg-3) unstable; urgency=medium
 .
   * Really enable arch=all build
 Closes: 890591
Checksums-Sha1:
 e35f2949d1d2869c2adafb7aa8d17f5120ab0711 2079 paml_4.9g+dfsg-3.dsc
 6566205d0a5ea4fe0e1fbfdd2c9bc413e3c2f942 5356 paml_4.9g+dfsg-3.debian.tar.xz
Checksums-Sha256:
 5cad784fb7890cc9584a1104b1da340682a229a735f71428aa0ebbdebad9fdb0 2079 
paml_4.9g+dfsg-3.dsc
 26735f010e7a730ace883f878f92b6cb9ec6dedcd9fc580679f89f9542914455 5356 
paml_4.9g+dfsg-3.debian.tar.xz
Files:
 3e21b2ff4b9444efdf3bf79be0ffe3bd 2079 science optional paml_4.9g+dfsg-3.dsc
 918f315a1ef40d5393ebc5f73afa8428 5356 science optional 
paml_4.9g+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlqWbN0RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGoCRAAhcrzE8fUgEvP4KHnVx7EcD0UN8YHx8jv
XfiPpb/Cjw7dsP2c7ktn4gyYwrzKKD1NXt/X7GrvcWMSYnPwaY6QBfDN4xEQKODq
Fuftm+bZhV8dSlASzO76YkYQpzT8lxV5FLCOEBUsZ9ImglGrQ+Rp7ByjiWudOqpu
6odsBfl//rn9Fq5F1giUxK53PaXZm+ZnHjWItwjQAg0Rkg9SnFpXdXkmBdS3EH7Y
6pEyV02NttUwDbtrHYHcKc3sZ0KK9p4l6S4i7xeZCh7nPxQPvRT6CcHAoGPtpuzc
IcTmFk/EhwKwEH0Iiwf2YglPhetWfSX1We7sx3G0017XIrKRmLM+cAEMY9F2IIyG
smM1KUJtTHx0Mjw8UKwR/+opWcOnYYpAg2EYz5sMNYZgSZNzC/ibT6VYa/oRdqJQ
Qlesb2shPC6a4xQk8XX+5R9A1O5bNw94lxUpseg0tWImO4Tle91GvSuuWjjjRoJU
p4raJvEuac2cP0ciPmS++V1GZ5nFNqXzyhSUkpYS0Vyzh30E4n1wrvx76ME6eEvt
Mle76gVqtA/Ad9/klFSWx0hg2Hsbzcr/vGZFJHnXTIToBofCBTz3DfR1vj2gizDM
ckrJNZCqC3RWO6PG4Dtv3crna4bwKoVglx+yYuffPqjT7FCcnWyV/tzNvGioPkew
F24FzEGpd64=
=i4p1
-END PGP SIGNATURE End Message ---

Bug#891716: ruby-rails-admin FTBFS: Could not find 'kaminari' (~> 0.14) - did find: [kaminari-1.0.1]

[Adrian Bunk]

Source: ruby-rails-admin
Version: 0.8.1+dfsg-3
Severity: serious
Tags: buster sid

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

...
┌──┐
│ Checking Rubygems dependency resolution on ruby2.3   │
└──┘

GEM_PATH=debian/ruby-rails-admin/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -e gem\ \"rails_admin\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'kaminari' (~> 0.14) - did find: [kaminari-1.0.1] (Gem::LoadError)

Bug#882103: stretch update for obfsproxy

[intrigeri]

Adrian Bunk:
> Alternatively, I can fix it for stretch if you don't object.

Yes, please :)

Cheers,
-- 
intrigeri