Bug#898958: marked as done (peruse: does not start)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jun 2018 04:34:59 +
with message-id 
and subject line Bug#898958: fixed in peruse 1.2+dfsg+20180219-1
has caused the Debian Bug report #898958,
regarding peruse: does not start
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.)


-- 
898958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: peruse
Version: 1.2+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I just run "peruse" command in my terminal (in fresh installation of 
peruse from apt), I get the following message that appears :

  Failed to load the component from disk. Reported error was: 
"file:///usr/share/peruse/qml/Main.qml:26 Type PeruseMain 
unavailable\nfile:///usr/share/peruse/qml/PeruseMain.qml:27 module 
\"org.kde.kirigami\" is not installed\n"

Thanks ! Et merci !



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

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

Versions of packages peruse depends on:
ii  kio 5.45.0-1
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-3
ii  libkf5archive5  5.45.0-1
ii  libkf5baloo55.45.0-1
ii  libkf5configcore5   5.45.0-1
ii  libkf5coreaddons5   5.45.0-1
ii  libkf5declarative5  5.45.0-1
ii  libkf5filemetadata3 5.45.0-1
ii  libkf5kiocore5  5.45.0-1
ii  libkf5kiowidgets5   5.45.0-1
ii  libqt5core5a5.10.1+dfsg-6+b1
ii  libqt5gui5  5.10.1+dfsg-6+b1
ii  libqt5qml5  5.10.1-4
ii  libqt5quick55.10.1-4
ii  libqt5widgets5  5.10.1+dfsg-6+b1
ii  libstdc++6  8.1.0-3
ii  peruse-common   1.2+dfsg-2
ii  qml-module-org-kde-kirigami25.45.0-1
ii  qml-module-org-kde-newstuff 5.45.0-1
ii  qml-module-qt-labs-folderlistmodel  5.10.1-4

peruse recommends no packages.

peruse suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: peruse
Source-Version: 1.2+dfsg+20180219-1

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

