Processed: severity of 909628 is serious

[Debian Bug Tracking System]

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

> severity 909628 serious
Bug #909628 [thunderbird] thunderbird: illegal instruction on non-SSE2 system
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: affects 909778

[Debian Bug Tracking System]

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

> affects 909778 src:freeciv src:audacious-plugins src:mupen64plus-input-sdl 
> src:mupen64plus-video-glide64 src:mupen64plus-ui-console src:fizmo-sdl2
Bug #909778 [libsdl2-dev] libsdl2-dev: SDL_config.h no longer in cflags 
provided by pkg-config/sdl2-config
Added indication that 909778 affects src:freeciv, src:audacious-plugins, 
src:mupen64plus-input-sdl, src:mupen64plus-video-glide64, 
src:mupen64plus-ui-console, and src:fizmo-sdl2
> thanks
Stopping processing here.

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

Bug#909813: rr FTBFS with kernel 4.18 headers

[Adrian Bunk]

Source: rr
Version: 5.2.0-2
Severity: serious
Tags: ftbfs

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

...
/build/1st/rr-5.2.0/src/test/keyctl.c: In function 'main':
/build/1st/rr-5.2.0/src/test/keyctl.c:44:38: error: 'struct keyctl_dh_params' 
has no member named 'private'; did you mean 'dh_private'?
   struct keyctl_dh_params params = {.private = private_key,
  ^~~
  dh_private
/usr/bin/cc -g -O2 -ffile-prefix-map=/build/1st/rr-5.2.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -msse2 -D__MMX__ -D__SSE__ -D__SSE2__ -D__USE_LARGEFILE64 
-pthread -g3 -Wstrict-prototypes -std=gnu11-Wl,-z,relro -Wl,-z,now 
CMakeFiles/kcmp.dir/src/test/kcmp.c.o  -o bin/kcmp -lrt -ldl 
make[3]: *** [CMakeFiles/keyctl.dir/build.make:66: 
CMakeFiles/keyctl.dir/src/test/keyctl.c.o] Error 1

Bug#908463: [Pkg-privacy-maintainers] Bug#908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy

[Antoine Beaupré]

On 2018-09-10 10:43:32, Antoine Beaupré wrote:
> On 2018-09-10 09:59:54, intrig...@debian.org wrote:
>> Package: torbrowser-launcher
>> Version: 0.2.9-4
>> Severity: serious
>> Tags: upstream fixed-upstream
>>
>> Hi,
>>
>> I've just pushed to commits to the upstream "develop" branch that fix
>> Tor Browser 8 for me. Without these, Tor Browser does start but with
>> e10s enabled, no tab will render as Firefox is not allowed to start
>> any "Web Content" process.
>
> I confirm this problem is real. It seems that as soon as anyone tries to
> upgrade torbrowser in Debian now it either fails with #908068 (before
> launcher upgrade) or this (after launcher upgrade).

For what it's worth, I was still getting that error with 0.2.9-5, but a
(forced) update to sid's 0.2.9-6 version fixes the issue on buster.

Thanks for all involved!

A.

-- 
Dr. King’s major assumption was that if you are nonviolent, if you
suffer, your opponent will see your suffering and will be moved to
change his heart. He only made one fallacious assumption: In order for
nonviolence to work, your opponent must have a conscience. The United
States has none.- Stokely Carmichael

Bug#908702: linux-image-4.18.0-1-amd64 prevents use of internet (more or les

[ghpy]

Dear maintainer,

~$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 
(rev 11)
00:05.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 3 
(rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management 
Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and 
Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and 
Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous 
Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and 
Protocol Registers (rev 11)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 2 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 3 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 4 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 8 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation P55 Chipset LPC Interface Controller (rev 
06)
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port 
SATA IDE Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller 
(rev 06)
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port 
SATA IDE Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Redwood HDMI Audio 
[Radeon HD 5000 Series]
02:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 
03)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 03)
04:00.0 SATA controller: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)
04:00.1 IDE interface: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)
06:00.0 IDE interface: Marvell Technology Group Ltd. Device 914d (rev 10)
09:01.0 Communication controller: Conexant Systems, Inc. HSF 56k HSFi Modem 
(rev 01)
09:02.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet 
Adapter (rev 10)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture 
Generic Non-Core Registers (rev 04)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture 
System Address Decoder (rev 04)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
3f:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller (rev 04)
3f:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Target Address Decoder (rev 04)
3f:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Test Registers (rev 04)
3f:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Channel 0 Control Registers (rev 04)
3f:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Channel 0 Address Registers (rev 04)
3f:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Channel 0 Rank Registers (rev 04)
3f:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Channel 0 Thermal Control Registers (rev 04)
3f:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Channel 1 Control Registers (rev 04)
3f:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Channel 1 Address Registers (rev 04)
3f:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Channel 1 Rank Registers (rev 04)
3f:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory 
Controller Channel 1 Thermal Control Registers (rev 04)

I will post the output of dmesg some other time this weekend, because I suppose 
it only makes sense when I am using kernel 4.18 which for obvious reasons I 
normally don't.

Regards
G. Heine

Processed: severity of 860751 is important

[Debian Bug Tracking System]

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

> severity 860751 important
Bug #860751 [mawk] mawk: segfaults on i386 during win32-loader build
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#909607: marked as done (CVE-2018-17336)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 20:43:16 +
with message-id 
and subject line Bug#909607: fixed in udisks2 2.8.1-1
has caused the Debian Bug report #909607,
regarding CVE-2018-17336
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.)


-- 
909607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udisks2
Version: 2.7.6-3
Severity: grave
Tags: security

This was assigned http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17336:
https://github.com/storaged-project/udisks/issues/578

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: udisks2
Source-Version: 2.8.1-1

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated udisks2 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: Fri, 28 Sep 2018 15:48:23 -0400
Source: udisks2
Binary: udisks2 udisks2-btrfs udisks2-lvm2 udisks2-doc libudisks2-0 
libudisks2-dev gir1.2-udisks-2.0
Architecture: source
Version: 2.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Jeremy Bicha 
Description:
 gir1.2-udisks-2.0 - GObject based library to access udisks2 - introspection 
data
 libudisks2-0 - GObject based library to access udisks2
 libudisks2-dev - GObject based library to access udisks2 - development files
 udisks2- D-Bus service to access and manipulate storage devices
 udisks2-btrfs - BTRFS support for udisks2
 udisks2-doc - udisks2 documentation
 udisks2-lvm2 - LVM2 support for udisks2
Closes: 909607
Changes:
 udisks2 (2.8.1-1) unstable; urgency=medium
 .
   [ Andreas Henriksson ]
   * New upstream release.
 - includes fix for CVE-2018-17336 (Closes: #909607)
   * Bump build-dependency version according to configure.ac changes
   * Drop patches from upstream now included in release
   * libudisks2-0.symbols: Add newly introduced symbols
 .
   [ Jeremy Bicha ]
   * Fix udevadm-called-without-guard lintian warning
Checksums-Sha1:
 0d098c7bbe08c36e7c8826c495581c51263083cc 3203 udisks2_2.8.1-1.dsc
 e69fc1a417f4d5e116487ca735bbef89e96cc0f4 1354879 udisks2_2.8.1.orig.tar.bz2
 7dcc19192c6c2151bd59ba0e27e91672f4fabe7e 14752 udisks2_2.8.1-1.debian.tar.xz
 298d61db6147ae6f0d449c34f2588c8be63857e0 10322 udisks2_2.8.1-1_source.buildinfo
Checksums-Sha256:
 61bdb0f17ef6e84a0e137cf8d340e4c518bd5f7a2a303c2d4ca5ae105b5bd365 3203 
udisks2_2.8.1-1.dsc
 4fcf49ef63c071bb35ea6351fdc2208dd6e54dfefd6ee29ee0c414f8dfde461c 1354879 
udisks2_2.8.1.orig.tar.bz2
 da946db47d144ae1a142205964ee909de49def52306673870251cfd9d4a8fad7 14752 
udisks2_2.8.1-1.debian.tar.xz
 d9e8d99719d43351b18a7470bc71a89640ad6ba03a90886210aa86b1b120b1fa 10322 
udisks2_2.8.1-1_source.buildinfo
Files:
 97bb63396ef6c444c03443138c7985d5 3203 admin optional udisks2_2.8.1-1.dsc
 aefebdb5a082f99b4f86cadc41352b3d 1354879 admin optional 
udisks2_2.8.1.orig.tar.bz2
 4a647d918fe17bac59e1ae83e8bdb993 14752 admin optional 
udisks2_2.8.1-1.debian.tar.xz
 9ebf6f7257f7d43ea9e9b25e224e63bb 10322 admin optional 
udisks2_2.8.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAluuhxEACgkQ5mx3Wuv+
bH34vA//SQtXVChwq4vPWNRCPpPvdLYT27BlamDkmespfH79/F8NqaCD/4Ylgn6V
W1Erss1S+gtMOLstNJSm1iDol4QxTDuFYUI9ytq7+M6CeLevmQJc0DjJnH3c3Vc3
/4fvGBDqpKJxSUY8cJRpqQ6kWiIkr4cp0wkIgmRxFrmQRMq4Xe/jx6RJSGaRfXcA
j9Z6lGdYF/YreclhyMIHetxPE5qpHZwYabQ+gDGBoTNHVZF88Hn2vEFnbldrb5jy
tq9pppQet30Hg4BhymDuJp/E1AiC/d6wEFBgwu1Vhj3pM50ChRLWc4ticzzrKroS
nWxXfXgVzJYdzjrGid5w2k7uXVT1CUC39D0DU1bbHEm3eMar6+DdixRTqujvZgUW
MhKf3YWp+JpiwA0JxR/Yy3snPfMw9hAgDjyMSqA9RFpOEusYiRCgFEYhwee6vita
uVutmizEEMdu3DQC5zyvHddNKtZ5fPyJxfezhNRkzCVyqWOiGk3Emh7e9emi3Eyp
FWWmQPY76uyrn3DISK4fGSEbc0ePv//t+6ibeZ2UdLTjHBYMfgUp3MVqiatr0izY
XChOQPKLnFRj26P4/h0zJ95jC0iyKJXGve8lmJvG7HiEMGSrRk2oeEJjN4aY8444
IuZULK3z4YE2gMIcH6UMg+A+Qk6kgxK0uDBF1g8D2/Zi81RHPRw=
=nwgt
-END PGP SIGNATURE End Message ---

Bug#902222: marked as done (celery-haystack: depends on django-celery-transactions which has been requested to be removed)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 20:36:14 +
with message-id 
and subject line Bug#90: fixed in celery-haystack 0.10-3
has caused the Debian Bug report #90,
regarding celery-haystack: depends on django-celery-transactions which has been 
requested to be removed
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.)


-- 
90: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: celery-haystack
Version: 0.10-2
Severity: serious
Control: block 897415 with -1

Hi,

celery-haystack depends on django-celery-transactions which has been
requested to be removed.


Andreas
--- End Message ---
--- Begin Message ---
Source: celery-haystack
Source-Version: 0.10-3

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated celery-haystack 
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: Fri, 28 Sep 2018 21:56:56 +0200
Source: celery-haystack
Binary: python-django-celery-haystack python3-django-celery-haystack
Architecture: source all
Version: 0.10-3
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-celery-haystack - utilize Celery for automatic haystack index 
updates
 python3-django-celery-haystack - utilize Celery for automatic haystack index 
updates (Python3 vers
Closes: 90
Changes:
 celery-haystack (0.10-3) unstable; urgency=low
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Michael Fladischer ]
   * Remove django-celery-transactions from Depends as it is no longer
 used (Closes: #90).
   * Bump debhelper compatibility and version to 11.
   * Bump Standards-Version to 4.2.1.
   * Clean up celery_haystack.egg-info/PKG-INFO to allow two builds in a
 row.
   * Enable autopkgtest-pkg-python testsuite.
Checksums-Sha1:
 e60def726b14e68038aae5ed5d08efabb6a7d49f 2116 celery-haystack_0.10-3.dsc
 5c227a82c052ea84b05b12da0c9f5f3aa4d8e85e 8299 celery-haystack_0.10.orig.tar.gz
 badb63150f78e0e086097266c538e255ca63023f 3532 
celery-haystack_0.10-3.debian.tar.xz
 d6303932bb21d88dc581020fe24c9c6d63e606c2 8659 
celery-haystack_0.10-3_amd64.buildinfo
 a0b512fa5590ab8d588af1430c9bb8a2d08f6036 9836 
python-django-celery-haystack_0.10-3_all.deb
 91d8b81f8a980cd9c48416d457036bc0a6788f17 9936 
python3-django-celery-haystack_0.10-3_all.deb
Checksums-Sha256:
 bb1b8782c3f35a93d47c4a9a7bde13ff4b5ec9558b90e15f36eb41fe144c6268 2116 
celery-haystack_0.10-3.dsc
 b6e2a3c70071bef0838ca1a7d9f14fae6c2ecf385704092e59b82147a1ee552e 8299 
celery-haystack_0.10.orig.tar.gz
 f59eb6592e200be09f3e27ea83c228df8b0c7a5e49ed1b96d213017ef8e17ab8 3532 
celery-haystack_0.10-3.debian.tar.xz
 7c7da3d4c010eab82f7f6934ab3392cccebc5a226b5e4a1f52d1d6fde4cd1464 8659 
celery-haystack_0.10-3_amd64.buildinfo
 d6fd416599fbb64c136ad510a0dd32bfa335740645d417c5f5b18efc8b1c807b 9836 
python-django-celery-haystack_0.10-3_all.deb
 0cc9c906545bf1b318ae64539584a8caba1edd306ed13361ef27c8b33fa5f888 9936 
python3-django-celery-haystack_0.10-3_all.deb
Files:
 58c756385c39614e1e82a9b9fd913a3d 2116 python optional 
celery-haystack_0.10-3.dsc
 6e398fd8f69b6d55682dbc9bd22a6fa1 8299 python optional 
celery-haystack_0.10.orig.tar.gz
 6d2c575bf3768e263ff2b95f47c2a746 3532 python optional 
celery-haystack_0.10-3.debian.tar.xz
 08de7b2748ce1332e324682d092a9425 8659 python optional 
celery-haystack_0.10-3_amd64.buildinfo
 f86914137d608bf20810c2503caf161d 9836 python optional 
python-django-celery-haystack_0.10-3_all.deb
 06f2e92fd07bf57acdcbc51b18d69e9f 9936 python optional 
python3-django-celery-haystack_0.10-3_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAluuiOoACgkQ/9PIi5l9
0WqYFwf/cjAQ2b3VH3BU87Kf9E4sAZjM8p2apyraabNmWuiStOvCi2lrhmm+koR7

Bug#904000: audacious: Opening URL fails

[Reiner Herrmann]

Control: found -1 3.7.2-1
Control: fixed -1 3.9-2

Tagging this with the version in stretch, as it was reported there.
I'm not able to reproduce it in unstable.


signature.asc
Description: PGP signature

Processed: Re: audacious: Opening URL fails

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.7.2-1
Bug #904000 [src:audacious] audacious: Opening URL fails
Marked as found in versions audacious/3.7.2-1.
> fixed -1 3.9-2
Bug #904000 [src:audacious] audacious: Opening URL fails
Marked as fixed in versions audacious/3.9-2.

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

Processed: tagging 891551

[Debian Bug Tracking System]

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

> tags 891551 + patch
Bug #891551 [src:faketime] faketime: FTBFS with GCC 8 - error: 'strncpy' 
specified bound 256 equals destination size
Bug #897747 [src:faketime] faketime: ftbfs with GCC-8
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#897774: infinipath-psm: ftbfs with GCC-8

[Reiner Herrmann]

Control: tags -1 + patch

The attached patch fixes the FTBFS with gcc 8.

Regards,
   Reiner
diff --git a/debian/patches/0003-gcc8.patch b/debian/patches/0003-gcc8.patch
new file mode 100644
index 000..b405d18
--- /dev/null
+++ b/debian/patches/0003-gcc8.patch
@@ -0,0 +1,29 @@
+Author: Reiner Herrmann 
+Description: Fix build with gcc 8
+ - psm_utils.c: reserve enough memory for both input strings and the fixed part
+ - psm_ep.c: e has sufficient space to copy including the NULL terminator,
+ which fixes a warning about truncation of the input string
+Bug-Debian: https://bugs.debian.org/897774
+
+--- a/psm_ep.c
 b/psm_ep.c
+@@ -1349,7 +1349,7 @@
+ 
+ b_new = (char *) devstr;
+ e = b_new + len;
+-strncpy(e, devstring, len-1);
++strncpy(e, devstring, len);
+ e[len-1] = '\0';
+ ee = e + len;
+ i = 0;
+--- a/psm_utils.c
 b/psm_utils.c
+@@ -955,7 +955,7 @@
+ 	union psmi_envvar_val env_fi;
+ 	char fvals_str[128];
+ 	char fname[128];
+-	char fdesc[256];
++	char fdesc[300];
+ 
+ 	snprintf(fvals_str, sizeof fvals_str - 1, "%d:%d:1", num, denom);
+ 	fvals_str[sizeof fvals_str - 1] = '\0';
diff --git a/debian/patches/series b/debian/patches/series
index c6d3224..cdf9028 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 0001-Fix-truncation-warnings-with-gcc7.patch
 0002-Include-sys-sysmacros.h-to-avoid-warning-about-minor.patch
+0003-gcc8.patch


signature.asc
Description: PGP signature

Processed: Re: infinipath-psm: ftbfs with GCC-8

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #897774 [src:infinipath-psm] infinipath-psm: ftbfs with GCC-8
Added tag(s) patch.

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

Bug#902222: Bug #902222 in celery-haystack marked as pending

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #90 in celery-haystack reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/celery-haystack/commit/d4b5d256243af19f56600097c1816e50a9776e2f


Remove django-celery-transactions from Depends as it is no longer used (Closes: 
#90).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/90

Processed: Bug #902222 in celery-haystack marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #90 [src:celery-haystack] celery-haystack: depends on 
django-celery-transactions which has been requested to be removed
Added tag(s) pending.

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

Bug#909076: ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--

[Markus Koschany]

Hi,

Am 28.09.18 um 20:54 schrieb Salvatore Bonaccorso:
[...]
> So this would imply changed behaviour in a stable release, and thus
> need extra care to not break more (ps2ascii might not be widely used
> still).

Thanks for sharing this information. I agree that changed behavior in a
stable release is suboptimal but leaving the package vulnerable is not
desirable as well. At the moment I am in favor to apply those two
commits that were mentioned before because they seem to make a real
difference. Perhaps there will be other bug reports that will point us
to a complete fix in the future, and as you said ps2ascii is probably
not widely used, so the regression is apparently rather minor. If it
turns out differently, let's take a look again.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#906351: marked as done (dune-istl: FTBFS in buster/sid (error: static assertion failed))

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 19:34:26 +
with message-id 
and subject line Bug#906351: fixed in dune-istl 2.6.0-2
has caused the Debian Bug report #906351,
regarding dune-istl: FTBFS in buster/sid (error: static assertion failed)
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.)


-- 
906351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dune-istl
Version: 2.6.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep --parallel --builddirectory=build
   dh_update_autotools_config -i -O--parallel -O--builddirectory=build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DBUILD_SHARED_LIBS=1
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DBUILD_SHARED_LIBS=1 ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features

[... snipped ...]

In file included from /usr/include/c++/8/map:60,
 from /<>/dune/istl/repartition.hh:7,
 from /<>/dune/istl/matrixredistribute.hh:6,
 from /<>/dune/istl/test/matrixredisttest.cc:7:
/usr/include/c++/8/bits/stl_tree.h: In instantiation of 'class 
std::_Rb_tree, Dune::FieldMatrix >, std::pair, Dune::FieldMatrix >, 
std::_Identity, Dune::FieldMatrix > >, Dune::{anonymous}::CompPair, 
std::allocator, Dune::FieldMatrix > > >':
/usr/include/c++/8/bits/stl_set.h:133:17:   required from 'class 
std::set, Dune::FieldMatrix >, 
Dune::{anonymous}::CompPair, std::allocator, 
Dune::FieldMatrix > > >'
/<>/dune/istl/matrixutils.hh:196:57:   required from 'void 
Dune::printGlobalSparseMatrix(const M&, C&, std::ostream&) [with M = 
Dune::BCRSMatrix, 
std::allocator > >; C = 
Dune::OwnerOverlapCopyCommunication >; std::ostream = 
std::basic_ostream]'
/<>/dune/istl/test/matrixredisttest.cc:78:26:   required from 'int 
testRepart(int, int) [with int BS = 1]'
/<>/dune/istl/test/matrixredisttest.cc:142:32:   required from here
/usr/include/c++/8/bits/stl_tree.h:457:21: error: static assertion failed: 
comparison object must be invocable as const
   static_assert(is_invocable_v,
 ^
/usr/include/c++/8/bits/stl_tree.h:964:7: warning: 'std::_Rb_tree<_Key, _Val, 
_KeyOfValue, _Compare, _Alloc>::~_Rb_tree() noexcept [with _Key = 
std::pair, Dune::FieldMatrix >; _Val = 
std::pair, Dune::FieldMatrix >; 
_KeyOfValue = std::_Identity, 
Dune::FieldMatrix > >; _Compare = Dune::{anonymous}::CompPair; 
_Alloc = std::allocator, 
Dune::FieldMatrix > >]' used but never defined
   ~_Rb_tree() _GLIBCXX_NOEXCEPT
   ^
/usr/include/c++/8/bits/stl_tree.h:699:4: warning: 'std::_Rb_tree<_Key, _Val, 
_KeyOfValue, _Compare, _Alloc>::_Rb_tree_impl<_Key_compare,  
>::_Rb_tree_impl() noexcept (false) [with _Key_compare = 
Dune::{anonymous}::CompPair; bool  = true; _Key = 
std::pair, Dune::FieldMatrix >; _Val = 
std::pair, Dune::FieldMatrix >; 
_KeyOfValue = std::_Identity, 
Dune::FieldMatrix > >; _Compare = Dune::{anonymous}::CompPair; 
_Alloc = std::allocator, 
Dune::FieldMatrix > >]' used but never defined
_Rb_tree_impl()
^
In file included from /usr/include/c++/8/set:61,
 from /usr/include/dune/common/parallel/remoteindices.hh:13,
 from /usr/include/dune/common/parallel/interface.hh:8,
 from /usr/include/dune/common/parallel/communicator.hh:18,
 from /<>/dune/istl/repartition.hh:25,
 from /<>/dune/istl/matrixredistribute.hh:6,
 from /<>/dune/istl/test/matrixredisttest.cc:7:
/usr/include/c++/8/bits/stl_set.h:353:7: warning: 'std::set<_Key, _Compare, 
_Alloc>::iterator std::set<_Key, _Compare, _Alloc>::end() const noexcept [with 
_Key = std::pair, Dune::FieldMatrix >; 
_Compare = Dune::{anonymous}::CompPair; _Alloc = 
std::allocator, Dune::FieldMatrix > >]' used but never defined
   end() 

Bug#909804: Excessive CPU usage at system startup

[Josh Triplett]

Package: gnome-software
Version: 3.28.2-1
Severity: grave

I don't know whether the bug here lies in gnome-software, packagekit, or
some combination of the two.

Every time I start my system, I see packagekit burning a huge amount of
CPU for a minute, and this affects the performance of the system until
it stops.

Corresponding to this, I see a large number of log messages like this:
Sep 28 12:24:38 s PackageKit[717]: search-file transaction /18520_ddabdebb from 
uid 1000 finished with success after 643ms
Sep 28 12:24:39 s PackageKit[717]: search-file transaction /18521_bbebdedd from 
uid 1000 finished with success after 301ms

On my most recent system boot, I see 167 such messages, spanning nearly
a minute worth of 100% CPU.

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

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

Versions of packages gnome-software depends on:
ii  appstream0.12.2-2
ii  apt-config-icons 0.12.2-2
ii  dconf-gsettings-backend [gsettings-backend]  0.30.0-1
ii  gnome-software-common3.28.2-1
ii  gsettings-desktop-schemas3.28.1-1
ii  libappstream-glib8   0.7.12-1
ii  libatk1.0-0  2.30.0-1
ii  libc62.27-6
ii  libcairo21.15.12-1
ii  libfwupd21.1.2-1
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libglib2.0-0 2.58.1-2
ii  libgnome-desktop-3-173.30.1-1
ii  libgspell-1-11.6.1-1
ii  libgtk-3-0   3.24.0-3
ii  libgtk3-perl 0.034-2
ii  libgudev-1.0-0   232-2
ii  libjson-glib-1.0-0   1.4.2-4
ii  libpackagekit-glib2-18   1.1.10-1
ii  libpolkit-gobject-1-00.105-21
ii  libsecret-1-00.18.6-3
ii  libsoup2.4-1 2.64.1-1
ii  packagekit   1.1.10-1
ii  software-properties-gtk  0.96.20.2-1

gnome-software recommends no packages.

Versions of packages gnome-software suggests:
pn  apt-config-icons-hidpi 
pn  fwupd  
pn  gnome-software-plugin-flatpak  
pn  gnome-software-plugin-limba
pn  gnome-software-plugin-snap 

-- no debconf information

Bug#881506: xul-ext-gnome-keyring doesn't work with firefox >=57

[Moritz Mühlenhoff]

On Wed, Sep 26, 2018 at 02:27:00AM +, Ximin Luo wrote:
> Moritz Mühlenhoff:
> > On Tue, Dec 05, 2017 at 01:46:00AM +, Ximin Luo wrote:
> >> Control: severity -1 important
> >> Control: tags -1 + upstream
> >> Control: forwarded -1 
> >> https://github.com/swick/mozilla-gnome-keyring/issues/48
> >>
> >> Mozilla are being slow.
> >>
> >> https://bugzilla.mozilla.org/show_bug.cgi?id=309807
> >> https://bugzilla.mozilla.org/show_bug.cgi?id=106400
> > 
> > Given the pushback in the bugs listed above this seems unlikely
> > to be fixed in Firefox any time soon, so maybe let's drop
> > the Firefox and restrict to Thunderbird (if that is confirmed
> > to be still working fine with TB60)?
> > 
> 
> Pretty sure it doesn't work with TB60, I just upgraded myself and am no 
> longer using this extension.

Shall we remove it from the archive?

Cheers,
Moritz

Bug#909076: ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--

[Mattia Rizzolo]

On Fri, Sep 28, 2018 at 08:54:24PM +0200, Salvatore Bonaccorso wrote:
> There is still the output changes produces, which might impact
> (build)-rdepends, so we might need to be extra careful here (although
> ps2ascii is possibly not widely used).

rather, I think very few software may be as annoying about their
dependencies output as diffoscope is.  And anyway it's only the
testsuite of diffoscope that it is.

> So this would imply changed behaviour in a stable release, and thus
> need extra care to not break more (ps2ascii might not be widely used
> still).

Diffoscope was later been updated to only check the output of ps2ascii
if the version reported was >= 9.21.
I think if that output change was to happen in a stable release and I
were asked to fix diffoscope, I'd just disable that one, rather the
going around asking dpkg what debian revision ghostscript has…

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#909778: libsdl2-dev: SDL_config.h no longer in cflags provided by pkg-config/sdl2-config

[Adrian Bunk]

On Fri, Sep 28, 2018 at 12:47:28PM +, Hugh McMaster wrote:
> On Friday, 28 September 2018 5:09 PM, Simon McVittie wrote:
> > This is a regression caused by fixing #909740. Hugh McMaster correctly
> > pointed out that /usr/include/ is one of the default search
> > paths for headers. However, SDL_config.h is designed to be included as
> >  after -I/usr/include/SDL2, not as ,
> > according to the design documented in  > parallel.html="">
> > and popularized by packages like GLib and GTK+; so moving it to
> > /usr/include//SDL2 does not make it includable. How was the
> > patch in #909740 tested?
> 
> > If sdl2-config didn't exist, then this would be easy to fix by adding
> > -I/usr/include//SDL2 to the pkg-config file (similar to what
> > happens in GLib); but doing the same thing in sdl2-config would give it
> > per-architecture variation and make it non-co-installable, so that isn't
> > an option here.
> 
> The best solution is to drop sdl2-config... but, sadly, that is in an ideal
> world.

sdl2-config is not to blame.

> Patching pkg-config is definitely the way to go.
>...

No, it is definitely not the way to go.

It is wrong that you are doing this fragile manual moving at all.

The following fixes it properly:
- revert the override_dh_install change, and
- add --includedir=\$${prefix}/include/$(DEB_HOST_MULTIARCH) to confflags

Things just work when you are using the facilities provided by the build 
system, instead of adding hack after hack when working against the build
system.

And doing it the right way automatically does the right thing for both 
pkg-config and sdl2-config.

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

Processed: found 909800 in 2.31.2+debian0-2

[Debian Bug Tracking System]

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

> found 909800 2.31.2+debian0-2
Bug #909800 [src:php-horde-core] php-horde-core: CVE-2017-16907 XSS via Color 
field
Marked as found in versions php-horde-core/2.31.2+debian0-2.
> thanks
Stopping processing here.

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

Processed: found 909800 in 2.27.6+debian1-2

[Debian Bug Tracking System]

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

> found 909800 2.27.6+debian1-2
Bug #909800 [src:php-horde-core] php-horde-core: CVE-2017-16907 XSS via Color 
field
Marked as found in versions php-horde-core/2.27.6+debian1-2.
> thanks
Stopping processing here.

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

Processed: tagging 909800

[Debian Bug Tracking System]

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

> tags 909800 + upstream
Bug #909800 [src:php-horde-core] php-horde-core: CVE-2017-16907 XSS via Color 
field
Ignoring request to alter tags of bug #909800 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#909076: ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--

[Salvatore Bonaccorso]

Hi,

Futher tests and comparisons make me confident that with
cc746214644deacd5233a1453ce660573af09443 needed the output of stretch
aligns to the one produced in unstable's ghostscript (9.25~dfsg-2).

There is still the output changes produces, which might impact
(build)-rdepends, so we might need to be extra careful here (although
ps2ascii is possibly not widely used).

I try to make my point with the following example runs, all done with
the test1.ps (sha256sum:
7377c695e4b31e18bc37f84f9f63d511f0417240728924bc08f270fcc9ab67e2) from
diffoscope. test1.txt is generated running with the appropriate
version of ps2ascii and as well recording the sa256sum of it.

jessie: ghostscript/9.06~dfsg-2+deb8u8
test1.txt: sha256sum: 
e28d37c7a2e9014c7533667d2be03df483c9e401d3b691c19e8b2fae82a72a4f
>cut-cut-cut-cut-cut-cut-
>
>
>Today's date: February 28, 2016
>
>1
>cut-cut-cut-cut-cut-cut-

stretch: ghostscript/9.20~dfsg-1
test1.txt: sha256sum: 
e28d37c7a2e9014c7533667d2be03df483c9e401d3b691c19e8b2fae82a72a4f
>cut-cut-cut-cut-cut-cut-
>
>
>Today's date: February 28, 2016
>
>1
>cut-cut-cut-cut-cut-cut-

stretch: ghostscript/9.20~dfsg-3.2+deb9u2
test1.txt: sha256sum: 
e28d37c7a2e9014c7533667d2be03df483c9e401d3b691c19e8b2fae82a72a4f
>cut-cut-cut-cut-cut-cut-
>
>
>Today's date: February 28, 2016
>
>1
>cut-cut-cut-cut-cut-cut-

stretch: ghostscript/9.20~dfsg-3.2+deb9u5
test1.txt: sha256sum: none
This one is which caused this report, as it fails

stretch: ghostscript/9.20~dfsg-3.2+deb9u6
test1.txt: sha256sum: 
d12feab3e64550bc146d180931c9310a4f95dae9809a82ccce068ed0a2e64a8f
>cut-cut-cut-cut-cut-cut-
>Today’s date: February 28, 2016
>   1
>cut-cut-cut-cut-cut-cut-

sid: ghostscript/9.25~dfsg-2
test1.txt: sha256sum: 
d12feab3e64550bc146d180931c9310a4f95dae9809a82ccce068ed0a2e64a8f
>cut-cut-cut-cut-cut-cut-
>Today’s date: February 28, 2016
>   1
>cut-cut-cut-cut-cut-cut-

So this would imply changed behaviour in a stable release, and thus
need extra care to not break more (ps2ascii might not be widely used
still).

Regards,
Salvatore

Bug#857954: libdevmapper-dev: broken symlink: /usr/lib//libdevmapper-event-lvm2.so -> /lib//libdevmapper-event-lvm2.so.2.02

[Helmut Grohne]

Control: severity -1 important

On Thu, Nov 09, 2017 at 04:11:00PM +0100, Andreas Beckmann wrote:
> The broken symlink has returned:
> 
> 0m22.2s ERROR: FAIL: Broken symlinks:
>   /usr/lib/x86_64-linux-gnu/libdevmapper-event-lvm2.so -> 
> /lib/x86_64-linux-gnu/libdevmapper-event-lvm2.so.2.02

1. Yes, this symlink is still broken in version 2:1.02.145-4.1.
2. The issue August Karlstrom was seeing, is a different one.
   libdevmapper.so.1.02.1 is a different file. That's unrelated to the
   symlink Andreas reported and if this is still a problem, it should be
   reported separately.
3. The file referenced does exist in package dmeventd. However
   libdevmapper-dev does not Depends: dmeventd.

I see two potential solutions to this problem:
A. Add dmeventd to libdevmapper-dev's Depends.
B. Remove usr/lib/*/libdevmapper-event-lvm2.so from
   debian/libdevmapper-dev.install.

It's unclear to me which solution is to be preferred here.

In any case, I don't see that this violates the Debian policy in any
way. It certainly isn't nice, but why should it be rc? Downgrading.

Helmut

Processed: Re: Bug#857954: libdevmapper-dev: broken symlink: /usr/lib//libdevmapper-event-lvm2.so -> /lib//libdevmapper-event-lvm2.so.2.02

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #857954 [libdevmapper-dev] libdevmapper-dev: broken symlink: 
/usr/lib//libdevmapper-event-lvm2.so -> 
/lib//libdevmapper-event-lvm2.so.2.02
Severity set to 'important' from 'serious'

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

Bug#876618: [Pkg-javascript-devel] Bug#876618: science.js build-depends on removed nodejs-legacy

[Bastien ROUCARIES]

Il

Le ven. 28 sept. 2018 à 07:27, Petter Reinholdtsen  a
écrit :

> Control: tags -1 + help upstream confirmed
>
> [Jérémy Lal]
> > Depending on nodejs-legacy was a serious bug in the first place.
> > Anyway (nodejs >= 6.11.2~) installs /usr/bin/node now.
>
> I had a look at this, and do not know how to fix it.  Replacing
> nodejs-legacy with nodejs in d/control is simple enough, but then the build
> fail like this:
>
> cat science.core.js science.lin.js science.stats.js >> science.v1.js
> uglifyjs < science.v1.js > science.v1.min.js
> node src/package.js > package.json
> (node:7549) [DEP0027] DeprecationWarning: util.puts is deprecated. Use
> console.log instead.
> rm science.stats.js science.lin.js science.core.js
> make[2]: Leaving directory '/home/pere/src/debian/science.js-debian'
> make[1]: Leaving directory '/home/pere/src/debian/science.js-debian'
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/home/pere/src/debian/science.js-debian'
> vows test/env-assert.js test/\*/\*-test.js
> module.js:549
> throw err;
> ^
>

Vow need to be updated or your pa ckage néed to dépend to node-glob

>
> Error: Cannot find module 'glob'
> at Function.Module._resolveFilename (module.js:547:15)
> at Function.Module._load (module.js:474:25)
> at Module.require (module.js:596:17)
> at require (internal/module.js:11:18)
> at Object. (/usr/lib/nodejs/vows/bin/vows:7:14)
> at Module._compile (module.js:652:30)
> at Object.Module._extensions..js (module.js:663:10)
> at Module.load (module.js:565:32)
> at tryModuleLoad (module.js:505:12)
> at Function.Module._load (module.js:497:3)
> make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1
> make[1]: Leaving directory '/home/pere/src/debian/science.js-debian'
> make: *** [debian/rules:8: build] Error 2
> dpkg-buildpackage: error: debian/rules build subprocess returned exit
> status 2
> debuild: fatal error at line 1152:
> dpkg-buildpackage -rfakeroot -us -uc -ui -ICVS -I.#* -I.cvsignore -I.bzr
> -I.svn -I.git failed
>
> Note, the git repo is at salsa now,
> https://salsa.debian.org/js-team/science.js.git >.
>
> --
> Happy hacking
> Petter Reinholdtsen
>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Bug#909313: marked as done ([xul-ext-sogo-connector] Not compatible with thunderbird 60 (New version exists))

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 18:05:01 +
with message-id 
and subject line Bug#909313: fixed in sogo-connector 60.0.0+gite2547a3-1
has caused the Debian Bug report #909313,
regarding [xul-ext-sogo-connector] Not compatible with thunderbird 60 (New 
version exists)
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.)


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