Debian distribution maintenance software
pp.
Simon Quigley  (supplier of updated peruse 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: Sat, 02 Jun 2018 22:38:37 -0500
Source: peruse
Binary: peruse peruse-common
Architecture: source
Version: 1.2+dfsg+20180219-1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Simon Quigley 
Description:
 peruse - comic book reader for KDE
 peruse-common - common files for peruse
Closes: 898958 900044
Changes:
 peruse (1.2+dfsg+20180219-1) unstable; urgency=medium
 .
   * Run wrap-and-sort.
   * Add missing QtQuick runtime dependencies (Closes: #900044).
   * New upstream Git snapshot, which ports to Kirigami 2 (Closes: #898958).
   * Remove upstream patch which is in the Git snapshot.
Checksums-Sha1:
 4bf9151e79790292ff81ca1210520eb5b824996d 2432 peruse_1.2+dfsg+20180219-1.dsc
 4a48487b4e74b89cbd79d1e9f9cf7cead4766cb4 162522 
peruse_1.2+dfsg+20180219.orig.tar.gz
 0c09774693804e33ac114a772957e2f2c39cfc61 4596 
peruse_1.2+dfsg+20180219-1.debian.tar.xz
 be260fbc8c1c6f1a5d1af7b38c51cb069e9c77a0 25303 
peruse_1.2+dfsg+20180219-1_source.buildinfo
Checksums-Sha256:
 6bc38be866d5f1137370938c94aa93a66c00c42fc111f8374777a96c2d164cd4 2432 
peruse_1.2+dfsg+20180219-1.dsc
 7fee5e4b0de97b005d8981a370373b76b1d57c38dae5247aa731e1c2b2f1612a 162522 

Bug#900044: marked as done (peruse: Failed to load the component from disk: QtQuick.Dialogs is not installed)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jun 2018 04:34:59 +
with message-id 
and subject line Bug#900044: fixed in peruse 1.2+dfsg+20180219-1
has caused the Debian Bug report #900044,
regarding peruse: Failed to load the component from disk: QtQuick.Dialogs is 
not installed
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.)


-- 
900044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: peruse
Version: 1.2+dfsg-2
Severity: important

Dear Maintainer,

I installed peruse on buster with `apt install peruse`, and on my first attempt
to run it I am greeted with a fantastic:

Failed to load the component from disk. Reported error was: 
"file:///usr/share/peruse/qml/Main.qml:24 module \"QtQuick.Dialogs\" is not 
installed\n"

To try to fix this error messages and the similar ones that follow when this
one is fixed, I installed the following packages:

 - qml-module-qtquick-dialogs
 - qml-module-qtquick-layouts
 - qml-module-qtquick-controls

Then, I got to the error message described in #898958 (peruse: does not start).
I was unable to install qml-module-org-kde-kirigami from apt (since it is not
in buster), but I downloaded/installed the stretch deb (as described in that
issue). Alas, more issues!

Failed to load the component from disk. Reported error was: 
"file:///usr/share/peruse/qml/Main.qml:26 Type PeruseMain 
unavailable\nfile:///usr/share/peruse/qml/PeruseMain.qml:256 Type Settings 
unavailable\nfile:///usr/share/peruse/qml/Settings.qml:161 Type FileDialog 
unavailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:48
 module \"Qt.labs.settings\" is not installed\n"

So, I installed qml-module-qt-labs-settings... and it finally started!

It looks like a few dependencies need to be added... (and kirigami needs to be
back in sid/buster?)

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

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

Versions of packages peruse depends on:
ii  kio 5.45.0-1
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-3
ii  libkf5archive5  5.45.0-1
ii  libkf5baloo55.45.0-1
ii  libkf5configcore5   5.45.0-1
ii  libkf5coreaddons5   5.45.0-1
ii  libkf5declarative5  5.45.0-1
ii  libkf5filemetadata3 5.45.0-1
ii  libkf5kiocore5  5.45.0-1
ii  libkf5kiowidgets5   5.45.0-1
ii  libqt5core5a5.10.1+dfsg-6+b1
ii  libqt5gui5  5.10.1+dfsg-6+b1
ii  libqt5qml5  5.10.1-4
ii  libqt5quick55.10.1-4
ii  libqt5widgets5  5.10.1+dfsg-6+b1
ii  libstdc++6  8.1.0-3
ii  peruse-common   1.2+dfsg-2
ii  qml-module-org-kde-kirigami25.45.0-1
ii  qml-module-org-kde-newstuff 5.45.0-1
ii  qml-module-qt-labs-folderlistmodel  5.10.1-4

peruse recommends no packages.

peruse suggests no packages.

-- no debconf information

-- 
Zebulon McCorkle
Email: zebmccor...@zeb.fun
IRC (feel free to /msg me):
 - zebmccorkle@Freenode
 - zebmccorkle@OFTC
 - zeb@EsperNet
 - zeb@hackint
 - zeb@PdgnCo
 - zeb@EFNet
PGP: 803A 0F47 82AD DDEA 46BE  055F F8F9 DB8C 1A54 6398
 (Zebulon McCorkle )


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: peruse
Source-Version: 1.2+dfsg+20180219-1

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

Debian distribution maintenance software
pp.
Simon Quigley  (supplier of updated peruse 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-

Processed: notfound 900637 in 0.4.3-5

[Debian Bug Tracking System]

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

> notfound 900637 0.4.3-5
Bug #900637 [python-catkin-pkg] python-catkin-pkg: catkin 0.7.12-2 and 
python-catkin-pkg 0.4.3-1 both provide /usr/bin/catkin_package_version
There is no source info for the package 'python-catkin-pkg' at version 
'0.4.3-5' with architecture ''
Unable to make a source version for version '0.4.3-5'
No longer marked as found in versions 0.4.3-5.
> thanks
Stopping processing here.

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

Bug#900629: debian-edu-install: breaks installation of samba

[Wolfgang Schweer]

On Sat, Jun 02, 2018 at 07:31:14PM +, Mike Gabriel wrote:
> On  Sa 02 Jun 2018 11:33:36 CEST, Holger Levsen wrote:
> 
> > https://jenkins.debian.net/job/chroot-installation_sid_install_education-workstation/1236//console
> > breaks as follows:
> > 
> > first:
> > 
> > Setting up debian-edu-install (2.10.9) ...
> > error: /var/lib/dpkg/info/debian-edu-install.postinst: Unable to read
> > from /etc/debian-edu/config.
> > info: Loading defaults from /usr/lib/debian-edu-install/defaults.common
> > info: Got profile ''
> > update-rc.d: warning: start and stop actions are no longer supported;
> > falling back to defaults
> 
> Not sure about the first one (above). Seems to be some inter-package (d-e-c
> and d-e-i) dependency issue. Where does the /etc/debian-edu/config file get
> created?

This first issue is like expected: As no profile is set (like done 
otherwise at installation time during profile choice), it can't be read. 
But this doesn't break things. See e.g. the successful src:debian-edu 
autopkgtest (search 'got profile'):
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/debian-edu/237298/log.gz

Similar for previous successfull jenkins runs like this one:
https://jenkins.debian.net/job/chroot-installation_sid_install_education-workstation/1234//consoleFull

So the first one is a non-issue.

> > and then, second:
> > 
> > Setting up samba-common-bin (2:4.8.2+dfsg-1) ...
> > Checking smb.conf
> > WARNING: The "syslog" option is deprecated
> > netbios name PROFITBRICKS-BUILD10-AMD64 is not a valid netbios name
> > ERROR: Invalid smb.conf
> > dpkg: error processing package samba-common-bin (--configure):
> >  installed samba-common-bin package post-installation script subprocess
> >  returned error exit status 255
> 
> This one is easy:  Note that the maximum length for a NetBIOS name is 15
> charactars. (from man 5 smb.conf, see "netbios name" option).

This is due to a changed behaviour of samba-common-bin, now parsing 
smb.conf to check for consistency. This is a kown issue with a proposed 
patch for debci, fixed in git; see: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898875

IMO, for Jenkins a similar hostname setting, maybe j-$EPOCH, would solve 
the problem.

So the second one is a non Debian Edu issue.

Wolfgang


signature.asc
Description: PGP signature

Processed: found 900637 in 0.4.3-1

[Debian Bug Tracking System]

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

> found 900637 0.4.3-1
Bug #900637 [python-catkin-pkg] python-catkin-pkg: catkin 0.7.12-2 and 
python-catkin-pkg 0.4.3-1 both provide /usr/bin/catkin_package_version
Marked as found in versions ros-catkin-pkg/0.4.3-1.
> thanks
Stopping processing here.

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

Processed: tagging 900636

[Debian Bug Tracking System]

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

> tags 900636 + buster sid
Bug #900636 [shrinksafe] [shrinksafe] Could not compile dojo: merge back with 
dojo
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#897568: Still an issue with stretch/backports

[Michael Wyraz]

Hello,

thank you very much in investigating in this. IMO the bug is not yet to 
be closed because it's still not in stretch/backports. That means for 
all who run the latest stable debian with a backport kernel, zfs is 
still broken.


For me this means that I have to be _very_ careful in upgrading my 
systems to not to break it (i.e. don't upgrade the kernel).


I like debian for it's stability, both on my desktop and on my servers. 
But with the current situation, I either have to switch to a different 
filesystem (bad, none of the production ready fs have those features 
provided by ZFS), not to use backports (bad, the zfs version 0.6.x has 
several issues) or to switch my distribution (bad, debian is the best ;) 
). So I'd really appreciate if those permanent ZFS issues could be 
finally fixed (e.g. by coordinating updated between the kernel 
maintainer and the zfs-dmks maintainer).


Best regards,

Michael.

Processed: tagging 834915

[Debian Bug Tracking System]

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

> tags 834915 + buster sid
Bug #834915 [src:node-temp] node-temp: FTBFS (AssertionError: 
temp.createWriteStream did not create a file)
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#900511: marked as done (libcurl4 Conflicts: libcurl3)

[Debian Bug Tracking System]

Your message dated Sat, 2 Jun 2018 23:14:40 +0300
with message-id <20180602201440.GA8777@localhost>
and subject line Re: Bug#900511: libcurl4 Conflicts: libcurl3
has caused the Debian Bug report #900511,
regarding libcurl4 Conflicts: libcurl3
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.)


-- 
900511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcurl4
Version: 7.60.0-2
Severity: serious

libcurl4 conflicts with libcurl3, which violates the stated purpose of
the "must" clause at Policy 8.1 (to allow multiple versions of a shared
library to be co-installable), even though it doesn't violate the letter
of the must (binary package name must change when SONAME changes).
Without the second sentence at Policy 8.1, the MUST requirement serves
no purpose, so I have given this severity serious.

This means that, regardless of what Debian does with packages depending
on libcurl, libcurl4 cannot be installed if the user has third party or
home brew software that requires libcurl3.

I found this because I have netsurf-gtk installed, which Depends:
libcurl3.  netsurf-gtk is currently the same version in stable and
unstable, but has been removed from testing.

...Marvin

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On Thu, May 31, 2018 at 12:37:00PM -0400, Marvin Renich wrote:
> Package: libcurl4
> Version: 7.60.0-2
> Severity: serious
> 
> libcurl4 conflicts with libcurl3, which violates the stated purpose of
> the "must" clause at Policy 8.1 (to allow multiple versions of a shared
> library to be co-installable), even though it doesn't violate the letter
> of the must (binary package name must change when SONAME changes).
> Without the second sentence at Policy 8.1, the MUST requirement serves
> no purpose, so I have given this severity serious.

Another purpose (not stated in the policy) is that software compiled 
against the old SONAME cannot work with the new SONAME, and changing
the package name is the cleanest solution to express that through the
package dependencies.

In most cases parallel installation of several SONAME versions of
a library is a working setup, but for cases like libcurl3->libcurl4
the only thing you could argue for would be changing the wording in
policy - parallel installation is not technically feasible here.

> This means that, regardless of what Debian does with packages depending
> on libcurl, libcurl4 cannot be installed if the user has third party or
> home brew software that requires libcurl3.

libcurl3 is not part of buster, and using libraries from previous 
releases that are no longer present in a new stable Debian release is 
not strictly supported - it works most of the time, but when problems
are reported a Breaks/Conflicts against that library is usually the
solution.

> I found this because I have netsurf-gtk installed, which Depends:
> libcurl3.  netsurf-gtk is currently the same version in stable and
> unstable, but has been removed from testing.

That's due to #869600.

> ...Marvin

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--- End Message ---

Bug#900629: debian-edu-install: breaks installation of samba

[Mike Gabriel]

Hi Holger,

On  Sa 02 Jun 2018 11:33:36 CEST, Holger Levsen wrote:


Package: debian-edu-install
Version: 2.10.9
Severity: serious

Hi,

https://jenkins.debian.net/job/chroot-installation_sid_install_education-workstation/1236//console
breaks as follows:

first:

Setting up debian-edu-install (2.10.9) ...
error: /var/lib/dpkg/info/debian-edu-install.postinst: Unable to read
from /etc/debian-edu/config.
info: Loading defaults from /usr/lib/debian-edu-install/defaults.common
info: Got profile ''
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults


Not sure about the first one (above). Seems to be some inter-package  
(d-e-c and d-e-i) dependency issue. Where does the  
/etc/debian-edu/config file get created?



and then, second:

Setting up samba-common-bin (2:4.8.2+dfsg-1) ...
Checking smb.conf
WARNING: The "syslog" option is deprecated
netbios name PROFITBRICKS-BUILD10-AMD64 is not a valid netbios name
ERROR: Invalid smb.conf
dpkg: error processing package samba-common-bin (--configure):
 installed samba-common-bin package post-installation script subprocess
 returned error exit status 255


This one is easy:  Note that the maximum length for a NetBIOS name is  
15 charactars. (from man 5 smb.conf, see "netbios name" option).


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpMVr2nmVwVV.pgp
Description: Digitale PGP-Signatur

Processed: tagging 804579

[Debian Bug Tracking System]

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

> tags 804579 + buster sid
Bug #804579 {Done: Olivier Sallou } [logol-bin] logol-bin: 
bogus hardcoded dependency on libncursesw5
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 900485

[Debian Bug Tracking System]

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

> tags 900485 + buster sid
Bug #900485 [src:python-pbcore] python-pbcore: FTBFS and Debci failure with 
NumPy 1.14
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: found 900248 in 390.59-1

[Debian Bug Tracking System]

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

> found 900248 390.59-1
Bug #900248 [nvidia-driver] nvidia-driver: update to 390.59 breaks direct 
rendering
Bug #900264 [nvidia-driver] bzflag is slow since nvidia-graphics-drivers 
390.59-1
Bug #900378 [nvidia-driver] glx-alternative-nvidia: Fails to enable proprietary 
accelerated OpenGL and does not report the problem
Marked as found in versions nvidia-graphics-drivers/390.59-1.
Marked as found in versions nvidia-graphics-drivers/390.59-1.
Marked as found in versions nvidia-graphics-drivers/390.59-1.
> thanks
Stopping processing here.

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

Processed: tagging 900431

[Debian Bug Tracking System]

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

> tags 900431 + buster sid
Bug #900431 [src:python-hdf5storage] python-hdf5storage: FTBFS and Debci 
failure with NumPy 1.14
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#900652: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called

[Emilio Pozuelo Monfort]

Source: guile-2.2
Version: 2.2.3+1-4
Severity: serious

Your package failed to build on armhf:

Running gc.test
FAIL: gc.test: gc: after-gc-hook gets called
[...]
Totals for this test run:
passes: 40732
failures:   1
unexpected passes:  0
expected failures:  10
unresolved test cases:  578
untested test cases:1
unsupported test cases: 1
errors: 0

FAIL: check-guile
==
1 of 1 test failed


Full log at https://buildd.debian.org/status/package.php?p=guile-2.2

Emilio

Processed: Re: Bug#900392: pymecavideo: Uses dh_python debhelper addon without declaring Build-Dependency to dh_python

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #900392 [src:pymecavideo] pymecavideo: Uses dh_python debhelper addon 
without  declaring Build-Dependency to dh_python
Severity set to 'important' from 'serious'

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

Bug#900392: pymecavideo: Uses dh_python debhelper addon without declaring Build-Dependency to dh_python

[Adrian Bunk]

Control: severity -1 important

On Wed, May 30, 2018 at 02:54:00PM +0800, Boyuan Yang wrote:
> Source: pymecavideo
> Version: 6.5-2
> Severity: serious
> Justification: missing-build-dependency-for-dh-addon
> 
> Dear Maintainer,
> 
> Lintian reported an error against your source package:
> 
> https://lintian.debian.org/tags/missing-build-dependency-for-dh-addon.html
> 
> The source package appears to be using a dh addon but doesn't build depend
> on the package that actually provides it. If it uses it, it must build depend
> on it.
>...

The package build depends on python3-all, which depends on dh-python.

So the dh-python build dependency is missing (and lintian does give
an error for that), but while this should be fixed it is currently
harmless.

> Regards,
> Boyuan Yang

cu
Adrian

-- 

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

Bug#899669: marked as done (python-certbot-dns-digitalocean: Invalid maintainer address letsencrypt-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 18:04:34 +
with message-id 
and subject line Bug#899669: fixed in python-certbot-dns-digitalocean 0.23.0-2
has caused the Debian Bug report #899669,
regarding python-certbot-dns-digitalocean: Invalid maintainer address 
letsencrypt-de...@lists.alioth.debian.org
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.)


-- 
899669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-certbot-dns-digitalocean
Version: 0.23.0-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of python-certbot-dns-digitalocean,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package python-certbot-dns-digitalocean since the
list address letsencrypt-de...@lists.alioth.debian.org used in the
Maintainer: field was not transferred to the alioth-lists service that
provides a continuation for the lists in the @lists.alioth.debian.org
domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
letsencrypt-de...@lists.alioth.debian.org is 17.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-certbot-dns-digitalocean
Source-Version: 0.23.0-2

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

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated 
python-certbot-dns-digitalocean 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: Sat, 02 Jun 2018 13:44:02 -0400
Source: python-certbot-dns-digitalocean
Binary: python3-certbot-dns-digitalocean python-certbot-dns-digitalocean-doc
Architecture: source
Version: 0.23.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Let's Encrypt 
Changed-By: Harlan Lieberman-Berg 
Description:
 python-certbot-dns-digitalocean-doc - Documentation for the DigitalOcean DNS 
plugin for Certbot
 python3-certbot-dns-digitalocean - DigitalOcean DNS plugin for Certbot
Closes: 899669
Changes:
 python-certbot-dns-digitalocean (0.23.0-2) unstable; urgency=medium
 .
   * Update maintainer email to tracker.d.o team address. (Closes: #899669)
Checksums-Sha1:
 793daa3596214c0dc0110eedc6f1762a1b975484 2756 
python-certbot-dns-digitalocean_0.23.0-2.dsc
 ac46be5f2c777afeb1bbf9287732404ac3dd1480 4428 
python-certbot-dns-digitalocean_0.23.0-2.debian.tar.xz
 a053e1c4c0c64ab98e045b52f12610e2f73440f7 8449 
python-certbot-dns-digitalocean_0.23.0-2_amd64.buildinfo
Checksums-Sha256:
 2d579a4fcfdf4f147fa330724c5c4fe956a2a68ae713510a1b139ae8e449bac5 2756 

Bug#900591: FTBFS against R 3.5: The C compiler identification is unknown

[Helmut Grohne]

On Sat, Jun 02, 2018 at 11:58:21AM +0300, Juhani Numminen wrote:
> On Fri, 1 Jun 2018 21:12:06 +0200 Sébastien Villemot  
> wrote:
> > Package: src:rkward
> > Severity: serious

> For a build log of the failure, see the link "rbuild (41KB)" at [1].
> 
> It seems that the cmake invocation is causing trouble. Consider these forms:
> 
> 1) CC='gcc -std=c99' cmake ...
> 2) CC='gcc -std=c99' cmake -DCMAKE_C_COMPILER='gcc -std=c99' ...

If you look around passing spaces in CC to cmake, you'll quickly  see
that this generally doesn't work well. Yes, there is a hack that can
separate one argument from the path, but that is more of an
implementation detail as far as I understand it. Thus I believe that
this usage is expectably prone to breakage. Not supporting spaces in CC
seems reasonable to me.

> The first one is okay and CMake handles the extra -std=c99 argument properly, 
> but
> the second one causes "-- The C compiler identification is unknown".
> This behavior is expected as CMAKE_C_COMPILER should be a full path.[6]
> 
> Debhelper[2] uses the second form when CC is set, as is done in rkward[3].
> The change was introduced in [4], to fix #897083[5].
> (Helmut Cc'd to notify of this unexpected breakage.)

Yes, the attribution to this debhelper bug is correct.

The proper way to pass -std=c99 would be CMAKE_C_FLAGS as far as I can
tell.

> On the other hand, maybe debian/rules of rkward needs to be changed. The 
> comment
> at [3] states that setting CC is required for "some installations of R", but 
> is
> it required in the Debian package specifically?
>
> In this case, 'gcc -std=c99' comes from "/usr/bin/R CMD config CC".
> I am also wondering why R should impose -std=c99. There exist many other 
> possible
> values for -std.[7]

Stuffing flags - and in particular -std=c99 - into CC looks wrong to me.
Maybe reassigning to R is the way to go.

Also note that using plain "gcc" here breaks cross compilation. R should
certainly return a triplet-prefixed CC like python does.

Most debhelper changes break some package. This one is no different. The
number of affected packages seems low to me and the feature being broken
was known to be fragile. I think it is reasonable to keep the new
debhelper behaviour.

Helmut

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 900533 900539
Bug #900533 [chromium] chromium 67.0.3396.62-1: youtube video, gif's, html5, 
and movies no longer work
Bug #900539 [chromium] Can no longer watch any YouTube movie
Severity set to 'grave' from 'normal'
Merged 900533 900539
> thanks
Stopping processing here.

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

Bug#899135: marked as done (always includes manpages in first binary package being built, resulting in fileconflicts)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 14:11:06 +
with message-id 
and subject line Bug#899135: fixed in powerline 2.6-2
has caused the Debian Bug report #899135,
regarding always includes manpages in first binary package being built, 
resulting in fileconflicts
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.)


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

Hi,

thank you for maintaining powerline in debian.

When locally rebuilding the package, I found the following issue:

  * dh_installman in rules is called unconditionally wrt/ to which
package it acts upon. that means that debhelper chooses to the first
binary package listed in control that gets built.

  * when building arch-indep only, the only binary package that is built
is fonts-powerline, so the manpages get put into fonts-powerline.

  * when building arch-dep only, the first binary package is powerline,
so the manpages get put into powerline.

  * since you've uploaded source + binary-all + binary-amd64 in your
upload to debian, the manpages get put into powerline.

  * since binary-all packages that have been part of the upload to
debian are not rebuild, the one you uploaded stays in the archive
without the manpages included. however, if that gets rebuilt, it
will get the manpages included and thus have conflicting files with
powerline.

...or in other words: src:powerline has conflicting files in
bin:powerline and bin:fonts-powerline iff every binary-indep and
binary-dep packages have been built seperatly.

this makes the build/upload non-deterministic which i believe in this
case varants severity serious.

I'll attach a patch after having recieved the bug number.

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: powerline
Source-Version: 2.6-2

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