Package: xul-ext-sogo-connector
Version: 31.0.5-2
Severity: important

--- Please enter the report below this line. ---

The version 31.0.5-2 is not compatible with thunderbird 60.
But it seems there exists already a new sogo-connector version which is 
compatible. Please update.



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

Debian Release: 9.5
  900 stretch packagecloud.io   900 stable 
security.debian.org   900 stable  ftp.ch.debian.org   800 
stretch-backports ftp.ch.debian.org   700 testing 
ftp.ch.debian.org   600 unstableftp.ch.debian.org   500 zesty 
   ppa.launchpad.net   500 stretch-pgdgapt.postgresql.org   500 
stable-updates  ftp.ch.debian.org   500 stable  repo.skype.com 
500 stable  linux.teamviewer.com   500 stable 
download.jitsi.org   500 preview linux.teamviewer.com

--- Package information. ---
Depends  (Version) | Installed
==-+-===
lightning  | 1:52.9.1-1
thunderbird (>= 31.0)  | 1:52.9.1-1
 OR icedove  (>= 31.0) |

Package's Recommends field is empty.

Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Source: sogo-connector
Source-Version: 60.0.0+gite2547a3-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated sogo-connector 
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: Fri, 28 Sep 2018 19:12:07 +0200
Source: sogo-connector
Binary: xul-ext-sogo-connector
Architecture: source
Version: 60.0.0+gite2547a3-1
Distribution: unstable
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Description:
 xul-ext-sogo-connector - transforms Thunderbird into a full DAV client for 
groupware serve
Closes: 858734 890513 909313
Changes:
 sogo-connector (60.0.0+gite2547a3-1) unstable; urgency=medium
 .
   * [8785a7e] New upstream version 31.0.6
   * [4498ec4] add files from package thunderbird-devel
- To get the upstream source build we need some files from the now no
  longer available package thunderbird-dev. Extracting these files from
  latest available version on snapshot.d.o and place the files with the
  debian/ folder.
   * [014690f] rebuild patch queue from patch-queue branch
- modified patch:
  sogo-connector.xpt-prepare-option-for-rebuild-the-.x.patch
  By the now different source folders for the required files from the old
  package thunderbird-dev we also need to modify the Makefile within the
  folder components/ so this file is referencing the new source folder for
  to get the AddOn build.
   * [a787dfb] New upstream version 60.0.0+gite2547a3
- Closes: #909313, #890513, #858734
   * [e3da533] d/control: remove B-D on thunderbird-dev
- Removing the no longer available package from the Build-Depends.
   * [99365db] debian/control: bump Standards-Version to 4.2.1
- No further changes needed.
   * [ca0be35] d/control: adjust Vcs fields to Salsa
- Packaging tree is now moved over to Salsa.
   * [e4632ef] d/watch: use https instead of http
   * [b31b662] d/control: adjust upstream Homepage
- Change the referencing Upstream URL to the new created GitHub site on
  https://github.com/inverse-inc/sogo-connector
   * [d02948f] d/watch: use new github sub site for the watch file
- And also use this URL within the watch file.
   * [cb51d79] rebuild patch queue from patch-queue branch
   * [f380573] d/rules: 

Processed: CVE-2017-16907 is also in php-horde-core

[Debian Bug Tracking System]

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

> clone 909739 -1
Bug #909739 [php-horde] php-horde: CVE-2017-16907 XSS via Color field
Bug 909739 cloned as bug 909800
> reassign -1 src:php-horde-core
Bug #909800 [php-horde] php-horde: CVE-2017-16907 XSS via Color field
Bug reassigned from package 'php-horde' to 'src:php-horde-core'.
No longer marked as found in versions php-horde/5.2.17+debian0-3, 
php-horde/5.2.13+debian0-1, and php-horde/5.2.1+debian0-2+deb8u3.
Ignoring request to alter fixed versions of bug #909800 to the same values 
previously set
> retitle -1 php-horde-core: CVE-2017-16907 XSS via Color field
Bug #909800 [src:php-horde-core] php-horde: CVE-2017-16907 XSS via Color field
Changed Bug title to 'php-horde-core: CVE-2017-16907 XSS via Color field' from 
'php-horde: CVE-2017-16907 XSS via Color field'.
> thanks
Stopping processing here.

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

Bug#889961: marked as done (courier-authdaemon: Upgrade failures in 0.68.0-4 package)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 19:16:35 +0200
with message-id <9c148518-144a-11f2-8303-e413c72d6...@rocketjump.eu>
and subject line courier-authdaemon: Upgrade failures in 0.68.0-4 package
has caused the Debian Bug report #889961,
regarding courier-authdaemon: Upgrade failures in 0.68.0-4 package
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.)


-- 
889961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-authdaemon
Version: 0.68.0-4+b1
Severity: critical
stop

The Courier authdaemon package is failing to configure during install.
Similar issue happened on the -3 package but I managed to get that to
install with manually stopping all courier processes before upgrading.
That workaround no longer has any effect.


aptitude upgrade
The following partially installed packages will be configured:
  courier-authdaemon courier-imap courier-pop
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up courier-pop (0.78.0-2+b1) ...
A dependency job for courier-pop.service failed. See 'journalctl -xe'
for details.
...


Setting up courier-imap (4.18.1+0.78.0-2+b1) ...
A dependency job for courier-imap.service failed. See 'journalctl -xe'
for details.
invoke-rc.d: initscript courier-imap, action "start" failed.
* courier-imap.service - Courier IMAP Daemon
   Loaded: loaded (/lib/systemd/system/courier-imap.service; enabled;
vendor preset: enabled)
   Active: inactive (dead) since Fri 2018-02-02 20:12:20 NZDT; 1 weeks 0
days ago
 Main PID: 705 (code=exited, status=0/SUCCESS)

Feb 09 21:44:44 rio systemd[1]: Dependency failed for Courier IMAP Daemon.
Feb 09 21:44:44 rio systemd[1]: courier-imap.service: Job
courier-imap.service/start failed with result 'dependency'.
Feb 09 21:45:03 rio systemd[1]: Dependency failed for Courier IMAP Daemon.
Feb 09 21:45:03 rio systemd[1]: courier-imap.service: Job
courier-imap.service/start failed with result 'dependency'.
Feb 09 21:45:09 rio systemd[1]: Dependency failed for Courier IMAP Daemon.
Feb 09 21:45:09 rio systemd[1]: courier-imap.service: Job
courier-imap.service/start failed with result 'dependency'.
Feb 09 21:45:39 rio systemd[1]: Dependency failed for Courier IMAP Daemon.
Feb 09 21:45:39 rio systemd[1]: courier-imap.service: Job
courier-imap.service/start failed with result 'dependency'.
Warning: Journal has been rotated since unit was started. Log output is
incomplete or unavailable.
dpkg: error processing package courier-imap (--configure):
 installed courier-imap package post-installation script subprocess
returned error exit status 1
Setting up courier-authdaemon (0.68.0-4+b1) ...
Job for courier-authdaemon.service failed because the service did not
take the steps required by its unit configuration.
See "systemctl status courier-authdaemon.service" and "journalctl -xe"
for details.
invoke-rc.d: initscript courier-authdaemon, action "start" failed.
* courier-authdaemon.service - Courier Authentification Daemon
   Loaded: loaded (/lib/systemd/system/courier-authdaemon.service;
disabled; vendor preset: enabled)
   Active: failed (Result: protocol) since Fri 2018-02-09 21:45:39 NZDT;
8ms ago
  Process: 4623 ExecStart=/usr/sbin/authdaemond start (code=exited,
status=0/SUCCESS)
 Main PID: 667 (code=exited, status=0/SUCCESS)

Feb 09 21:45:39 rio systemd[1]: Starting Courier Authentification Daemon...
Feb 09 21:45:39 rio systemd[1]: courier-authdaemon.service: Can't open
PID file /run/courier/authdaemon/pid (yet?) after start: No such file or
directory
Feb 09 21:45:39 rio systemd[1]: courier-authdaemon.service: Failed with
result 'protocol'.
Feb 09 21:45:39 rio systemd[1]: Failed to start Courier Authentification
Daemon.
dpkg: error processing package courier-authdaemon (--configure):
 installed courier-authdaemon package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
 courier-pop
 courier-imap
 courier-authdaemon
E: Sub-process /usr/bin/dpkg returned an error code (1)

Setting up courier-pop (0.78.0-2+b1) ...
A dependency job for courier-pop.service failed. See 'journalctl -xe'
for details.
...

Setting up courier-authdaemon (0.68.0-4+b1) ...
Job for courier-authdaemon.service failed because the service did not
take the steps required by its unit configuration.
See "systemctl status courier-authdaemon.service" and "journalctl -xe"
for details.
invoke-rc.d: initscript courier-authdaemon, 

Bug#909470: marked as done (r-cran-shinythemes: needs to be rebuilt for r-api-3.5)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 17:19:47 +
with message-id 
and subject line Bug#909470: fixed in r-cran-shinythemes 1.1.1+dfsg-2
has caused the Debian Bug report #909470,
regarding r-cran-shinythemes: needs to be rebuilt for r-api-3.5
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.)


-- 
909470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-shinythemes
Version: 1.1.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

r-cran-shinythemes/amd64 unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/i386 unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/arm64 unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/armel unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/armhf unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/mips unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/mips64el unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/mipsel unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/ppc64el unsatisfiable Depends: r-api-3.4
r-cran-shinythemes/s390x unsatisfiable Depends: r-api-3.4


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: r-cran-shinythemes
Source-Version: 1.1.1+dfsg-2

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated r-cran-shinythemes 
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: Fri, 28 Sep 2018 18:52:56 +0200
Source: r-cran-shinythemes
Binary: r-cran-shinythemes
Architecture: source
Version: 1.1.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Dylan Aïssi 
Description:
 r-cran-shinythemes - Themes for Shiny