Debian distribution maintenance software
pp.
Jerome Charaoui  (supplier of updated powerline 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, 01 Jun 2018 15:32:49 -0400
Source: powerline
Binary: fonts-powerline powerline powerline-doc python-powerline 
python-powerline-doc python3-powerline
Architecture: source all amd64
Version: 2.6-2
Distribution: unstable
Urgency: medium
Maintainer: Jerome Charaoui 
Changed-By: Jerome Charaoui 
Description:
 fonts-powerline - prompt and statusline utility (symbols font)
 powerline  - prompt and statusline utility
 powerline-doc - prompt and statusline utility (documentation)
 python-powerline - prompt and statusline utility (Python 2.x module)
 python-powerline-doc - prompt and statusline utility (transitional package)
 python3-powerline - prompt and statusline utility (Python 3.x module)
Closes: 899135 899142 899150 899153 899165 899178 899184 900331
Changes:
 powerline (2.6-2) unstable; urgency=medium
 .
   [ Daniel Baumann ]
   * Install manapages into the powerline package only (Closes: #899135)
   * Automatically update fontconfig cache using dpkg trigger (Closes: #899142)
   * Update vim instructions in README.Debian (Closes: #899150)
   * Add debconf support to enable powerline for all users (Closes: #899184)
   * Set default shell theme to default_leftonly (Closes: #899153)
   * Switch to use python3 by default (Closes: #899165)
   * Include /etc/powerline as configuration directory (Closes: #899178)
   * Apply patch from Andreas Schneider to fix build with GCC-7 (Closes: 
#900331)
   * Rename python-powerline-doc to powerline-doc for consistency
   * Apply various updates and fixes to control, watch and copyright files
   * Update packaging to debhelper version 11
   * Update packaging to standards version 4.1.4
 .
   [ Jerome Charaoui ]
   * Fix privacy breaches in documentation
   * Update NEWS file
Checksums-Sha1:
 00e92bea1b6a960494b779a391a215ef97b8f8fc 2327 powerline_2.6-2.dsc
 9689aec2e91ffeebc31fcfce75c71fad09c5ab2a 13744 

Bug#900637: python-catkin-pkg: catkin 0.7.12-2 and python-catkin-pkg 0.4.3-1 both provide /usr/bin/catkin_package_version

[Steve Cotton]

Package: python-catkin-pkg
Version: 0.4.3-5
Severity: grave
Justification: renders package uninstallable, so it should show up in 
apt-listbugs

Hi,

python-catkin-pkg 0.4.3-1 doesn't declare conflicts or breaks on catkin 
0.7.12-2, but they can't be installed together, and catkin 0.7.12-2 depends on 
python-catkin-pkg.

Unpacking python-catkin-pkg (0.4.3-1) over (0.4.2-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/python-catkin-pkg_0.4.3-1_all.deb (--unpack):
 trying to overwrite '/usr/bin/catkin_package_version', which is also in 
package catkin 0.7.12-2
Errors were encountered while processing:
 /var/cache/apt/archives/python-catkin-pkg_0.4.3-1_all.deb


Versions of packages installed:
ii  catkin0.7.12-2
ii  python-catkin-pkg 0.4.2-3

I assume this is waiting for catkin 0.7.13 to be packaged, but please declare 
the versioned dependency.

Thanks,
Steve

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

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

Versions of packages python-catkin-pkg depends on:
ii  libpython2.7-stdlib [python-argparse]  2.7.15-1
ii  python 2.7.15~rc1-1
ii  python-dateutil2.6.1-1
ii  python-docutils0.14+dfsg-3
ii  python-pyparsing   2.2.0+dfsg1-2

python-catkin-pkg recommends no packages.

python-catkin-pkg suggests no packages.

-- no debconf information

Processed: reassign 900443 to elpa-usepackage, retitle 900443 to Fails to byte compile with unversioned emacs ...

[Debian Bug Tracking System]

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

> reassign 900443 elpa-usepackage
Bug #900443 [emacs-gtk] error: Unable to activate package ‘use-package’. 
Required package ‘bind-key-1.0’ is unavailable
Bug reassigned from package 'emacs-gtk' to 'elpa-usepackage'.
Warning: Unknown package 'elpa-usepackage'
Warning: Unknown package 'elpa-usepackage'
No longer marked as found in versions emacs/1:25.2+1-7.
Warning: Unknown package 'elpa-usepackage'
Warning: Unknown package 'elpa-usepackage'
Ignoring request to alter fixed versions of bug #900443 to the same values 
previously set
Warning: Unknown package 'elpa-usepackage'
> retitle 900443 Fails to byte compile with unversioned emacs
Bug #900443 [elpa-usepackage] error: Unable to activate package ‘use-package’. 
Required package ‘bind-key-1.0’ is unavailable
Warning: Unknown package 'elpa-usepackage'
Changed Bug title to 'Fails to byte compile with unversioned emacs' from 
'error: Unable to activate package ‘use-package’. Required package 
‘bind-key-1.0’ is unavailable'.
Warning: Unknown package 'elpa-usepackage'
> severity 900443 important
Bug #900443 [elpa-usepackage] Fails to byte compile with unversioned emacs
Warning: Unknown package 'elpa-usepackage'
Severity set to 'important' from 'grave'
Warning: Unknown package 'elpa-usepackage'
> thanks
Stopping processing here.

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

Bug#900636: [shrinksafe] Could not compile dojo: merge back with dojo

[Bastien ROUCARIES]

Package: shrinksafe
Severity: grave

Hi;

This package fail to compile dojo.

Dojo is the current upstream so merge back in dojo

Bastien

Bug#900591: marked as done (FTBFS against R 3.5: The C compiler identification is unknown)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 13:20:57 +
with message-id 
and subject line Bug#900591: fixed in rkward 0.7.0b-1
has caused the Debian Bug report #900591,
regarding FTBFS against R 3.5: The C compiler identification is unknown
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.)


-- 
900591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rkward
Version: 0.7.0-1
Severity: serious
Control: block 896667 by -1 

Dear Maintainer,

The R 3.5 transition has just started (see #896667), and consequently the
rebuild of rkward has been triggered.

But the rebuild failed, apparently because the C compiler is not properly
detected (I did not investigate whether this error is actually related to R 3.5
or is due to some other unrelated change):

 
https://buildd.debian.org/status/fetch.php?pkg=rkward=amd64=0.7.0-1=1523909885=0

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rkward
Source-Version: 0.7.0b-1

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

Debian distribution maintenance software
pp.
Thomas Friedrichsmeier  (supplier of 
updated rkward package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Jun 2018 09:00:00 +0100
Source: rkward
Binary: rkward rkward-data
Architecture: source
Version: 0.7.0b-1
Distribution: unstable
Urgency: low
Maintainer: Thomas Friedrichsmeier 
Changed-By: Thomas Friedrichsmeier 
Description:
 rkward - KDE frontend to the R statistics language
 rkward-data - KDE frontend to the R statistics language - data files
Closes: 895875 900591
Changes:
 rkward (0.7.0b-1) unstable; urgency=low
 .
   * New upstream release
 Includes missing translation files in rkward-data
   * Replace kdoctools-dev dependency with libkf5doctools-dev
 closes: #895875
   * Depend on r-api-3.5 when built against r-base-core >= 3.5.0
   * Do not depend on r-api-3.4 when built against r-base-core < 3.4.0
   * Remove explicit specification of C compiler
 closes: #900591
Checksums-Sha1:
 682a4a07b087f01faa6f9a151db5efda9dbd9b59 2025 rkward_0.7.0b-1.dsc
 9604b4cd77f50d514b6b7775e850c30b4f9e3e06 3978972 rkward_0.7.0b.orig.tar.gz
 6f459f1b6b0ec4cdc5257ae9e12b4e3d6baa245b 7496 rkward_0.7.0b-1.debian.tar.xz
 9ec3ad071ee036fa9a680170ae4402681cdf1d53 5892 rkward_0.7.0b-1_source.buildinfo
Checksums-Sha256:
 49f22b972df63c72778281b725acb4628a9003fbd2db9f158c18a5e075dd0da1 2025 
rkward_0.7.0b-1.dsc
 556e7bc8d3b8383e60c20c630f899075a6d39a04d29e56f4278191bb6ff853f4 3978972 
rkward_0.7.0b.orig.tar.gz
 88c1cf228b15f7d56b63ab52583d5f0b75b1f4435de59f014652e80371941d95 7496 
rkward_0.7.0b-1.debian.tar.xz
 4c57e3a4c4451e9dde54cb1e9da0c4189451e49ce9fbc2b3b29699fc51d938de 5892 
rkward_0.7.0b-1_source.buildinfo
Files:
 739741a05d152f915d4312924323d0b7 2025 math optional rkward_0.7.0b-1.dsc
 a678008a571c7dacd5c13d62817ead7a 3978972 math optional 
rkward_0.7.0b.orig.tar.gz
 86ebfa95af60b323fb595f3da8aae6d9 7496 math optional 
rkward_0.7.0b-1.debian.tar.xz
 7f97e7b01ede5aeb4724529f426c4f0b 5892 math optional 
rkward_0.7.0b-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAlsSlZIACgkQq2RfQGKG
p9A/jQ/+MV/w7H73Gc+sR2iHxZXLgx7Rgt2JLCYZ7YBzeqHsMuOThIPXnzUINl4s
TvgLiQYQDpcvnAenBPOPqv8UD4/JTn/XanaDdTaqjYncLNsdbyPQ58/Rdyg8eQLs
otkjhSyXgcJR0doKTNH63pXLNewGHIuwDYcE/tV+WW2fzh3qePXZowin3MOxqR7F
sti1hTYnZHGcJ+iO6mEDqMlOIeNz2NVF1WKJyuKKENJaFDi6I0eS1Gf2Z1ORCZNj
toSiTC9KiNLw8sJ2c09ufPwZeAbBN2Cd8o7cOluG5nmR/uCYqAsNFi4r1Wf3K4Dq
1NukicID4uhl8JbHiEPrZBKRP1wsQhSVHytzEfnohudmTUWFq3Sl4nA5e14w1EYx
a6IeHa5M57K3yBAaPSxVenE8i5WW7BQAy2KkUn+ZtkF1GP5LHa2exFofAwqyzZe+
JCocu8E/JzonJ05WRRG3nNWFxSwoH3mMV7FDYmpiqieeUbQNyS6EGUGbT6lwp5T1
XmPDynbWw4nmCwq4YqbIzQJL3WB6gObf0MkTUl9wAoOq3c0QISYCyKeJgY5IN6hQ
annpgvIlUdi/pZtWxznFnUjmeR79yaQFcN5uqh5l8k8F53w1wBmw32Rkk3xwW84c

Bug#248496: raise priority

[Markus Koschany]

Control: severity -1 normal
Control: tags -1 moreinfo

On Sat, 2 Jun 2018 12:18:22 +0200 Salvo Tomaselli 
wrote:
> severity 248496 grave
> thanks
> 
> Raising priority, since the game does not run at all and the package
> seems completely abandoned.
> 
> If I'm right, the package will eventually just be dropped.

Hello,

the game works for me on amd64 and i386 in Sid. I cannot confirm that
the game is unusable for the majority of users hence I think severity
grave is not justified in this case.

Please note that the package has been orphaned. It simply needs a new
maintainer.

https://bugs.debian.org/869291

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: raise priority

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #248496 [pacman] pacman: X Error of failed request
Severity set to 'normal' from 'grave'
> tags -1 moreinfo
Bug #248496 [pacman] pacman: X Error of failed request
Added tag(s) moreinfo.

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

Bug#900591: FTBFS against R 3.5: The C compiler identification is unknown

[Thomas Friedrichsmeier]

On Sat, 2 Jun 2018 11:58:21 +0300
Juhani Numminen  wrote:
> On the other hand, maybe debian/rules of rkward needs to be changed.
> The comment at [3] states that setting CC is required for "some
> installations of R", but is it required in the Debian package
> specifically?

In fact, my approach to fixing this is to remove the specification of
CC (and CXX, F77) form R CMD config. This was added, historically, in
2007, when R was forcing GCC 4.2, while GCC 4.1 was still the default,
and Ubuntu did not even have GCC 4.1. Since there was some
incompatibility between 4.2 and 4.1 (fortran, I believe), linking would
fail unless using the same version. Handling this in rules, instead of
dependencies was the only way to allow building for debian and ubuntu
from the same source, then. It should not be needed, today.

A fixed package is on mentors. I cannot upload myself. Lisandro has
sponsored the last couple of uploads, and I've contacted him, this
morning. (Note that technically, this is also a new upstream release,
but the single upstream change is a hotfix to ensure proper
installation of translations).

Regards
Thomas


pgp61MHKPp_U7.pgp
Description: OpenPGP digital signature

Bug#894360: icedtea-web (build) depends on openjdk-8

[Emilio Pozuelo Monfort]

On Thu, 29 Mar 2018 15:46:07 +0300 Adrian Bunk  wrote:
> Source: icedtea-web
> Version: 1.6.2-3.1
> Severity: serious
> Tags: buster sid
> 
> openjdk-8-jdk is not expected to be part of the buster release.
> 
> icedtea-web build depends on openjdk-8 and icedtea-{netx,8-plugin}
> have openjdk-8-jre dependencies.

There is upstream support for JDK 9. I don't see upstream support for JDK 10,
but maybe I missed it. Has anybody tried to build it with default-jdk / JDK 10?

Emilio

Bug#900618: marked as forwarded (tseries: unsatisfiable versioned dependency on quantmod (>= 0.4.9))

[Debian Bug Tracking System]

Your message dated Sat, 2 Jun 2018 07:16:03 -0500
with message-id <23314.35459.92662.255...@rob.eddelbuettel.com>
has caused the   report #900618,
regarding tseries: unsatisfiable versioned dependency on quantmod (>= 0.4.9)
to be marked as having been forwarded to the upstream software
author(s) Kurt Hornik 

(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.)


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

Hello Kurt,

In the big rebuild for R 3.5.0 within Debian an issue came up with tseries ->
quantmod. I think this is from when you switched to using Josh's data fetcher
in quantmod.  Seemingly you made a type in Depends as Graham noticed.

I am somewhat surprised this did not throw up an error on the CRAN side.  Any
idea why the "unsatisfiable" depends passed?  Does a '-' silently become a
'.' here ?

Cheers,  Dirk


On 2 June 2018 at 09:21, Graham Inggs wrote:
| Source: tseries
| Version: 0.10-44-1
| Severity: serious
| Tags: patch
| X-Debbugs-CC: r-pkg-t...@alioth-lists.debian.net
| 
| Hi Dirk
| 
| Due to some new magic in dh-r, r-cran-tseries gains a versioned
| dependency on quantmod (>= 0.4.9), but we have 0.4-13-1 in the archive
| and this makes r-cran-tseries not installable.
| 
| My guess is this was a typo upstream, and they meant 0.4-9 instead of 0.4.9.
| 
| Please consider including my patch, attached.
| 
| Regards
| Graham
| x[DELETED ATTACHMENT fix-quantmod-version.patch, text/x-patch]

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org--- End Message ---

Bug#900618: tseries: unsatisfiable versioned dependency on quantmod (>= 0.4.9)

[Dirk Eddelbuettel]

On 2 June 2018 at 09:21, Graham Inggs wrote:
| Source: tseries
| Version: 0.10-44-1
| Severity: serious
| Tags: patch
| X-Debbugs-CC: r-pkg-t...@alioth-lists.debian.net
| 
| Hi Dirk
| 
| Due to some new magic in dh-r, r-cran-tseries gains a versioned
| dependency on quantmod (>= 0.4.9), but we have 0.4-13-1 in the archive
| and this makes r-cran-tseries not installable.
| 
| My guess is this was a typo upstream, and they meant 0.4-9 instead of 0.4.9.

Great catch. I kinda concur, but will follow-up.

| Please consider including my patch, attached.

My instinct would have been to just remove the versioning ... given that we
know we have the current quantmod. But this should work too and is likely
the better way.

Dirk
 
| Regards
| Graham
| x[DELETED ATTACHMENT fix-quantmod-version.patch, text/x-patch]

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

[Vasudev Kamath]

Hi Thomas,

I read through and prepared a version to experimental which symlinks
fa-solid-900.ttf as fontawesome-webfont.ttf. I've uploaded it to
experimental, can you please check if this helps?.

@Others Please let me know if this new version in experimental with
suggestion from Thomas improves situation in your cases.

If it improves then I will move this change to unstable.

Cheers,

Vasudev

--

Bug#899660: marked as done (pycryptopp: Invalid maintainer address tahoe-deb...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 11:20:06 +
with message-id 
and subject line Bug#899660: fixed in pycryptopp 0.7.1-4
has caused the Debian Bug report #899660,
regarding pycryptopp: Invalid maintainer address 
tahoe-deb...@lists.alioth.debian.org
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.)


-- 
899660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pycryptopp
Version: 0.7.1-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of pycryptopp,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package pycryptopp since the list address
tahoe-deb...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
tahoe-deb...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pycryptopp
Source-Version: 0.7.1-4

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

Debian distribution maintenance software
pp.
Vasudev Kamath  (supplier of updated pycryptopp 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: Sat, 02 Jun 2018 16:28:37 +0530
Source: pycryptopp
Binary: python-pycryptopp
Architecture: source
Version: 0.7.1-4
Distribution: unstable
Urgency: medium
Maintainer: Tahoe Packaging Team 
Changed-By: Vasudev Kamath 
Description:
 python-pycryptopp - Python wrappers for the Crypto++ library
Closes: 899660
Changes:
 pycryptopp (0.7.1-4) unstable; urgency=medium
 .
   * Use tracker team address in maintainer field.
 Closes: bug#899660, Thanks to Christoph Biedl.
   * debian/control:
 + Mark package as compliant with Debian Policy 4.1.3
 + Use salsa url in Vcs-* fields.
   * debian/patches/no-version-in-setup.patch:
 + Fix typo in DEP-3 header.
Checksums-Sha1:
 f7643922db3f611b4340fe3c0e5bcb99dc4982ed 2200 pycryptopp_0.7.1-4.dsc
 a8dfa0e0e69d97ce3e34b2cbb0de201361d6 12620 pycryptopp_0.7.1-4.debian.tar.xz
Checksums-Sha256:
 0974989473c72684ceb67bff5d1606ceaae2876bf8cef6a0e46c42cac1938571 2200 
pycryptopp_0.7.1-4.dsc
 43bb4a5895347577664a8b52c93737520b877583deced8ae97536348a96063f2 12620 
pycryptopp_0.7.1-4.debian.tar.xz
Files:
 ccc37db6e2d072dfabb965a39bbab66c 2200 python optional pycryptopp_0.7.1-4.dsc
 775212ab34de00d789a5dc9d7f3cb6a9 12620 python optional 
pycryptopp_0.7.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#899661: #899661 pydoctor: Invalid maintainer address calendarserver-maintain...@lists.alioth.debian.org

[Ian Jackson]

Hi.  Hopefully you are aware of the closure of alioth.  A package of
yours, "pydoctor", is affected because it mentions a now-closed
mailing list in its Maintainer field.  Please see for more information:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899661

Can you please let me know what your plans are, and whether and on
what kind of timescale you will be able to fix this yourself ?

In the absence of better information, I guess my best option is
probably to do an NMU of the package to change the maintainer address
to your name and email address (from Uploaders).  Alternatively if you
are no longer interested then for now it probably ought to be regarded
as orphaned.

Or, maybe there are people reading this who would like to help.

(My interest is that one of my packages depends indirectly on
pydoctor, and the RC bug in pydoctor has started the testing
autoremoval clock.)

Regards,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#899755: marked as done (zfec: Invalid maintainer address tahoe-deb...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 11:06:35 +
with message-id 
and subject line Bug#899755: fixed in zfec 1.5.2-2
has caused the Debian Bug report #899755,
regarding zfec: Invalid maintainer address tahoe-deb...@lists.alioth.debian.org
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.)


-- 
899755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zfec
Version: 1.5.2-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of zfec,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package zfec since the list address
tahoe-deb...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
tahoe-deb...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: zfec
Source-Version: 1.5.2-2

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

Debian distribution maintenance software
pp.
Vasudev Kamath  (supplier of updated zfec 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: Sat, 02 Jun 2018 16:02:12 +0530
Source: zfec
Binary: python-zfec python3-zfec
Architecture: source
Version: 1.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Tahoe Packaging Team 
Changed-By: Vasudev Kamath 
Description:
 python-zfec - fast erasure codec, with Python bindings
 python3-zfec - fast erasure codec, with Python 3 bindings
Closes: 899755
Changes:
 zfec (1.5.2-2) unstable; urgency=medium
 .
   * Use tracker team address in maintainers field.
 Closes: bug#899755, Thanks to Christoph Biedl.
Checksums-Sha1:
 5009fa2c157a14dbdc86741d9110219ab6947737 2144 zfec_1.5.2-2.dsc
 6df9d39f7888489a12849e944d93f96e479a8bd4 11056 zfec_1.5.2-2.debian.tar.xz
Checksums-Sha256:
 d7b153d64428db7069a03ccef6fe66393db5ab1425d163ee89ce42dbaa66324b 2144 
zfec_1.5.2-2.dsc
 417fea8fa4d8d258be9f988d7050ea342d711d19f4c29f40fd85a66b6090618c 11056 
zfec_1.5.2-2.debian.tar.xz
Files:
 1c2a6ffae217eb02598ae90b94c4b14b 2144 python optional zfec_1.5.2-2.dsc
 c764fc8f51bf540cd03fe2148c082321 11056 python optional 
zfec_1.5.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEExRfCXeQIdZ2YpMlrbI90rodwC34FAlsSdXMXHHZhc3VkZXZA
Y29weW5pbmphLmluZm8ACgkQbI90rodwC34rSg//V8z4xl7wADgHYT5Sf/Ep5e0y
STOcJOWUeLNgXkgSYqHuTGzC6gCQxjkASmI2v/1Eh//HhKaVvXN1OMx6J1eAjsB/

Bug#899706: marked as done (tahoe-lafs: Invalid maintainer address tahoe-deb...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 10:52:42 +
with message-id 
and subject line Bug#899706: fixed in tahoe-lafs 1.12.1-5
has caused the Debian Bug report #899706,
regarding tahoe-lafs: Invalid maintainer address 
tahoe-deb...@lists.alioth.debian.org
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.)


-- 
899706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tahoe-lafs
Version: 1.12.1-4
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of tahoe-lafs,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package tahoe-lafs since the list address
tahoe-deb...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
tahoe-deb...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: tahoe-lafs
Source-Version: 1.12.1-5

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

Debian distribution maintenance software
pp.
Vasudev Kamath  (supplier of updated tahoe-lafs 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: Sat, 02 Jun 2018 15:50:55 +0530
Source: tahoe-lafs
Binary: tahoe-lafs
Architecture: source
Version: 1.12.1-5
Distribution: unstable
Urgency: medium
Maintainer: Tahoe Packaging Team 
Changed-By: Vasudev Kamath 
Description:
 tahoe-lafs - Secure distributed file store
Closes: 899706
Changes:
 tahoe-lafs (1.12.1-5) unstable; urgency=medium
 .
   * Use tracker team address in maintainers field.
 Closes: bug#899706, Thanks to Christoph Biedl.
Checksums-Sha1:
 e20adc8133741d1aee95d4b6005497f93f742fa2 2166 tahoe-lafs_1.12.1-5.dsc
 80390d1170264b4f75dbd56999ffa1281b2838c1 15624 
tahoe-lafs_1.12.1-5.debian.tar.xz
Checksums-Sha256:
 de0e297822951759320a3d8eefcf41452e256f8fbe4ce3386854b9777ec49cbc 2166 
tahoe-lafs_1.12.1-5.dsc
 2231ff2aa830e43f0feed5def7fc8265052e4629f138dfc4bb892e963a5d95a7 15624 
tahoe-lafs_1.12.1-5.debian.tar.xz
Files:
 62ffe5c8dd9780a3712ad4f02f29fda2 2166 utils optional tahoe-lafs_1.12.1-5.dsc
 2cee60c0a1d90fe40d4127715262d41d 15624 utils optional 
tahoe-lafs_1.12.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEExRfCXeQIdZ2YpMlrbI90rodwC34FAlsScnsXHHZhc3VkZXZA
Y29weW5pbmphLmluZm8ACgkQbI90rodwC35DNBAAsacnSXisKiT+mh6QWezvR1S0
bovvY7Ij8+qptsBdVkVQgKKCaEPZ+Ssqc7ulWWclvM/gVAxjIn7xciGSAGHuQAby

Bug#899766: ivtv-utils: Invalid maintainer address pkg-mythtv-maintain...@lists.alioth.debian.org

[Ian Campbell]

On Thu, 2018-05-24 at 09:27 +0100, Ian Campbell wrote:
> So I think removing ivtv-utils from Debian is probably the best
> answer.
> Unless someone from the X-Debbugs-Cc line suggests oherwise I will do
> so, lets say on or after 1 June 2018 (a bit over a week from today).

Done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900631

Ian.

Bug#900615: osmosis FTBFS Could not resolve all dependencies for configuration ':osmosis-hstore-jdbc:compileClasspath'

[Christoph Berg]

Re: Sebastiaan Couwenberg 2018-06-02 

> > Could not resolve all dependencies for configuration
> > ':osmosis-hstore-jdbc:compileClasspath'.
> >> Could not resolve com.ongres.scram:client:debian.
> >   Required by:
> >   project :osmosis-hstore-jdbc > org.postgresql:postgresql:debian
> >> No cached version of com.ongres.scram:client:debian available for
> > offline mode.
> 
> libscram-java is a transitive dependency of libpostgresql-jdbc-java, but
> the latter doesn't have a dependency on libscram-java.

Hi,

adding the dependency to libpostgresql-jdbc-java is not the correct
solution because when used as JDBC driver at runtime, where
applications load the .jar file as plugin, things just work fine.
/usr/share/java/postgresql.jar bundles the scram class.

I wonder if adding a libpostgresql-jdbc-java-dev package that depends
on libscram-java would be the correct solution, but that's out of line
with how the rest of the Java packages work.

@java-team: comments?

Christoph

Processed: raise priority

[Debian Bug Tracking System]

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

> severity 248496 grave
Bug #248496 [pacman] pacman: X Error of failed request
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#865952: marked as done (cl-fiveam: Fails to load the ASDF system)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 10:04:34 +
with message-id 
and subject line Bug#865952: fixed in cl-fiveam 1.4.1-2
has caused the Debian Bug report #865952,
regarding cl-fiveam: Fails to load the ASDF system
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.)


-- 
865952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-fiveam
Version: 1.3-1
Severity: important

Dear Maintainer,

It is impossible to load the cl-fiveam system inside lisp because
according to fiveam.asdf, it depends on `:net.didierverna.asdf-flv',
but the Debian package doesn't install it.
--- End Message ---
--- Begin Message ---
Source: cl-fiveam
Source-Version: 1.4.1-2

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated cl-fiveam 
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: Sat, 02 Jun 2018 11:44:17 +0200
Source: cl-fiveam
Binary: cl-fiveam
Architecture: source
Version: 1.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Sébastien Villemot 
Description:
 cl-fiveam  - simple regression testing framework for Common Lisp
Closes: 865952
Changes:
 cl-fiveam (1.4.1-2) unstable; urgency=medium
 .
   * Move maintenance to Debian Common Lisp Team.
 Thanks to Dimitri Fontaine for his work on this package
   * Bump to debhelper compat level 11
   * Use secure URL in Homepage field
   * Add d/watch file
   * Remove B-D on dh-lisp
   * Bump S-V to 4.1.4
   * Update Vcs-* fields for move to salsa
   * Add missing dependencies on cl-trivial-backtrace and cl-asdf-flv
 (Closes: #865952)
   * Simplify d/rules; remove useless symlinks under /u/s/common-lisp/systems
   * Use secure URLs in d/copyright
   * Expand long description
   * Add an autopkgtest that runs the testsuite on sbcl, ecl and clisp
   * Mark as M-A foreign
Checksums-Sha1:
 c58140ffd4870d79da93babbe53e20bc9ec8b16b 1991 cl-fiveam_1.4.1-2.dsc
 acb07cc67edea7aeae3a5901291abdbc082aeecd 3036 cl-fiveam_1.4.1-2.debian.tar.xz
 8a97a79a3a29e86f2fd4a0d55877ae58a226edc5 5467 cl-fiveam_1.4.1-2_amd64.buildinfo
Checksums-Sha256:
 6a5fa96654f3a54b3afb74e6f1158b677a6fcdac1b9543c451ab01a04706bdca 1991 
cl-fiveam_1.4.1-2.dsc
 efc78479885e73f892c73b32e20267812ffccd97af4863a76141d0cc51a266cd 3036 
cl-fiveam_1.4.1-2.debian.tar.xz
 afae6143b7c75854dffc4e9b6c0a112c2164b19729969fe39fce0e28183f635e 5467 
cl-fiveam_1.4.1-2_amd64.buildinfo
Files:
 8ade3930b94c4a1f30ace04e1f4372fe 1991 lisp optional cl-fiveam_1.4.1-2.dsc
 0e49b1c44e3892a445e5bd4f6c3efc15 3036 lisp optional 
cl-fiveam_1.4.1-2.debian.tar.xz
 2ee71e080020b5c4a42c3ae93ad63138 5467 lisp optional 
cl-fiveam_1.4.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlsSZ60ACgkQLOzpNQ7O
vkrrYg//cjtQcATxMps6pwgfmFAh4qzRHZ7l2XnUfgezJkKaJHJ9OxDsupBNb5qj
Cd7D+kY3c5RgP2OThR9fPqn0Oxkv0/C8YvbKygVM8GToY/tDshWFscu9XFCwUGcd
OFq6ldxtmxhzTQhdYr4yGNLDHmmFIe7qqDXKnPZOyIB2YCQ3Zspe8NA0ISJsFh4X
1yw5FwvWBiTzKEWyqIVVIFbqPDUFA8iP88Y20Ui0jEGALznGCst5I5CkRy3jh2qb
q4cW2iP2fLUV1iPO0uYal5momG1TUPWSA+qYNsfyFXwj2hGHjC/i3Zkq978jz/aJ
otvYlg29FrXNEzM4U8jEQ2KzZT6uf8vV82F8gOyTaV0vwD39BdKw6hJrq57CjQWy
CSwqz99n8v/0JiZql/OYLwdEEMp8zPMxOluw8x6eHowGuv6mSxPUPY0JCocgPU5L
PwMA806ULFx5dadjewgSh0XXrohtfgvHEh67TKgN2180vqfrUROo6R6bJ6fZqWVM
HUWIkZHvgSE1lkmnoG1fz4iGdPKlfNZs6oFiYAhdMFqO2l/vNeEDCjH0be7ViNRJ
a5uKWH5lHomR45ixJ/KhGkywzectFU2OHydLn2BFb0+Wjc95e3g8HoUQgRwHABLx
gez6Gj+QfAyFMvJjAXQdv2g9PGXHvUmha4xPGh42XQzw060WpZU=
=W3kg
-END PGP SIGNATURE End Message ---

Bug#900629: debian-edu-install: breaks installation of samba

[Holger Levsen]

Package: debian-edu-install
Version: 2.10.9
Severity: serious

Hi,

https://jenkins.debian.net/job/chroot-installation_sid_install_education-workstation/1236//console
breaks as follows:

first:

Setting up debian-edu-install (2.10.9) ...
error: /var/lib/dpkg/info/debian-edu-install.postinst: Unable to read
from /etc/debian-edu/config.
info: Loading defaults from /usr/lib/debian-edu-install/defaults.common
info: Got profile ''
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults

and then, second:

Setting up samba-common-bin (2:4.8.2+dfsg-1) ...
Checking smb.conf
WARNING: The "syslog" option is deprecated
netbios name PROFITBRICKS-BUILD10-AMD64 is not a valid netbios name
ERROR: Invalid smb.conf
dpkg: error processing package samba-common-bin (--configure):
 installed samba-common-bin package post-installation script subprocess
 returned error exit status 255


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#900591: FTBFS against R 3.5: The C compiler identification is unknown

[Juhani Numminen]

On Fri, 1 Jun 2018 21:12:06 +0200 Sébastien Villemot  
wrote:
> Package: src:rkward
> Version: 0.7.0-1
> Severity: serious
> Control: block 896667 by -1 
> 
> Dear Maintainer,
> 
> The R 3.5 transition has just started (see #896667), and consequently the
> rebuild of rkward has been triggered.
> 
> But the rebuild failed, apparently because the C compiler is not properly
> detected (I did not investigate whether this error is actually related to R 
> 3.5
> or is due to some other unrelated change):

For a build log of the failure, see the link "rbuild (41KB)" at [1].

It seems that the cmake invocation is causing trouble. Consider these forms:

1) CC='gcc -std=c99' cmake ...
2) CC='gcc -std=c99' cmake -DCMAKE_C_COMPILER='gcc -std=c99' ...

The first one is okay and CMake handles the extra -std=c99 argument properly, 
but
the second one causes "-- The C compiler identification is unknown".
This behavior is expected as CMAKE_C_COMPILER should be a full path.[6]

Debhelper[2] uses the second form when CC is set, as is done in rkward[3].
The change was introduced in [4], to fix #897083[5].
(Helmut Cc'd to notify of this unexpected breakage.)

On the other hand, maybe debian/rules of rkward needs to be changed. The comment
at [3] states that setting CC is required for "some installations of R", but is
it required in the Debian package specifically?

In this case, 'gcc -std=c99' comes from "/usr/bin/R CMD config CC".
I am also wondering why R should impose -std=c99. There exist many other 
possible
values for -std.[7]


Cheers,
Juhani


[1] 
https://tests.reproducible-buildds.org/debian/rb-pkg/unstable/armhf/rkward.html
[2] 
https://sources.debian.org/src/debhelper/11.3.2/lib/Debian/Debhelper/Buildsystem/cmake.pm/#L90
[3] https://sources.debian.org/src/rkward/0.7.0-1/debian/rules/#L25
[4] 
https://salsa.debian.org/debian/debhelper/commit/a5eb0dc3c3a16d12c7a26ac42b93a35b931188d3
[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897083
[6] https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_COMPILER.html
[7] https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html

Processed: found 900623 in 0.2.6-1

[Debian Bug Tracking System]

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

> found 900623 0.2.6-1
Bug #900623 [cl-interpol] missing dependency on cl-unicode
Marked as found in versions cl-interpol/0.2.6-1.
> thanks
Stopping processing here.

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

Processed: found 900622 in 0.1.5-3

[Debian Bug Tracking System]

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

> found 900622 0.1.5-3
Bug #900622 [cl-unicode] missing dependency on cl-ppcre
Marked as found in versions cl-unicode/0.1.5-3.
> thanks
Stopping processing here.

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

Bug#900155: marked as done (cl-csv fails to load, missing parser.lisp)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 08:49:28 +
with message-id 
and subject line Bug#900155: fixed in cl-csv 20180228-2
has caused the Debian Bug report #900155,
regarding cl-csv fails to load, missing parser.lisp
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.)


-- 
900155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-csv
Version: 20180228-1
Severity: grave

cl-csv is unusable. Trying to load it fails with:

  Failed to find the TRUENAME of 
/usr/share/common-lisp/source/cl-csv/parser.lisp:
No such file or directory

Obviously parser.lisp is missing in the package.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cl-csv
Source-Version: 20180228-2

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated cl-csv 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: Sat, 02 Jun 2018 10:35:38 +0200
Source: cl-csv
Binary: cl-csv
Architecture: source
Version: 20180228-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Sébastien Villemot 
Description:
 cl-csv - Common Lisp library providing easy CSV reading and writing
Closes: 900155
Changes:
 cl-csv (20180228-2) unstable; urgency=medium
 .
   * Move maintenance to Debian Common Lisp Team.
 Thanks to Dimitri Fontaine for his work on this package
   * Add missing parser.lisp inside cl-csv (Closes: #900155)
   * Merge cl-csv-clsql and cl-csv-data-table into cl-csv
   * Drop symlinks to *.asd in /u/s/common-lisp/systems/
   * Bump to debhelper compat level 11
   * Remove B-D on dh-lisp
   * Update Vcs-* fields for move to salsa
   * Create d/watch which tracks upstream git HEAD
   * Use secure URL in Format field of d/copyright
   * Bump to S-V 4.1.4
   * Rewrite package long description
   * Add autopkgtest that loads the main system with ASDF in sbcl, ecl and
 clisp. Can't yet run the testsuite nor load the auxiliary systems
 because of missing dependencies
Checksums-Sha1:
 2b660db95cf7403ce81269e47b2e971ff34df1d8 1981 cl-csv_20180228-2.dsc
 07744e789defbbe1b5a5cfe045429b5a978ac580 3296 cl-csv_20180228-2.debian.tar.xz
 d8f51cbbcc283028de0cee219af339869d940d18 5461 cl-csv_20180228-2_amd64.buildinfo
Checksums-Sha256:
 98d914f49630b6cd8c0fa1b4f20e63dae732b4d68ed3104ec41956deddac33d2 1981 
cl-csv_20180228-2.dsc
 7759ab6fd0522ee6c0051a07f30a965fc439619e5e7458ab2743e09766fa5e1f 3296 
cl-csv_20180228-2.debian.tar.xz
 68b6d9f3731d3b2dfeb3c749894d857398cd753dbef7ac57cf75b855f76374f7 5461 
cl-csv_20180228-2_amd64.buildinfo
Files:
 9388677fd282a01786aec1ca3d8442ad 1981 lisp optional cl-csv_20180228-2.dsc
 2a12b56e096ac7771ee144ca7177381b 3296 lisp optional 
cl-csv_20180228-2.debian.tar.xz
 29a5ded6880710dd049ebb605a02e673 5461 lisp optional 
cl-csv_20180228-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlsSV8IACgkQLOzpNQ7O
vkrd7A//VVKdT1o649PcSHHB6KE6/xRsWov3ZjF9FjC1XMNHJQ8Op+Qik1W4qV8l
S+H3h+0lG0rkkQsJ5LCKQfExuClAseoTtJUxX1i4hWWU5uijBsnayK/u15jZNBu7
4HuQPrlKH4VvyZEpVaCKZWDebHvr/GkpH8XgZCPZVetUdxamslznvk+LT9K7twp4
WPUMLWB0BCufWLWQxmBTfCiiIXZnvraxfcK1R2iRTUwB8w+4ulKl0hgfYE0vUmJA
/lSK2d0l4rgl7TWMAAZM1kA0VkD8ZlJP+Agj6C5x7tHqrdjLZczhAEl1gHOi9f6V
l4R/fu33G0Aqkfk9+HgOH+EDVKOR9o0JaSkVQmve/2Z/WrwEH9j9PU1TO2MLyBcZ
3Fpqt3hmZ+Imw0id012Zv/aawu/vEgCq51izQvp604inwt7DMf/cVGsO3+C+dMDR
x7BOiuSJXhvy6kBpgQ3TcbPKkSWJ13GOxIzYZ/gMv0PYodn1P3yZC9h4FX3ln4KH
FUWSqmJm7ofRQQHEPNvfwnLM7I598Zpa31mNJKcu7SNjnu1vUPGb3WkO4iWnnzhp
lzK1JjjnSZKuhDdVl9Cjhmjai37aK99653t67sgLSDILQ83H36AzUnFe81GJy0sY
W1/e6HwMFiUh8kKwTRhdeSJL1k0qRLe+Rs+KFvwY+BjWVg2EVgM=
=mQx8
-END PGP SIGNATURE End Message ---

Bug#900623: missing dependency on cl-unicode

[Sébastien Villemot]

Package: cl-interpol
Version: 20171227-1
Severity: serious
Control: affects -1 cl-csv

Loading of cl-interpol fails if cl-unicode is not installed on the system; it
should be added as a dependency.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Processed: missing dependency on cl-unicode

[Debian Bug Tracking System]

Processing control commands:

> affects -1 cl-csv
Bug #900623 [cl-interpol] missing dependency on cl-unicode
Added indication that 900623 affects cl-csv

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

Bug#900622: missing dependency on cl-ppcre

[Sébastien Villemot]

Package: cl-unicode
Version: 20180328-1
Severity: serious
Control: affects -1 cl-unicode cl-csv

Loading of cl-unicode fails if cl-ppcre is not installed on the system; it
should be added as a dependency.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Processed: missing dependency on cl-ppcre

[Debian Bug Tracking System]

Processing control commands:

> affects -1 cl-unicode cl-csv
Bug #900622 [cl-unicode] missing dependency on cl-ppcre
Added indication that 900622 affects cl-unicode and cl-csv

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

Bug#900618: tseries: unsatisfiable versioned dependency on quantmod (>= 0.4.9)

[Graham Inggs]

Source: tseries
Version: 0.10-44-1
Severity: serious
Tags: patch
X-Debbugs-CC: r-pkg-t...@alioth-lists.debian.net

Hi Dirk

Due to some new magic in dh-r, r-cran-tseries gains a versioned
dependency on quantmod (>= 0.4.9), but we have 0.4-13-1 in the archive
and this makes r-cran-tseries not installable.

My guess is this was a typo upstream, and they meant 0.4-9 instead of 0.4.9.

Please consider including my patch, attached.

Regards
Graham
Description: Fix unsatisfiable versioned dependency on quantmod
Author: Graham Inggs 
Last-Update: 2018-06-02

--- a/DESCRIPTION
+++ b/DESCRIPTION
@@ -9,7 +9,7 @@
 comment = "BDS test code"))
 Description: Time series analysis and computational finance.
 Depends: R (>= 2.10.0)
-Imports: graphics, stats, utils, quadprog, zoo, quantmod (>= 0.4.9)
+Imports: graphics, stats, utils, quadprog, zoo, quantmod (>= 0.4-9)
 License: GPL-2
 NeedsCompilation: yes
 Packaged: 2018-04-15 15:14:39 UTC; hornik

Bug#831548: [Pkg-javascript-devel] RM: mtasc -- ROM; obsoleted by newer standard web technologies

[Bastien ROUCARIES]

Le sam. 2 juin 2018 à 08:59, Niels Thykier  a écrit :

> On Sat, 23 Dec 2017 06:58:52 +0800 Paul Wise  wrote:
> > Control: severity -1 serious
> > Control: severity 831553 normal
> >
> > Hi everyone,
> >
> > The buster cycle is the right time to remove mtasc from the Debian
> > archive. It has been unmaintained in Debian and upstream for years. The
> > web ecosystem is moving away from Flash towards standard web tech,
> > which can now replace most use of Flash. Debian should encourage our
> > upstreams to move towards standard web tech like HTML5 and JavaScript.
> >
> > Please talk to your upstreams about transitioning away from
> > ActionScript 2 towards HTML5 JavaScript. If they need to still
> > support Flash for some users, then they should switch to something
> > like Haxe but they should not build Flash files by default.
> >
> > On Fri, 22 Dec 2017 17:29:50 -0500 Scott Kitterman wrote:
> >
> > > 15 months later all but one of those bugs is still open.  Can you
> either work
> > > with the maintainers to get them done or close this request until it's
> ripe
> > > for processing.
> >
> > --
> > bye,
> > pabs
> >
> > https://wiki.debian.org/PaulWise
>
> Hi,
>
> This package (dojo) is officially maintained by the Javascript team but
> appears to be de facto unmaintained.  It has several RC bugs and is
> stalling the removal of obsolete packages (admittedly only from unstable).
>
> If you are still interested in maintaining the package, then please
> resolve the RC bugs (at the very least this bug, which is blocking
> others).  If there is no visible progress on resolving this bug in a
> month from now, I will assume you are no longer interested in it and
> that you will support a removal of dojo from unstable.
>
> I have explicitly included all listed maintainers and uploaders (except
> for Frank, which appears to have disclaimed interest in this package per
> #863693)
>
> Thanks,
> ~Niels
>

Will get a glimpse.

BTw it means that a few lintian warning are now fatal because ftbfs...

Bastien

>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Processed: Re: Bug#900615: osmosis FTBFS Could not resolve all dependencies for configuration ':osmosis-hstore-jdbc:compileClasspath'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:libpgjava
Bug #900615 [osmosis] osmosis FTBFS Could not resolve all dependencies for 
configuration ':osmosis-hstore-jdbc:compileClasspath'
Bug reassigned from package 'osmosis' to 'src:libpgjava'.
No longer marked as found in versions osmosis/0.46-3.
Ignoring request to alter fixed versions of bug #900615 to the same values 
previously set
> found -1 libpgjava/42.2.2-2
Bug #900615 [src:libpgjava] osmosis FTBFS Could not resolve all dependencies 
for configuration ':osmosis-hstore-jdbc:compileClasspath'
Marked as found in versions libpgjava/42.2.2-2.
> retitle -1 libpostgresql-jdbc-java: no Depends on libscram-java
Bug #900615 [src:libpgjava] osmosis FTBFS Could not resolve all dependencies 
for configuration ':osmosis-hstore-jdbc:compileClasspath'
Changed Bug title to 'libpostgresql-jdbc-java: no Depends on libscram-java' 
from 'osmosis FTBFS Could not resolve all dependencies for configuration 
':osmosis-hstore-jdbc:compileClasspath''.
> affects -1 src:osmosis
Bug #900615 [src:libpgjava] libpostgresql-jdbc-java: no Depends on libscram-java
Added indication that 900615 affects src:osmosis
> tags -1 patch
Bug #900615 [src:libpgjava] libpostgresql-jdbc-java: no Depends on libscram-java
Added tag(s) patch.

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

Bug#900608: marked as done (nikto: CVE-2018-11652)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jun 2018 06:49:23 +
with message-id 
and subject line Bug#900608: fixed in nikto 1:2.1.5-3
has caused the Debian Bug report #900608,
regarding nikto: CVE-2018-11652
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.)


-- 
900608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nikto
Version: 1:2.1.5-1
Severity: grave
Tags: patch security upstream fixed-upstream
Justification: user security hole

Hi,

The following vulnerability was published for nikto.

CVE-2018-11652[0]:
| CSV Injection vulnerability in Nikto 2.1.6 and earlier allows remote
| attackers to inject arbitrary OS commands via the Server field in an
| HTTP response header, which is directly injected into a CSV report.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-11652
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11652
[1] 
https://github.com/sullo/nikto/commit/e759b3300aace5314fe3d30800c8bd83c81c29f7

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: nikto
Source-Version: 1:2.1.5-3

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

Debian distribution maintenance software
pp.
Vincent Bernat  (supplier of updated nikto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Jun 2018 08:07:33 +0200
Source: nikto
Binary: nikto
Architecture: source
Version: 1:2.1.5-3
Distribution: unstable
Urgency: high
Maintainer: Vincent Bernat 
Changed-By: Vincent Bernat 
Description:
 nikto  - web server security scanner
Closes: 900608
Changes:
 nikto (1:2.1.5-3) unstable; urgency=high
 .
   * d/control: point Vcs-* to salsa.debian.org.
   * d/patches: fix CSV injection vulnerability. CVE-2018-11652.
 Closes: #900608.
Checksums-Sha1:
 8884037995ecfa0e3a484e397e6213b7201f4207 1802 nikto_2.1.5-3.dsc
 c8f58f77726397e4fafbc482340b1377d0c4aee6 6872 nikto_2.1.5-3.debian.tar.xz
 b4662a49219d7370a09226af3cb150ce9c5f111c 5606 nikto_2.1.5-3_amd64.buildinfo
Checksums-Sha256:
 5105eb13f6e2b18f67719051c8f409daf69893d98d800a9d831114bb32fe1bf5 1802 
nikto_2.1.5-3.dsc
 dcb94f8c24ca4119f0810177ce29a647dc92c0ea235ef67cabc30c314a7d26b4 6872 
nikto_2.1.5-3.debian.tar.xz
 d5da87f98c75b7d59c7b41f9e85d36ca2771956fb8b26e933fc03b6ff5ee7d68 5606 
nikto_2.1.5-3_amd64.buildinfo
Files:
 b9edd7db4294222579b60d37c1e0f70d 1802 non-free/net extra nikto_2.1.5-3.dsc
 1d7573b08fa3d836bfcc50c3348701fe 6872 non-free/net extra 
nikto_2.1.5-3.debian.tar.xz
 7b62ccf705e93198db33c06a171a1d42 5606 non-free/net extra 
nikto_2.1.5-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAlsSOdwSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5+NEP/Rkwplm677cs2wFJp12gtwa3Wo1AbE2o
8TKigebitm4sTku/GjbaP94vLtuHoa3YXm+guYKU28rN1UaAyOijufPES25Tpapa
0ue6pmhJZG6jbEh+gbPk3oDiC5IubBFQNSxsvLAfx+f8TKsT7LL96uYvaBGfIkfm
mvDOl79xW4i6nebP1rhq/0TnQybJ2ud3LoywLMa4AaWhojITeH1pxGc+4lPWsUJA
giB/nXzJTHMcNQm7nKbz0d0cZNcaWn6H6suUhnjwHXxR3AN1Icux0LwtJef1Lc11
nhJSZn8DgWwddsRe8/OQ0MvauR/gZjzOY6EZw+MJHkoGGDyl+5Seqo01UQLitgVj
TolaaU/i+b4TGHqmU95cM/4nn2vhS+eJPM96bq/LOT2p915CtpAohCx4Oa43Dbqb
WwNAdTBQW8AsC5uwPKmyjhh5LQoIf80cLOKnJEIniop1Lzrmkrhx+2wm5tTZsFD6
cnGRv6W+Wl9AR4wHc977H+EetB2W3sF8YgbbFcW/fIo61P5M0lQsOiIsyAchxeM+
xl8tuSpqFBM/cVyAC+zlvFRvCHihJJ/uwdWWaWxVFQWnxD6vewS/x/qMEMvkkykQ
KL2HFHH83XJh6RDoDFmWTz8nsIMXUls3rlkQc0pUOhLdkluhNtScHLgisgwrKPIM
gf0bOUo1nPR8
=/KnC
-END PGP SIGNATURE End Message ---

Bug#900615: osmosis FTBFS Could not resolve all dependencies for configuration ':osmosis-hstore-jdbc:compileClasspath'

[Sebastiaan Couwenberg]

Control: reassign -1 src:libpgjava
Control: found -1 libpgjava/42.2.2-2
Control: retitle -1 libpostgresql-jdbc-java: no Depends on libscram-java
Control: affects -1 src:osmosis
Control: tags -1 patch

On 06/02/2018 08:25 AM, Pirate Praveen wrote:
> * What went wrong:
> Could not resolve all dependencies for configuration
> ':osmosis-hstore-jdbc:compileClasspath'.
>> Could not resolve com.ongres.scram:client:debian.
>   Required by:
>   project :osmosis-hstore-jdbc > org.postgresql:postgresql:debian
>> No cached version of com.ongres.scram:client:debian available for
> offline mode.

libscram-java is a transitive dependency of libpostgresql-jdbc-java, but
the latter doesn't have a dependency on libscram-java.

The attached patch fixes the issue.

Kind Regards,

Bas

From e80ef0cefee18b820ff6ed1325e0e3d8ac800f0c Mon Sep 17 00:00:00 2001
From: Bas Couwenberg 
Date: Sat, 2 Jun 2018 08:48:04 +0200
Subject: Add libscram-java to libpostgresql-jdbc-java dependencies.

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index b8fd4fca..da51057c 100644
--- a/debian/control
+++ b/debian/control
@@ -29,7 +29,7 @@ Homepage: https://jdbc.postgresql.org/
 Package: libpostgresql-jdbc-java
 Architecture: all
 Multi-Arch: foreign
-Depends: ${maven:Depends}, ${misc:Depends}
+Depends: libscram-java, ${maven:Depends}, ${misc:Depends}
 Recommends: ${maven:OptionalDepends}
 Conflicts: libpgjava (<= 7.4.7-3), libpg-java (<= 9.1-901-1)
 Provides: libpgjava, libpg-java
-- 
2.11.0



signature.asc
Description: OpenPGP digital signature

Bug#900615: osmosis FTBFS Could not resolve all dependencies for configuration ':osmosis-hstore-jdbc:compileClasspath'

[Pirate Praveen]

package: osmosis
version: 0.46-3
severity: serious

While building with protobuf 3.5.2 from experimental, this build failed,
but I think this is unrelated to protobuf change.

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all dependencies for configuration
':osmosis-hstore-jdbc:compileClasspath'.
> Could not resolve com.ongres.scram:client:debian.
  Required by:
  project :osmosis-hstore-jdbc > org.postgresql:postgresql:debian
   > No cached version of com.ongres.scram:client:debian available for
offline mode.

* Try:
Run with --debug option to get more log output.

* Exception is:
org.gradle.api.artifacts.ResolveException: Could not resolve all
dependencies for configuration ':osmosis-hstore-jdbc:compileClasspath'.
at
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration.rethrowFailure(DefaultLenientConfiguration.java:178)
at
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$1.collectFiles(DefaultLenientConfiguration.java:127)
at
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.doGetFiles(DefaultConfiguration.java:516)
at
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.getFiles(DefaultConfiguration.java:367)
at
org.gradle.api.internal.artifacts.configurations.DefaultConfiguration_Decorated.getFiles(Unknown
Source)
at
org.gradle.api.internal.file.AbstractFileCollection.iterator(AbstractFileCollection.java:68)
at
org.gradle.api.internal.changedetection.state.AbstractFileCollectionSnapshotter$FileCollectionVisitorImpl.visitCollection(AbstractFileCollectionSnapshotter.java:133)
at
org.gradle.api.internal.file.AbstractFileCollection.visitRootElements(AbstractFileCollection.java:234)
at
org.gradle.api.internal.file.CompositeFileCollection.visitRootElements(CompositeFileCollection.java:185)
at
org.gradle.api.internal.changedetection.state.AbstractFileCollectionSnapshotter.snapshot(AbstractFileCollectionSnapshotter.java:71)
at
org.gradle.api.internal.changedetection.rules.AbstractNamedFileSnapshotTaskStateChanges.buildSnapshots(AbstractNamedFileSnapshotTaskStateChanges.java:87)
at
org.gradle.api.internal.changedetection.rules.AbstractNamedFileSnapshotTaskStateChanges.(AbstractNamedFileSnapshotTaskStateChanges.java:54)
at
org.gradle.api.internal.changedetection.rules.InputFilesTaskStateChanges.(InputFilesTaskStateChanges.java:28)
at
org.gradle.api.internal.changedetection.rules.TaskUpToDateState.(TaskUpToDateState.java:55)
at
org.gradle.api.internal.changedetection.changes.DefaultTaskArtifactStateRepository$TaskArtifactStateImpl.getStates(DefaultTaskArtifactStateRepository.java:164)
at
org.gradle.api.internal.changedetection.changes.DefaultTaskArtifactStateRepository$TaskArtifactStateImpl.isUpToDate(DefaultTaskArtifactStateRepository.java:79)
at
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:51)
at
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
at
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:46)
at
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)
at
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.execute(DefaultTaskGraphExecuter.java:236)
at
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.execute(DefaultTaskGraphExecuter.java:228)
at org.gradle.internal.Transformers$4.transform(Transformers.java:169)
at
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106)
at
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:61)
at
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:228)
at
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:215)
at
org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:77)
at