Closes: 909470
Changes:
 r-cran-shinythemes (1.1.1+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Rebuilt for r-api-3.5 (Closes: #909470).
   * Bump Standards-Version: 4.2.1 (no changes needed).
Checksums-Sha1:
 d84413d796252dda43c16fdd14fb327df34a86db 2149 
r-cran-shinythemes_1.1.1+dfsg-2.dsc
 b141d6f8c7dec633579d4728ecec97e8efbc4351 4320 
r-cran-shinythemes_1.1.1+dfsg-2.debian.tar.xz
 d17d8e888225a6113577ff9bbc646d15c35894b0 10322 
r-cran-shinythemes_1.1.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 55c2cb8702da9b02e7fa618ed4e5afe53642a2f687820a28d771b2af2c8e91b6 2149 
r-cran-shinythemes_1.1.1+dfsg-2.dsc
 b10d18b19113d745484fd4a4af7bd8492d9ac45521fa25d3f79b20333f31cb66 4320 
r-cran-shinythemes_1.1.1+dfsg-2.debian.tar.xz
 6f6da6e9eaf92e352c54ae424b3f5183b261a53326fe3b1e665a0440659b5f75 10322 
r-cran-shinythemes_1.1.1+dfsg-2_amd64.buildinfo
Files:
 868c515bab02763e2873f3ec6ed90dd6 2149 gnu-r optional 
r-cran-shinythemes_1.1.1+dfsg-2.dsc
 5aa340077a430ed321e4658585f5f91f 4320 gnu-r optional 
r-cran-shinythemes_1.1.1+dfsg-2.debian.tar.xz
 baad02654a9636a090993e8a59aad281 10322 gnu-r optional 
r-cran-shinythemes_1.1.1+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAluuXcoVHGJvYi5keWJp
YW5AZ21haWwuY29tAAoJEGEu8WE+BQ9UJ7YP/iElqlQxhG3FjU5+ozUxs6C+4ta5
Uqi/GR2KcFEi0eWB14NpQlGH4xDWAmyB8Yo2CtseEcYqisq4klm0L/a5BkpQ5E3u
AG1ay0ZS1tGfu3V88e9HQ5wRo72Qljl7JXZAdqk8KOOY7WPqqRUXlGH4AkyuidWS
Y8ZsJZ1XrVib/ATVMm1T81mquDmxBO4gUproWiHsibCNzvtmIJzA/ZBFmlztH/6N
2jn2RoyUFQAWm3RFyS9VXWVJFHVVyX8rTczap+HCyf7jO0tc11x8ShrKmpElZlWf
oRxsaQDqBE4NJeJNzafHCfNcLRtTNPZ2HoLYvaal1vNbH0BMD8prJLty1z7iChbr
KiPxcltCtiatlPL2jkf0aCB5gbq+UadlehIs2N9NcoeH/955tIDq0egS7kx/Jbc0
qhO0qbJOdqGO2kn7n6W31oicCC5e1Dhoo5cLGbVXj/9IRlNnUZfZGkDI85xzMmk+
Qdm/pqvYZb8AjZP8UWBsvKcRuLPbMprgxwwHHbzFUsuIvKoKdpYb8gZtlIU7TBPh
y5FojDaDGo7zGrSccNWOTPizf3XSorBIW1Ix/wVIreQmRF0oOposHeSESTX9otg1
Yary4HKbGN/eYMT8dTtBvpSRKlQlOfS3bZRozVKOzPW7rUc0ZRUeQX3jL+ULm/G5
ncwoDQxEMPqIPZFE
=+61P
-END PGP SIGNATURE End Message ---

Bug#864800: marked as done (Mail::DeliveryStatus::BounceParser contains a live virus and some real spam/phishing mails)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 17:05:22 +
with message-id 
and subject line Bug#864800: fixed in libmail-deliverystatus-bounceparser-perl 
1.542+repacked-1
has caused the Debian Bug report #864800,
regarding Mail::DeliveryStatus::BounceParser contains a live virus and some 
real spam/phishing mails
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.)


-- 
864800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmail-deliverystatus-bounceparser-perl
Version: 1.531-1
Severity: serious
X-Debbugs-CC: Ricardo Signes 
Control: forwarded -1 Ricardo Signes 
Control: found -1 1.536-1
Control: found -1 1.542-1
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team

The Mail::DeliveryStatus::BounceParser source contains a live virus and
some real spam/phishing mails. This is leading to Netcraft and other
virus detection systems on the Internet reporting Debian mirrors as
malicious, which potentially reduces the reputation of debian.org on
various anti-spam and anti-malware services. Please fix this in
upstream git, with a new release on CPAN and in all Debian suites.

https://incident.netcraft.com/w/b0d11ab53944/
https://incident.netcraft.com/w/ffb6f95e5301/

To fix this you will need to strip the account-password.zip attachment
from t/corpus/virus-caused-multiple-weird-reports.msg and if possible
strip the phishing/spam content from the other files, while ensuring
that the tests still pass despite changes to the corpus but that the
new files in the corpus do not trip any anti-virus checkers:

https://www.virustotal.com/

$ clamdscan --fdpass --infected | sed "s|`pwd`/||"
t/corpus/virus-caused-multiple-weird-reports.msg: Win.Worm.Mytob-331 FOUND
t/corpus/spam-with-badly-parsed-email.msg: 
Sanesecurity.Phishing.Ivt.6456.UNOFFICIAL FOUND
t/corpus/spam-lots-of-bogus-addresses.msg: Sanesecurity.Spam.8684.UNOFFICIAL 
FOUND

--- SCAN SUMMARY ---
Infected files: 3
Time: 0.087 sec (0 m 0 s)

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: libmail-deliverystatus-bounceparser-perl
Source-Version: 1.542+repacked-1

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated 
libmail-deliverystatus-bounceparser-perl 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: Fri, 28 Sep 2018 13:48:12 +0200
Source: libmail-deliverystatus-bounceparser-perl
Binary: libmail-deliverystatus-bounceparser-perl
Architecture: source
Version: 1.542+repacked-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Xavier Guimard 
Closes: 864800
Description: 
 libmail-deliverystatus-bounceparser-perl - module for analyzing bounce messages
Changes:
 libmail-deliverystatus-bounceparser-perl (1.542+repacked-1) unstable; 
urgency=medium
 .
   * Team upload
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Nathan Handler from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ Xavier Guimard ]
   * Repack excluding viruses found by uscan (Closes: #864800)
   * Declare compliance with policy 4.2.1
   * Remove dependency to libtest-simple-perl (>= 0.94)
   * Bump debhelper compatibility to 10
Checksums-Sha1: 
 f81396c650f0f8a3dcb9a81c1b3b1c96df652880 2497 
libmail-deliverystatus-bounceparser-perl_1.542+repacked-1.dsc
 51a846124bd138510f11c05b493625c100db7f57 134689 
libmail-deliverystatus-bounceparser-perl_1.542+repacked.orig.tar.gz
 e8a6bc7ceb6fb3c30854d5e9ae25b072b55060c0 2996 
libmail-deliverystatus-bounceparser-perl_1.542+repacked-1.debian.tar.xz
Checksums-Sha256: 
 ac14d1ca76264543bbd06bc6660e7782042e15aff3470693314d396169d5ea88 2497 

Bug#909799: adios: Incomplete debian/copyright?

[Chris Lamb]

Source: adios
Version: 1.13.1-7
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Alastair McKinstry , 
ftpmas...@debian.org

Hi,

I just ACCEPTed adios from NEW but noticed it was missing attribution 
in debian/copyright for at least Michael Sweet, Seungyoung Kim, Jong
Choi, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.

(It would also be great if you used the "real" DEP-5 style? You are so
close as it is, after all.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#909785: python-pcl: Incomplete debian/copyright and/or "freeware" source code?

[Chris Lamb]

Jochen,

> Do you have a proposal how to better document this?

Not entirely sure what you mean by "better" as you currently do not
document this at all (unless I am missing something).

However, as a concrete suggestion I would add "Comment" section to your
debian/copyright and almost-literally copy your (own) words, ie.:

  > This is only a comment, copied from the PCL sources (and I believe not 
  > even true over there).

  
Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#909770: gdm3: Does not show the list of users and fails to start any session

[Sergio Villar Senin]

> I basically started without plyumouth enabled and the screen becomes
black with the cursor in the top left corner of the screen.

I obviously meant _disabled_

BR

Bug#909785: python-pcl: Incomplete debian/copyright and/or "freeware" source code?

[Jochen Sprickerhof]

Hi Chris,

* Chris Lamb  [2018-09-28 10:07]:

I just ACCEPTed python-pcl from NEW but noticed it was missing
attribution or similar in debian/copyright for at least some files
listed as "freeware" (!= is this even DFSG-free software?).


I guess you are talking about this line:

https://salsa.debian.org/python-team/modules/python-pcl/blob/master/pcl/pcl_segmentation.pxd#L760

This is only a comment, copied from the PCL sources (and I believe not 
even true over there). The actual license of python-pcl is stated over 
here:


https://salsa.debian.org/python-team/modules/python-pcl/blob/master/docs/source/license.rst

Do you have a proposal how to better document this?

Cheers Jochen


signature.asc
Description: PGP signature

Processed: Still usable after all...

[Debian Bug Tracking System]

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

> severity 909381 normal
Bug #909381 [xemacs21] xemacs21: Error while loading 00debian: Variable binding 
depth exceeds max-specpdl-size
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#909770: gdm3: Does not show the list of users and fails to start any session

[Sergio Villar Senin]

O Ven, 28-09-2018 ás 12:47 +0100, Simon McVittie escribiu:
> On Fri, 28 Sep 2018 at 11:01:09 +0200, Sergio Villar Senin wrote:
> > O Xov, 27-09-2018 ás 22:39 +0100, Simon McVittie escribiu:
> > > On Thu, 27 Sep 2018 at 23:16:05 +0200, Sergio Villar Senin wrote:
> > > >The background of the plyumouth theme is shown but the list
> > > > of
> > > >users is not there as expected.
> 
> How many screens are you using, and how are they connected?  From
> your
> log it looks as though the answer might be one laptop internal panel,
> connected via eDP, and no external screens. Is that correct?

That's correct

> If you are using a plymouth theme that resembles the background you
> would
> expect for the gdm greeter (user list), please retry with a different
> plymouth theme such as softwave or lines and tell me what you see?
> (What
> I'm trying to determine here is whether the most recent pixels on
> your
> screen came from plymouth or gdm.)

I basically started without plyumouth enabled and the screen becomes
black with the cursor in the top left corner of the screen. At that
point I tried to attach an external screen, and guess what? then I
could see the VTs in F2,F3... and in F1 there was the gray background
(nothing else just that) from gdm.

> > I don't see anything specially wrong there except these lines:
> > 
> > laptop kernel: [drm:intel_dp_start_link_train [i915]] *ERROR*
> > [CONNECTOR:71:eDP-1] Link Training failed at link rate = 27,
> > lane
> > count = 2
> 
> I agree. This looks more like a kernel bug than anything else - I'm
> not
> sure that this is anything that gdm3 can fix - but I'll try to get a
> bit more information about what does and doesn't work before
> reassigning.
> 
> If you follow the workaround that you described (involving
> suspend/resume),
> do you get a similar warning about link training after resuming?

After resuming everything seems to work fine and I haven't seen any
error in the journal.

> You said that lightdm works OK. Do you get similar warnings about
> link
> training when using lightdm?

Not a single one. The last warning appears just after the
"/usr/lib/gdm3/gdm-x-session[3172]: (II) modeset(0)" lines.

> If you edit /etc/gdm3/daemon.conf and edit it to have
> 
> [daemon]
> WaylandEnable=false
> 
> then go back to gdm, does that make it work?

No luck, same result.

BR

Bug#876618: marked as done (science.js build-depends on removed nodejs-legacy)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 13:35:21 +
with message-id 
and subject line Bug#876618: fixed in science.js 1.9.3-2
has caused the Debian Bug report #876618,
regarding science.js build-depends on removed nodejs-legacy
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.)


-- 
876618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: science.js
Version: 1.9.3-1
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:science.js : Depends: nodejs-legacy but it is not installable
--- End Message ---
--- Begin Message ---
Source: science.js
Source-Version: 1.9.3-2

We believe that the bug you reported is fixed in the latest version of
science.js, 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.
Petter Reinholdtsen  (supplier of updated science.js 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: Fri, 28 Sep 2018 13:16:36 +
Source: science.js
Binary: libjs-sciencejs
Architecture: source
Version: 1.9.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Petter Reinholdtsen 
Description:
 libjs-sciencejs - JavaScript library for scientific and statistical computing
Closes: 876618
Changes:
 science.js (1.9.3-2) unstable; urgency=medium
 .
   * Moved code to salsa.debian.org.
   * Updated Standards-Version from 3.9.8 to 4.2.1.
   * Started using pristine-tar and enforce its use in d/gbp.conf.
   * Disabled self testing during build until bug #909779 in vows is fixed.
   * Replaced nodejs-legacy build dependency with nodejs. (Closes: #876618)
Checksums-Sha1:
 8175a8d237542f862693ed4614513a1fc8394a9c 2086 science.js_1.9.3-2.dsc
 4509c3ad62f236bcb29aeee44270bf948bcd2fdd 2572 science.js_1.9.3-2.debian.tar.xz
 d6aa414a6efe7afcbebf7b67db5baab666f8468b 7684 
science.js_1.9.3-2_source.buildinfo
Checksums-Sha256:
 3370497ec7f0d84322b2d916b356281699cd3b668e78168afc3c9be6ae378183 2086 
science.js_1.9.3-2.dsc
 ed6b68e314c42888e3551aa887e42975abd0cba23d0152b7c31c267a58be502d 2572 
science.js_1.9.3-2.debian.tar.xz
 836fbac69056a4fc92e860a60cc7b1e68789d4f99fd3794a1831898f2a37719a 7684 
science.js_1.9.3-2_source.buildinfo
Files:
 810b703a4e599a5c121814c7fa6f78f2 2086 web optional science.js_1.9.3-2.dsc
 b4b7f6a5c5bce1acad90b956d9e9e055 2572 web optional 
science.js_1.9.3-2.debian.tar.xz
 bda8cdc72bf3b73c801acc49130c8b8b 7684 web optional 
science.js_1.9.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAluuKjEACgkQgSgKoIe6
+w5boA//VxQUDIZucvg5fgob5sQ8hicNLkcAXiIfHD1XTptFugqDX0gHhtTtzr02
nuq4bnQuxV9fVuGfKNWPhTsRYpvLWG9g413paP+MK1mDJnXaSjPFmnVWusJl0TUT
E5gE7iPJyBhVZVGtaxTLlXseuKw4NywK/BRDizbbUKlUWRvL7r128bBGlI2HZU7Y
1b1j6zPqRRNxZZpFXbJ+7HOl59O1jjEMG8EF50UArMX3+HXHUQrk3VgLDLCPhfW7
fjb6Te4F9BSc54aL+5JYKxc5DmDW2IRqS5rmYCxe0NHCQZVFO5n4Ht0jLQ9Mt146
KZYtGAzdpkxRbzB6oOlzxncvOlJGb2JgeJ/wXNBDjARgaKptBkCskWqbvIaEm0k0
cEttltDyLYxyW3Sh1eCWl9lu9CWSJiOFKBmejdcdbljConhTvVokEqR6AtRTxRx8
n9ZSXTWIOimRcCaY8l8Oc5TEm+jg3IQvRutdeh3EkBu8DWa8BBxf9/K0aXJjl8aT
vAy4MhKUSh0lWmeVnuotA94NQAW2A0niibX+FUj9XWD8oiNXQtSXjzr+q4shnhXm
sA3QebizGJXyZsB0JdLy9lOTunRXuuvrhtQz1M8fkSH4hc4IX/AymOkx4BMa2+Dg
fbK7+y5K7tF8mOlqaMr/CfIcNpL/XMaiSW9hbMrGBQ+hfYAOnuk=
=KtPD
-END PGP SIGNATURE End Message ---

Bug#899197: marked as done (bolt FTBFS: bolt-enum-types.c:5:10: fatal error: bolt-enums.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 08:04:31 -0400
with message-id 

and subject line Re: bolt FTBFS: bolt-enum-types.c:5:10: fatal error: 
bolt-enums.h: No such file or directory
has caused the Debian Bug report #899197,
regarding bolt FTBFS: bolt-enum-types.c:5:10: fatal error: bolt-enums.h: 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.)


-- 
899197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bolt
Version: 0.3-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

bolt fails to build from source on unstable:

| dpkg-buildpackage: info: source package bolt
| dpkg-buildpackage: info: source version 0.3-3
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Jeremy Bicha 
|  dpkg-source --before-build bolt-0.3
| dpkg-buildpackage: info: host architecture amd64
|  fakeroot debian/rules clean
| dh clean
|dh_clean
|  debian/rules build
| dh build
|dh_update_autotools_config
|dh_autoreconf
|debian/rules override_dh_auto_configure
| make[1]: Entering directory '/<>'
| dh_auto_configure -- \
|   --libexecdir=/usr/lib/bolt \
|   -Dprivileged-group=sudo
|   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu 
--libexecdir=lib/x86_64-linux-gnu --libexecdir=/usr/lib/bolt 
-Dprivileged-group=sudo
| The Meson build system
| Version: 0.46.1
| Source dir: /<>
| Build dir: /<>/obj-x86_64-linux-gnu
| Build type: native build
| Project name: bolt
| Native C compiler: cc (gcc 7.3.0 "cc (Debian 7.3.0-19) 7.3.0")
| Appending CFLAGS from environment: '-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security'
| Appending LDFLAGS from environment: '-Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
-Wl,--as-needed'
| Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
| Build machine cpu family: x86_64
| Build machine cpu: x86_64
| Compiler for C supports arguments -fstack-protector-strong: YES
| Compiler for C supports arguments -Waggregate-return: YES
| Compiler for C supports arguments -Wunused: YES
| Compiler for C supports arguments -Warray-bounds: YES
| Compiler for C supports arguments -Wcast-align: YES
| Compiler for C supports arguments -Wclobbered: YES
| Compiler for C supports arguments -Wdeclaration-after-statement: YES
| Compiler for C supports arguments -Wempty-body: YES
| Compiler for C supports arguments -Wformat=2: YES
| Compiler for C supports arguments -Wformat-nonliteral: YES
| Compiler for C supports arguments -Wformat-security: YES
| Compiler for C supports arguments -Wformat-signedness: YES
| Compiler for C supports arguments -Wignored-qualifiers: YES
| Compiler for C supports arguments -Wimplicit-function-declaration: YES
| Compiler for C supports arguments -Winit-self: YES
| Compiler for C supports arguments -Wmissing-declarations: YES
| Compiler for C supports arguments -Wmissing-format-attribute: YES
| Compiler for C supports arguments -Wmissing-include-dirs: YES
| Compiler for C supports arguments -Wmissing-noreturn: YES
| Compiler for C supports arguments -Wmissing-parameter-type: YES
| Compiler for C supports arguments -Wmissing-prototypes: YES
| Compiler for C supports arguments -Wnested-externs: YES
| Compiler for C supports arguments -Wno-discarded-qualifiers 
-Wdiscarded-qualifiers: YES
| Compiler for C supports arguments -Wno-missing-field-initializers 
-Wmissing-field-initializers: YES
| Compiler for C supports arguments -Wno-strict-aliasing -Wstrict-aliasing: YES
| Compiler for C supports arguments -Wno-suggest-attribute=format 
-Wsuggest-attribute=format: YES
| Compiler for C supports arguments -Wno-unused-parameter -Wunused-parameter: 
YES
| Compiler for C supports arguments -Wold-style-definition: YES
| Compiler for C supports arguments -Woverride-init: YES
| Compiler for C supports arguments -Wpointer-arith: YES
| Compiler for C supports arguments -Wredundant-decls: YES
| Compiler for C supports arguments -Wreturn-type: YES
| Compiler for C supports arguments -Wshadow: YES
| Compiler for C supports arguments -Wsign-compare: YES
| Compiler for C supports arguments -Wstrict-aliasing: YES
| Compiler for C supports arguments -Wstrict-prototypes: YES
| Compiler for C supports arguments -Wtype-limits: YES
| Compiler for C supports arguments -Wundef: YES
| Compiler for C supports arguments -Wuninitialized: YES
| Compiler 

Bug#909770: gdm3: Does not show the list of users and fails to start any session

[Simon McVittie]

On Fri, 28 Sep 2018 at 11:01:09 +0200, Sergio Villar Senin wrote:
> O Xov, 27-09-2018 ás 22:39 +0100, Simon McVittie escribiu:
> > On Thu, 27 Sep 2018 at 23:16:05 +0200, Sergio Villar Senin wrote:
> > >The background of the plyumouth theme is shown but the list of
> > >users is not there as expected.

How many screens are you using, and how are they connected?  From your
log it looks as though the answer might be one laptop internal panel,
connected via eDP, and no external screens. Is that correct?

If you are using a plymouth theme that resembles the background you would
expect for the gdm greeter (user list), please retry with a different
plymouth theme such as softwave or lines and tell me what you see? (What
I'm trying to determine here is whether the most recent pixels on your
screen came from plymouth or gdm.)

> I don't see anything specially wrong there except these lines:
> 
> laptop kernel: [drm:intel_dp_start_link_train [i915]] *ERROR*
> [CONNECTOR:71:eDP-1] Link Training failed at link rate = 27, lane
> count = 2

I agree. This looks more like a kernel bug than anything else - I'm not
sure that this is anything that gdm3 can fix - but I'll try to get a
bit more information about what does and doesn't work before reassigning.

If you follow the workaround that you described (involving suspend/resume),
do you get a similar warning about link training after resuming?

You said that lightdm works OK. Do you get similar warnings about link
training when using lightdm?

If you edit /etc/gdm3/daemon.conf and edit it to have

[daemon]
WaylandEnable=false

then go back to gdm, does that make it work?

smcv

Bug#909284: minidlna: Minidlna needs libavcodec.so.57 which is not a dependancy

[Alexander Gerasiov]

Hello Alexander,

On Fri, 28 Sep 2018 13:48:21 +0300
Alexander Gerasiov  wrote:

> Hello Dean,
> 
> What distribution do you use?
> 
> I'm afraid it's not Debian, but Raspbian derivative.
> 
> I cant reproduce it with current debian archive. May be you should
> report to raspbian and ask binNMU for minidlna (or libavformat58, as
> minidlna do not links libavcodec itself).

Oh, it's not libavformat58, which should be rebuilt, but libchromaprint:

> /usr/sbin/minidlnad: /usr/lib/arm-linux-gnueabihf/libavcodec.so.58:
> version `LIBAVCODEC_57' not found (required by
> /usr/lib/arm-linux-gnueabihf/libchromaprint.so.1)

> 
> On Fri, 21 Sep 2018 10:26:25 +1000
> Dean  wrote:
> 
> > Package: minidlna
> > Version: 1.2.1+dfsg-1+b1
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > * What led up to the situation?
> > I think i may have removed libavcodec57 at some point.
> > Now when i start the service It starts with the following in the
> > journal: /usr/sbin/minidlnad: error while loading shared libraries:
> > libavcodec.so.57: cannot open shared object file: No such file or
> > directory raspberrypi systemd[1]: minidlna.service: About to
> > execute: /etc/init.d/minidlna start
> > raspberrypi systemd[1]: minidlna.service:
> > Forked /etc/init.d/minidlna as 5123
> > raspberrypi systemd[1]: minidlna.service: Changed dead -> start
> > raspberrypi systemd[1]: Starting LSB: minidlna server...
> > raspberrypi systemd[5123]: minidlna.service: Executing:
> > /etc/init.d/minidlna start
> > raspberrypi systemd[1]: minidlna.service: Child 5123 belongs to
> > minidlna.service.
> > raspberrypi systemd[1]: minidlna.service: Control process exited,
> > code=exited status=0
> > raspberrypi systemd[1]: minidlna.service: Got final SIGCHLD for
> > state start. raspberrypi systemd[1]: minidlna.service: Changed
> > start -> exited raspberrypi systemd[1]: minidlna.service: Job
> > minidlna.service/start finished, result=done
> > raspberrypi systemd[1]: Started LSB: minidlna server.
> > raspberrypi systemd[1]: minidlna.service: Failed to send unit change
> > signal for minidlna.service: Connection reset by peer
> > * What exactly did you do (or not do) that was effective (or
> > ineffective)? I first tried linking libavcodec58 to 57 but then it
> > looks for version 57 of the rest of its libraries
> > I then tried to link each of the successive so's it complained about
> > (libavformat, libavutils, ...) with no avail
> > I then tried to install libavcodec57 but it is no longer in the repo
> > * What was the outcome of this action?
> > ln -s /usr/lib/arm-linux-gnueabihf/libavcodec.so.58.18.100
> > /usr/lib/arm-linux-gnueabihf/libavcodec.so.57
> > systemctl start minidlna:
> > /usr/sbin/minidlnad: /usr/lib/arm-linux-gnueabihf/libavcodec.so.58:
> > version `LIBAVCODEC_57' not found (required by
> > /usr/lib/arm-linux-gnueabihf/libchromaprint.so.1)
> > * What outcome did you expect instead?
> > I was hoping minidlna would work with libav* version 58
> > 
> > -- System Information:
> > Distributor ID: Raspbian
> > Description: Raspbian GNU/Linux testing (buster)
> > Release: testing
> > Codename: buster
> > Architecture: armv7l
> > 
> > Kernel: Linux 4.14.70-v7+ (SMP w/4 CPU cores)
> > Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
> > LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > 
> > Versions of packages minidlna depends on:
> > ii adduser 3.117
> > ii libavformat58 7:4.0.2-1+b2
> > ii libavutil56 7:4.0.2-1+b2
> > ii libc6 2.27-6+rpi1
> > ii libexif12 0.6.21-5
> > ii libflac8 1.3.2-3
> > ii libid3tag0 0.15.1b-13
> > ii libjpeg62-turbo 1:1.5.2-2+b1
> > ii libogg0 1.3.2-1
> > ii libsqlite3-0 3.24.0-1
> > ii libvorbis0a 1.3.6-1
> > ii lsb-base 9.20170808+rpi1
> > 
> > minidlna recommends no packages.
> > 
> > minidlna suggests no packages.
> > 
> > -- Configuration Files:
> > /etc/minidlna.conf changed:
> > media_dir=V,/mnt/media/Movies
> > media_dir=V,/mnt/media/Kids
> > merge_media_dirs=no
> > db_dir=/var/cache/minidlna
> > log_dir=/var/log
> > root_container=V
> > network_interface=eth0
> > port=8200
> > friendly_name="redacted"
> > inotify=yes
> > album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg
> > album_art_names=AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg
> > album_art_names=Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
> > 
> > 
> > -- no debconf information  
> 
> 
> 



-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: g...@cs.msu.su  WWW: http://gerasiov.net  TG/Skype: gerasiov
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1

Bug#909284: marked as done (minidlna: Minidlna needs libavcodec.so.57 which is not a dependancy)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 13:48:21 +0300
with message-id <20180928134821.49731...@dwarf.gerasiov.net>
and subject line Re: Bug#909284: minidlna: Minidlna needs libavcodec.so.57 
which is not a dependancy
has caused the Debian Bug report #909284,
regarding minidlna: Minidlna needs libavcodec.so.57 which is not a dependancy
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.)


-- 
909284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: minidlna
Version: 1.2.1+dfsg-1+b1
Severity: important

Dear Maintainer,

* What led up to the situation?
I think i may have removed libavcodec57 at some point.
Now when i start the service It starts with the following in the journal:
/usr/sbin/minidlnad: error while loading shared libraries:
libavcodec.so.57: cannot open shared object file: No such file or directory
raspberrypi systemd[1]: minidlna.service: About to execute:
/etc/init.d/minidlna start
raspberrypi systemd[1]: minidlna.service: Forked /etc/init.d/minidlna as
5123
raspberrypi systemd[1]: minidlna.service: Changed dead -> start
raspberrypi systemd[1]: Starting LSB: minidlna server...
raspberrypi systemd[5123]: minidlna.service: Executing:
/etc/init.d/minidlna start
raspberrypi systemd[1]: minidlna.service: Child 5123 belongs to
minidlna.service.
raspberrypi systemd[1]: minidlna.service: Control process exited,
code=exited status=0
raspberrypi systemd[1]: minidlna.service: Got final SIGCHLD for state start.
raspberrypi systemd[1]: minidlna.service: Changed start -> exited
raspberrypi systemd[1]: minidlna.service: Job minidlna.service/start
finished, result=done
raspberrypi systemd[1]: Started LSB: minidlna server.
raspberrypi systemd[1]: minidlna.service: Failed to send unit change
signal for minidlna.service: Connection reset by peer
* What exactly did you do (or not do) that was effective (or ineffective)?
I first tried linking libavcodec58 to 57 but then it looks for version
57 of the rest of its libraries
I then tried to link each of the successive so's it complained about
(libavformat, libavutils, ...) with no avail
I then tried to install libavcodec57 but it is no longer in the repo
* What was the outcome of this action?
ln -s /usr/lib/arm-linux-gnueabihf/libavcodec.so.58.18.100
/usr/lib/arm-linux-gnueabihf/libavcodec.so.57
systemctl start minidlna:
/usr/sbin/minidlnad: /usr/lib/arm-linux-gnueabihf/libavcodec.so.58: version
`LIBAVCODEC_57' not found (required by
/usr/lib/arm-linux-gnueabihf/libchromaprint.so.1)
* What outcome did you expect instead?
I was hoping minidlna would work with libav* version 58

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

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

Versions of packages minidlna depends on:
ii adduser 3.117
ii libavformat58 7:4.0.2-1+b2
ii libavutil56 7:4.0.2-1+b2
ii libc6 2.27-6+rpi1
ii libexif12 0.6.21-5
ii libflac8 1.3.2-3
ii libid3tag0 0.15.1b-13
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libogg0 1.3.2-1
ii libsqlite3-0 3.24.0-1
ii libvorbis0a 1.3.6-1
ii lsb-base 9.20170808+rpi1

minidlna recommends no packages.

minidlna suggests no packages.

-- Configuration Files:
/etc/minidlna.conf changed:
media_dir=V,/mnt/media/Movies
media_dir=V,/mnt/media/Kids
merge_media_dirs=no
db_dir=/var/cache/minidlna
log_dir=/var/log
root_container=V
network_interface=eth0
port=8200
friendly_name="redacted"
inotify=yes
album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg
album_art_names=AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg
album_art_names=Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg


-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Dean,

What distribution do you use?

I'm afraid it's not Debian, but Raspbian derivative.

I cant reproduce it with current debian archive. May be you should
report to raspbian and ask binNMU for minidlna (or libavformat58, as
minidlna do not links libavcodec itself).

On Fri, 21 Sep 2018 10:26:25 +1000
Dean  wrote:

> Package: minidlna
> Version: 1.2.1+dfsg-1+b1
> Severity: important
> 
> Dear Maintainer,
> 
> * What led up to the situation?
> I think i may have removed libavcodec57 at some point.
> Now when i start the service It starts with the following in the
> journal: /usr/sbin/minidlnad: error while loading shared libraries:
> 

Bug#909076: ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--

[Markus Koschany]

Hi,

Am 28.09.18 um 00:16 schrieb Salvatore Bonaccorso:
> Hi Markus,
> 
> On Thu, Sep 27, 2018 at 10:33:06PM +0200, Markus Koschany wrote:
[...]
>> The text is correctly displayed now in Jessie but the Stretch version
>> shows Chinese characters instead. Hence I would appreciate it if you
>> could double-check and verify the output on your terminals.
> 
> The commit might be part indeed of the solution, that is to switch to
> the txtwrite device. In the bisect I did, I already used as well a
> variant with using the txtwrite device. This is what lead to
> previously posted git bisect log (with commits between a broken one in
> the 9.20 series, up to the a less broken one[*], and in each iteration
> always applying as strategy the mentioned commit for fixing the CVE
> and which caused the regression, and calling gs directly with the
> needed parameter using the txtwrite device).
> 
> I know already that e.g. using the commit
> http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=cc746214644deacd5233a1453ce660573af09443
> (*and* using the txtwrite device) seems to improve the situation. But
> there are still dispalying discrepancies and regressions with test
> files. So this is not enough for the stretch built at least :-/.
> In the jessie patched version, you did exact the same documents with
> old version and with patched one for e.g. alpahet.ps and waterfall.ps?

Could you post your test files somewhere and describe what you expect to
see? I would like to test them too. In Jessie it is sufficient to just
switch to the txtwrite device. If I apply the other Git commit
cc746214644deacd5233a1453ce660573af09443 then I even get the same
results in Stretch.

It is not surprising that both versions behave differently. The version
in Jessie is ancient and from 2012. A lot of bugs could have been
introduced and fixed between 2012 and today.






signature.asc
Description: OpenPGP digital signature

Bug#909263: marked as done (Postfixadmin 3.0 to 3.2 upgrade: SQLite upgrade fails)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 10:35:43 +
with message-id 
and subject line Bug#909263: fixed in postfixadmin 3.2-4
has caused the Debian Bug report #909263,
regarding Postfixadmin 3.0 to 3.2 upgrade: SQLite upgrade fails
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.)


-- 
909263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfixadmin
Version: 3.2-3
Severity: important
Tags: patch fixed-upstream

Dear Maintainer,

please take a look at issue 177 [1]. Currently it's impossible to use
the upgrade.php script with SQLite! I've tested the commits ceb2610 [2]
and 31c5e6d [3], they are included in patch [4]. Now the upgrade works
like a charm at Debian Buster. I've NOT tested MySQL or pgSQL upgrade!

I don't know if the next Postfixadmin release will be ready before the
Buster freeze, so please consider adding a patch to solve this problem.

Thanks!

-- 
Regards,
Christian

[1]: https://github.com/postfixadmin/postfixadmin/issues/177
[2]:
https://github.com/postfixadmin/postfixadmin/commit/ceb261036a1758e96b1879c298343d2702ab531c
[3]:
https://github.com/postfixadmin/postfixadmin/commit/31c5e6dd2e74678b8c12791538e7212bbf8ee543
[4]:
https://github.com/froonix/postfixadmin/blob/debian-buster-20180920/diff_postfixadmin-3.2..debian-buster-20180920.patch
--- End Message ---
--- Begin Message ---
Source: postfixadmin
Source-Version: 3.2-4

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated postfixadmin 
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: Fri, 28 Sep 2018 11:19:19 +0200
Source: postfixadmin
Binary: postfixadmin
Architecture: source all
Version: 3.2-4
Distribution: unstable
Urgency: medium
Maintainer: Norman Messtorff 
Changed-By: Christoph Martin 
Description:
 postfixadmin - Virtual mail hosting interface for Postfix
Closes: 909263
Changes:
 postfixadmin (3.2-4) unstable; urgency=medium
 .
   * fix sqlite database upgrade (closes: #909263)
Checksums-Sha1:
 aa85e97da94504d2b911090d14c79b85ce14af07 1965 postfixadmin_3.2-4.dsc
 e38eee5709f3b33f5eddcdf59eba90e12b6eb1e8 8144 postfixadmin_3.2-4.debian.tar.xz
 a6c026dcc3871cc42a48bc377c055982c6cf0b8b 1041004 postfixadmin_3.2-4_all.deb
 ded08cee7e27dcafe1ddd1608426fe251a680c8d 7134 
postfixadmin_3.2-4_amd64.buildinfo
Checksums-Sha256:
 66926b5aed2f0ec4fe6a2d1e03c05bc362318e94b00db6ee08968cac38cb05c9 1965 
postfixadmin_3.2-4.dsc
 9bdffcce46b2961f7a0f8a485eaf70ae8d350efbd9d80563eda7cb60cb7c2974 8144 
postfixadmin_3.2-4.debian.tar.xz
 94f376d6a295d0284b693475bd93c0ef7b986dfd416e358825821ed92a7dcc8d 1041004 
postfixadmin_3.2-4_all.deb
 6b88d1d61461cac1263f0cfaa932c4a8d062571a82b4222302da62813706d1fd 7134 
postfixadmin_3.2-4_amd64.buildinfo
Files:
 af5a14f8bf3bdc25798e659dbee1d35a 1965 admin optional postfixadmin_3.2-4.dsc
 2bdf4be93ef29457202ce77fcf0630a6 8144 admin optional 
postfixadmin_3.2-4.debian.tar.xz
 807221f438cb3d46a65237a60c7a8cc3 1041004 admin optional 
postfixadmin_3.2-4_all.deb
 dd2ce778ca389f7f63dc4ade7240bac5 7134 admin optional 
postfixadmin_3.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOfrwsFcJT/ueFKkqgMEJ8ujseQEFAlut/pgACgkQgMEJ8ujs
eQFegg//fVk3nhX0YoQwn/Bk62qo3oQiPzvrDLcOSqcdfABH3FNV63MaD+Edi01z
fOndXU6YSm0sUgxFobWD9gBZ4IPKEDC3CzgilHmV3egjX0SBhK++w0sGbEBuNNH4
k/NKbS3ZFYC3EUJ0OaqsilPb071NHpCS4OnEtofjKIMtCd6kimVVYDbbLw+ROy1e
FuOKfOzK+IXnU9c0KHVEczFua0fREAfZ7NUf6oWRjKdnGnhBJftk5AFXfFpmsITu
BFjJPqYZgXLQhO1Mx43OjWsmFFotSIGuhqMRnZXXPClBdCCpDuq9t5HOvETpaqhT
9L7kXLJExt9omyFfbQTpCNrys3Bxo5e+41W5d9d9+g9hvPJ4uX5Hx/Pr8coOQLp5
zRcFy4HkXZlT/22PuOuLwRuq/MqBfBo4ktzAemsvg8hOOnOwLtxAcp8WgyOYoA3q
ILY9FS1pWp6Ut4CfOXKIhryJFMui0qaeXIISS1Xo5NZlwMJTh1YNQAcMcJH28T0h
qDKCi41C7WQoYLE81856aQiGZ5Uc0dOXgNIpxasDLQPVIs+oJ45U6YTlndpvY30F
eKcSFyzQdcS8wReKBnzHVSiXj3GMm/OR4vt/lPhHh9ah2S39bvxq6TWYdhg8oEnp
9mBWIO2U4UcGkP7IgnzRh8UdpWdPqMBtk53prY0p45LYQpwxZq4=
=DAjY
-END PGP SIGNATURE End 

Bug#909761: marked as done (porechop FTBFS: command 'PorechopClean' has no such option 'all')

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 10:35:34 +
with message-id 
and subject line Bug#909761: fixed in porechop 0.2.3+dfsg-3
has caused the Debian Bug report #909761,
regarding porechop FTBFS: command 'PorechopClean' has no such option 'all'
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.)


-- 
909761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: porechop
Version: 0.2.3+dfsg-2
Severity: serious
Tags: ftbfs

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

...
debian/rules clean
dh clean --with python3 --buildsystem pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py clean 
running clean
error: error in 
/<>/porechop-0.2.3+dfsg/.pybuild/cpython3_3.6/.pydistutils.cfg: 
command 'PorechopClean' has no such option 'all'
E: pybuild pybuild:338: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit code 13
make: *** [debian/rules:11: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: porechop
Source-Version: 0.2.3+dfsg-3

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated porechop 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: Fri, 28 Sep 2018 12:11:40 +0200
Source: porechop
Binary: porechop
Architecture: source
Version: 0.2.3+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Mattia Rizzolo 
Description:
 porechop   - adapter trimmer for Oxford Nanopore reads
Closes: 909761
Changes:
 porechop (0.2.3+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to fix FTBFS in the clean target.  Closes: #909761
Checksums-Sha1:
 079e941ec181f6e8424bbb4d2723ed28a8f9a80f 2062 porechop_0.2.3+dfsg-3.dsc
 729c8777e112f44eb08c17f7996fb6ee3d3c5c83 5468 
porechop_0.2.3+dfsg-3.debian.tar.xz
 0e4e03fbf3389ec8d22aee2377bcdc042a7283a6 6513 
porechop_0.2.3+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 6fd1bc6218dcfabb83bfc63df5a6630d79f89fd2db23382957117ea7945992e9 2062 
porechop_0.2.3+dfsg-3.dsc
 35e3eaadf65c13b989f83c6e537e269a77253de9712a0d4b496a727a9aeebda7 5468 
porechop_0.2.3+dfsg-3.debian.tar.xz
 4e9b3170d10023e611290817da01d1b7f50e30007692893d14ab0f4588d1bdf1 6513 
porechop_0.2.3+dfsg-3_amd64.buildinfo
Files:
 ee3792d9f6d99163668447c6d53efb3e 2062 science optional 
porechop_0.2.3+dfsg-3.dsc
 9841628e325d20ed9e3f7cbecfd75783 5468 science optional 
porechop_0.2.3+dfsg-3.debian.tar.xz
 a93a33a62ae8f169cc452670f0c6a30c 6513 science optional 
porechop_0.2.3+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlut/wQACgkQCBa54Yx2
K63mgw//TolSdqOzdc6oq3bYD2cMEnfzl2gO0H/lP15soY9VokHLaEQ2ygjaGt84
o95Izd5MUF13VKhY1uEY8VOTZTcY9fuYvPhRxvzq1bP7IH/jT6EOvqpyuGreA5BE
zjAQI3kZ8PD1vKEGNp4mHOBJtiEDd2nKoFF8ULNnr9VbIz/3ufdusUusJbhiIyVL
NK5bKVZNmqzzKb1Bu6Jx54ae+O1LzyYAExzkQdRX/73IJCkr7KwX8+mAb2REmZPk
GNwO5X0lqnKbr4xqM2eZv8mq7MKZt6wM2JW/n6hzBaLL+L03+g4JG4hiVQHNVu/U
8tEhGiN4d6RVE6B7/qgAeaurnQWZPVQxR+hBHdQ8qZ4Ut8EIj26OnGGdgaZZiCKU
qkY+Fp3U+lj0PAC8AqZLovs/RHwGkLw45QzhAa9ILJgJUAO9d9Ld399vxhAvl1Gp
a9d07hKR7TqNfeUsTnTLtR37w0ult7i0uE3HyPSaVcyET1w8SRnXn2tdiJLpnS0E
BIoXBicJuuZcdbADcCrrU9QPeCWtJLa+jJGDKJsuUEX0DZYmRh4v0AcpgIhTy8Nk
R8ACJeYiJV+C3ee7VD5zZ+9OkwoY2tFpUVVYKyoGMsE6Gk3v6ZRpioSPzJB9sUuN
l5bg7rTBX/joQ77Sirglyn/MYoWbW5g8ulPEDg2ansxgMbuwB+o=
=smTe
-END PGP SIGNATURE End Message ---

Bug#909761: porechop FTBFS: command 'PorechopClean' has no such option 'all'

[Andreas Tille]

Hi Mattia,

I can confirm that I get the same result:  Works on local machine (here
running testing) and fails with that error in pbuilder.

BTW, if I drop the

 --buildsystem pybuild

this problem vanishes.  So I guess pybuild is doing some magic.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#909766: rapmap FTBFS with spdlog 1:1.1.0-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #909766 [src:rapmap] rapmap FTBFS with spdlog 1:1.1.0-1
Added tag(s) help.

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

Bug#909766: rapmap FTBFS with spdlog 1:1.1.0-1

[Andreas Tille]

Control: tags -1 help

On Thu, Sep 27, 2018 at 11:38:55PM +0300, Adrian Bunk wrote:
> Source: rapmap
> Version: 0.5.0+dfsg-3
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rapmap.html
> 
> ...
> In file included from /build/1st/rapmap-0.5.0+dfsg/src/RapMapUtils.cpp:26:
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp: In function 'void 
> rapmap::utils::writeSAMHeader(IndexT&, std::shared_ptr)':
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:86:18: error: 
> 'MemoryWriter' is not a member of 'fmt'
>  fmt::MemoryWriter hd;
>   ^~~~
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:87:6: error: 'hd' was 
> not declared in this scope
>   hd.write("@HD\tVN:1.0\tSO:unknown\n");
>   ^~
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp: In function 'void 
> rapmap::utils::writeSAMHeader(IndexT&, std::ostream&)':
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:106:18: error: 
> 'MemoryWriter' is not a member of 'fmt'
>  fmt::MemoryWriter hd;
>   ^~~~
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:107:6: error: 'hd' was 
> not declared in this scope
>   hd.write("@HD\tVN:1.0\tSO:unknown\n");
>   ^~
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp: At global scope:
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:125:43: error: expected 
> template-name before '<' token
>  class FixedBuffer : public fmt::Buffer {
>^
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:125:43: error: expected 
> '{' before '<' token
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:125:43: error: expected 
> unqualified-id before '<' token
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:136:44: error: expected 
> class-name before '{' token
>  class FixedWriter : public fmt::Writer {
> ^
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:138:25: error: field 
> 'buffer_' has incomplete type 'rapmap::utils::FixedBuffer'
>  FixedBuffer buffer_;
>  ^~~
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:125:11: note: forward 
> declaration of 'class rapmap::utils::FixedBuffer'
>  class FixedBuffer : public fmt::Buffer {
>^~~
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp: In constructor 
> 'rapmap::utils::FixedWriter::FixedWriter(char*, std::size_t)':
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:141:30: error: expected 
> class-name before '(' token
>  : fmt::Writer(buffer_), buffer_(array, size) {}
>   ^
> /build/1st/rapmap-0.5.0+dfsg/include/RapMapUtils.hpp:141:30: error: expected 
> '{' before '(' token
> ...

I admit my limited knowledge in C++ does not enable me to see a
conncetion between the update of spdlog and these errors but a test
build with libspdlog from testing passed flawlessly.  However, later in
the log there are also

...
In file included from /usr/include/c++/8/memory:81,
 from /usr/include/c++/8/thread:39,
 from /build/rapmap-0.5.0+x/src/RapMapSAMapper.cpp:33:
/usr/include/c++/8/bits/shared_ptr.h:719:5: note: candidate: 'template std::shared_ptr<_Tp> std::make_shared(_Args&& ...)'
 make_shared(_Args&&... __args)
 ^~~
/usr/include/c++/8/bits/shared_ptr.h:719:5: note:   template argument 
deduction/substitution failed:
/build/rapmap-0.5.0+x/src/RapMapSAMapper.cpp:588:80: error: template argument 1 
is invalid
   auto consoleSink = 
std::make_shared();

^
/build/rapmap-0.5.0+x/src/RapMapSAMapper.cpp:589:62: error: no matching 
function for call to 'create(const char [10], )'
   auto consoleLog = spdlog::create("stderrLog", {consoleSink});
  ^


which are looking similar to the problem in #909763 (thus I again took
the freedom to set Gert in CC).

I see another option to work around the current issue since rapmap comes
with its own copy of spdlog (in latest Git version 0.16.3).  I could
revert the exclusion from the rapmap source code as long as upstream has
not yet switched to spdlog 1.1. (and ask in an issue for the migration).

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#909698: rakudo: perl6-tap-harness fails to configure: Could not open /usr/share/perl6/install-dist.p6. Failed to stat file: no such file or directory

[Robert Lemmen]

Hi Axel,

On Thu, Sep 27, 2018 at 02:33:05PM +0200, Axel Beckert wrote:
> That might help for other cases, but not this one. As far as I
> understand, the file is at
> 
>   /usr/share/perl6/tools/install-dist.p6
>   ^^^
> 
> but /usr/share/perl6/rakudo-helper.pl looks for it at
> 
>   /usr/share/perl6/install-dist.p6
>   ^
> 
> So from my point of view that bug can be fixed by adding "tools/" to
> the script path at line 43 of /usr/share/perl6/rakudo-helper.pl.

totally correct, the (pending upload) version -2 does just that.

regards  robert

-- 
Robert Lemmen   http://www.semistable.com 


signature.asc
Description: PGP signature

Bug#909785: python-pcl: Incomplete debian/copyright and/or "freeware" source code?

[Chris Lamb]

Source: python-pcl
Version: 0.3.0~rc1+dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jochen Sprickerhof , 
ftpmas...@debian.org

Hi,

I just ACCEPTed python-pcl from NEW but noticed it was missing 
attribution or similar in debian/copyright for at least some files
listed as "freeware" (!= is this even DFSG-free software?).

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#909698: marked as done (rakudo: perl6-tap-harness fails to configure: Could not open /usr/share/perl6/install-dist.p6. Failed to stat file: no such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 09:04:40 +
with message-id 
and subject line Bug#909698: fixed in rakudo 2018.09-2
has caused the Debian Bug report #909698,
regarding rakudo: perl6-tap-harness fails to configure: Could not open 
/usr/share/perl6/install-dist.p6. Failed to stat file: 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.)


-- 
909698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rakudo
Version: 2018.09-1
Severity: serious
Control: affects -1 perl6-tap-harness

Hi,

perl6-tap-harness fails to install for me as follows on a Raspberry Pi
with Debian Sid armhf:

[…]
Setting up perl6-tap-harness (0.20180415-1) ...
Could not open /usr/share/perl6/install-dist.p6. Failed to stat file: no such 
file or directory
module perl6-tap-harness compilation failed: 256 at 
/usr/share/perl6/rakudo-helper.pl line 44.
dpkg: error processing package perl6-tap-harness (--configure):
 installed perl6-tap-harness package post-installation script subprocess 
returned error exit status 2
[…]
Errors were encountered while processing:
 perl6-tap-harness

The file /usr/share/perl6/install-dist.p6 does not neither exist on
that installation nor does it belong to any installed package.

Also "apt-file search /usr/share/perl6/install-dist.p6" doesn't find
that file, neither on Debian Sid armhf nor on Debian Sid amd64.

Funnily I have perl6-tap-harness successfully installed on amd64
despite I can't find  /usr/share/perl6/install-dist.p6 there either.

Reason for this is probably the switch from
/usr/share/perl6/install-dist.pl to
/usr/share/perl6/tools/install-dist.p6 between 2018.06-1 and
2018.09-1. Please note that this path contains "tools" while the error
message doesn't have "tools" in the path.

Since it's /usr/share/perl6/rakudo-helper.pl which contains that
erroneous path, the issue is not in perl6-tap-harness but in rakudo.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: armhf (armv7l)

Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages perl6-tap-harness depends on:
ii  rakudo  2018.09-1

perl6-tap-harness recommends no packages.

perl6-tap-harness suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rakudo
Source-Version: 2018.09-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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert Lemmen  (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: SHA256

Format: 1.8
Date: Fri, 28 Sep 2018 10:17:52 +0200
Source: rakudo
Binary: rakudo
Architecture: source amd64
Version: 2018.09-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Robert Lemmen 
Description:
 rakudo - Perl 6 implementation on top of Moar virtual machine
Closes: 909698
Changes:
 rakudo (2018.09-2) unstable; urgency=medium
 .
   * Fix install-dist.p6 location in rakudo-helper.pl (closes: #909698)
Checksums-Sha1:
 bf98a90b4b7ab30bef965ac699e9adbc5b2638c7 2648 rakudo_2018.09-2.dsc
 613c07ff651a17cabb23fe2d883b717c7349e72a 16504 rakudo_2018.09-2.debian.tar.xz
 1199c01fae4b74d503a0a3c91a4464f76df322c6 164924 
rakudo-dbgsym_2018.09-2_amd64.deb
 93a3234036fe89d36833a1707bb57fcf8b7f8535 6205 rakudo_2018.09-2_amd64.buildinfo
 6c7420794c359ff2634e6f046d0a14a1a3dcef97 3381476 rakudo_2018.09-2_amd64.deb
Checksums-Sha256:
 d902cafe80d2730660f973039557ffd05003532b08f301aed737841e7e03ac82 2648 
rakudo_2018.09-2.dsc
 0c837462d5d624904a29e9fdc9f108f8fcca271d609d78cf4381ee6e8cdc2536 16504 
rakudo_2018.09-2.debian.tar.xz
 4911f75b1c47f8ef5691b1e13c0452b7b11a8fbeb2ff7945f866bc46ccb3c440 164924 

Bug#909784: python-treetime: Incomplete debian/copyright?

[Chris Lamb]

Source: python-treetime
Version: 0.5.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andreas Tille , ftpmas...@debian.org

Hi,

I just ACCEPTed python-treetime from NEW but noticed it was missing 
attribution in debian/copyright for at least Emma Hodcroft.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#909770: gdm3: Does not show the list of users and fails to start any session

[Sergio Villar Senin]

O Xov, 27-09-2018 ás 22:39 +0100, Simon McVittie escribiu:
> Control: tags -1 + moreinfo
> 
> On Thu, 27 Sep 2018 at 23:16:05 +0200, Sergio Villar Senin wrote:
> >The background of the plyumouth theme is shown but the list of
> >users is not there as expected.
> 
> When this happens, what messages appear in the system log (systemd
> journal or syslog)?
> 
> > Sometimes I press the power button and the system suspends to
> > RAM. When resuming then the gdm login screen is there, *but* if I
> > try to
> > enter any session (GNOME) it does not work. The authentication
> > seems
> > to succeed but then the screen becomes blank and there is no
> > possibility to even switch to the terminals via Ctr-Alt-Fx.
> 
> When this happens, what messages appear in the system log (systemd
> journal or syslog)?

This is the boot log https://pastebin.com/PiwQdiR2

I don't see anything specially wrong there except these lines:

laptop kernel: [drm:intel_dp_start_link_train [i915]] *ERROR*
[CONNECTOR:71:eDP-1] Link Training failed at link rate = 27, lane
count = 2

BTW I noticed that it is possible to enter the session by following the
next steps:
1- Boot
2- Nothing is shown. Press power button to suspend
3- Resume laptop. gdm is shown
4- Enter credentials. Succeeds.
5- Nothing is shown. Press power button to suspend
6- Resume laptop. GNOME session is opened and working normally

That's why I think it's probably the same bug although I am no longer
sure it's a gdm3 issue, perhaps something related to the intel drivers.

BR

Bug#909506: marked as done (inetutils-telnetd: calls update-inetd with wrong arguments)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 08:41:53 +
with message-id 
and subject line Bug#909506: fixed in inetutils 2:1.9.4-4
has caused the Debian Bug report #909506,
regarding inetutils-telnetd: calls update-inetd with wrong arguments
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.)


-- 
909506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: inetutils-telnetd
Version: 2:1.9.4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

  Removing inetutils-telnetd (2:1.9.4-3+b1) ...
  update-inetd: error: --group is only relevant with --add
  dpkg: error processing package inetutils-telnetd (--remove):
   installed inetutils-telnetd package post-removal script subprocess returned 
error exit status 255


update-inetd got more strict recently and rejects superfluous
usage of --group


cheers,

Andreas


inetutils-telnetd_2:1.9.4-3+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: inetutils
Source-Version: 2:1.9.4-4

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated inetutils 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: Fri, 28 Sep 2018 09:39:04 +0200
Source: inetutils
Binary: inetutils-ftp inetutils-ftpd inetutils-inetd inetutils-ping 
inetutils-traceroute inetutils-syslogd inetutils-talk inetutils-talkd 
inetutils-telnet inetutils-telnetd inetutils-tools
Architecture: source
Version: 2:1.9.4-4
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Description:
 inetutils-ftp - File Transfer Protocol client
 inetutils-ftpd - File Transfer Protocol server
 inetutils-inetd - internet super server
 inetutils-ping - ICMP echo tool
 inetutils-syslogd - system logging daemon
 inetutils-talk - talk to another user
 inetutils-talkd - remote user communication server
 inetutils-telnet - telnet client
 inetutils-telnetd - telnet server
 inetutils-tools - base networking utilities (experimental package)
 inetutils-traceroute - trace the IPv4 route to another host
Closes: 909506
Changes:
 inetutils (2:1.9.4-4) unstable; urgency=medium
 .
   * Do not pass --group to update-inetd --remove. Closes: #909506
   * Switch to debhelper compatibility level 11.
   * Bump Standards-Version to 4.2.1 (no changes needed).
   * Use dh_autoreconf instead of manually cleaning and calling autoreconf.
Checksums-Sha1:
 ef137d3c6f6eaa86f3bed26c4daf068392bcd19c 2695 inetutils_1.9.4-4.dsc
 96e5c35892bfce22eb33821355292ed0aba5f9f2 76880 inetutils_1.9.4-4.debian.tar.xz
 e385d633fabb638259c312bd32dcb092ff98ffb2 12724 
inetutils_1.9.4-4_amd64.buildinfo
Checksums-Sha256:
 2e573040af527163de4689171204101a7339d617c1aac27ab37d6441b58668ec 2695 
inetutils_1.9.4-4.dsc
 0da6826ff64bfc1ef915ac7f4a4edc8692b50c4cf41d8ddd26556041f24df4a5 76880 
inetutils_1.9.4-4.debian.tar.xz
 9818d06d7d9d767a4070fbafcff6784c14e13659de125078ebc226bb538f924d 12724 
inetutils_1.9.4-4_amd64.buildinfo
Files:
 6f34c8d87ccc74d7aba8c3a72c1503d4 2695 net optional inetutils_1.9.4-4.dsc
 b3aac344a3c5d7960c552d1790c38811 76880 net optional 
inetutils_1.9.4-4.debian.tar.xz
 1367806b8a241450562f03e86a5ed8a4 12724 net optional 
inetutils_1.9.4-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAlut39AACgkQuXK/PqSu
V6OHEQ//U9FlmHxQ2UzcsWjI5Qhc+N5S+GsGGVyfu5Hbbxf7tZxfPI2pnmBAsv52
Fe1Tq5iYWcZRkfx4GovvJ+tVuIkMtzgj4KgxQCAccQzjC64xk7LYN3W0CaEfmWou
4gDBz8qZtzJODFnxIKahjVTOpbxmAoR+Kj+sEJlOherAj8T/3zU/qoyk8JA8w90u
Flcc+6Z+0cvGRtyqLpUBVAh41WhaEFaF8xENZriUxh2yFE4ZFSW83paqRkNbDpAp
cChsW4G+q4EihTes5XgjEX2fPTerayX0a1whcgTZS3XL0TcHQS8CHIZsvErDv6WC
9Xshg98gw+G2paffl+0Rdp8vIUpzw/5Ze+Ypl8u27ix1N0RBsGUfoixyvlWHPbef
T8wEOaVv2LAkV1hpJJM6/eVh2VnuvaKHVWR04WbaYCkruVrB9ATgBw5X0eCbQXEZ

Bug#909758: marked as done (update-inetd should conflict with package versions broken by stricter argument handling)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 08:43:49 +
with message-id 
and subject line Bug#909758: fixed in update-inetd 4.48
has caused the Debian Bug report #909758,
regarding update-inetd should conflict with package versions broken by stricter 
argument handling
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.)


-- 
909758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: update-inetd
Version: 4.46
Severity: serious
Control: block -1 by 909505 909503 909506

Especially the micro-httpd and inetutils-telnetd cases might
otherwise have the potential to be bad if the prerm would run
on package removal after update-inetd has been upgraded.
--- End Message ---
--- Begin Message ---
Source: update-inetd
Source-Version: 4.48

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated update-inetd 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: Fri, 28 Sep 2018 10:12:53 +0200
Source: update-inetd
Binary: update-inetd
Architecture: source
Version: 4.48
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Description:
 update-inetd - inetd configuration file updater
Closes: 909758
Changes:
 update-inetd (4.48) unstable; urgency=medium
 .
   * Add debconf translations:
 - Catalan (Guillem Jover).
   * Bump Standards-Version to 4.2.0 (no changes needed).
   * Turn the --group and --pattern usage with --add into a warning. While
 it is invalid usage, it does not deserve (yet) the unexpected breakage
 it is causing. Let's postpone erroring out for later. Closes: #909758
Checksums-Sha1:
 5e1370a132ac1992a887af4eb98d6fe1c31ab530 1554 update-inetd_4.48.dsc
 7ed2a7b9dab5d9db066b8d94c4431ae9477bb182 29700 update-inetd_4.48.tar.xz
 46536eb4903df033fbe0bddd55412b018fc82ff0 5340 update-inetd_4.48_amd64.buildinfo
Checksums-Sha256:
 edf70adce5b9ec94c013dacd4d38ae4f1346bc427321c01c87be40036fa6bd43 1554 
update-inetd_4.48.dsc
 c2786ec2d4a7a58b399d280bf9ea98a63dd6c897985b5d35bf37bc933bb0551f 29700 
update-inetd_4.48.tar.xz
 6c99e3bb5c74c18ececabc95fd71478d9d7cd1816678bd3d4e34c9f5c7ffc312 5340 
update-inetd_4.48_amd64.buildinfo
Files:
 2efeeb6c03aa0ab37a7679d2ed09639c 1554 admin optional update-inetd_4.48.dsc
 26f265f619ce188f852f0c5882b3f85c 29700 admin optional update-inetd_4.48.tar.xz
 1aea708e89370fe3ab0ce57cb9fcce69 5340 admin optional 
update-inetd_4.48_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAlut4+UACgkQuXK/PqSu
V6Pe4Q/+Muj9/RS3Wk4CD/xwTelnGW91QH3u/VE0Z5QVFLg3TYKgX/5aOjLJQptI
09dRX82f/D5vOYttE7dR4kUy0QKM13yhYJlZFO7Egogx32JMKi9Vg76oFKLuJ21w
doqHJh1PLC4aCgghVfRM9VRoKZLo2e89faMeTr0BeLwAB/R6H3uANm2xCLDOEuHF
vhpIxT2s7FBBluxbRRdhZ9FtMcHPH/N+gnGXCw8P+qr6VGIN4PkE4EGUqaJwUSE1
z7eEIrwkULVaxGolbs2qT1DG/+8B3lBbD7/skYXecIJro0s+J0tbABkssQLV7QC2
nxVSM3jjstSMcs7EY/NDoVL5+5/NgHacmAR4g6WzVjfBGkb+m5GUlVeia68LeAFJ
mtI7EGevuwk8nV4i/T3bNnsCfiEy9aiUzAlpzQ7A+DS8tMRcIzi07IThw2P7KVpX
JAzViGuJdsUQX0yt2ozMUecn1FEG+F0VAHzyDn/Vd9yr82J8N2lX2ydo6CtPOpqe
/domiJ86hjcJiDV+L9Ci0imD+rO+TE1G0lLZvJGNMogxopNsfe5w3nMX0CBlnUoc
bOOCPRXay6+3HfSnGduhMDpuoSJu3chSoiYtAlvAMNM90JwYaqRJvkqDJ3cNuKZo
GRovrxpzGUTvyy2tW6HDpsb4BZ04jvmtbEUWZgd3IxJpYAqof2U=
=jmp9
-END PGP SIGNATURE End Message ---

Bug#909763: hinge FTBFS with spdlog 1:1.1.0-1

[Andreas Tille]

Control: tags -1 help

Hi,

On Thu, Sep 27, 2018 at 11:28:04PM +0300, Adrian Bunk wrote:
> Source: hinge
> Version: 0.5.0-3
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hinge.html
> 
> ...
> /build/1st/hinge-0.5.0/src/filter/filter.cpp:200:53: error: 'stdout_sink_st' 
> is not a member of 'spdlog::sinks'
>  sinks.push_back(std::make_shared());
>  ^~
> /build/1st/hinge-0.5.0/src/filter/filter.cpp:200:53: error: 'stdout_sink_st' 
> is not a member of 'spdlog::sinks'
> /build/1st/hinge-0.5.0/src/filter/filter.cpp:200:69: error: no matching 
> function for call to 'make_shared< >()'
>  sinks.push_back(std::make_shared());
>  ^
> In file included from /usr/include/c++/8/memory:81,
>  from /usr/include/spdlog/common.h:14,
>  from /usr/include/spdlog/spdlog.h:10,
>  from /build/1st/hinge-0.5.0/src/filter/filter.cpp:22:
> /usr/include/c++/8/bits/shared_ptr.h:719:5: note: candidate: 'template _Tp, class ... _Args> std::shared_ptr<_Tp> std::make_shared(_Args&& ...)'
>  make_shared(_Args&&... __args)
>  ^~~
> ...

Spdlog upstream has again changed its interface (its a bit hard to track
since its just a header library and we have no chance to detect this via
symbols file).  I've checked upstream git and I think the relevant
change is here:

   
https://github.com/gabime/spdlog/commit/9df2bd256e148c00cbac690558d0c2ebf6b1b52d

in file include/spdlog/spdlog.h line 29.

So the code of hinge needs to be adapted to the change

  - auto new_logger = std::make_shared(logger_name, 
std::move(sink));
  + auto new_logger = std::make_shared(std::move(logger_name), 
std::move(sink));

Unfurtunately my non-existing knowledge of C++ leaves me a bit helpless
here.  Gert, you once helped out with a previous spdlog adaption.  Would
you be able with another patch again?

Kind regards

Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#909763: hinge FTBFS with spdlog 1:1.1.0-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #909763 [src:hinge] hinge FTBFS with spdlog 1:1.1.0-1
Added tag(s) help.

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

Bug#909778: libsdl2-dev: SDL_config.h no longer in cflags provided by pkg-config/sdl2-config

[Simon McVittie]

On Fri, 28 Sep 2018 at 08:30:27 +0300, Adrian Bunk wrote:
> In file included from /usr/include/SDL2/SDL_main.h:25,
>  from /usr/include/SDL2/SDL.h:32,
>  from 
> /build/1st/fifechan-0.1.4+git20180904/include/fifechan/sdl/sdlgraphics.hpp:68,
>  from 
> /build/1st/fifechan-0.1.4+git20180904/include/fifechan/sdl.hpp:68,
>  from 
> /build/1st/fifechan-0.1.4+git20180904/src/sdl/sdl.cpp:69:
> /usr/include/SDL2/SDL_stdinc.h:31:10: fatal error: SDL_config.h: No such file 
> or directory
>  #include "SDL_config.h"
>   ^~
> 
> Root cause:
> 
> $ pkg-config --cflags sdl2
> -D_REENTRANT -I/usr/include/SDL2
> $ sdl2-config --cflags
> -I/usr/include/SDL2 -D_REENTRANT
> $ dpkg -S SDL_config.h
> libsdl2-dev:amd64: /usr/include/x86_64-linux-gnu/SDL2/SDL_config.h

This is a regression caused by fixing #909740. Hugh McMaster correctly
pointed out that /usr/include/ is one of the default search
paths for headers. However, SDL_config.h is designed to be included as
 after -I/usr/include/SDL2, not as ,
according to the design documented in 
and popularized by packages like GLib and GTK+; so moving it to
/usr/include//SDL2 does not make it includable. How was the
patch in #909740 tested?

If sdl2-config didn't exist, then this would be easy to fix by adding
-I/usr/include//SDL2 to the pkg-config file (similar to what
happens in GLib); but doing the same thing in sdl2-config would give it
per-architecture variation and make it non-co-installable, so that isn't
an option here.

Here is a possible solution that I think respects all the constraints,
although I have not tested it:

* move SDL_config.h to /usr/include//SDL2/_real_SDL_config.h
  or similar (so that it has the same level of parallel-installability
  as SDL2 itself, and is clearly not part of the SDL API)

* create /usr/include/SDL2/SDL_config.h containing:

  /* Debian-specific, for multiarch support */
  #include 

To avoid regressions like this in future, I would recommend adding an
autopkgtest that compiles C code that calls some trivial function from
SDL in the most recommended way, and checks that it works correctly,
similar to debian/tests/build in packages like dbus and glib2.0. In the
case of SDL2, it should probably be compiled twice: once using
pkg-config to get the required CFLAGS and libraries, and once using
sdl2-config, to make sure both work.

smcv

Bug#907157: [3dprinter-general] Bug#907157: cura-engine: diff for NMU version 1:3.3.0-2.1

[Gregor Riepl]

> I've prepared an NMU for cura-engine (versioned as 1:3.3.0-2.1) and 
> uploaded it to DELAYED/15. Please feel free to tell me if I should 
> cancel it.

Thanks for uploading.

As the patch is from upstream, I assume it won't be required for newer
CuraEngine versions?

I had hoped that I could continue working on Cura, as there are a bunch of
open questions (like how to package stb). But I simply didn't have time to do 
so.

But it's better to provide a quick fix than to wait for an update 
indefinitely...

Bug#909779: vows: Cannot find module 'glob'

[Petter Reinholdtsen]

Package: node-vows
Version: 0.8.1-3
Severity: serious

The vows script no longer seem to work in unstable.  I discovered this
when trying to get science.js building.  It fail with this error message
when running it without any argument, as well as when running it with
arguments.

module.js:549
throw err;
^

Error: Cannot find module 'glob'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (/usr/lib/nodejs/vows/bin/vows:7:14)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)

This make me believe the script fail for everyone, and I set the
severity to reflect that.

-- 
Happy hacking
Petter Reinholdtsen

Bug#909759: marked as done (tnseq-transit is not installable)

[Debian Bug Tracking System]

Your message dated Fri, 28 Sep 2018 06:20:17 +
with message-id 
and subject line Bug#909759: fixed in tnseq-transit 2.2.1-2
has caused the Debian Bug report #909759,
regarding tnseq-transit is not installable
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.)


-- 
909759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tnseq-transit
Version: 2.2.1-1
Severity: serious

The following packages have unmet dependencies:
 tnseq-transit : Depends: python-wxpython but it is not installable
--- End Message ---
--- Begin Message ---
Source: tnseq-transit
Source-Version: 2.2.1-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated tnseq-transit 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: Fri, 28 Sep 2018 07:54:04 +0200
Source: tnseq-transit
Binary: tnseq-transit
Architecture: source
Version: 2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 tnseq-transit - statistical calculations of essentiality of genes or genomic 
regi
Closes: 909759
Changes:
 tnseq-transit (2.2.1-2) unstable; urgency=medium
 .
   * Add dh_python to Build-Depends
 Closes: #909759
Checksums-Sha1:
 63644238410bd3d80c5161fe55f4540f06633c4a 2063 tnseq-transit_2.2.1-2.dsc
 db8ecb4a48303074ede33244c21777f60a159e64 2448 
tnseq-transit_2.2.1-2.debian.tar.xz
Checksums-Sha256:
 f3f788711cf6427560fc4e8c38a0b1397e21cb9bd317dc19b35731588fed8308 2063 
tnseq-transit_2.2.1-2.dsc
 58c9c42afcf9394397275435b15b21c0ec66b80d2378255759088253497dc235 2448 
tnseq-transit_2.2.1-2.debian.tar.xz
Files:
 670d1bb90e7b5a5322d41667cea65017 2063 science optional 
tnseq-transit_2.2.1-2.dsc
 bf354ae0815d3ae9f0e99478e385a352 2448 science optional 
tnseq-transit_2.2.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlutw5gRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFAuA//fBHbr2w2/ucuAcv1YzMWdjLBb+ps+Yb6
A00dM7EBv5jl+eO8MOe4OdU2nznUV6FLnbNqPnvjeYLsjLbOF+oXsqkKKkfC/CpC
ZJ9CaYPLtOo33jrwlIieR/j/3wcq6OO5HVg1Tr39/I5l2ntPlfFAxbBwZ+C/zOlx
UdzdtW9uileDJ0k0EyEb1ibc8LKVqntiQDB3g51S7yd30xVQsUHzpnvrkGxnrdZ9
QiCBnMR419DqjLiJze4fQfYHQBKdBCLCZCxpzElgiV9rfaLnOI4mwM3b5FAZYeJP
DKukNKAHrE+Zqdzax8dq9Q12uL/DU/OuX1dcOwb0iTLmYIKYGln6S/P1aiB41QYj
xKJ5TKzBm2DojnvUMtu21SnTsYRthyawYtK7uJWQwcgrzKi7g6BQ2t0Pd0uiN8v2
4WY1VtaoY+2jI4DfCBuaslnvgvYnhwWgVby4itXYD9140VxbiVnNQ/mg1n+fm+SZ
AcGknJmUU4f3DvnhhAN6/HCu+0y++0/jx+fqQQyh7lxaC3dUtde5MPCxmGlsU6fo
q0cuQw9Fxarq/gX4/FDUZ/kssDqNt/maQmmtKHGdV/aN219XaKY9kyCLrA7DeBPo
l84oDNRNAwdFvdeX/emnv4MMlTMNzaRIxojpUoTmI5LO3+4/KyE70R21XYOtENzR
RoU+yBJSdNs=
=uc1e
-END PGP SIGNATURE End Message ---

Bug#909767: salmon FTBFS with spdlog 1:1.1.0-1

[Andreas Tille]

Hi Adrian,

thanks again for your tough QA work.

On Thu, Sep 27, 2018 at 11:40:04PM +0300, Adrian Bunk wrote:
> Source: salmon
> Version: 0.7.2+ds1-3
> Severity: serious
> Tags: ftbfs

Salmon is heavily lagging behind upstream due to complex packaging.  The
latest version made it very high on my todo list.  My guess is that
upstream has adapted to the new spdlog interface and this issue will be
solved automatically.  I hope to manage it in the next 2-3 weeks.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#876618: [Pkg-javascript-devel] Bug#876618: science.js build-depends on removed nodejs-legacy

[Petter Reinholdtsen]

[Pirate Praveen]
> Just add node-glob as build dependency.

Thank you for looking into this.  I tried adding the dependency, but the
build still fail the same way.  I am using this patch.

diff --git a/debian/control b/debian/control
index 0deb2dc..81ba240 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,8 @@ Priority: optional
 Build-Depends:
  debhelper (>= 9),
  dh-buildinfo,
- nodejs-legacy,
+ nodejs,
+ node-glob,
  node-uglify,
  node-vows,
 Standards-Version: 4.2.1

-- 
Happy hacking
Petter Reinholdtsen