Bug#883993: horizon: [INTL:ru] Updated Russian translation of debconf template

[Lev Lamberov]

Package: horizon
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached the updated Russian debconf translation for horizon.

Regards,
Lev Lamberov


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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the horizon package.
#
# Yuri Kozlov , 2013.
# Lev Lamberov , 2017.
msgid ""
msgstr ""
"Project-Id-Version: horizon 2013.1.3-2\n"
"Report-Msgid-Bugs-To: hori...@packages.debian.org\n"
"POT-Creation-Date: 2017-11-15 21:55+\n"
"PO-Revision-Date: 2017-12-10 11:46+0500\n"
"Last-Translator: Lev Lamberov \n"
"Language-Team: Russian \n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
"X-Generator: Poedit 2.0.4\n"

#. Type: boolean
#. Description
#: ../openstack-dashboard-apache.templates:2001
msgid "Activate Dashboard and disable default VirtualHost?"
msgstr "Активировать Dashboard и отключить VirtualHost по умолчанию?"

#. Type: boolean
#. Description
#: ../openstack-dashboard-apache.templates:2001
msgid ""
"The Apache package sets up a default web site and a default page, configured "
"in /etc/apache2/sites-available/default."
msgstr ""
"В пакете Apache веб-сайт и страница по умолчанию уже настроены в /etc/"
"apache2/sites-available/default."

#. Type: boolean
#. Description
#: ../openstack-dashboard-apache.templates:2001
msgid ""
"If this option is not selected, Horizon will be installed using /horizon "
"instead of the webroot."
msgstr ""
"Если эта опция не выбрана, то Horizon будет установлен в каталог /horizon, а "
"не в каталог с веб-сайтами."

#. Type: boolean
#. Description
#: ../openstack-dashboard-apache.templates:2001
msgid ""
"Choose this option to replace that default with the OpenStack Dashboard "
"configuration."
msgstr ""
"Выберите, нужно ли заменить настройку по умолчанию на настройку из Openstack "
"Dashboard."

#. Type: boolean
#. Description
#: ../openstack-dashboard-apache.templates:3001
msgid "Should the Dashboard use HTTPS?"
msgstr "Использовать HTTPS в Dashboard?"

#. Type: boolean
#. Description
#: ../openstack-dashboard-apache.templates:3001
msgid ""
"Select this option if you would like Horizon to be served over HTTPS only, "
"with a redirection to HTTPS if HTTP is in use."
msgstr ""
"Выберите, нужно ли включить доступ к Horizon только по HTTPS, с "
"перенаправлением на HTTPS в случае использования HTTP."

#. Type: string
#. Description
#: ../openstack-dashboard.templates:2001
msgid "Allowed hostname(s)"
msgstr "Разрешённые имена узлов"

#. Type: string
#. Description
#: ../openstack-dashboard.templates:2001
msgid ""
"Please enter the list of hostnames that can be used to reach your OpenStack "
"Dashboard server. This is a security measure to prevent HTTP Host header "
"attacks, which are possible even under many seemingly-safe web server "
"configurations."
msgstr ""
"Введите список имён узлов, которые могут использоваться для обращения к "
"вашему серверу OpenStack Dashboard. Это требование безопасности, чтобы "
"предотвратить атаки по HTTP-заголовку Host, которые возможны даже при "
"использовании многих кажущихся безопасными настроек веб-сервера."

#. Type: string
#. Description
#: ../openstack-dashboard.templates:2001
msgid ""
"Enter values separated by commas. Any space will be removed, so you can add "
"some to make it more readable."
msgstr ""
"Введите значения, разделяя их запятыми. Пробелы будут удалены, поэтому вы "
"можете их добавить для лучшей читаемости."

#. Type: string
#. Description
#: ../openstack-dashboard.templates:2001
msgid ""
"Values in this list can be fully qualified names like \"www.example.com\", "
"in which case they will be matched against the request's Host header exactly "
"(case-insensitive, not including port). A value beginning with a period can "
"be used as a subdomain wildcard: \".example.com\" will match example.com, "
"www.example.com, and any other subdomain of example.com. A value of \"*\" "
"will match anything; in this case you are responsible for providing your own "
"validation of the Host header (perhaps in middleware; if so this middleware "
"must be listed first in MIDDLEWARE)."
msgstr ""
"Значения в этом списке являются полными именами, например, «www.example."
"com», в этом случае они будут соответствовать заголовку Host того, кто "
"передал запрос (они 

Bug#883992: install to harddrive, ignore connected usb, reboot with preseeded grub

[Raymond Burkholder]

Package: grub-installer
Version: 1.140+deb9u1

Is there a magic incantation for preseed files to install to a harddrive
when usb is present?

There are two stages:  usb appears as /dev/sda during install process, but
appears as something else, maybe /dev/sdd during normal boot

Therefore, the target drive might be /dev/sdb during install, but shows as
/dev/sda during normal boot.

My almost working preseed file has:


# install to /dev/sdb (main harddrive), when usb shows as /dev/sda
# these two lines are correct and working for the install process
d-ipartman-auto/select_diskselect  /dev/sdb
d-i partman-auto/disk   string  /deb/sdb

# grub 
# the first value is correct to install grub
d-i  grub-installer/bootdev  string /dev/sdb

# a couple of items I've seen both true and false, but do not seem to affect
the outcome:
d-i grub-installer/only_debian boolean false
d-i grub-installer/with_other_os boolean false

# I am not sure how to get these values to work properly, or maybe I am
missing something
d-i grub-installer/choose_bootdev   select  /dev/sda2
d-i grub-pc/install_devices multiselect /dev/sda2

=

The final boot should be /dev/sda2, but /boot/grub/grub.cfg seems to take on
/dev/sdb2.

The important piece here:  HOW does one get /dev/sda2 (instead of /dev/sdb2)
into /boot/grub/grub.cfg?


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Bug#883991: colplot: [INTL:ru] Updated Russian translation of debconf template

[Lev Lamberov]

Package: colplot
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached the updated Russian debconf translation for colplot.

Regards,
Lev Lamberov


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

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

Versions of packages colplot depends on:
pn  collectl  
ii  debconf [debconf-2.0] 1.5.65
pn  gnuplot   
pn  libgetopt-simple-perl 
ii  perl  5.26.1-3
ii  perl-base [libio-socket-ip-perl]  5.26.1-3
pn  perl-tk   
ii  ucf   3.0036

Versions of packages colplot recommends:
pn  apache2 | lighttpd | nginx | httpd  

Versions of packages colplot suggests:
pn  apache2  
# translation of ru.po to Russian
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the colplot package.
#
# Yuri Kozlov , 2009, 2011, 2012.
# Lev Lamberov , 2017.
msgid ""
msgstr ""
"Project-Id-Version: colplot 0.8.7g-3\n"
"Report-Msgid-Bugs-To: colp...@packages.debian.org\n"
"POT-Creation-Date: 2016-02-11 11:28-0700\n"
"PO-Revision-Date: 2017-12-10 11:32+0500\n"
"Last-Translator: Lev Lamberov \n"
"Language-Team: Russian \n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.0.4\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"

#. Type: select
#. Choices
#: ../colplot.templates:2001
#| msgid "Apache2"
msgid "apache2"
msgstr "apache2"

#. Type: select
#. Choices
#: ../colplot.templates:2001
msgid "lighttpd"
msgstr "lighttpd"

#. Type: select
#. Choices
#: ../colplot.templates:2001
msgid "None"
msgstr "не настраивать"

#. Type: select
#. Description
#: ../colplot.templates:2002
msgid "Web server:"
msgstr "Веб-сервер:"

#. Type: select
#. Description
#: ../colplot.templates:2002
msgid ""
"Please select the web server for which Colplot should be automatically "
"configured."
msgstr ""
"Выберите веб-сервер, для которого нужно автоматически настроить Сolplot."

#. Type: select
#. Description
#: ../colplot.templates:2002
msgid "Select \"None\" if you would like to configure the web server manually."
msgstr "Выберите «не настраивать», если хотите настроить веб-сервер вручную."

#~ msgid "Which kind of web server should be used by colplot?"
#~ msgstr "Тип используемого colplot веб-сервера"

#~ msgid "Apache, Apache-SSL, Apache2, All, None"
#~ msgstr "Apache, Apache-SSL, Apache2, все, ни одного"

Bug#883990: wdm: [INTL:ru] Updated Russian translation of debconf template

[Lev Lamberov]

Package: wdm
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached the updated Russian debconf translation for wdm.

Regards,
Lev Lamberov


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

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

Versions of packages wdm depends on:
ii  debconf [debconf-2.0]   1.5.65
ii  libc6   2.25-3
ii  libpam-modules  1.1.8-3.6
ii  libpam-runtime  1.1.8-3.6
ii  libpam0g1.1.8-3.6
ii  libselinux1 2.7-2
pn  libwings3   
pn  libwraster6 
pn  libwutil5   
ii  libx11-62:1.6.4-3
ii  libxau6 1:1.0.8-1+b2
ii  libxdmcp6   1:1.1.2-3
ii  libxinerama12:1.1.3-1+b3
ii  libxmu6 2:1.1.2-2
ii  lsb-base9.20170808
ii  psmisc  23.1-1
ii  x11-apps7.7+6+b1
ii  x11-common  1:7.7+19
ii  x11-utils   7.7+3+b1
ii  x11-xserver-utils   7.7+7+b1
ii  xserver-xorg [xserver]  1:7.7+19

wdm recommends no packages.

Versions of packages wdm suggests:
ii  xfonts-base  1:1.0.4+nmu1
# translation of ru.po to Russian
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Yuri Kozlov , 2009.
# Lev Lamberov , 2017.
msgid ""
msgstr ""
"Project-Id-Version: wdm 1.28-3.1\n"
"Report-Msgid-Bugs-To: w...@packages.debian.org\n"
"POT-Creation-Date: 2017-10-08 21:22+0200\n"
"PO-Revision-Date: 2017-12-10 11:29+0500\n"
"Last-Translator: Lev Lamberov \n"
"Language-Team: Russian \n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.0.4\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"

#. Type: select
#. Description
#: ../templates:1001
msgid "Desired default display manager."
msgstr "Желаемый менеджер дисплея по умолчанию."

#. Type: select
#. Description
#: ../templates:1001
msgid ""
"A display manager is a program that provides graphical login capabilities "
"for the X Window System."
msgstr ""
"Менеджер дисплея – это программа, предоставляющая возможность графического "
"входа в X Window System."

#. Type: select
#. Description
#: ../templates:1001
msgid ""
"Only one display manager can manage a given X server, but multiple display "
"manager packages are installed.  Please select which display manager should "
"run by default."
msgstr ""
"Только один менеджер дисплея может управлять заданным X-сервером, но в "
"системе может быть установлено сразу несколько пакетов менеджеров дисплея. "
"Выберите, какой менеджер дисплея должен запускаться по умолчанию."

#. Type: select
#. Description
#: ../templates:1001
msgid ""
"(Multiple display managers can run simultaneously if they are configured to "
"manage different servers; to achieve this, configure the display managers "
"accordingly, edit each of their init scripts in /etc/init.d, and disable the "
"check for a default display manager.)"
msgstr ""
"(Несколько менеджеров дисплея могут работать одновременно, если они "
"обслуживают разные серверы; для этого выполняется соответствующая настройка "
"менеджеров дисплея посредством редактирования их сценариев инициализации в /"
"etc/init.d, и выключения проверки менеджера дисплея по умолчанию.)"

Bug#794295: lintian: please complain about development packages that make cross building impossible

[Helmut Grohne]

Hi Chris,

TL;DR: I suggest ignoring Multi-Arch: foreign packages for the purpose of
this tag to remove false positives.

Explanation:

On Sat, Dec 09, 2017 at 10:44:26PM +, Chris Lamb wrote:
> I've implemented this in Git:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=fc226826c81a5642779e422d927aa334e2ff1587
> 
> I hope it's useful :)

Thank you!

In the mean time, I gained a bit more experience with these issues and
wonder whether there should be an additional restriction:

some libraries are header-only or split their tools into separate
Multi-Arch: foreign packages.  A quick grep-dctrl -F Section libdevel -a
-F Multi-Arch foreign -sPackage -n suggests that this is true for 130
packages. Now the question is: How many of these ship ELF executables?
Hard to answer, but the following ship some (not necessarily ELF)
executables:

libkf5akonadi-dev: /usr/bin/akonadi2xml
libkf5akonadi-dev: /usr/bin/akonaditest
libkf5akonadi-dev-bin: /usr/bin/akonadi_knut_resource
libboost1.61-tools-dev: /usr/bin/b2
libboost1.61-tools-dev: /usr/bin/bcp
libboost1.61-tools-dev: /usr/bin/bjam
libboost1.61-tools-dev: /usr/bin/inspect
libboost1.61-tools-dev: /usr/bin/quickbook
libboost1.62-tools-dev: /usr/bin/b2
libboost1.62-tools-dev: /usr/bin/bcp
libboost1.62-tools-dev: /usr/bin/bjam
libboost1.62-tools-dev: /usr/bin/inspect
libboost1.62-tools-dev: /usr/bin/quickbook
libboost1.63-tools-dev: /usr/bin/b2
libboost1.63-tools-dev: /usr/bin/bcp
libboost1.63-tools-dev: /usr/bin/bjam
libboost1.63-tools-dev: /usr/bin/inspect
libboost1.63-tools-dev: /usr/bin/quickbook
libglib2.0-dev-bin: /usr/bin/gdbus-codegen
libglib2.0-dev-bin: /usr/bin/glib-genmarshal
libglib2.0-dev-bin: /usr/bin/glib-gettextize
libglib2.0-dev-bin: /usr/bin/glib-mkenums
libglib2.0-dev-bin: /usr/bin/gobject-query
libglib2.0-dev-bin: /usr/bin/gtester
libglib2.0-dev-bin: /usr/bin/gtester-report
libc-dev-bin: /usr/bin/gencat
libc-dev-bin: /usr/bin/mtrace
libc-dev-bin: /usr/bin/rpcgen
libc-dev-bin: /usr/bin/sotruss
libc-dev-bin: /usr/bin/sprof
icu-devtools: /usr/bin/derb
icu-devtools: /usr/bin/genbrk
icu-devtools: /usr/bin/gencfu
icu-devtools: /usr/bin/gencnval
icu-devtools: /usr/bin/gendict
icu-devtools: /usr/bin/genrb
icu-devtools: /usr/bin/icuinfo
icu-devtools: /usr/bin/makeconv
icu-devtools: /usr/bin/pkgdata
icu-devtools: /usr/bin/uconv
icu-devtools: /usr/sbin/escapesrc
icu-devtools: /usr/sbin/genccode
icu-devtools: /usr/sbin/gencmn
icu-devtools: /usr/sbin/gennorm2
icu-devtools: /usr/sbin/gensprep
icu-devtools: /usr/sbin/icupkg
libkf5coreaddons-bin-dev: /usr/bin/desktoptojson
lib3ds-dev: /usr/bin/3dsdump
libmikmod-config: /usr/bin/libmikmod-config
libpng-tools: /usr/bin/png-fix-itxt
libpng-tools: /usr/bin/pngfix
libvncserver-config: /usr/bin/libvncserver-config
qtchooser: /usr/bin/assistant
qtchooser: /usr/bin/designer
qtchooser: /usr/bin/lconvert
qtchooser: /usr/bin/linguist
qtchooser: /usr/bin/lrelease
qtchooser: /usr/bin/lupdate
qtchooser: /usr/bin/moc
qtchooser: /usr/bin/pixeltool
qtchooser: /usr/bin/qcollectiongenerator
qtchooser: /usr/bin/qdbus
qtchooser: /usr/bin/qdbuscpp2xml
qtchooser: /usr/bin/qdbusviewer
qtchooser: /usr/bin/qdbusxml2cpp
qtchooser: /usr/bin/qdoc
qtchooser: /usr/bin/qdoc3
qtchooser: /usr/bin/qgltf
qtchooser: /usr/bin/qhelpconverter
qtchooser: /usr/bin/qhelpgenerator
qtchooser: /usr/bin/qlalr
qtchooser: /usr/bin/qmake
qtchooser: /usr/bin/qml
qtchooser: /usr/bin/qml1plugindump
qtchooser: /usr/bin/qmlbundle
qtchooser: /usr/bin/qmlcachegen
qtchooser: /usr/bin/qmleasing
qtchooser: /usr/bin/qmlimportscanner
qtchooser: /usr/bin/qmljs
qtchooser: /usr/bin/qmllint
qtchooser: /usr/bin/qmlmin
qtchooser: /usr/bin/qmlplugindump
qtchooser: /usr/bin/qmlprofiler
qtchooser: /usr/bin/qmlscene
qtchooser: /usr/bin/qmltestrunner
qtchooser: /usr/bin/qmlviewer
qtchooser: /usr/bin/qtchooser
qtchooser: /usr/bin/qtconfig
qtchooser: /usr/bin/qtdiag
qtchooser: /usr/bin/qtpaths
qtchooser: /usr/bin/qtplugininfo
qtchooser: /usr/bin/qvkgen
qtchooser: /usr/bin/rcc
qtchooser: /usr/bin/repc
qtchooser: /usr/bin/uic
qtchooser: /usr/bin/uic3
qtchooser: /usr/bin/xmlpatterns
qtchooser: /usr/bin/xmlpatternsvalidator
libsimage-dev: /usr/bin/simage-config
libkf5sonnet-dev-bin: /usr/bin/gentrigrams
libkf5sonnet-dev-bin: /usr/bin/parsetrigrams
uwsgi-dev: /usr/bin/dh_uwsgi
libwayland-bin: /usr/bin/wayland-scanner
wine64-tools: /usr/bin/widl-stable
wine64-tools: /usr/bin/winebuild-stable
wine64-tools: /usr/bin/winecpp-stable
wine64-tools: /usr/bin/winedump-stable
wine64-tools: /usr/bin/wineg++-stable
wine64-tools: /usr/bin/winegcc-stable
wine64-tools: /usr/bin/winemaker-stable
wine64-tools: /usr/bin/wmc-stable
wine64-tools: /usr/bin/wrc-stable
wine64-development-tools: /usr/bin/widl-development
wine64-development-tools: /usr/bin/winebuild-development
wine64-development-tools: /usr/bin/winecpp-development
wine64-development-tools: /usr/bin/winedump-development
wine64-development-tools: /usr/bin/wineg++-development
wine64-development-tools: 

Bug#883989: libreoffice-draw does not allow editing glue points

[Thomas Vaughan]

Package: libreoffice-draw
Version: 1:6.0.0~beta1-2
Severity: normal

Dear Maintainer,

For the last few months, I have been unable to add visible glue points or to
edit existing glue points in an old drawing.  This problem has persisted since
I upgraded from stable to unstable.

I recently tried the beta of libreoffice-6 in experimental, but it shows the
same behavior.

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

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

Versions of packages libreoffice-draw depends on:
ii  libavahi-client3 0.7-3
ii  libavahi-common3 0.7-3
ii  libc62.25-3
ii  libcdr-0.1-1 0.1.4-1
ii  libdbus-1-3  1.12.2-1
ii  libdbus-glib-1-2 0.108-3
ii  libfreehand-0.1-10.1.2-2
ii  libgcc1  1:7.2.0-17
ii  libglib2.0-0 2.54.2-1
ii  libicu57 57.1-8
ii  liblcms2-2   2.8-4
ii  libmspub-0.1-1   0.1.2-4+b1
ii  libmwaw-0.3-30.3.13-1
ii  libodfgen-0.1-1  0.1.6-2
ii  libpagemaker-0.0-0   0.0.3-2
ii  libpng16-16  1.6.34-1
ii  libqxp-0.0-0 0.0.0-1
ii  libreoffice-core 1:6.0.0~beta1-2
ii  librevenge-0.0-0 0.0.4-6
ii  libstaroffice-0.0-0  0.0.5-1
ii  libstdc++6   7.2.0-17
ii  libvisio-0.1-1   0.1.6-1
ii  libwpd-0.10-10   0.10.2-2
ii  libwpg-0.3-3 0.3.1-3
ii  libxml2  2.9.4+dfsg1-5.1
ii  libzmf-0.0-0 0.0.2-1
ii  uno-libs35.4.3-4+b1
ii  ure  5.4.3-4+b1
ii  zlib1g   1:1.2.8.dfsg-5

libreoffice-draw recommends no packages.

libreoffice-draw suggests no packages.

Versions of packages libreoffice-core depends on:
ii  fontconfig2.12.6-0.1
ii  fonts-opensymbol  2:102.10+LibO5.4.3-4
ii  libboost-date-time1.62.0  1.62.0+dfsg-4+b2
ii  libboost-locale1.62.0 1.62.0+dfsg-4+b2
ii  libc6 2.25-3
ii  libcairo2 1.15.8-2
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.1+git20160603-3+b1
ii  libcups2  2.2.6-2
ii  libcurl3-gnutls   7.57.0-1
ii  libdbus-1-3   1.12.2-1
ii  libdbus-glib-1-2  0.108-3
ii  libdconf1 0.26.1-1
ii  libeot0   0.01-4+b1
ii  libepoxy0 1.4.3-1
ii  libexpat1 2.2.3-2
ii  libexttextcat-2.0-0   3.4.5-1
ii  libfontconfig12.12.6-0.1
ii  libfreetype6  2.8.1-0.1
ii  libgcc1   1:7.2.0-17
ii  libglib2.0-0  2.54.2-1
ii  libgpgmepp6   1.9.0-8
ii  libgraphite2-31.3.10-6
ii  libharfbuzz-icu0  1.7.2-1
ii  libharfbuzz0b 1.7.2-1
ii  libhunspell-1.6-0 1.6.2-1
ii  libhyphen02.8.8-5
ii  libice6   2:1.0.9-2
ii  libicu57  57.1-8
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  liblcms2-22.8-4
ii  libldap-2.4-2 2.4.45+dfsg-1
ii  libmythes-1.2-0   2:1.2.4-3
ii  libneon27-gnutls  0.30.2-2
ii  libnspr4  2:4.16-1+b1
ii  libnss3   2:3.34-1
ii  libodfgen-0.1-1   0.1.6-2
ii  liborcus-0.13-0   0.13.1-3
ii  libpng16-16   1.6.34-1
ii  libpoppler68  0.57.0-2
ii  librdf0   1.0.17-1.1
ii  libreoffice-common1:6.0.0~beta1-2
ii  librevenge-0.0-0  0.0.4-6
ii  libsm62:1.2.2-1+b3
ii  libstdc++67.2.0-17
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.3-1+b3
ii  libxml2   2.9.4+dfsg1-5.1
ii  libxmlsec11.2.25-1
ii  libxmlsec1-nss1.2.25-1
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1
ii  libxslt1.11.1.29-5
ii  uno-libs3 5.4.3-4+b1
ii  ure   5.4.3-4+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.24+nmu5

-- no debconf information

Bug#883988: gcc-5-cross-ports: fix ftbfs due to mips64 ld.so.1 move

[YunQiang Su]

Package: src:gcc-5-cross-ports
Version: 14

recently, we patched dpkg-cross to don't ship ld.so.1 for mips64 and mipsn32
in /usr//lib, and keep them in
/usr//lib{32,64}

This is due to libc6-mipsel-mips64el-cross ships its ld.so.1 also to
/usr//lib
which will trigger file conflicts when install packages.

This scheme is following the old-years mips multilib.

So, for gcc cross building, we need to add /usr//lib{32,64} to the
search dir for dh_shlibdeps.

-- 
YunQiang Su
--- gcc/debian/rules.defs   2017-11-19 22:15:53.0 +
+++ gcc/debian/rules.defs   2017-12-09 17:10:18.477424936 +
@@ -2059,6 +2059,10 @@
$(with_build_sysroot)/usr/lib/$(call mlib_to_march,$(2)) \
$(with_build_sysroot)$(subst /usr,,/$(usr_lib$(2))) \
$(with_build_sysroot)/$(usr_lib$(2)) \
+   $(if $(findstring mips64,$(DEB_TARGET_ARCH)), \
+ $(with_build_sysroot)/$(usr_lib64)) \
+   $(if $(findstring mipsn32,$(DEB_TARGET_ARCH)), \
+ $(with_build_sysroot)/$(usr_libn32)) \
$(if $(filter yes,$(biarchsf) $(biarchhf)), \
  $(with_build_sysroot)/usr/$(call mlib_to_march,$(2))/lib) \
$(if $(filter yes, $(with_common_libs)),, \

Bug#880566: [Pkg-crosswire-devel] Bug#880566: Sponsorship request

[Roberto C . Sánchez]

On Mon, Nov 20, 2017 at 11:49:12AM +, Teus Benschop wrote:
>The newest packaging available from [1] fixes this bug.
>I am asking for assistance with reviewing and uploading this packaging.
>[1] [1]https://anonscm.debian.org/gitweb/?p=pkg-crosswire/bibletime.git

Hi Teus,

Apologies for the long delay.  The package looks good, so I have
uploaded it.  Also, there was no tag in Git for 2.11.1-1, so I also
tagged it and pushed the tag.

Regards,

-Roberto

-- 
Roberto C. Sánchez


signature.asc
Description: PGP signature

Bug#883470: isenkram: Update package data for virtualization technologies

[Petter Reinholdtsen]

[Raphaël Hertzog]
> I noticed that the modaliases file mentions "virtualbox-ose-guest-x11" but
> nowadays it should be "virtualbox-guest-x11".

Note, the preferred way to maintain the list of hardware-package
mappings is by adding AppStream metadata into the individual packages.
This way the information is available everywhere, not only for
isenkram.  See
https://wiki.debian.org/AppStream/Guidelines#Announcing_supported_hardware >
for instructions on how to do this.  I update the modaliases file
included in the isenkram package using the data available from
appstream, but hope to drop the modalises file completely in the future
once every mapping there is also available using appstream.  So far, 97
such mappings are missing. :(

This is the mapping you talk about in this case:

Package: virtualbox-ose-guest-x11
Modaliases: unused(pci:v80EEdBEEFsv*)

Is the PCI ID a good marker?

Anyway, I added this to work with both new and old package names:

Package: virtualbox-guest-x11
Modaliases: unused(pci:v80EEdBEEFsv*)

It will be included in the next upload.

> Also that suggestion is only applicable if you have Xorg installed.
> You might want to have virtualbox-guest-dkms (or -utils) as default
> package selection and somehow suggest the -x11 only if you have Xorg
> (not sure if that's something that is possible in isenkram).

I can only map from hardware to package, there is no conditionals
involved at the isenkram level.

Is there some way to use different hardware markers for this?

> It would be nice if you could review packages to be installed
> for other virtualization technologies:
> - there's qemu-guest-agent for qemu
> - maybe there are others that you are missing

I'm happy to adjust the mapping file on request, but am unlikely to have
capacity to do a review on my own any time soon.

--
Happy hacking
Petter Reinholdtsen

Bug#878227: [Pkg-crosswire-devel] Bug#878227: Sponsorship request

[Roberto C . Sánchez]

On Tue, Nov 21, 2017 at 12:56:25PM +, Teus Benschop wrote:
>The newest bibledit package is available from [1]. The version number
>is [1]5.0.331. This is a request for sponsorship, for review and for
>upload.
>Thank you!
>[1] [2]https://anonscm.debian.org/cgit/pkg-crosswire/bibledit-gtk.git/
> 
Hi Teus,

Apoligies for the long delay.  The package looks good so I have uploaded
it.

Regards,

-Roberto

-- 
Roberto C. Sánchez


signature.asc
Description: PGP signature

Bug#883977: *** stack smashing detected ***: evolution terminated

[gregor herrmann]

On Sat, 09 Dec 2017 18:01:35 -0500, Joachim Breitner wrote:

[qutoing changed]

> On Sat, 09 Dec 2017 17:38:48 -0500 Joachim Breitner  
> wrote:

> > I just upgraded evolution-data-server from 3.26.2.1-1 to 3.26.2.1-1.1,
> > and now evolution will not start again: Even before a windows appears, I
> > get the backtrace further down.  The various eds components start
> > successfully. Removing ~/.cache/evolution does not help.

Confirmed, both the bug and ...

> rebuilding evolution fixes the problem for me.

... that a rebuild of evolution is enough.
 
> Maybe re-assign to evolution?

Or to release.debian.org asking for a binNMU?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Beatles


signature.asc
Description: Digital Signature

Bug#883366: python-mechanicalsoup: new upstream version 0.9.0

[Paul Wise]

On Sat, 2017-12-09 at 18:04 +, Ghislain Vaillant wrote:

> I'd be happy to update the packaging of MechanicalSoup to the latest 
> upstream release. However, version 0.8.0 has been under RFS for more 
> than a month, and has yet to be answered [1].

I would suggest that you follow the Python team FAQ about sponsoring:

https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin#Request_For_Sponsorship

So, when you file an RFS, XCC the debian-python list, add it to the IRC
channel topic, mention the RFS and add it to the TODO wiki page.

https://www.debian.org/Bugs/Reporting#xcc

> This is not an isolated case unfortunately, and my personal motivation 
> is suffering as a result.

You can also ping the folks who sponsored the package before:

$ who-uploads python-mechanicalsoup
Uploads for python-mechanicalsoup:
0.7.0-1 to unstable: Gianfranco Costamagna 
0.6.0-1 to unstable: Anton Gladky 

Debian's general lack of people regularly doing sponsorship is a long
standing problem that needs a change of culture to fix. In recent years
it has been changing a bit as new people dedicate some of their Debian
time to sponsoring. We still have some way to go though.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#883922: tracyburroughs640,your recent order402524

[Tracy Burroughs]

 I know if I won money where in the f*** is it how come you didn't send it
to my address you already got my address I signed up for every one of these
God damn things what's the deal keep asking me for verification you send me
another survey to stupid f* f*** you where's my money

tracy

On Dec 9, 2017 8:53 AM, "AmazonOffer"  wrote:

we would like to Thankyou





































































Your message dated Sat, 09 Dec 2017 15:58:31 + with message-id and
subject line Bug#883922: fixed in evolution-data-server 3.26.2.1-1.1 has
caused the Debian Bug report #883922, regarding libical3-dev: libical-dev
provides should be versioned 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.) -- 883922:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883922
Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

-- Forwarded message --
From: Matthias Klose 
To: Debian Bug Tracking System 
Cc:
Bcc:
Date: Sat, 9 Dec 2017 13:23:25 +0100
Subject: fix dependencies for libical3
Package: src:evolution-data-server
Version: 3.26.2.1
Severity: serious
Tags: sid buster patch

please fix the (build)dependencies for libical3, by either dropping the
versioned libical-dev dependency, or by introducing an alternative
libical3-dev
dependency.




-- Forwarded message --
From: Matthias Klose 
To: 883922-cl...@bugs.debian.org
Cc:
Bcc:
Date: Sat, 09 Dec 2017 15:58:31 +
Subject: Bug#883922: fixed in evolution-data-server 3.26.2.1-1.1
Source: evolution-data-server
Source-Version: 3.26.2.1-1.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated evolution-data-server
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, 09 Dec 2017 13:52:27 +0100
Source: evolution-data-server
Binary: evolution-data-server evolution-data-server-common
evolution-data-server-tests evolution-data-server-dev
evolution-data-server-doc libedataserver-1.2-22 libedataserver1.2-dev
gir1.2-edataserver-1.2 libedataserverui-1.2-1 libedataserverui1.2-dev
gir1.2-edataserverui-1.2 libcamel-1.2-60 libcamel1.2-dev gir1.2-camel-1.2
libebook-1.2-19 libebook1.2-dev gir1.2-ebook-1.2 libedata-book-1.2-25
libedata-book1.2-dev gir1.2-ebookcontacts-1.2 libebook-contacts-1.2-2
libebook-contacts1.2-dev libecal-1.2-19 libecal1.2-dev libedata-cal-1.2-28
libedata-cal1.2-dev libebackend-1.2-10 libebackend1.2-dev
Architecture: source
Version: 3.26.2.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Evolution Maintainers 
Changed-By: Matthias Klose 
Description:
 evolution-data-server - evolution database backend server
 evolution-data-server-common - architecture independent files for
Evolution Data Server
 evolution-data-server-dev - Development files for evolution-data-server
(metapackage)
 evolution-data-server-doc - Documentation files for the Evolution Data
Server libraries
 evolution-data-server-tests - Installed tests for the evolution database
backend server
 gir1.2-camel-1.2 - GObject introspection for the Camel library
 gir1.2-ebook-1.2 - GObject introspection for the EBook library
 gir1.2-ebookcontacts-1.2 - GObject introspection for the EBook Contacts
library
 gir1.2-edataserver-1.2 - GObject introspection for the EDataServer library
 gir1.2-edataserverui-1.2 - GObject introspection for the EDataServerUI
library
 libcamel-1.2-60 - Evolution MIME message handling library
 libcamel1.2-dev - Development files for libcamel
 libebackend-1.2-10 - Utility library for evolution data servers
 libebackend1.2-dev - Utility library for 

Bug#883987: rheolef: FTBFS error: partial specialization ... after instantiation ...

[Andreas Beckmann]

Source: rheolef
Version: 6.7-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

rheolef did FTBFS during the binNMU against the new cgal:

https://buildd.debian.org/status/package.php?p=rheolef=unstable

>From the amd64 log:

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../config -I../../util/qd 
-I../../include -I/usr/include/openmpi -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -Wno-unused -Wno-strict-aliasing 
-Wno-literal-suffix -Wno-deprecated-declarations -O3 -MT point_predicate.lo -MD 
-MP -MF .deps/point_predicate.Tpo -c point_predicate.cc  -fPIC -DPIC -o 
.libs/point_predicate.o
In file included from /usr/include/boost/container/detail/flat_tree.hpp:29:0,
 from /usr/include/boost/container/flat_map.hpp:29,
 from /usr/include/CGAL/config.h:123,
 from /usr/include/CGAL/basic.h:29,
 from /usr/include/CGAL/Cartesian/Cartesian_base.h:28,
 from /usr/include/CGAL/Cartesian.h:28,
 from ../../include/rheolef/cgal_kernel.h:42,
 from ../../include/rheolef/cgal_traits.h:24,
 from point_predicate.cc:34:
/usr/include/boost/container/detail/pair.hpp:433:8: error: partial 
specialization of 'struct boost::is_enum >' after 
instantiation of 'struct boost::is_enum >' [-fpermissive]
 struct is_enum< ::std::pair >
^~~~
Makefile:1130: recipe for target 'point_predicate.lo' failed
make[4]: *** [point_predicate.lo] Error 1


Andreas

Bug#883916: openafs: [INTL:ru] Updated Russian translation of debconf template

[Benjamin Kaduk]

tags 883916 pending
thanks

Hi Lev,

On Sat, Dec 09, 2017 at 03:25:12PM +0500, Lev Lamberov wrote:
> 
> Dear Maintainer,
> 
> please find attached the updated Russian debconf translation for openafs.

Thanks!  I've put it into our version control so it should appear in
the next upload.

-Ben

Bug#883986: openscad: FTBFS on mips/mipsel: virtual memory exhausted: Cannot allocate memory

[Andreas Beckmann]

Source: openscad
Version: 2015.03-2+dfsg-2
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

openscad did run out of memory during the recent binNMU on mips/mipsel:

https://buildd.debian.org/status/package.php?p=openscad=unstable


Andreas

Bug#785551: Gpredict 2.0 is now available

[Maitland Bottoms]

On Sun, 10 Dec 2017 00:48:10 +0100
Alexandru Csete  wrote:

> Hello,
> 
> Gpredict 2.0 is now available with Goocanvas 2 / Gtk+ 3 support:
> https://github.com/csete/gpredict/releases/tag/v2.0
> 
> This release contains an initial port to Gtk+ 3. There are still many
> widgets that need to ported and this will give many compile time
> warnings. However, the application builds and runs fine already now.,
> and I hope this will be sufficient to prevent removal of gpredict from
> Debian.
> 
> A new release will be made in 3-4 weeks where the remaining widgets
> have been updated.
> 
> Cheers
> 
> Alex
> 

Awesome - thanks!

So I have been following along, and have some updated Debian packaging.
I have added src/gtk-event-list.c src/print-pass.c and
src/sat-pref-layout-utils.c to po/POTFILES.in
but there may still be more work needed to build with intltoolize.

-Maitland

Bug#883985: cmor: FTBFS on !linux architectures

[Andreas Beckmann]

Source: cmor
Version: 3.2.8-1
Severity: important
Tags: patch

Hi,

cmor FTBFS on the non-linux architectures:

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

Attached are two patches to treat kFreeBSD and Hurd like Linux w.r.t.
guessing the fortran compiler.

build-tested on kfreebsd-amd64 porterbox only.



Andreas
>From b6277f949ae3854e04ff57c75c607075d7878181 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Sun, 10 Dec 2017 01:56:10 +
Subject: [PATCH 1/2] add Vcs-Browser URL and use https:// for Vcs-Git

---
 debian/changelog | 6 ++
 debian/control   | 3 ++-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 68b6473..7c5f6f4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cmor (3.2.8-2) UNRELEASED; urgency=medium
+
+  * Add Vcs-Browser URL and use https:// for Vcs-Git.
+
+ -- Andreas Beckmann   Sun, 10 Dec 2017 01:54:58 +
+
 cmor (3.2.8-1) unstable; urgency=medium
 
   * New upstream release
diff --git a/debian/control b/debian/control
index d74b53e..706dc3d 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,8 @@ Build-Conflicts: libcmor2, python-cmor, python3-cmor
 Standards-Version: 4.1.1
 X-Python-Version: >= 2.6
 Homepage:  https://pcmdi.github.io/cmor-site/
-Vcs-Git: git://anonscm.debian.org/debian-science/packages/cmor.git
+Vcs-Git: https://anonscm.debian.org/git/debian-science/packages/cmor.git
+Vcs-Browser: https://anonscm.debian.org/cgit/debian-science/packages/cmor.git
 
 Package: libcmor2
 Section: libs
-- 
2.5.1

>From 72361134efc6a6732600f511a7fe82308f0fc2c5 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Sun, 10 Dec 2017 02:09:31 +
Subject: [PATCH 2/2] treat kFreeBSD and Hurd like Linux w.r.t. guessing the
 fortran compiler

---
 debian/changelog  |  1 +
 debian/patches/kfreebsd.patch | 14 ++
 debian/patches/series |  1 +
 3 files changed, 16 insertions(+)
 create mode 100644 debian/patches/kfreebsd.patch

diff --git a/debian/changelog b/debian/changelog
index 7c5f6f4..81ad3dd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 cmor (3.2.8-2) UNRELEASED; urgency=medium
 
   * Add Vcs-Browser URL and use https:// for Vcs-Git.
+  * Treat kfreeBSD and Hurd like Linux w.r.t. guessing the fortran compiler.
 
  -- Andreas Beckmann   Sun, 10 Dec 2017 01:54:58 +
 
diff --git a/debian/patches/kfreebsd.patch b/debian/patches/kfreebsd.patch
new file mode 100644
index 000..8bb3ee1
--- /dev/null
+++ b/debian/patches/kfreebsd.patch
@@ -0,0 +1,14 @@
+Author: Andreas Beckmann 
+Description: treat kFreeBSD and Hurd like Linux w.r.t. guessing the fortran 
compiler
+
+--- a/include/cdTime/cfortran.h
 b/include/cdTime/cfortran.h
+@@ -206,7 +206,7 @@ only C calling FORTRAN subroutines will
+ #define   f2cFortran 
+ #define gFortran /* 8/26/08 (KMCCARTY) */
+ #endif
+-#ifdefined(__GNUC__) && defined(linux) /* 06/21/00 PDW (CFITSIO) */
++#ifdefined(__GNUC__) && (defined(linux) || 
defined(__FreeBSD_kernel__) || defined(__GNU__)) /* 06/21/00 PDW (CFITSIO) */
+ #define   f2cFortran 
+ #define gFortran /* 8/26/08 (KMCCARTY) */
+ #endif
diff --git a/debian/patches/series b/debian/patches/series
index f626619..0f81787 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -6,3 +6,4 @@ cmor_ver.patch
 python3.patch
 disable_tests.patch
 prepare-name.patch
+kfreebsd.patch
-- 
2.5.1

Bug#883984: odds stacked against human player

[Gary Koskenmaki]

Package: xmille
Version: 2.0-13
Severity: normal

Dear Maintainer,

I just finished a set of 5 games against the computer.  The results
were a little worse than usual but not by much.  I lost all 5 games,
and in 10 hands in those 5 games I scored no points at all.  This was
no fault of my own, for I cannot score if I am not dealt cards with
which it is possible to score.  In those 10 games I averaged a little
less than two Go cards per game, and I was not dealt the first one in
each game until more than half way through the deck. At the same time I
was dealt either 0 or 1 hazard card per game for which the computer had
an immediate solution--coup fourre or a remedy card and then a
Go.  Thus, the computer had all the odds on its side.  

I have played Mille Bornes for at least 30 years and I do not recall
ever seeing such poor odds in a two-handed game on a regular basis.  If
one player gets a hot streak of cards the worm will turn a few games
later in the other player's favor.  That never happens in this
computerized version.  

The computer wins 75-80% of the time and it's due to the computer
getting the winning cards and the human rarely getting the winning
cards.  This is not a complaint that comes from playing a few games
against the computer, or from not being a skilled Mille Bornes
player.  I am a skilled Mille Bornes player who wins on a consistent
basis against human players.  I have played a few hundred games against
the computer and the odds on being dealt winning cards do not even out.
As a result there is no way to hold your own against the computer.

How about evening out the odds between computer and human?



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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 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 xmille depends on:
ii  libc6 2.25-3
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2

xmille recommends no packages.

xmille suggests no packages.

-- no debconf information

Bug#883983: RFS: txtorcon/0.19.3-3 [RC]

[Nicolas Braud-Santoni]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: pkg-privacy-maintain...@lists.alioth.debian.org, j...@debian.org, 
a...@debian.org
Control: block 881668 by -1
Control: tag 881668 + pending

Dear mentors,

I am looking for a sponsor for the package “txtorcon”:

 * Package name: txtorcon
   Version : 0.19.3-3
   Upstream Author : meejah 
 * URL : https://github.com/meejah/txtorcon
 * License : Expat, BSD-3
   Section : python


The source package can be found on mentors.debian.org:

https://mentors.debian.net/package/txtorcon

Alternatively, the packaging repository is available on alioth.d.o:

https://anonscm.debian.org/git/pkg-privacy/packages/txtorcon.git


Changes since the last upload:

  * Team upload.
  * Moving signing key to debian/upstream/
  * debian/control
* Depend on ipaddress, not ipaddr (Closes: #881668)
* Replace `Priority: extra` with `optional`
* Declare compliance with Debian Policy version 4.1.2
  No change required
* Use HTTPS URIs
  * Removed privacy-infringing buttons.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#874928: [kalternatives] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Hi! There seems to be work in progress, so please do no file the bug.

Thanks!

El 9 dic. 2017 12:51 a.m., "Boyuan Yang" <073p...@gmail.com> escribió:

> X-Debbugs-CC: p...@kde.org debian-qt-...@lists.debian.org
>
> 在 2017年11月28日星期二 CST 上午9:55:54，Boyuan Yang 写道：
> > X-Debbugs-CC: p...@kde.org debian-qt-...@lists.debian.org
> >
> > Hello all,
> >
> > I'm wondering about the future of package "kalternatives" in Debian. It
> has
> > not been updated for 7 years, now affected by Qt4 removal and I cannot
> find
> > the upstream VCS for it.
> >
> > Will there be any porting efforts? If yes, please let me know; if not, we
> > could consider submitting removal request to get this out of Debian
> > unstable.
> >
> > PS: I'm the current maintainer of package "galternatives" in Debian.
> >
> > Thanks,
> > Boyuan Yang
>
> Hello,
>
> Since there's no response, I'm going to file an RM bug for package
> kalternatives within one month.
>
> Please let me know if anyone is willing to work on it and port it to Qt5.
>
> Thanks,
> Boyuan Yang

Bug#883972: samba: FTBFS on kfreebsd: error: storage size of 'cr' isn't known

[Andrew Bartlett]

On Sat, 2017-12-09 at 23:04 +0100, Andreas Beckmann wrote:
> Source: samba
> Version: 2:4.7.3+dfsg-1
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: kfreebsd
> 
> Hi,
> 
> that 4.7.x uploads of samba FTBFS on kfreebsd:

> [2706/4004] Compiling ctdb/tests/src/ipalloc_read_known_ips.c
> 08:44:02 runner /usr/bin/gcc -g -O2 
> -fdebug-prefix-map=/«BUILDDIR»/samba-4.7.3+dfsg=. -fstack-protector-strong 
> -Wformat -Werror=format-security -fPIE -fPIC -D_REENTRANT 
> -D_POSIX_PTHREAD_SEMANTICS 
> -DCTDB_HELPER_BINDIR="/usr/lib/x86_64-kfreebsd-gnu/ctdb" 
> -DLOGDIR="/var/log/ctdb" -DCTDB_ETCDIR="/etc/ctdb" 
> -DCTDB_VARDIR="/var/lib/ctdb" -DCTDB_RUNDIR="/var/run/ctdb" -fstack-protector 
> -DSTATIC_fake_ctdbd_MODULES=NULL -DSTATIC_fake_ctdbd_MODULES_PROTO=extern 
> void __fake_ctdbd_dummy_module_proto(void) -MD -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Idefault/ctdb -I../ctdb -Idefault/include/public 
> -I../include/public -Idefault/source4 -I../source4 -Idefault/lib -I../lib 
> -Idefault/source4/lib -I../source4/lib -Idefault/source4/include 
> -I../source4/include -Idefault/include -I../include -Idefault/lib/replace 
> -I../lib/replace -Idefault/ctdb/include -I../ctdb/include -Idefault -I.. 
> -Idefault/lib/util/charset -I../lib/util/charset -Idefault/libcli/util 
> -I../libcli/util -Idefault/lib/crypto -I../lib/crypto -Idefault/lib/async_req 
> -I../lib/async_req -Idefault/dynconfig -I../dynconfig -I/usr/local/include 
> -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1 
> -D_XOPEN_SOURCE_EXTENDED=1 ../ctdb/tests/src/ipalloc_read_known_ips.c -c -o 
> default/ctdb/tests/src/ipalloc_read_known_ips_134.o
> ../ctdb/tests/src/fake_ctdbd.c: In function 'client_send':
> ../ctdb/tests/src/fake_ctdbd.c:3081:15: error: storage size of 'cr' isn't 
> known
>   struct ucred cr;
>^~
> ../ctdb/tests/src/fake_ctdbd.c:3082:25: error: invalid application of 
> 'sizeof' to incomplete type 'struct ucred'
>   socklen_t crl = sizeof(struct ucred);
>  ^~
> ../ctdb/tests/src/fake_ctdbd.c:3095:35: error: 'SO_PEERCRED' undeclared 
> (first use in this function); did you mean 'SO_PEERLABEL'?
>   ret = getsockopt(fd, SOL_SOCKET, SO_PEERCRED, , );
>^~~
>SO_PEERLABEL
> ../ctdb/tests/src/fake_ctdbd.c:3095:35: note: each undeclared identifier is 
> reported only once for each function it appears in
> [2707/4004] Compiling lib/pthreadpool/tests.c
> 08:44:02 runner /usr/bin/gcc -g -O2 
> -fdebug-prefix-map=/«BUILDDIR»/samba-4.7.3+dfsg=. -fstack-protector-strong 
> -Wformat -Werror=format-security -fPIE -fPIC -D_REENTRANT 
> -D_POSIX_PTHREAD_SEMANTICS 
> -DCTDB_HELPER_BINDIR="/usr/lib/x86_64-kfreebsd-gnu/ctdb" 
> -DLOGDIR="/var/log/ctdb" -DCTDB_ETCDIR="/etc/ctdb" 
> -DCTDB_VARDIR="/var/lib/ctdb" -DCTDB_RUNDIR="/var/run/ctdb" -fstack-protector 
> -DSTATIC_pthreadpooltest_MODULES=NULL 
> -DSTATIC_pthreadpooltest_MODULES_PROTO=extern void 
> __pthreadpooltest_dummy_module_proto(void) -MD -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Idefault/lib/pthreadpool -I../lib/pthreadpool 
> -Idefault/include/public -I../include/public -Idefault/source4 -I../source4 
> -Idefault/lib -I../lib -Idefault/source4/lib -I../source4/lib 
> -Idefault/source4/include -I../source4/include -Idefault/include -I../include 
> -Idefault/lib/replace -I../lib/replace -Idefault/ctdb/include 
> -I../ctdb/include -Idefault/ctdb -I../ctdb -Idefault -I.. 
> -Idefault/libcli/util -I../libcli/util -I/usr/local/include -D_SAMBA_BUILD_=4 
> -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 
> ../lib/pthreadpool/tests.c -c -o default/lib/pthreadpool/tests_2.o
> Waf: Leaving directory `/«BUILDDIR»/samba-4.7.3+dfsg/bin'
> Build failed:  -> task failed (err #1): 
>   {task: cc fake_ctdbd.c -> fake_ctdbd_134.o}
> debian/rules:102: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

This was introduced in the fix for 
https://bugzilla.samba.org/show_bug.cgi?id=13012

Can you please take up the regression upstream?  There is interest in
fixing FreeBSD, talk to Timur I. Bakeyev (CC'ed) in particular.  

(There is very strong preference to not carry Debian-specific patches
unless they are already upstream.)

Lastly however, it looks like what is desired here is simply not
possible:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215202

You may wish to disabled building CTDB on kfreebsd or find a way not to
build the tests.

Sorry,

Andrew Bartlett

-- 
Andrew Bartlett   http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba

Bug#883982: iputils-ping: man page typo

[Noah Meyerhans]

Control: tags -1 + fixed-upstream pending

On Sun, Dec 10, 2017 at 02:53:54AM +0200, Alex wrote:
> man page contains typo for option '-f' (line 39). Currently it states "while
> for ever ECHO_REPLY" which was probably meant to be "for every".
> If somebody could point me to instructions on how to access source package, I
> could fix it myself.

Thanks for the report. This has already been fixed upstream, please see

https://github.com/iputils/iputils/blob/master/doc/ping.xml#L126



signature.asc
Description: PGP signature

Bug#883833: [Pkg-e-devel] Bug#883833: e17: FTBFS if $HOME is not writable

[Ross Vandegrift]

Control: tags -1 pending

Looks good, patch applied.

Ross

On Fri, Dec 08, 2017 at 08:07:31AM +0100, Andreas Metzler wrote:
> Control: tags -1 patch
> 
> On 2017-12-08 Andreas Beckmann  wrote:
> > Source: e17
> > Version: 0.22.1-1
> > Severity: serious
> > Justification: fails to build from source (but built successfully in the 
> > past)
> 
> > e17 FTBFS if $HOME is not existent (and therefore not writable) as
> > enforced by current pbuilder.
> > See also Policy 9.2.3.
> 
> > From the attached log:
> 
> > FATAL: Cannot create run dir '/nonexistent/.run' - errno=2
> 
> edje_cc seems to need a writeable ~/.
> 
> cu Andreas
> -- 
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'

> From 68546024af75578f47e42236077792ec33eb8646 Mon Sep 17 00:00:00 2001
> From: Andreas Metzler 
> Date: Fri, 8 Dec 2017 08:03:54 +0100
> Subject: [PATCH] Fix FTBFS with HOME="/nonexistent".
> 
> Copy fake_home.sh from efl and run dh_auto_build under it. edje_cc needs a
> writeable HOME. Closes: #883833
> ---
>  debian/changelog|  7 +++
>  debian/fake_home.sh | 15 +++
>  debian/rules|  4 
>  3 files changed, 26 insertions(+)
>  create mode 100755 debian/fake_home.sh
> 
> diff --git a/debian/changelog b/debian/changelog
> index 316806a9f..6f1bee871 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +e17 (0.22.1-2) UNRELEASED; urgency=medium
> +
> +  * Copy fake_home.sh from efl and run dh_auto_build under it. edje_cc needs 
> a
> +writeable HOME. Closes: #883833
> +
> + -- Andreas Metzler   Fri, 08 Dec 2017 08:01:08 +0100
> +
>  e17 (0.22.1-1) experimental; urgency=medium
>  
>* New upstream release
> diff --git a/debian/fake_home.sh b/debian/fake_home.sh
> new file mode 100755
> index 0..2902878e1
> --- /dev/null
> +++ b/debian/fake_home.sh
> @@ -0,0 +1,15 @@
> +#!/bin/sh
> +
> +cleanup () {
> +[ -n "$temp_HOME" ] && rm -r "$temp_HOME"
> +[ -n "$temp_XDG_RUNTIME_DIR" ] && rm -r "$temp_XDG_RUNTIME_DIR"
> +}
> +
> +trap cleanup EXIT
> +
> +temp_HOME=$(mktemp -d)
> +temp_XDG_RUNTIME_DIR=$(mktemp -d)
> +
> +env HOME="$temp_HOME" \
> +XDG_RUNTIME_DIR="$temp_XDG_RUNTIME_DIR" \
> +$*
> diff --git a/debian/rules b/debian/rules
> index eafe076d0..de55ca691 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -11,6 +11,10 @@ 
> ARCH_PATH=$(DEB_HOST_GNU_SYSTEM)-$(DEB_HOST_GNU_CPU)-$(RELEASE)
>  override_dh_auto_configure:
>   dh_auto_configure --verbose
>  
> +override_dh_auto_build:
> + $(CURDIR)/debian/fake_home.sh \
> + dh_auto_build -O--buildsystem=meson --verbose
> +
>  override_dh_lintian:
>   sed -e "s/MULTIARCH/$(DEB_TARGET_MULTIARCH)/" \
>   -e "s/ARCH_PATH/$(ARCH_PATH)/" \
> -- 
> 2.15.0
> 

> ___
> Pkg-e-devel mailing list
> pkg-e-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-e-devel

Bug#880047: bug is still valid

[Eggert Ehmke]

I run Debian 9.1 with postgrey 1.36-3 where the bug is still valid. I had to 
create a file:

/usr/lib/tmpfiles.d/postgrey.conf

with content:

d /run/postgrey 0755 root root

to be able to reboot my system without problem.

Cheers
Eggert

Bug#883980: base-files: After updating to 9.3, Screen Sporadically Goes Blank

[Santiago Vila]

reassign 883980 chromium,linux
thanks

On Sat, Dec 09, 2017 at 05:45:33PM -0600, Hanlyu Sarang wrote:
> Package: base-files
> Version: 9.9+deb9u3
> Severity: important
> 
> Dear Maintainer,
> 
> I upgraded to Debian 9.3 today, using aptitude update/aptitude upgrade, then
> rebooted the computer. Everything seemed to be OK.
> 
> But then, when using Chromium on Youtube, the entire screen would go Blank
> (actually Black) whenever I moved the mouse and it was over the playing video.
> When I switched to Terminatior to fire up report-bug, I noticed also that when
> I type a character on the command line (bash), the screen also goes black.
> 
> When the screen goes black, it happens for about 1 second, then returns to
> normal. No flashing or funny noises. The screen goes black for a second, then
> comes back on, normal brightness.
> 
> I have been using Debian 9, and upgrading periodically, for the past 3-4
> months. This has never happed before. I have not made any changes to the
> hardware.
> 
> I am running a Toshiba Satellite, recent model with Intel I5 processor (and
> integrated graphics, no graphics card).
> 
> I am not certain if base-files is the correct place to file this report, but
> base-files was one of the packages downloaded when I upgraded to 9.3.

This is very unlikely a problem with base-files, as the only change for
the point release is to raise /etc/debian_version from 9.2 to 9.3 (so
that the exact point release is shown in bug reports like this one).

So I am reassigning this to chromium and the kernel.

However, please be ready to provide the chromium and kernel maintainers
with additional info as they ask, because this could be a bug in other
packages too.

[ I would bet this has something to do with the kernel. To be sure
  try installing the kernel in Debian 9.2 (from snapshot.debian.org) and
  see if the problem disappears when using the old kernel ].

Thanks.

Bug#883980: base-files: After updating to 9.3, Screen Sporadically Goes Blank

[Gerard M. Vignes]

On Sat, 09 Dec 2017 17:45:33 -0600 Hanlyu Sarang 
 wrote:

Package: base-files
Version: 9.9+deb9u3
Severity: important

Dear Maintainer,

I upgraded to Debian 9.3 today, using aptitude update/aptitude upgrade, then
rebooted the computer. Everything seemed to be OK.


I am including additional information, as 3 text file attachments, from 
running diagnostics on my system. Output from running:

cat /proc/cpuinfo
dpkg --get-selections
lspci | egrep -i 'vga|2d|3d'


processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 61
model name  : Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
stepping: 4
microcode   : 0x19
cpu MHz : 2200.000
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 20
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb 
intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 
smep bmi2 erms invpcid rdseed adx smap xsaveopt dtherm ida arat pln pts
bugs:
bogomips: 4389.67
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 61
model name  : Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
stepping: 4
microcode   : 0x19
cpu MHz : 2052.563
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 2
apicid  : 2
initial apicid  : 2
fpu : yes
fpu_exception   : yes
cpuid level : 20
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb 
intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 
smep bmi2 erms invpcid rdseed adx smap xsaveopt dtherm ida arat pln pts
bugs:
bogomips: 4389.67
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 2
vendor_id   : GenuineIntel
cpu family  : 6
model   : 61
model name  : Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
stepping: 4
microcode   : 0x19
cpu MHz : 2200.000
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 1
initial apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 20
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb 
intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 
smep bmi2 erms invpcid rdseed adx smap xsaveopt dtherm ida arat pln pts
bugs:
bogomips: 4389.67
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 3
vendor_id   : GenuineIntel
cpu family  : 6
model   : 61
model name  : Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
stepping: 4
microcode   : 0x19
cpu MHz : 2200.134
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 2
apicid  : 3
initial apicid  : 3
fpu : yes
fpu_exception   : yes
cpuid level : 20
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer 

Bug#883957: kopanocore support for ical 3

[Carsten Schoenert]

Hello Juhani,

On Sun, Dec 10, 2017 at 01:57:18AM +0200, Juhani Numminen wrote:
> Control: tags -1 fixed-upstream
> 
> Please see
> 
> https://stash.kopano.io/projects/KC/repos/kopanocore/commits/0768d5d5a04

unfortunately this commit is a bit far behand the last release of 8.4.4
so it's not so easy as it's seems.

And starting with 8.4.0 Kopano also has placed the private libraries into
/usr/lib and not into /usr/lib/kopano any longer, that's the main reason
we haven't updated the package version in Debian until now.

Regards
Carsten

Bug#883976: nfs-common: Shell script executed by systemd to mount net /home * /var fails

[Raphaël Halimi]

Le 09/12/2017 à 23:32, Duncan Hare a écrit :
> Why during boot are the messages:
> 
> mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/var  /var in /etc/fstab
> mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/home /home in /etc/fstab
> 
> being generated as though the root id during boot is a normal unprivilaged 
> unser?
> /usr/bin/setup-var-home.sh:
> #!/bin/bash
> H=$(hostname);
> #H="b827ebc23849";
> /bin/mount 192.168.1.10:/nsfroot/${H:0:-6}"/"${H:6:12}"/var  /var";
> /bin/mount 192.168.1.10:/nsfroot/${H:0:-6}"/"${H:6:12}"/home /home";
I'm not sure a shell script is the best way to mount NFS exports at boot
(I have read your other recent bug reports, I'm aware that you're
currently encountering problems with NFS mounts at boot, but running a
shell script for solving this seems a bit overkill to me), but in this
case, this has nothing to do with NFS or systemd, it's your shell script
which is flawed.

More precisely, you placed the double-quotes in a way that makes the
shell consider everything after /bin/mount as one long argument. You
could remove those double-quotes altogether, since it seems you name
your NFS exports according to your machines' hostnames, and a hostname
can't contain spaces ([1]), but if you absolutely want to hold onto
them, try to correctly quote the different arguments, for example:

/bin/mount 192.168.1.10:/nsfroot/"${H:0:-6}"/"${H:6:12}"/var  /var

or:

/bin/mount 192.168.1.10:/nsfroot/"${H:0:-6}/${H:6:12}"/var  /var

or:

/bin/mount 192.168.1.10:/nsfroot/"${H:0:-6}/${H:6:12}/var"  /var

or, to be absolutely clear as to what the mount command expects, and how
to quote arguments accordingly:

/bin/mount "192.168.1.10:/nsfroot/${H:0:-6}/${H:6:12}/var"  "/var"

I understand that you may be a bit frustrated with those aforementioned
problems you're currently encountering with your NFS mounts at boot, but
filing bug reports at the drop of a hat is counter-productive. Not only
are you nagging this package's maintainers, but also other people (like
me) who don't maintain this package but subscribed to receive its bug
reports.

After verifying that what I'm suggesting works as you expect (but then
again, I sincerely doubt a shell script is the way to go here), please
spare the maintainers a bit of their (precious) time and close this bug.

[1] https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_hostnames

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#883957: kopanocore support for ical 3

[Juhani Numminen]

Control: tags -1 fixed-upstream

Please see

https://stash.kopano.io/projects/KC/repos/kopanocore/commits/0768d5d5a04

Regards,
Juhani

Bug#877663: MIMEDefang Restarts Broken with systemd

[Richard Laager]

I ran into a problem with my systemd units for MIMEDefang. There is a
race condition between mimedefang-multiplexor creating the socket and
mimedefang trying to access it. If the multiplexor doesn't create the
socket in time, mimedefang fails on startup.

This is happening because Type=simple services are assumed to be running
immediately. This is documented in systemd.service(5), which says, "In
this mode, if the process offers functionality to other processes on the
system, its communication channels should be installed before the daemon
is started up (e.g. sockets set up by systemd, via socket activation),
as systemd will immediately proceed starting follow-up units."

I have attached updated versions to correct this. These change to
Type=forking and drop the -D flag. With the change to Type=forking, I
have also brought back pid files. Since systemd requires the pid file
path to be hardcoded (as the argument to PIDFile), I put it in /run
rather than the $SPOOLDIR (which the administrator can change). It can't
be directly in /run, as the daemon writes the pidfile after dropping
privileges, so we have to create a /run/mimedefang subdirectory owned by
$MX_USER. This requires some indirection, as $MX_USER can also be
customized by the administrator. I only create this directory for
mimedefang-multiplexor.service (and not mimedefang.service), as
mimedefang.service is already ordered after mimedefang-multiplexor.service.

Long term, the ideal answer is to use systemd's socket activation. This
would allow the services to startup in parallel. Another alternative
would be to use Type=notify. Either requires changes to the mimedefang C
code.

-- 
Richard

[Unit]
Description=MIMEDefang E-mail Filter
Documentation=man:mimedefang(8)
Before=multi-user.target
Before=postfix.service
Before=sendmail.service
After=remote-fs.target
After=systemd-journald-dev-log.socket
BindsTo=mimedefang-multiplexor.service
After=mimedefang-multiplexor.service
PropagatesReloadTo=mimedefang-multiplexor.service

[Service]
Type=forking
PIDFile=/run/mimedefang/mimedefang.pid
Restart=on-failure
TimeoutStopSec=30s
# LC_ALL=C may not be necessary for mimedefang, but it is for
# mimedefang-multiplexor, so upstream prefers it here also to be consistent.
Environment=LC_ALL=C 
MX_SOCKET=/var/spool/MIMEDefang/mimedefang-multiplexor.sock MX_USER=defang 
SOCKET=/var/spool/MIMEDefang/mimedefang.sock
EnvironmentFile=-/etc/default/mimedefang
ExecStartPre=/bin/rm -f $SOCKET
ExecStart=/bin/sh -c 'exec /usr/bin/mimedefang \
`[ -n "$LOOPBACK_RESERVED_CONNECTIONS" ] && echo "-R 
$LOOPBACK_RESERVED_CONNECTIONS"` \
-m $MX_SOCKET \
`[ -n "$SPOOLDIR" ] && echo "-z $SPOOLDIR"` \
`[ -n "$MX_USER" ] && echo "-U $MX_USER"` \
`[ -n "$SYSLOG_FACILITY" ] && echo "-S $SYSLOG_FACILITY"` \
`[ "$MX_RELAY_CHECK" = "yes" ] && echo "-r"` \
`[ "$MX_HELO_CHECK" = "yes" ] && echo "-H"` \
`[ "$MX_SENDER_CHECK" = "yes" ] && echo "-s"` \
`[ "$MX_RECIPIENT_CHECK" = "yes" ] && echo "-t"` \
`[ "$KEEP_FAILED_DIRECTORIES" = "yes" ] && echo "-k"` \
`[ "$MD_EXTRA" != "" ] && echo $MD_EXTRA` \
`[ "$MD_SKIP_BAD_RCPTS" = "yes" ] && echo "-N"` \
"`[ -n "$X_SCANNED_BY" ] && \
  ( [ "$X_SCANNED_BY" = "-" ] && \
echo "-X" || echo "-x$X_SCANNED_BY" )`" \
`[ "$MD_ALLOW_GROUP_ACCESS" = "yes" ] && echo "-G"` \
`[ "$ALLOW_NEW_CONNECTIONS_TO_QUEUE" = "yes" ] && echo "-q"` \
-p $SOCKET -P /run/mimedefang/mimedefang.pid'
ExecStopPost=/bin/rm -f $SOCKET
# Make this service eligible for a reload, so we can propagate it to
# mimedefang-multiplexor.service.
ExecReload=/bin/true

[Install]
WantedBy=multi-user.target
[Unit]
Description=MIMEDefang E-mail Filter (Multiplexor)
Documentation=man:mimedefang-multiplexor(8)
After=remote-fs.target
After=systemd-journald-dev-log.socket
PartOf=mimedefang.service

[Service]
Type=forking
PIDFile=/run/mimedefang/mimedefang-multiplexor.pid
Restart=on-failure
TimeoutStopSec=30s
KillMode=mixed
# Locale should be set to "C" for generating valid date headers
Environment=LC_ALL=C MX_BUSY=600 MX_LOG=yes MX_MAXIMUM=10 MX_MINIMUM=2 
MX_SOCKET=/var/spool/MIMEDefang/mimedefang-multiplexor.sock MX_USER=defang
EnvironmentFile=-/etc/default/mimedefang
# This can be removed with MIMEDefang 2.82:
SuccessExitStatus=1
ExecStartPre=/bin/rm -f $MX_SOCKET
ExecStartPre=/bin/sh -c '/usr/bin/install -d \
`[ -n "$MX_USER" ] && echo "-o $MX_USER"` \
/run/mimedefang'
ExecStart=/bin/sh -c 'HOME=${SPOOLDIR:=/var/spool/MIMEDefang} \
exec /usr/bin/mimedefang-multiplexor \
`[ "$MX_EMBED_PERL" = "yes" ] && echo "-E"` \
`[ -n "$SPOOLDIR" ] && echo "-z $SPOOLDIR"` \
`[ -n "$FILTER" ] && echo "-f $FILTER"` \
`[ -n "$SYSLOG_FACILITY" ] && echo "-S $SYSLOG_FACILITY"` \
`[ -n "$SUBFILTER" ] && echo "-F $SUBFILTER"` \
`[ -n "$MX_MINIMUM" ] && echo "-m $MX_MINIMUM"` \
`[ -n "$MX_MAXIMUM" ] && echo "-x $MX_MAXIMUM"` \
`[ -n "$MX_MAP_SOCKET" ] && echo "-N $MX_MAP_SOCKET"` \
`[ -n 

Bug#883981: openjdk-9: embeds jquery.js when creating javadoc

[Markus Koschany]

Package: src:openjdk-9
Version: 9.0.1+11-1
Severity: normal

Hi,

when I create javadoc with openjdk-9, Lintian warns me about
a embedded-javascript-library. For instance libjide-oss-java is
currently affected by this issue.

https://lintian.debian.org/maintainer/pkg-java-maintain...@lists.alioth.debian.org.html#libjide-oss-java

Apparently openjdk-9 uses an internal copy of jquery.js. It would be
better if this could be avoided by automatically symlinking against the system
library.

Regards,

Markus

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/2 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/dash
Init: unable to detect

Bug#785551: Gpredict 2.0 is now available

[Alexandru Csete]

Hello,

Gpredict 2.0 is now available with Goocanvas 2 / Gtk+ 3 support:
https://github.com/csete/gpredict/releases/tag/v2.0

This release contains an initial port to Gtk+ 3. There are still many
widgets that need to ported and this will give many compile time
warnings. However, the application builds and runs fine already now.,
and I hope this will be sufficient to prevent removal of gpredict from
Debian.

A new release will be made in 3-4 weeks where the remaining widgets
have been updated.

Cheers

Alex

Bug#880467: jasperreports: CVE-2017-14941, CVE-2017-5528, CVE-2017-5529

[Emmanuel Bourg]

Le 10/12/2017 à 00:07, Markus Koschany a écrit :

> However we should always be able to assess security vulnerabilities.
> Just hoping that nobody will ever use the Debian library in some other
> context is negligent. I would be really disappointed when I built an
> Java app with Debian's system libraries and then I have to find out that
> it is basically unsupported and contains security holes because it is
> "just" a build-dependency for some other project.

I tend to disagree with this reasoning. We can't support any usage of
the libraries we ship, we don't have the resources for that. Our
responsibility should be limited to the code that we actually use in
Debian. Java developers don't use the system libraries anyway, they
typically pull the jars from Maven Central and bundle them with their
applications. Patching unused features would really be a waste of time.


> To be fair: CVE-2017-5533 and CVE-2017-5528 probably do not affect us
> because we ship the Jasperreports Library and not the server. Please
> correct me if I am wrong.

I don't know, I'm not familiar enough with jasperreports. I can just
observe that the Spring modules depending on it are nowhere used in
Debian yet.


> Thus said maybe you are able to find the relevant changes or you get a
> more helpful reply from the support guys. Otherwise I would try to
> disable jasperreports in libspring-java which appears to be optional. (I
> know probably requires another patch...)

libspring-java is already quite complicated. An additional patch to
maintain would be a hindrance, especially for disabling the usage of a
library we don't really care about. On the other hand maintaining such a
patch is maybe less complicated than regularly upgrading jasperreports,
that's probably worth investigating. If we go that route I'd rather see
libspring-java upgraded to the version 5.0 before patching it.


> For reference here is the link to my support request:
> 
> https://community.jaspersoft.com/questions/1072461/security-update-cve-2017-14941-cve-2017-5528-cve-2017-5529

I'm not convinced they understood the context and our point of view.
Upgrading the library was just the obvious solution to the issue raised,
that doesn't make the answer hostile or uncooperative. I'd suggest
asking the developers directly instead of going through a sales or
customer support representative.

Emmanuel Bourg

Bug#883980: base-files: After updating to 9.3, Screen Sporadically Goes Blank

[Hanlyu Sarang]

Package: base-files
Version: 9.9+deb9u3
Severity: important

Dear Maintainer,

I upgraded to Debian 9.3 today, using aptitude update/aptitude upgrade, then
rebooted the computer. Everything seemed to be OK.

But then, when using Chromium on Youtube, the entire screen would go Blank
(actually Black) whenever I moved the mouse and it was over the playing video.
When I switched to Terminatior to fire up report-bug, I noticed also that when
I type a character on the command line (bash), the screen also goes black.

When the screen goes black, it happens for about 1 second, then returns to
normal. No flashing or funny noises. The screen goes black for a second, then
comes back on, normal brightness.

I have been using Debian 9, and upgrading periodically, for the past 3-4
months. This has never happed before. I have not made any changes to the
hardware.

I am running a Toshiba Satellite, recent model with Intel I5 processor (and
integrated graphics, no graphics card).

I am not certain if base-files is the correct place to file this report, but
base-files was one of the packages downloaded when I upgraded to 9.3.

Thank you.



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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 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 base-files depends on:
ii  gawk [awk]  1:4.1.4+dfsg-1
ii  mawk [awk]  1.3.3-17+b3

base-files recommends no packages.

base-files suggests no packages.

-- no debconf information

Bug#883979: libsoup: .test local development domain not recognized

[lauren]

Package: libsoup2.4-1
Version: 2.60.2-1
Severity: important
File: libsoup

Dear Maintainer,


   * What led up to the situation?
using .test as a local development machine domain TLD

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
i have to type http:// in front of every .test domain or i get a web 
search

   * What was the outcome of this action?
typing http://blah.test works but so should blah.test

   * What outcome did you expect instead?
that typing blah.test would work as well - i realize that typing 
http:// might not seem
like a big deal, and in the grand scheme of things it isn't, but it 
gets *really* old
really quick, and besides it *should* work as it is the recommended TLD 
to use for local
development work etc


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

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

Versions of packages libsoup2.4-1:amd64 depends on:
ii  glib-networking   2.54.1-1
ii  libc6 2.25-3
ii  libglib2.0-0  2.54.1-1
ii  libgssapi-krb5-2  1.15.2-2
ii  libsqlite3-0  3.21.0-1
ii  libxml2   2.9.4+dfsg1-5.1

libsoup2.4-1:amd64 recommends no packages.

libsoup2.4-1:amd64 suggests no packages.

-- no debconf information

Bug#883978: RFS: parcimonie/0.10.3-2

[Nicolas Braud-Santoni]

Package: sponsorship-requests
Severity: wishlist
Control: block 883975 by -1
Control: tag 883975 + pending
X-Debbugs-CC: pkg-privacy-maintain...@lists.alioth.debian.org, j...@debian.org

Dear mentors,

I am looking for a sponsor for the package “parcimonie”:

 * Package name: parcimonie
   Version : 0.10.3-2
   Upstream Author : intrigeri 
 * URL : 
https://gaffer.ptitcanardnoir.org/intrigeri/code/parcimonie/
 * License : Artistic or GPL-1+
   Section : net


The source package can be found on mentors.debian.org:

https://mentors.debian.net/package/parcimonie

Alternatively, the packaging repository is available on alioth.d.o:

https://anonscm.debian.org/git/pkg-privacy/packages/parcimonie.git


Changes since the last upload:

  * debian/control
* Remove obsolete dependency (gnupg2) (Closes: #883975).
* Drop repeated `Section: net`.
* Declare compliance with Debian policy v4.1.2.0.
  No changes required.
  * Use HTTPS URIs for gaffer.ptitcanardnoir.org.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#883977: *** stack smashing detected ***: evolution terminated

[Joachim Breitner]

Hi,

rebuilding evolution fixes the problem for me.

Maybe re-assign to evolution?

Joachim

On Sat, 09 Dec 2017 17:38:48 -0500 Joachim Breitner  wrote:
> Package: evolution-data-server
> Version: 3.26.2.1-1.1
> Severity: grave
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi,
> 
> marking this as grave under the assumption that I am not the only one
> affected, please downgrade if it is specific to my setup for some
> reason.
> 
> I just upgraded evolution-data-server from 3.26.2.1-1 to 3.26.2.1-1.1,
> and now evolution will not start again: Even before a windows appears, I
> get the backtrace further down.  The various eds components start
> successfully. Removing ~/.cache/evolution does not help.
> 
> I have no idea what went wrong, but obviously things are failing quite
> badly…
> 
> Cheers,
> Joachim
> 
> 
> 
> ~ $ evolution
> *** stack smashing detected ***: evolution terminated
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x7230b)[0x7f6ac43b630b]
> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f6ac4441957]
> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f6ac4441920]
> /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19(+0x3d30c)[0x7f6ab799b30c]
> /usr/lib/evolution/libevolution-calendar.so.0(+0x97163)[0x7f6a90318163]
> /usr/lib/evolution/libevolution-calendar.so.0(+0x9d197)[0x7f6a9031e197]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f6ac79f0f9d]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22cae)[0x7f6ac7a03cae]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f6ac7a0c485]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f6ac7a0ce9f]
> /usr/lib/evolution/libevolution-calendar.so.0(e_cal_model_set_time_range+0xe1)[0x7f6a902d2b91]
> /usr/lib/evolution/modules/module-calendar.so(+0x20a49)[0x7f6a8ea16a49]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f6ac79f0f9d]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22cae)[0x7f6ac7a03cae]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f6ac7a0c485]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f6ac7a0ce9f]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_window_get_shell_view+0xb7)[0x7f6ac93a5797]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_window_set_active_view+0x42)[0x7f6ac93a6692]
> /usr/lib/evolution/libevolution-shell.so.0(+0x27176)[0x7f6ac93a7176]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_setv+0x23e)[0x7f6ac79f8a4e]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_set_property+0x1e)[0x7f6ac79f99de]
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x10dcc3)[0x7f6ac7d42cc3]
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_bind_with_mapping+0x311)[0x7f6ac7d459c1]
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_bind+0x2a)[0x7f6ac7d45cea]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_window_private_constructed+0x49b)[0x7f6ac93a880b]
> /usr/lib/evolution/libevolution-shell.so.0(+0x250bc)[0x7f6ac93a50bc]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x157a0)[0x7f6ac79f67a0]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_valist+0x3d0)[0x7f6ac79f8460]
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0x99)[0x7f6ac79f87d9]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_window_new+0x3b)[0x7f6ac93a51ab]
> /usr/lib/evolution/libevolution-shell.so.0(e_shell_create_shell_window+0xd5)[0x7f6ac9395765]
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

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

Bug#883976: Acknowledgement (nfs-common: Shell script executed by systemd to mount net /home * /var fails)

[Duncan Hare]

Systemcrl list-dpendencies
default.target
● ├─display-manager.service
● ├─dphys-swapfile.service
● ├─raspi-config.service
● ├─systemd-update-utmp-runlevel.service
● └─multi-user.target
●   ├─avahi-daemon.service
●   ├─console-setup.service
●   ├─cron.service
●   ├─dbus.service
●   ├─dhcpcd.service
●   ├─dphys-swapfile.service
●   ├─hciuart.service
●   ├─networking.service
●   ├─plymouth-quit-wait.service
●   ├─plymouth-quit.service
●   ├─raspberrypi-net-mods.service
●   ├─raspi-config.service
●   ├─rc-local.service
●   ├─rsync.service
●   ├─rsyslog.service
●   ├─sshswitch.service
●   ├─systemd-ask-password-wall.path
●   ├─systemd-logind.service
●   ├─systemd-update-utmp-runlevel.service
●   ├─systemd-user-sessions.service
●   ├─triggerhappy.service
●   ├─basic.target
●   │ ├─-.mount
●   │ ├─alsa-restore.service
●   │ ├─alsa-state.service
●   │ ├─setup-var-home.service <- Unit I used to mount /home & 
/var.
●   │ ├─tmp.mount
●   │ ├─paths.target
●   │ ├─slices.target
●   │ │ ├─-.slice
●   │ │ └─system.slice
●   │ ├─sockets.target
●   │ │ ├─avahi-daemon.socket
●   │ │ ├─dbus.socket
●   │ │ ├─systemd-initctl.socket
●   │ │ ├─systemd-journald-audit.socket
●   │ │ ├─systemd-journald-dev-log.socket
●   │ │ ├─systemd-journald.socket
●   │ │ ├─systemd-udevd-control.socket
●   │ │ ├─systemd-udevd-kernel.socket
●   │ │ └─triggerhappy.socket
●   │ ├─sysinit.target
●   │ │ ├─dev-hugepages.mount
●   │ │ ├─dev-mqueue.mount
●   │ │ ├─fake-hwclock.service
●   │ │ ├─keyboard-setup.service
●   │ │ ├─kmod-static-nodes.service
●   │ │ ├─plymouth-read-write.service
●   │ │ ├─plymouth-start.service
●   │ │ ├─proc-sys-fs-binfmt_misc.automount
●   │ │ ├─sys-fs-fuse-connections.mount
●   │ │ ├─sys-kernel-debug.mount
●   │ │ ├─systemd-ask-password-console.path
●   │ │ ├─systemd-binfmt.service
●   │ │ ├─systemd-hwdb-update.service
●   │ │ ├─systemd-journal-flush.service
●   │ │ ├─systemd-journald.service
●   │ │ ├─systemd-machine-id-commit.service
●   │ │ ├─systemd-modules-load.service
●   │ │ ├─systemd-random-seed.service
●   │ │ ├─systemd-sysctl.service
●   │ │ ├─systemd-timesyncd.service
●   │ │ ├─systemd-tmpfiles-setup-dev.service
●   │ │ ├─systemd-tmpfiles-setup.service
●   │ │ ├─systemd-udev-trigger.service
●   │ │ ├─systemd-udevd.service
●   │ │ ├─systemd-update-utmp.service
●   │ │ ├─cryptsetup.target
●   │ │ ├─local-fs.target
●   │ │ │ ├─boot.mount
●   │ │ │ ├─systemd-remount-fs.service
●   │ │ │ └─tmp.mount
●   │ │ └─swap.target
●   │ └─timers.target
●   │   ├─apt-daily-upgrade.timer
●   │   ├─apt-daily.timer
●   │   └─systemd-tmpfiles-clean.timer
●   ├─getty.target
●   │ ├─getty-static.service●   │ └─getty@tty1.service
●   ├─nfs-client.target
●   │ ├─auth-rpcgss-module.service
●   │ ├─nfs-blkmap.service
●   │ └─remote-fs-pre.target
●   └─remote-fs.target
● ├─-.mount
● └─nfs-client.target
●   ├─auth-rpcgss-module.service
●   ├─nfs-blkmap.service
●   └─remote-fs-pre.target

 Duncan Hare

714 931 7952

   

Bug#880467: jasperreports: CVE-2017-14941, CVE-2017-5528, CVE-2017-5529

[Emmanuel Bourg]

Le 09/12/2017 à 23:49, Moritz Mühlenhoff a écrit :

> Yeah, but libspring-java is not the issue here, it's jasperreports:
> We ship a jasperreports package of an uncooperative upstream which
> would need to see full backports across all supported suites since
> they don't tell us how to fix this with backports (or actually any
> vulnerability information).

Yes but since jasperreports isn't used anyway there is no need to
backport the fixes, that's the point I was trying to make. Until
jasperreports is actually used in Debian we can educate upstream about
the importance of documenting the security fixes.

Bug#880467: jasperreports: CVE-2017-14941, CVE-2017-5528, CVE-2017-5529

[Markus Koschany]

Am 09.12.2017 um 23:43 schrieb Emmanuel Bourg:
> Le 09/12/2017 à 23:29, Moritz Mühlenhoff a écrit :
> 
>> I'd say let's kick it out, then. We have a build dependency (and run time
>> dependencies) on libspring-java, can we axe it out there?
> 
> jasperreports is just a build dependency of some unused parts of
> libspring-java. No application in Debian needs it at run time. So these
> vulnerabilities can be safely ignored in the stable releases.

The situation with jasperreports is not great. I understand your
reasoning but I agree with Moritz that this is a more general issue with
jasperreports. My motivation to upgrade the library back in 2015 from
version 4 to 6 was libspring-java because this is something I use
personally and it is also a quite important piece of Java software.

However we should always be able to assess security vulnerabilities.
Just hoping that nobody will ever use the Debian library in some other
context is negligent. I would be really disappointed when I built an
Java app with Debian's system libraries and then I have to find out that
it is basically unsupported and contains security holes because it is
"just" a build-dependency for some other project.

To be fair: CVE-2017-5533 and CVE-2017-5528 probably do not affect us
because we ship the Jasperreports Library and not the server. Please
correct me if I am wrong.

Thus said maybe you are able to find the relevant changes or you get a
more helpful reply from the support guys. Otherwise I would try to
disable jasperreports in libspring-java which appears to be optional. (I
know probably requires another patch...)

For reference here is the link to my support request:

https://community.jaspersoft.com/questions/1072461/security-update-cve-2017-14941-cve-2017-5528-cve-2017-5529


Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#881936: apparmor: support usrmerge

[Héctor Orón Martínez]

Hello,

2017-12-07 19:12 GMT+01:00 intrigeri :
> Control: retitle -1 the upstream test suite does not support usrmerge
>
> intrigeri:
>> Can you please send this upstream as a merge request there:
>
>>   https://gitlab.com/apparmor/apparmor/
>
>> ?
>
>> If you prefer not to, I can forward. But IIRC it's not your first
>> contribution so on the long term, it would make sense if you would
>> send your proposed changes directly upstream :)
>
> Ping?

Sorry it felt through the cracks... here it is now...

https://gitlab.com/apparmor/apparmor/merge_requests/33

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#883212: blktap FTBFS with glibc 2.25

[Juhani Numminen]

Control: tags -1 fixed-upstream 

On Thu, 30 Nov 2017 20:38:55 +0200 Adrian Bunk  wrote:
> Source: blktap
> Version: 2.0.90-4
> Severity: serious
> Tags: buster sid
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/blktap.html
> 
> ...
> tap-ctl-allocate.c: In function 'tap_ctl_make_device':
> tap-ctl-allocate.c:114:13: error: In the GNU C Library, "makedev" is defined
> ...

Looks like this should be the fix:
https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=796dea37f

Thanks,
Juhani

Bug#880467: jasperreports: CVE-2017-14941, CVE-2017-5528, CVE-2017-5529

[Moritz Mühlenhoff]

On Sat, Dec 09, 2017 at 11:43:38PM +0100, Emmanuel Bourg wrote:
> Le 09/12/2017 à 23:29, Moritz Mühlenhoff a écrit :
> 
> > I'd say let's kick it out, then. We have a build dependency (and run time
> > dependencies) on libspring-java, can we axe it out there?
> 
> jasperreports is just a build dependency of some unused parts of
> libspring-java. No application in Debian needs it at run time. So these
> vulnerabilities can be safely ignored in the stable releases.

Yeah, but libspring-java is not the issue here, it's jasperreports:
We ship a jasperreports package of an uncooperative upstream which
would need to see full backports across all supported suites since
they don't tell us how to fix this with backports (or actually any
vulnerability information).

Cheers,
   Moritz

Bug#883622: transition: analitza 17.08

[Pino Toscano]

In data venerdì 8 dicembre 2017 19:52:13 CET, Emilio Pozuelo Monfort ha scritto:
> On 05/12/17 21:57, Pino Toscano wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Hi,
> > 
> > I would like to request a slot for the analitza 17.08.x transition.
> > There are only two affected sources:
> > - kalgebra (which will get a sourceful upload)
> > - cantor, which just needs a rebuild
> > 
> > I will wait for this weekend for the batch of 17.08 uploads I did last
> > weekend to migrate to testing: the reason is that the new versions of
> > analitza and kalgebra carry their translations files, right now shipped
> > as part of kde-l10n (and thus a coordinated upload is needed, I will
> > take care of it).
> 
> Ack.

Uploaded few hours ago, and analitza and kalgebra already built
everywhere.

-- 
Pino Toscano

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

Bug#883624: transition: libkf5kipi + marble 17.08

[Pino Toscano]

In data venerdì 8 dicembre 2017 19:53:03 CET, Emilio Pozuelo Monfort ha scritto:
> On 05/12/17 22:03, Pino Toscano wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Hi,
> > 
> > I would like to request a slot for the transitions of libkf5kipi 17.08
> > and marble 17.08.  I'm requesting a single slot for them as the impact
> > of each is limited, and they boh affect digikam (big source, so one
> > rebuild can be avoided).
> > 
> > The sources affected by libkf5kipi are:
> > - digikam
> > - gwenview
> > - kde-spectacle
> > - kphotoalbum
> > The sources affected by marble are:
> > - digikam
> > - kreport
> > - libkf5kgeomap
> > 
> > I will wait for this weekend for the batch of 17.08 uploads I did last
> > weekend to migrate to testing: the reason is that the new versions of
> > libkf5kipi and marble carry their translations files, right now shipped
> > as part of kde-l10n (and thus a coordinated upload is needed, I will
> > take care of it).
> 
> You can go ahead.

Uploaded libkf5kipi, marble and libkf5kgeomap few hours ago, and all of
them already built everywhere.

-- 
Pino Toscano

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

Bug#880467: jasperreports: CVE-2017-14941, CVE-2017-5528, CVE-2017-5529

[Emmanuel Bourg]

Le 09/12/2017 à 23:29, Moritz Mühlenhoff a écrit :

> I'd say let's kick it out, then. We have a build dependency (and run time
> dependencies) on libspring-java, can we axe it out there?

jasperreports is just a build dependency of some unused parts of
libspring-java. No application in Debian needs it at run time. So these
vulnerabilities can be safely ignored in the stable releases.

Emmanuel Bourg

Bug#794295: lintian: please complain about development packages that make cross building impossible

[Chris Lamb]

tags 794295 + pending
thanks

Hey Helmut,

I've implemented this in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=fc226826c81a5642779e422d927aa334e2ff1587

I hope it's useful :)


Regards,

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

Bug#883977: *** stack smashing detected ***: evolution terminated

[Joachim Breitner]

Package: evolution-data-server
Version: 3.26.2.1-1.1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

marking this as grave under the assumption that I am not the only one
affected, please downgrade if it is specific to my setup for some
reason.

I just upgraded evolution-data-server from 3.26.2.1-1 to 3.26.2.1-1.1,
and now evolution will not start again: Even before a windows appears, I
get the backtrace further down.  The various eds components start
successfully. Removing ~/.cache/evolution does not help.

I have no idea what went wrong, but obviously things are failing quite
badly…

Cheers,
Joachim



~ $ evolution
*** stack smashing detected ***: evolution terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7230b)[0x7f6ac43b630b]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f6ac4441957]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f6ac4441920]
/usr/lib/x86_64-linux-gnu/libecal-1.2.so.19(+0x3d30c)[0x7f6ab799b30c]
/usr/lib/evolution/libevolution-calendar.so.0(+0x97163)[0x7f6a90318163]
/usr/lib/evolution/libevolution-calendar.so.0(+0x9d197)[0x7f6a9031e197]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f6ac79f0f9d]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22cae)[0x7f6ac7a03cae]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f6ac7a0c485]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f6ac7a0ce9f]
/usr/lib/evolution/libevolution-calendar.so.0(e_cal_model_set_time_range+0xe1)[0x7f6a902d2b91]
/usr/lib/evolution/modules/module-calendar.so(+0x20a49)[0x7f6a8ea16a49]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f6ac79f0f9d]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22cae)[0x7f6ac7a03cae]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xa75)[0x7f6ac7a0c485]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f6ac7a0ce9f]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_window_get_shell_view+0xb7)[0x7f6ac93a5797]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_window_set_active_view+0x42)[0x7f6ac93a6692]
/usr/lib/evolution/libevolution-shell.so.0(+0x27176)[0x7f6ac93a7176]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_setv+0x23e)[0x7f6ac79f8a4e]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_set_property+0x1e)[0x7f6ac79f99de]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x10dcc3)[0x7f6ac7d42cc3]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_bind_with_mapping+0x311)[0x7f6ac7d459c1]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_settings_bind+0x2a)[0x7f6ac7d45cea]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_window_private_constructed+0x49b)[0x7f6ac93a880b]
/usr/lib/evolution/libevolution-shell.so.0(+0x250bc)[0x7f6ac93a50bc]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x157a0)[0x7f6ac79f67a0]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_valist+0x3d0)[0x7f6ac79f8460]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0x99)[0x7f6ac79f87d9]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_window_new+0x3b)[0x7f6ac93a51ab]
/usr/lib/evolution/libevolution-shell.so.0(e_shell_create_shell_window+0xd5)[0x7f6ac9395765]
evolution(+0x432f)[0x55d1949af32f]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7f6ac7717e15]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4b1e0)[0x7f6ac77181e0]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xc2)[0x7f6ac77184f2]
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_main+0x85)[0x7f6ac8200345]
evolution(main+0x6d4)[0x55d1949af144]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f6ac4364561]
evolution(_start+0x2a)[0x55d1949af1fa]
=== Memory map: 
55d1949ab000-55d1949b2000 r-xp  fd:01 12719680   
/usr/bin/evolution
55d194bb2000-55d194bb3000 r--p 7000 fd:01 12719680   
/usr/bin/evolution
55d194bb3000-55d194bb4000 rw-p 8000 fd:01 12719680   
/usr/bin/evolution
55d1955c2000-55d196b22000 rw-p  00:00 0  [heap]
7f6a5000-7f6a50022000 rw-p  00:00 0 
7f6a50022000-7f6a5400 ---p  00:00 0 
7f6a5400-7f6a54022000 rw-p  00:00 0 
7f6a54022000-7f6a5800 ---p  00:00 0 
7f6a5800-7f6a58022000 rw-p  00:00 0 
7f6a58022000-7f6a5c00 ---p  00:00 0 
7f6a5e7fd000-7f6a5e7fe000 ---p  00:00 0 
7f6a5e7fe000-7f6a5effe000 rw-p  00:00 0 
7f6a5effe000-7f6a5efff000 ---p  00:00 0 
7f6a5efff000-7f6a5f7ff000 rw-p  00:00 0 
7f6a5f7ff000-7f6a5f80 ---p  00:00 0 
7f6a5f80-7f6a6000 rw-p  00:00 0 
7f6a6000-7f6a60022000 rw-p  00:00 0 
7f6a60022000-7f6a6400 ---p  00:00 0 
7f6a6400-7f6a64022000 rw-p  00:00 0 
7f6a64022000-7f6a6800 ---p  00:00 0 
7f6a6800-7f6a68022000 rw-p  00:00 0 
7f6a68022000-7f6a6c00 ---p  00:00 0 

Bug#883976: nfs-common: Shell script executed by systemd to mount net /home * /var fails

[Duncan Hare]

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

Netboot file system on /devnfs (except that dev/nfs causes errors) so rootfs is 
mounted per fstab.
Trying to mount nfs file system for var and home and the mount fails.

When linux is fully up, and I'm logged into a user, su to root
the file systems can be mounted with no error message.

Why during boot are the messages:

mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/var  /var in /etc/fstab
mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/home /home in /etc/fstab

being generated as though the root id during boot is a normal unprivilaged 
unser?

fstab:

proc /proc   procdefaults   
0 0
/dev/mmcblk0p1   /boot   vfatdefaults,ro
0 2
#PARTUUID=62bc0a1f-02/   ext4defaults,noatime   
0 1
192.168.1.10:/nfsroot/r.32.test  /   nfs defaults,rw
0 0
#192.168.1.10:/nfsroot/b827eb/c23849/var  /var   nfs defaults,rw
0 0
#192.168.1.10:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw   
 0 0
#browne:/nfsroot/b827eb/c23849/home  /home   nfs defaults,rw
0 0
tmpfs/tmptmpfs   
nodev,nosuid,size=1%,mode=1777 0 0

systemctl unit:

[Unit]
Description=Setup directory tree in var filesystem
DefaultDependencies=no
After=local-fs.target
Before=basic.target

[Service]
Type=oneshot
ExecStart=/usr/bin/setup-var-home.sh

[Install]
WantedBy=basic.target

hostname:
b827ebc23849

/usr/bin/setup-var-home.sh:
#!/bin/bash
H=$(hostname);
#H="b827ebc23849";
/bin/mount 192.168.1.10:/nsfroot/${H:0:-6}"/"${H:6:12}"/var  /var";
/bin/mount 192.168.1.10:/nsfroot/${H:0:-6}"/"${H:6:12}"/home /home";

systemctl status

● setup-var-home.service - Setup directory tree in var filesystem
   Loaded: loaded (/lib/systemd/system/setup-var-home.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2017-12-09 13:43:43 PST; 22min 
ago
  Process: 267 ExecStart=/usr/bin/setup-var-home.sh (code=exited, 
status=1/FAILURE)
 Main PID: 267 (code=exited, status=1/FAILURE)

Dec 09 13:43:42 b827ebc23849 systemd[1]: Starting Setup directory tree in var 
filesystem...
Dec 09 13:43:43 b827ebc23849 setup-var-home.sh[267]: mount: can't find 
192.168.1.10:/nsfroot/b827eb/c23849/var  /var in /etc/fstab
Dec 09 13:43:43 b827ebc23849 setup-var-home.sh[267]: mount: can't find 
192.168.1.10:/nsfroot/b827eb/c23849/home /home in /etc/fstab
Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Main process 
exited, code=exited, status=1/FAILURE
Dec 09 13:43:43 b827ebc23849 systemd[1]: Failed to start Setup directory tree 
in var filesystem.
Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Unit entered 
failed state.
Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Failed with 
result 'exit-code'.

mount command output

192.168.1.10:/nfsroot/r.32.test on / type nfs 
(rw,relatime,vers=3,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.10,mountvers=3,mountp$
devtmpfs on /dev type devtmpfs 
(rw,relatime,size=405220k,nr_inodes=101305,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/net_cls type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=8200k)
/dev/mmcblk0p1 on /boot type vfat 
(ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)

Bug#880467: jasperreports: CVE-2017-14941, CVE-2017-5528, CVE-2017-5529

[Moritz Mühlenhoff]

On Wed, Nov 01, 2017 at 08:42:43PM +0100, Markus Koschany wrote:
> Short update:
> 
> One staff member told me that my options are to read the advisories,
> which don't contain any detailed information or patches, or, if I have a
> commercial license, to contact support. Great, let's buy a license to
> get more information about security bugs.

WTF

> So far the only viable option would be to upgrade to the latest upstream
> release and backport that to Wheezy, Jessie and Stretch as well but I'm
> not thrilled to maintain another Oracle-like Java package when it comes
> to security bugs.

I'd say let's kick it out, then. We have a build dependency (and run time
dependencies) on libspring-java, can we axe it out there?

Cheers,
Moritz

Bug#883975: parcimonie should not depend on gnupg2 (transitional package)

[Nicolas Braud-Santoni]

Package: parcimonie
Version: 0.10.3-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

parcimonie depends on both gnupg and gnupg2, and the later is a transitional
package for the former.  This prevents me from uninstalling the trans. package.


Best,

  nicoo

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

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

Versions of packages parcimonie depends on:
ii  dirmngr  2.2.3-1
ii  gnupg2.2.3-1
ii  gnupg2   2.2.3-1
ii  libclone-perl0.39-1
ii  libconfig-general-perl   2.63-1
ii  libfile-homedir-perl 1.002-1
ii  libfile-which-perl   1.21-1
ii  libgnupg-interface-perl  0.52-9
ii  libipc-system-simple-perl1.25-3
ii  liblist-moreutils-perl   0.416-1+b3
ii  libmoo-perl  2.003003-1
ii  libmoox-late-perl0.015-3
ii  libmoox-options-perl 4.023-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.104-1
ii  libtime-duration-parse-perl  0.13-1
ii  libtry-tiny-perl 0.28-1
ii  libtype-tiny-perl1.002001-1
ii  libtypes-path-tiny-perl  0.005-1
ii  perl 5.26.1-3
ii  torsocks 2.2.0-2

Versions of packages parcimonie recommends:
ii  libglib-perl3:1.326-1+b2
ii  libgtk3-perl0.032-1
ii  liblocale-gettext-perl  1.07-3+b3
ii  libnet-dbus-glib-perl   0.33.0-2+b2
ii  libnet-dbus-perl1.1.0-4+b3
ii  libpango-perl   1.227-2+b1
ii  libtime-duration-perl   1.20-1
ii  tor 0.3.1.9-1

parcimonie suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAlosY8wZHG5pY29sYXNA
YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z4+NAD/4gw1dkydH3iJf5tADE7tMK
GLQw19lz3Z0fp5h8vWDe7sMvhRlNv4vDDzOg7AFIMOks0iI6F6iSZm3SAlusgx96
mx7QJvPIKZL2NyKFhb0OnToqQvvdIXegnQ2buJ7CY0u8qmIf/gA4XOyznk2a/Ow4
6do7advTOHup0b8Kuk5i3ZXy5inERiFCsWfpgxC5B40eQMQO7uBZmlASRe15dRPL
/Tl3rSTHa2hN9Wd7yeeVPhTZAgqInArISFgm2eKZQMtgJn9F4LVmlzTUlV/5J3it
769kiZyVYtmLuRYuDactPnr44ndn8R3fEDurrWnIn7FRtik1BfLezFd4gSmBFbIB
H/gEdICALYbI4e8USO3N8I/QRvSKO/PbyVpvWo15svOsvQyFEI1saDSpgeG5aJxw
htLSqCArfhb0Qk5rndDDma5poABGn/m0hdxWgWpFZYf0kKYxqKiDAUT65itXVlK1
wgHmBU/rIY4PcqOAZHOlH9BpJRh+Ob12mqDdBP6rRvbIaC3KTID8Y910w1AyYJ4y
tI9r9Z50PCdvGNGMpmuerEgDGHc9PMTnByji6YMIh2s3sG/Nce0xtx8CUWEdj2so
vbaLmw1VJlEJqQMlK3FxrUy0uWlrYjG32aoLpETDIfP6WiPU6IV4WGMBUOXLpoSV
EGOZg0xF3HdBrNODknfNTQ==
=+YM9
-END PGP SIGNATURE-

Bug#883974: abinit: FTBFS on mips64el: test failures

[Andreas Beckmann]

Source: abinit
Version: 8.0.8-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

abinit FTBFS on mips64el:

https://buildd.debian.org/status/fetch.php?pkg=abinit=mips64el=8.0.8-4=1511985974=0


Andreas

Bug#883973: fonts-wine: Please move the ttf/otf fonts to /usr/share/fonts

[Rogério Brito]

Package: fonts-wine
Version: 2.0.3-1
Severity: wishlist

Please, 

For the benefit of other programs (thinking here especially of evince/atril
and other PDF viewers, but also for people that need to collaborate with
Windows users in an office environment), please put the Tahoma clone and
other fonts under /usr/share/fonts.

This will make what we already have in the repos much more useful, in a
Gelstalt-like manner.


Thanks,

Rogério.


-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

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

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.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 fonts-wine is related to:
ii  fonts-wine  2.0.3-1
ii  wine2.0.3-1
ii  wine32  2.0.3-1
pn  wine64  

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#883972: samba: FTBFS on kfreebsd: error: storage size of 'cr' isn't known

[Andreas Beckmann]

Source: samba
Version: 2:4.7.3+dfsg-1
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

that 4.7.x uploads of samba FTBFS on kfreebsd:

https://buildd.debian.org/status/fetch.php?pkg=samba=kfreebsd-amd64=2%3A4.7.3%2Bdfsg-1=1511513078=0
https://buildd.debian.org/status/fetch.php?pkg=samba=kfreebsd-i386=2%3A4.7.3%2Bdfsg-1=1511474624=0

[...]
08:44:02 runner /usr/bin/gcc -g -O2 
-fdebug-prefix-map=/«BUILDDIR»/samba-4.7.3+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIE -fPIC -D_REENTRANT 
-D_POSIX_PTHREAD_SEMANTICS 
-DCTDB_HELPER_BINDIR="/usr/lib/x86_64-kfreebsd-gnu/ctdb" 
-DLOGDIR="/var/log/ctdb" -DCTDB_ETCDIR="/etc/ctdb" 
-DCTDB_VARDIR="/var/lib/ctdb" -DCTDB_RUNDIR="/var/run/ctdb" -fstack-protector 
-DSTATIC_ctdb_takeover_tests_MODULES=NULL 
-DSTATIC_ctdb_takeover_tests_MODULES_PROTO=extern void 
__ctdb_takeover_tests_dummy_module_proto(void) -MD -Wdate-time 
-D_FORTIFY_SOURCE=2 -Idefault/ctdb -I../ctdb -Idefault/ctdb/include 
-I../ctdb/include -Idefault/include/public -I../include/public 
-Idefault/source4 -I../source4 -Idefault/lib -I../lib -Idefault/source4/lib 
-I../source4/lib -Idefault/source4/include -I../source4/include 
-Idefault/include -I../include -Idefault/lib/replace -I../lib/replace -Idefault 
-I.. -Idefault/lib/util/charset -I../lib/util/charset -Idefault/libcli/util 
-I../libcli/util -Idefault/dynconfig -I../dynconfig -Idefault/lib/crypto 
-I../lib/crypto -I/usr/local/include -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 
-D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 
../ctdb/tests/src/ipalloc_read_known_ips.c -c -o 
default/ctdb/tests/src/ipalloc_read_known_ips_132.o
[2705/4004] Compiling ctdb/tests/src/fake_ctdbd.c
08:44:02 runner /usr/bin/gcc -g -O2 
-fdebug-prefix-map=/«BUILDDIR»/samba-4.7.3+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIE -fPIC -D_REENTRANT 
-D_POSIX_PTHREAD_SEMANTICS 
-DCTDB_HELPER_BINDIR="/usr/lib/x86_64-kfreebsd-gnu/ctdb" 
-DLOGDIR="/var/log/ctdb" -DCTDB_ETCDIR="/etc/ctdb" 
-DCTDB_VARDIR="/var/lib/ctdb" -DCTDB_RUNDIR="/var/run/ctdb" -fstack-protector 
-DSTATIC_fake_ctdbd_MODULES=NULL -DSTATIC_fake_ctdbd_MODULES_PROTO=extern void 
__fake_ctdbd_dummy_module_proto(void) -MD -Wdate-time -D_FORTIFY_SOURCE=2 
-Idefault/ctdb -I../ctdb -Idefault/include/public -I../include/public 
-Idefault/source4 -I../source4 -Idefault/lib -I../lib -Idefault/source4/lib 
-I../source4/lib -Idefault/source4/include -I../source4/include 
-Idefault/include -I../include -Idefault/lib/replace -I../lib/replace 
-Idefault/ctdb/include -I../ctdb/include -Idefault -I.. 
-Idefault/lib/util/charset -I../lib/util/charset -Idefault/libcli/util 
-I../libcli/util -Idefault/lib/crypto -I../lib/crypto -Idefault/lib/async_req 
-I../lib/async_req -Idefault/dynconfig -I../dynconfig -I/usr/local/include 
-D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 
../ctdb/tests/src/fake_ctdbd.c -c -o default/ctdb/tests/src/fake_ctdbd_134.o
[2706/4004] Compiling ctdb/tests/src/ipalloc_read_known_ips.c
08:44:02 runner /usr/bin/gcc -g -O2 
-fdebug-prefix-map=/«BUILDDIR»/samba-4.7.3+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIE -fPIC -D_REENTRANT 
-D_POSIX_PTHREAD_SEMANTICS 
-DCTDB_HELPER_BINDIR="/usr/lib/x86_64-kfreebsd-gnu/ctdb" 
-DLOGDIR="/var/log/ctdb" -DCTDB_ETCDIR="/etc/ctdb" 
-DCTDB_VARDIR="/var/lib/ctdb" -DCTDB_RUNDIR="/var/run/ctdb" -fstack-protector 
-DSTATIC_fake_ctdbd_MODULES=NULL -DSTATIC_fake_ctdbd_MODULES_PROTO=extern void 
__fake_ctdbd_dummy_module_proto(void) -MD -Wdate-time -D_FORTIFY_SOURCE=2 
-Idefault/ctdb -I../ctdb -Idefault/include/public -I../include/public 
-Idefault/source4 -I../source4 -Idefault/lib -I../lib -Idefault/source4/lib 
-I../source4/lib -Idefault/source4/include -I../source4/include 
-Idefault/include -I../include -Idefault/lib/replace -I../lib/replace 
-Idefault/ctdb/include -I../ctdb/include -Idefault -I.. 
-Idefault/lib/util/charset -I../lib/util/charset -Idefault/libcli/util 
-I../libcli/util -Idefault/lib/crypto -I../lib/crypto -Idefault/lib/async_req 
-I../lib/async_req -Idefault/dynconfig -I../dynconfig -I/usr/local/include 
-D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 
../ctdb/tests/src/ipalloc_read_known_ips.c -c -o 
default/ctdb/tests/src/ipalloc_read_known_ips_134.o
../ctdb/tests/src/fake_ctdbd.c: In function 'client_send':
../ctdb/tests/src/fake_ctdbd.c:3081:15: error: storage size of 'cr' isn't known
  struct ucred cr;
   ^~
../ctdb/tests/src/fake_ctdbd.c:3082:25: error: invalid application of 'sizeof' 
to incomplete type 'struct ucred'
  socklen_t crl = sizeof(struct ucred);
 ^~
../ctdb/tests/src/fake_ctdbd.c:3095:35: error: 'SO_PEERCRED' undeclared (first 
use in this function); did you mean 'SO_PEERLABEL'?
  ret = getsockopt(fd, SOL_SOCKET, SO_PEERCRED, , );
   ^~~
   SO_PEERLABEL

Bug#877966: This is happening again

[Santiago Vila]

reopen 877966
thanks

Hi.

While building a lot of packages today, I found that this is happening again:

503  Quorum weight not reached [IP: 151.101.112.204 80]


Thanks.

Bug#883971: gparted won't start on Wayland

[Byron]

Package: gparted
Version: 0.25.0-1+b1
Severity: important

Dear Maintainer,

I am running Debian 9.3 with GNOME 3.22.

As the title suggests, gparted runs fine on Xorg but has problems with
Xwayland.

When running gparted as root on a GNOME Wayland session, I get:

Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/home.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1001.mount → /dev/null.
Created symlink /run/systemd/system/run-user-117.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
No protocol specified

(gpartedbin:9080): Gtk-WARNING **: cannot open display: :0
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/home.mount.
Removed /run/systemd/system/run-user-1001.mount.
Removed /run/systemd/system/run-user-117.mount.
Removed /run/systemd/system/tmp.mount.

The program immediately exits after these messages without popping up any sort
of graphical window. However, when I run the same gparted command from an Xorg
session (as root), gparted starts up fine and works normally.

Thank you for taking your time to read this. =)

Byron

P.S. I marked this bug as "important" because of the universal desire to
replace Xorg with Wayland. Any developer please feel free to change the
severity.



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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 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 gparted depends on:
ii  libatkmm-1.6-1v5  2.24.2-2
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libglib2.0-0  2.50.3-2
ii  libglibmm-2.4-1v5 2.50.0-1
ii  libgtk2.0-0   2.24.31-2
ii  libgtkmm-2.4-1v5  1:2.24.5-1
ii  libpangomm-1.4-1v52.40.1-3
ii  libparted-fs-resize0  3.2-17
ii  libparted23.2-17
ii  libsigc++-2.0-0v5 2.10.0-1
ii  libstdc++66.3.0-18
ii  libuuid1  2.29.2-1

gparted recommends no packages.

Versions of packages gparted suggests:
pn  dmraid 
ii  dmsetup2:1.02.137-2
ii  dosfstools 4.1-1
pn  gpart  
pn  jfsutils   
pn  kpartx 
pn  mtools 
ii  ntfs-3g1:2016.2.22AR.1+dfsg-1
pn  reiser4progs   
pn  reiserfsprogs  
pn  xfsprogs   
ii  yelp   3.22.0-1

-- no debconf information

Bug#883684: fluidsynth: symbols changed on !linux architectures

[Andreas Beckmann]

Followup-For: Bug #883684
Control: found -1 1.1.8-2

Hi,

there were three groups of missing symbols on !linux, you only handled
one of them in 1.1.8-2.


Andreas

Bug#859649: debian-policy: Please add CC0-1.0 to common-licenseso

[Sean Whitton]

Hello,

On Sat, Dec 09 2017, Bill Allombert wrote:

> What work are you referring to ?

Longer copyright files are more painful to edit.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#211353: chrony: please add debconf question for entering timeserver

[Noah Meyerhans]

On Mon, Nov 16, 2015 at 11:30:05PM +0100, Vincent Blut wrote:
> Marking as wontfix as I’m definitely not sure implementing the debconf
> mechanism
> for such thing is the right approach.

Hi. At a recent debian-cloud sprint, we made the choice to switch from
ntpd to chrony for our cloud images. As some of the cloud providers
offer their own local NTP services, we'd like the ability to specify
an entry for such a source in the default images for a given service. As
such, I'd like to ask on behalf of the cloud team that you reconsider
providing a debconf option to select a time source. I'm happy to send
patches if that'll help.

My suggestion would be to maintain the current pool.ntp.org entry as the
default, and offer a debconf option to override this value at debconf's
low priority so it won't bother most people installing the package.

See, for example, the following docs about the AWS NTP service,
https://aws.amazon.com/about-aws/whats-new/2017/11/introducing-the-amazon-time-sync-service/
and
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html#configure-amazon-time-service

Thanks
noah



signature.asc
Description: PGP signature

Bug#883970: qtwebsockets-opensource-src FTCBFS: does not pass cross tools to qmake

[Helmut Grohne]

Source: qtwebsockets-opensource-src
Version: 5.9.2-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

qtwebsockets-opensource-src fails to cross build from source, because it
does not pass cross tools to qmake. Nowadays, debhelper should handle
that task and simply deferring it to dh_auto_configure makes the cross
build succeed. Please consider applying the attached.

Helmut
diff --minimal -Nru qtwebsockets-opensource-src-5.9.2/debian/changelog 
qtwebsockets-opensource-src-5.9.2/debian/changelog
--- qtwebsockets-opensource-src-5.9.2/debian/changelog  2017-10-28 
10:26:24.0 +0200
+++ qtwebsockets-opensource-src-5.9.2/debian/changelog  2017-12-09 
22:07:12.0 +0100
@@ -1,3 +1,10 @@
+qtwebsockets-opensource-src (5.9.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 09 Dec 2017 22:07:12 +0100
+
 qtwebsockets-opensource-src (5.9.2-3) unstable; urgency=medium
 
   * Make the tests results not fatal also on mips64el.
diff --minimal -Nru qtwebsockets-opensource-src-5.9.2/debian/control 
qtwebsockets-opensource-src-5.9.2/debian/control
--- qtwebsockets-opensource-src-5.9.2/debian/control2017-10-28 
10:26:24.0 +0200
+++ qtwebsockets-opensource-src-5.9.2/debian/control2017-12-09 
22:07:10.0 +0100
@@ -8,7 +8,7 @@
Timo Jyrinki ,
Dmitry Shachnev ,
Simon Quigley 
-Build-Depends: debhelper (>= 10.3),
+Build-Depends: debhelper (>= 10.9.2~),
libssl1.0-dev,
pkg-kde-tools,
qml-module-qtquick2,
diff --minimal -Nru qtwebsockets-opensource-src-5.9.2/debian/rules 
qtwebsockets-opensource-src-5.9.2/debian/rules
--- qtwebsockets-opensource-src-5.9.2/debian/rules  2017-10-28 
10:26:24.0 +0200
+++ qtwebsockets-opensource-src-5.9.2/debian/rules  2017-12-09 
22:06:51.0 +0100
@@ -20,7 +20,7 @@
rm -fv include/QtWebSockets/QtWebSocketsDepends
 
 override_dh_auto_configure:
-   qmake QT_BUILD_PARTS+=tests
+   dh_auto_configure -- QT_BUILD_PARTS+=tests
 
 override_dh_auto_build-indep:
dh_auto_build -Smakefile -- docs

Bug#883969: debian-policy: please add CC-BY-SA-4.0 to common licenses

[Markus Koschany]

Package: debian-policy
Version: 4.1.2.0
Severity: normal

Hi,

as discussed on debian-devel [1] I would like to see that more DFSG
licenses are added to /usr/share/common-licenses and that package
maintainers are just allowed to reference them.

License: CC-BY-SA-4.0
Source: https://creativecommons.org/licenses/by-sa/4.0/
Example packages: 
https://wiki.debian.org/DFSGLicenses#Creative_Commons_Attribution_Share-Alike_.28CC-BY-SA.29_v4.0

Regards,

Markus

[1] https://lists.debian.org/debian-devel/2017/12/msg00209.html

Bug#883967: qtwebkit-examples-opensource-src FTCBFS: does not pass cross tools to qmake

[Helmut Grohne]

Source: qtwebkit-examples-opensource-src
Version: 5.9.1+dfsg-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

qtwebkit-examples-opensource-src fails to cross build from source,
because it does not pass cross tools to qmake. Nowadays, debhelper
should handle that task and simply deferring it to dh_auto_configure
makes the cross build succeed. Please consider applying the attached.

Helmut
diff --minimal -Nru 
qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/changelog 
qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/changelog
--- qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/changelog
2017-08-16 19:27:59.0 +0200
+++ qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/changelog
2017-12-09 21:55:19.0 +0100
@@ -1,3 +1,10 @@
+qtwebkit-examples-opensource-src (5.9.1+dfsg-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 09 Dec 2017 21:55:19 +0100
+
 qtwebkit-examples-opensource-src (5.9.1+dfsg-2) unstable; urgency=medium
 
   * Release to unstable.
diff --minimal -Nru qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/control 
qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/control
--- qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/control  2017-08-16 
19:27:18.0 +0200
+++ qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/control  2017-12-09 
21:26:31.0 +0100
@@ -8,7 +8,7 @@
Felix Geyer ,
Timo Jyrinki ,
Dmitry Shachnev 
-Build-Depends: debhelper (>= 9.20160114~),
+Build-Depends: debhelper (>= 10.9.2~),
libglib2.0-dev,
libicu-dev,
libqt5opengl5-dev (>= 5.9.0+dfsg~),
diff --minimal -Nru qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/rules 
qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/rules
--- qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/rules2017-07-26 
23:47:25.0 +0200
+++ qtwebkit-examples-opensource-src-5.9.1+dfsg/debian/rules2017-12-09 
21:26:12.0 +0100
@@ -13,9 +13,6 @@
 %:
dh $@ --parallel
 
-override_dh_auto_configure:
-   qmake
-
 override_dh_auto_clean:
dh_auto_clean
rm -rf doc/qtwebkitexamples doc/qtwebkitexamples.qch .qmake.cache

Bug#883968: debian-policy: please add CC-BY-SA-3.0 to common licenses

[Markus Koschany]

Package: debian-policy
Version: 4.1.2.0
Severity: normal

Hi,

as discussed on debian-devel [1] I would like to see that more DFSG
licenses are added to /usr/share/common-licenses and that package
maintainers are just allowed to reference them.

License: CC-BY-SA-3.0
Source: https://creativecommons.org/licenses/by-sa/3.0/
Example packages: 
https://wiki.debian.org/DFSGLicenses#Creative_Commons_Attribution_Share-Alike_.28CC-BY-SA.29_v3.0

Regards,

Markus

[1] https://lists.debian.org/debian-devel/2017/12/msg00209.html

Bug#883966: debian-policy: please add MIT/Expat to common licenses

[Markus Koschany]

Package: debian-policy
Version: 4.1.2.0
Severity: normal

Hi,

as discussed on debian-devel [1] I would like to see that more DFSG
licenses are added to /usr/share/common-licenses and that package
maintainers are just allowed to reference them.

License: MIT / Expat
Source: https://opensource.org/licenses/mit-license.php
Example packages: https://wiki.debian.org/DFSGLicenses#The_MIT_License

Regards,

Markus

[1] https://lists.debian.org/debian-devel/2017/12/msg00209.html

Bug#883965: nm-connection-editor crashes when opening a connection

[Marco d'Itri]

Package: network-manager-gnome
Version: 1.8.6-1
Severity: important

Since 1-2 months, nm-connection-editor immediately crashes when I click 
on the "modify" button.

(gdb) run
Starting program: /usr/bin/nm-connection-editor 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeade2700 (LWP 29377)]
[New Thread 0x7fffea5e1700 (LWP 29378)]
[New Thread 0x7fffe9542700 (LWP 29379)]
[New Thread 0x7fffe8d41700 (LWP 29380)]

Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault.
0x77bab4d3 in modules_initialized (object=, 
res=0x55f21f40, user_data=user_data@entry=0x55fac380) at 
src/libnma/nma-cert-chooser-button.c:98
98  src/libnma/nma-cert-chooser-button.c: No such file or directory.
(gdb) bt
#0  0x77bab4d3 in modules_initialized (object=, 
res=0x55f21f40, user_data=user_data@entry=0x55fac380) at 
src/libnma/nma-cert-chooser-button.c:98
#1  0x754ecd23 in process_result (unused=0x0, call=0x55f21f40) at 
gck/gck-call.c:151
#2  process_completed (klass=) at gck/gck-call.c:165
#3  0x754ed65c in _gck_call_async_go (call=0x55fbb1d0) at 
gck/gck-call.c:498
#4  0x766d6745 in g_type_create_instance (type=) at 
../../../../gobject/gtype.c:1866
#5  0x766b75e8 in g_object_new_internal 
(class=class@entry=0x55f22400, params=params@entry=0x7fffb080, 
n_params=n_params@entry=2) at ../../../../gobject/gobject.c:1797
#6  0x766b9460 in g_object_new_valist (object_type=93825003062448, 
first_property_name=first_property_name@entry=0x77eb "model", 
var_args=var_args@entry=0x7fffb1d0) at ../../../../gobject/gobject.c:2120
#7  0x766b97d9 in g_object_new (object_type=, 
first_property_name=first_property_name@entry=0x77eb "model") at 
../../../../gobject/gobject.c:1640
#8  0x77babe12 in nma_cert_chooser_button_new 
(flags=flags@entry=NMA_CERT_CHOOSER_BUTTON_FLAG_NONE) at 
src/libnma/nma-cert-chooser-button.c:447
#9  0x77bac8ae in init (cert_chooser=0x5588c3c0) at 
src/libnma/nma-pkcs11-cert-chooser.c:481
#10 0x77ba7eab in constructor (type=, 
n_construct_properties=, construct_properties=) 
at src/libnma/nma-cert-chooser.c:635
#11 0x766b741e in g_object_new_with_custom_constructor (n_params=2, 
params=0x7fffb550, class=0x55fa7ca0) at 
../../../../gobject/gobject.c:1715
#12 g_object_new_internal (class=class@entry=0x55fa7ca0, 
params=params@entry=0x7fffb550, n_params=n_params@entry=2) at 
../../../../gobject/gobject.c:1795
#13 0x766b9460 in g_object_new_valist (object_type=93825003059152, 
first_property_name=, var_args=var_args@entry=0x7fffb6a0) at 
../../../../gobject/gobject.c:2120
#14 0x766b97d9 in g_object_new (object_type=, 
first_property_name=) at ../../../../gobject/gobject.c:1640
#15 0x555a25fc in ?? ()
#16 0x5559e427 in ?? ()
#17 0x555a05af in ?? ()
#18 0x555746a3 in ?? ()
#19 0x766b1f9d in g_closure_invoke (closure=0x55d9e0d0, 
return_value=0x0, n_param_values=2, param_values=0x7fffbaf0, 
invocation_hint=0x7fffba70) at ../../../../gobject/gclosure.c:804
#20 0x766c4cae in signal_emit_unlocked_R 
(node=node@entry=0x55c14d40, detail=detail@entry=0, 
instance=instance@entry=0x55bcdba0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffbaf0) at 
../../../../gobject/gsignal.c:3635
#21 0x766cd485 in g_signal_emit_valist (instance=0x55bcdba0, 
signal_id=, detail=0, var_args=var_args@entry=0x7fffbcc0) at 
../../../../gobject/gsignal.c:3391
#22 0x766cde9f in g_signal_emit (instance=, 
signal_id=, detail=) at 
../../../../gobject/gsignal.c:3447
#23 0x55571453 in ?? ()
#24 0x5556beed in ?? ()
#25 0x5556d746 in ?? ()
#26 0x766b1f9d in g_closure_invoke (closure=0x55acaeb0, 
return_value=0x0, n_param_values=1, param_values=0x7fffc030, 
invocation_hint=0x7fffbfb0) at ../../../../gobject/gclosure.c:804
#27 0x766c4cae in signal_emit_unlocked_R 
(node=node@entry=0x559cad40, detail=detail@entry=0, 
instance=instance@entry=0x55b54590, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffc030) at 
../../../../gobject/gsignal.c:3635
#28 0x766cd485 in g_signal_emit_valist 
(instance=instance@entry=0x55b54590, signal_id=signal_id@entry=274, 
detail=0, var_args=var_args@entry=0x7fffc238) at 
../../../../gobject/gsignal.c:3391
#29 0x766ce378 in g_signal_emit_by_name (instance=0x55b54590, 
detailed_signal=0x7769e81e "clicked") at ../../../../gobject/gsignal.c:3487
#30 0x766b21d6 in _g_closure_invoke_va (closure=0x55917870, 
return_value=0x0, instance=0x55b336c0, args=0x7fffc590, n_params=0, 
param_types=0x0) at ../../../../gobject/gclosure.c:867
#31 

Bug#873356: gnome-todo: Don't split into separate binaries

[Jeremy Bicha]

On Sat, Nov 11, 2017 at 10:40 AM, Michael Biebl  wrote:
> This needs to be sorted out upstream first.

I think I'm satisfied with upstream's response now and the package split.

Hideki, could you bump the Breaks/Replaces in your next upload so that
Ubuntu can sync from Debian? (Ubuntu hasn't taken the package split
yet because of the unusual situation reported here). You can close
this bug with that upload.

Thanks,
Jeremy Bicha

Bug#883964: qtsensors-opensource-src FTCBFS: does not pass cross tools to qmake

[Helmut Grohne]

Source: qtsensors-opensource-src
Version: 5.9.2-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

qtsensors-opensource-src fails to cross build from source, because it
does not pass cross tools to qmake. Nowadays, debhelper should handle
that task and simply deferring it to dh_auto_configure makes the cross
build succeed. Please consider applying the attached.

Helmut
diff --minimal -Nru qtsensors-opensource-src-5.9.2/debian/changelog 
qtsensors-opensource-src-5.9.2/debian/changelog
--- qtsensors-opensource-src-5.9.2/debian/changelog 2017-10-26 
23:20:55.0 +0200
+++ qtsensors-opensource-src-5.9.2/debian/changelog 2017-12-09 
21:22:47.0 +0100
@@ -1,3 +1,10 @@
+qtsensors-opensource-src (5.9.2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 09 Dec 2017 21:22:47 +0100
+
 qtsensors-opensource-src (5.9.2-2) unstable; urgency=medium
 
   * Upload to unstable.
diff --minimal -Nru qtsensors-opensource-src-5.9.2/debian/control 
qtsensors-opensource-src-5.9.2/debian/control
--- qtsensors-opensource-src-5.9.2/debian/control   2017-10-26 
23:20:55.0 +0200
+++ qtsensors-opensource-src-5.9.2/debian/control   2017-12-09 
21:22:44.0 +0100
@@ -8,7 +8,7 @@
Timo Jyrinki ,
Dmitry Shachnev ,
Simon Quigley 
-Build-Depends: debhelper (>= 10),
+Build-Depends: debhelper (>= 10.9.2~),
pkg-kde-tools,
qtbase5-private-dev (>= 5.9.2+dfsg~),
qtdeclarative5-private-dev (>= 5.9.2~),
diff --minimal -Nru qtsensors-opensource-src-5.9.2/debian/rules 
qtsensors-opensource-src-5.9.2/debian/rules
--- qtsensors-opensource-src-5.9.2/debian/rules 2017-10-26 23:20:55.0 
+0200
+++ qtsensors-opensource-src-5.9.2/debian/rules 2017-12-09 21:22:19.0 
+0100
@@ -20,7 +20,7 @@
dh $@ --with pkgkde_symbolshelper
 
 override_dh_auto_configure:
-   qmake QT_BUILD_PARTS+=tests
+   dh_auto_configure -- QT_BUILD_PARTS+=tests
 
 override_dh_auto_build-indep:
dh_auto_build -Smakefile -- docs

Bug#883963: stretch-pu: package xchain/1.0.1-9~deb9u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Let's fix the dependency problem of xchain in stretch, too. #878090
It calls /usr/bin/wish, therefore it needs to depend on wish and not
tk8.5 (which no longer provides the generic wish binary, that's tk8.6
realm now).

The Standards-Version and Priority bump are metadata only changes.


Andreas
diff -Nru xchain-1.0.1/debian/changelog xchain-1.0.1/debian/changelog
--- xchain-1.0.1/debian/changelog   2017-01-15 23:25:46.0 +0100
+++ xchain-1.0.1/debian/changelog   2017-12-09 21:02:31.0 +0100
@@ -1,3 +1,25 @@
+xchain (1.0.1-9~deb9u1) stretch; urgency=medium
+
+  * QA upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sat, 09 Dec 2017 21:02:31 +0100
+
+xchain (1.0.1-9) unstable; urgency=medium
+
+  * QA upload.
+  * Revert path change, depend on "wish" only. Re-closes: #878090
+
+ -- Adam Borowski   Thu, 12 Oct 2017 20:12:24 +0200
+
+xchain (1.0.1-8) unstable; urgency=medium
+
+  * QA upload.
+  * Update path to wish (it's /usr/bin/wish8.5 now). Closes: #878090
+  * Priority optional.
+
+ -- Adam Borowski   Thu, 12 Oct 2017 09:14:07 +0200
+
 xchain (1.0.1-7) unstable; urgency=medium
 
   * QA upload.
diff -Nru xchain-1.0.1/debian/control xchain-1.0.1/debian/control
--- xchain-1.0.1/debian/control 2017-01-15 23:25:46.0 +0100
+++ xchain-1.0.1/debian/control 2017-10-12 20:12:19.0 +0200
@@ -1,15 +1,15 @@
 Source: xchain
 Section: games
-Priority: extra
+Priority: optional
 Maintainer: Debian QA Group 
-Standards-Version: 3.9.8
+Standards-Version: 4.1.1
 Build-Depends: debhelper (>= 10)
 Vcs-Browser: https://anonscm.debian.org/git/collab-maint/xchain.git
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/xchain.git
 
 Package: xchain
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, tk8.5 | wish
+Depends: ${shlibs:Depends}, ${misc:Depends}, wish
 Description: strategy game for 2-4 players
  Chain Reaction is a classic strategy game for 2-4 players. Players take turns
  to place tokens on an 8x8 board. When a square exceeds its maximum value, it

Bug#883961: libgnome-todo: Not actually a library

[Jeremy Bicha]

Package: libgnome-todo
Version: 3.26.2-1

The libgnome-todo package does not actually contain a library. It only
contains two plugins. I suggest you could move these plugins to the
main gnome-todo package and stop building libgnome-todo.

Alternatively, you could rename libgnome-todo to something like
gnome-todo-plugins if you think there is a good reason why people
would want to have gnome-todo installed without the plugins. (Since
it's currently a depends of gnome-todo, I think my first suggestion is
better and doesn't require going through the NEW queue.)

See https://gitlab.gnome.org/GNOME/gnome-todo/issues/92 which says
that it is intentional for gnome-todo to offer a gir and development
files but not a library.

Thanks,
Jeremy Bicha

Bug#883962: gmic: please make bash-completion code to load dynamically

[Georgios Zarkadas]

Package: gmic
Version: 1.7.9+zart-4+b1
Severity: wishlist
Tags: patch

Dear Maintainer,

The supplied patch converts gmic's bash-completion code to the new,
dynamically-loading format and moves it from /etc/bash_completion.d
to /usr/share/bash-completion/completions.  In parallel, it reduces file
size by about 33%, from 130 KB to 87 KB.

I currently use it in the 1.6.0.1 version and have succesfuly built it for
1.7.9+zart-4.  The format of the bash-completion code (being generated
programaticaly by the application itself) appears fairly stable across
version changes; thus the cost to maintain the added sed expressions
in debian/rules seems manageable.

Please, consider it.

regards
Georgios Zarkadas
diff --git a/debian/rules b/debian/rules
index 254dd84..11476dc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -67,6 +67,21 @@ override_dh_install:
 	# FIX CImg.h file name to avoid problems with cimg-dev
 	sed -i 's,CImg.h,gmic_CImg.h,g' debian/libgmic-dev/usr/include/gmic.h
 	mv debian/libgmic-dev/usr/include/CImg.h debian/libgmic-dev/usr/include/gmic_CImg.h
+	# convert bash-completion code to load dynamically and also reduce its size
+	mkdir -p debian/gmic/usr/share/bash-completion/completions
+	sed -z -e 's:/etc/bash_completion\.d/gmic:/usr/share/bash-completion/completions/gmic:' \
+	  -e 's/\(_gmic\)_stdlib/\1/g' \
+	  -e 's/\(\tCOMPREPLY=()\)/\t_init_completion || return\n\1/' \
+	  -e 's/)\n\t\t\(COMPREPLY=\)/) \1/g' \
+	  -e 's/)\n\t\t\(return 0\)\n\t\t;;/); \1;;/g' \
+	  -e 's/\\\n[[:space:]]*/ /g' \
+	  -e 's/\t\t"\(-[-a-zA-Z0-9_]*\)" | "\(--[-a-zA-Z0-9_]*\)")/\t\1|\2)/g' \
+	  -e 's/\t\t"/\t"/g' \
+	  -e 's/\n\topts="[^"]*"\n//' \
+	  -e 's/\n\tcase "\${prev}" in/\n\topts=\$(echo "\$coms" | sed "s: \\([^ ]\\+\\): -\\1 --\\1:g")\n\tcase \$prev in/' \
+	   debian/gmic/etc/bash_completion.d/gmic \
+	   >debian/gmic/usr/share/bash-completion/completions/gmic
+	rm -r debian/gmic/etc/bash_completion.d
 
 .PHONY: override_dh_auto_test override_dh_compress override_dh_auto_build override_dh_install
 

Bug#883707: ace-of-penguins: On new installed Debian 9 ace-freecell crashes on

[Dr. Claudia Neumann]

Hi Markus,

Am Samstag, 9. Dezember 2017, 19:22:20 CET schrieben Sie:
> Am 09.12.2017 um 18:45 schrieb Dr. Claudia Neumann:
> > Hi Markus,
> > 
> >  
> 
> > no, no nvidia card:
> Hi Claudia,
> 
> thanks for the reply. Ok then I suspect something doesn't play well with
> ace-freecell and KDE but I have to setup a new system to confirm that.
> 
> [...]
> 
> > I tried it on my first laptop with another user (no configuration files
> > at all). The same error with ace-freecell.
> 
> Do you use Debian Stretch and KDE on this one too?

Yes

> > I know ace-freecell works on Linux mint.
> 
> I presume the version is exactly the same as in Debian? They usually
> just copy Debian packages. No KDE here?

On Linux Mint (older version) it is ace-of-penguins 1.4_0ubuntu2. It is Xfce.

Best regards

Claudia
 
> Regards,
> 
> Markus

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

[Salvatore Bonaccorso]

Hi

> I only have a terrible java KVM app available for seeing the console, and from
> what I can see, it logs with timestamps [0.811] through [0.841] (typing in
> from an image - excuse any typos, and leaving out long hexadecimal numbers
> that might not be interesting)

here is one captured from a console (for completeness):

[0.425445] general protection fault:  [#1] SMP
[0.485003] Modules linked in:
[0.521588] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW 
3.16.0-4-amd64 #1 Debian 3.16.51-2
[0.630874] Hardware name: Sun Microsystems Sun Fire X4140/Sun Fire 
X4140, BIOS 0ABMN068 10/26/2009
[0.743251] task: 88021f4db2d0 ti: 88021f4f task.ti: 
88021f4f
[0.832756] RIP: 0010:[]  [] 
build_sched_domains+0x72d/0xcf0
[0.937939] RSP: :88021f4f3df8  EFLAGS: 00010216
[1.001457] RAX:  RBX:  RCX: 0004
[1.086807] RDX: 00016d48 RSI:  RDI: 0200
[1.172154] RBP: 88021f6b2598 R08: 88021f6b3960 R09: 0124
[1.257488] R10:  R11: 88021f4f3b06 R12: 88021f6b3940
[1.342845] R13: 0200 R14: 88021f6a20c0 R15: 0200
[1.428191] FS:  () GS:880227c0() 
knlGS:
[1.524975] CS:  0010 DS:  ES:  CR0: 8005003b
[1.593668] CR2: 880427fff000 CR3: 01813000 CR4: 07f0
[1.679030] Stack:
[1.703015]  8802 88021f6b3958 88021f6b2500 
88021f6a20c0
[1.791889]     
880426f3c080
[1.880812]   f1c8  

[1.969682] Call Trace:
[1.998903]  [] ? sched_init_smp+0x398/0x452
[2.068660]  [] ? mutex_lock+0xe/0x2a
[2.131133]  [] ? put_online_cpus+0x23/0x80
[2.199847]  [] ? stop_machine+0x2c/0x40
[2.265451]  [] ? kernel_init_freeable+0xdd/0x1e1
[2.340404]  [] ? rest_init+0x80/0x80
[2.402867]  [] ? kernel_init+0xa/0xf0
[2.466382]  [] ? ret_from_fork+0x58/0x90
[2.533018]  [] ? rest_init+0x80/0x80
[2.595491] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd a6 81 
bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e 8e 81 <48> 8b 
14 10 b8 01 00 00 00 49 89 54 24 10 f0 0
f c1 02 85 c0 75
[2.827913] RIP  [] build_sched_domains+0x72d/0xcf0
[2.905062]  RSP 
[2.946759] ---[ end trace d66b66b984085567 ]---
[3.001983] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[3.001983]
[3.111285] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[3.111285]

Salvatore

Bug#883960: kcalcore fails to build with libical3

[Matthias Klose]

Package: src:kcalcore
Version: 4:16.04.2-1
Severity: serious
Tags: sid buster

kcalcore fails to build with libical3. It looks like there is libical3 support
in version 17.11.90.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

[Brian Potkin]

tags 883765 unreproducible
thanks.


On Sat 09 Dec 2017 at 20:06:28 +0530, P V Mathew wrote:

> Sorry for the delay.
> Unfortunately had to downgrade my desktop to Debian stretch. That is okay
> now.

At least you are printing now.

> The same errors occur on laptop(Debian Buster) also.  Hence, will send the
> details.
> Tried lp -d PDF a.ps. The subject error is printed again.

I am unable to reproduce this behaviour with printer-driver-cups-pdf.

> The error_log remains empty.

Or this. Please try (as root)

 cupsfilter -p /etc/cups/PDF.ppd -m printer/foo -e /etc/services > 2>log > 
out.ps

Post log here.

> The access_log remains empty.
> The cups-pdf_log remains empty.
> cupsd.conf is attached.

Your cupsd.conf worked for me.

> also output of dpkg --get-selections |grep cups is attached.

Seems ok.

Do you have apparmor running?

 systemctl status apparmor.service

Regards,

Brian.

Bug#883959: stretch-pu: package cappuccino/0.5.1-8~deb9u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Let's fix the missing dependency on gir1.2-gtk-3.0, #879848, by
rebuilding the package from sid. This also adds a 
  /usr/games/cappuccino -> ../bin/cappuccino
symlink.


Andreas
diff -u cappuccino-0.5.1/debian/changelog cappuccino-0.5.1/debian/changelog
--- cappuccino-0.5.1/debian/changelog
+++ cappuccino-0.5.1/debian/changelog
@@ -1,3 +1,24 @@
+cappuccino (0.5.1-8~deb9u1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * rebuild for stretch.
+
+ -- Andreas Beckmann   Sat, 09 Dec 2017 20:38:28 +0100
+
+cappuccino (0.5.1-8) unstable; urgency=medium
+
+  * Fixes broken symlink in /usr/games. Closes: #880714
+- Thanks to Chris Lamb.
+
+ -- Breno Leitao   Mon, 06 Nov 2017 14:25:01 -0500
+
+cappuccino (0.5.1-7) unstable; urgency=medium
+
+  * Adding gir1.2-gtk-3.0 as a dependency. Closes: #879848
+  * Adding a link to /usr/games/cappuccino
+
+ -- Breno Leitao   Fri, 03 Nov 2017 07:52:46 -0400
+
 cappuccino (0.5.1-6) unstable; urgency=medium
 
   * Fix python dependency, moving the debian/rules file to
diff -u cappuccino-0.5.1/debian/control cappuccino-0.5.1/debian/control
--- cappuccino-0.5.1/debian/control
+++ cappuccino-0.5.1/debian/control
@@ -3,12 +3,12 @@
 Priority: optional
 Homepage: https://labs.truelite.it/projects/cappuccino
 Maintainer: Breno Leitao 
-Standards-Version: 3.7.2
+Standards-Version: 4.1.0
 Build-Depends: debhelper (>> 5.0.0), python3, python3-gi, polygen
 
 Package: cappuccino
 Architecture: all
-Depends: python3, python3-gi, polygen, ${misc:Depends}
+Depends: python3, python3-gi, polygen, ${misc:Depends},  gir1.2-gtk-3.0
 Description: utility to let your boss think that you're working hard
  Run this software on your computer when you are not motivated to work, and
  enjoy doing something different. If your boss come in your cubicle, he'll
diff -u cappuccino-0.5.1/debian/rules cappuccino-0.5.1/debian/rules
--- cappuccino-0.5.1/debian/rules
+++ cappuccino-0.5.1/debian/rules
@@ -44,6 +44,10 @@
polygen -seed 0 
$(CURDIR)/debian/cappuccino/usr/share/cappuccino/cappuccino.grm > /dev/null
polygen -seed 0 
$(CURDIR)/debian/cappuccino/usr/share/cappuccino/compileline.grm > /dev/null
 
+   # As it is considered a game, put a link at /usr/games
+   mkdir $(CURDIR)/debian/cappuccino/usr/games
+   ln -s /usr/bin/cappuccino 
$(CURDIR)/debian/cappuccino/usr/games/cappuccino
+
 # Build architecture-independent files here.
 binary-indep: build install
dh_testdir

Bug#882082: gnome-shell: Frequent segfaults in libgobject (through libgjs)

[Thibaut Girka]

reassign 882082 gnome-shell-pomodoro 0.13.3-1
retitle 882082 gnome-shell-pomodoro frequently crashes gnome-shell when 
notifications pop up
forwarded https://github.com/codito/gnome-pomodoro/issues/320
tags 882082 fixed-upstream
thanks

On Thu, Dec 07, 2017 at 06:11:37PM -0500, Jeremy Bicha wrote:
> On Tue, Dec 5, 2017 at 3:20 AM, Thibaut Girka  wrote:
> > I have a few gnome-shell extensions enabled: Alternatetab, Application menu,
> > Removable drive menu, Places status indicator and Pomodoro, all from Debian.
> 
> Please also disable all your GNOME Shell extensions, reboot and let us
> know if you can still reproduce the frequent crashes. It is possible
> for GNOME Shell extensions to crash GNOME.

Having tested different combinations of GNOME Shell extensions throughout the
day, I am fairly confident the culprit is gnome-shell-pomodoro.
I will thus reassign the bug accordingly.

> The Debian GNOME team has limited ability to help troubleshoot these
> issues. I encourage you to also forward this bug to GNOME.

Now that I have identified the culprit, I have found that the issue has already
been reported and fixed upstream:
https://github.com/codito/gnome-pomodoro/issues/320

Bug#742364: Patch to document debian/missing-sources

[Holger Levsen]

On Sat, Dec 09, 2017 at 12:16:35PM -0700, Sean Whitton wrote:
> I am seeking seconds for the following patch:
> 
> > diff --git a/policy/ch-source.rst b/policy/ch-source.rst
> > index 37c4442..f8f768f 100644
> > --- a/policy/ch-source.rst
> > +++ b/policy/ch-source.rst
> > @@ -686,6 +686,26 @@ even if most environment variables and build paths are 
> > varied.  It is
> >  intended for this stricter standard to replace the above when it is
> >  easier for packages to meet it.
> >  
> > +Missing sources: ``debian/missing-sources``
> > +---
> > +
> > +Sometimes upstream does not include the source code for some files in
> > +the upstream tarball.  In order to satisfy the DFSG for packages in
> > +``main`` or ``contrib``, you should either:
> > +
> > +1. repack the upstream tarball to include those sources; or
> > +2. include a copy of the sources in the ``debian/missing-sources``
> > +   directory.
> > +
> > +There is an optional convention to organise the contents of
> > +``debian/missing-sources`` in the following way.  For a sourceless
> > +file ``foo`` in the subdirectory ``bar`` of the upstream tarball,
> > +where the source of ``foo`` has extension ``baz``, the source is to be
> > +located at ``debian/missing-sources/bar/foo.baz``.  For example,
> > +according to this convention, the C source code of an executable
> > +``checksum/util`` is to be located at
> > +``debian/missing-sources/checksum/util.c``.
> > +
> >  .. [#]
> > See the file ``upgrading-checklist`` for information about policy
> > which has changed between different versions of this document.

seconded & thanks for your work on this!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#838834: ussp-push: cannot send any file

[franiortiz hotmail]

I cannot send any file to my phone.
Example calling with debug options

ussp-push --debug 7E:F2:45:45:43:12@25 "/tmp/img1.jpg" "/img1.jpg"
pushing file /tmp/img1.jpg
name=/tmp/img1.jpg, size=357919
__obex_connect: client_context_t = 0x8df460
Registered transport
Set user data
Created new objext
Started a new request

[.. and hangs here...]--

That happen on:
Debian Release: stretch/stable
Linux 4.9.59-v7 armv7l
 

Bug#883936: fix the build with libical3

[Jeremy Bicha]

Control: tags -1 +pending

On Sat, Dec 9, 2017 at 12:05 PM, Matthias Klose  wrote:
> patch at

I'll be fixing gnome-calendar with
https://gitlab.gnome.org/GNOME/gnome-calendar/commit/ad404c2.patch

Thanks,
Jeremy Bicha

Bug#883958: claws-mail fails to build with libical3

[Matthias Klose]

Package: src:claws-mail
Version: 3.15-1
Severity: serious
Tags: patch sid buster

claws-mail fails to build with libical3

patch at
http://launchpadlibrarian.net/348656446/claws-mail_3.15.1-1build1_3.15.1-1ubuntu1.diff.gz

Bug#883957: kopanocore fails to build with libical3

[Matthias Klose]

Package: src:kopanocore
Version: 8.3.4-4
Tags: sid buster
Severity: serious

kopanocore fails to build with libical3.

libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -I./common
-I./common/include/kopano -DLINUX -I./common/include -I../../common/include
-I../../m4lcommon/include -I../../provider/common/include
-I../../provider/libserver/include -I../../ECtools/archiver/include
-I../../inetmapi/include -I../../swig/include -I../../swig/python/include
-DNDEBUG -DUNICODE -DUSE_EPOLL -DLDAP_THREAD_SAFE -DMAPICONFIGDIR=\"/etc/mapi\"
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/kopano\"
"-DSOAP_CMAC=__attribute__((visibility(\"default\")))" -DSOAP_FMAC3=SOAP_CMAC
-DSOAP_FMAC5=SOAP_CMAC -DSOAP_NMAC=SOAP_CMAC -Iprovider/soap -I../../common
-I../../libfreebusy -I../../libsync -I../../m4lcommon -I../../mapi4linux/include
-I../../provider/client -I../../provider/common -I../../provider/include
-I../../provider/libserver -I../../provider/plugins -I../../libfreebusy
-I../../libicalmapi -I../../ECtools/archiver -I/usr/include/x86_64-linux-gnu
-DWITH_OPENSSL -DWITH_GZIP -DHAVE_OPENSSL_SSL_H -DHAVE_ZLIB_H -isystem
/usr/include/mit-krb5 -DLDAP_DEPRECATED=1 -I/usr/include/mysql
-I/usr/include/vmime/ -I/usr/include/p11-kit-1 -I/usr/include/libxml2
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wmissing-declarations -std=c++11
-Wno-variadic-macros -O2 -fno-strict-aliasing -Wno-sign-compare
-fvisibility=hidden -fvisibility-inlines-hidden -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c ../../libicalmapi/icaluid.cpp  -fPIC -DPIC -o
libicalmapi/.libs/icaluid.o
../../libicalmapi/icalrecurrence.cpp: In member function ‘HRESULT
KC::ICalRecurrence::HrCreateICalRecurrence(KC::TIMEZONE_STRUCT, bool,
KC::recurrence*, icalcomponent*)’:
../../libicalmapi/icalrecurrence.cpp:767:17: error: ‘icaltime_from_timet’ was
not declared in this scope
 ittExDate = icaltime_from_timet(LocalToUTC(exc, sTZgmt), bIsAllDay);
 ^~~
../../libicalmapi/icalrecurrence.cpp:767:17: note: suggested alternative:
‘icaltime_as_timet’
 ittExDate = icaltime_from_timet(LocalToUTC(exc, sTZgmt), bIsAllDay);
 ^~~
 icaltime_as_timet
../../libicalmapi/icalrecurrence.cpp:769:17: error: ‘icaltime_from_timet’ was
not declared in this scope
 ittExDate = icaltime_from_timet(LocalToUTC(exc, sTimeZone), 0);
 ^~~
../../libicalmapi/icalrecurrence.cpp:769:17: note: suggested alternative:
‘icaltime_as_timet’
 ittExDate = icaltime_from_timet(LocalToUTC(exc, sTimeZone), 0);
 ^~~
 icaltime_as_timet
../../libicalmapi/icalrecurrence.cpp:771:14: error: ‘icaltimetype {aka struct
icaltimetype}’ has no member named ‘is_utc’; did you mean ‘is_date’?
ittExDate.is_utc = 1;
  ^~
  is_date
../../libicalmapi/icalrecurrence.cpp: In member function ‘HRESULT
KC::ICalRecurrence::HrCreateICalRecurrenceType(KC::TIMEZONE_STRUCT, bool,
KC::recurrence*, icalrecurrencetype*)’:
../../libicalmapi/icalrecurrence.cpp:882:17: error: ‘icaltime_from_timet’ was
not declared in this scope
   icRec.until = icaltime_from_timet(lpRecurrence->getEndDate() +
lpRecurrence->getStartTimeOffset(), bIsAllday);
 ^~~
../../libicalmapi/icalrecurrence.cpp:882:17: note: suggested alternative:
‘icaltime_as_timet’
   icRec.until = icaltime_from_timet(lpRecurrence->getEndDate() +
lpRecurrence->getStartTimeOffset(), bIsAllday);
 ^~~
 icaltime_as_timet
../../libicalmapi/icalrecurrence.cpp:883:15: error: ‘struct icaltimetype’ has no
member named ‘is_utc’; did you mean ‘is_date’?
   icRec.until.is_utc = 0;
   ^~
   is_date
Makefile:3808: recipe for target 'libicalmapi/icalrecurrence.lo' failed
make[3]: *** [libicalmapi/icalrecurrence.lo] Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/<>/debian/build'
Makefile:4508: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1

Bug#883955: Important: lshw-gtk

[Joshua Blagden]

Package: lshw-gtk

Version: 02.18-0.1

Severity: Important


Dear Debian developers and maintainers, lshw-gtk is does not provide
nearly the amount of hardware information that it's supposed to.


Here is a copy of what it shows for my system with serial number and
uuid redacted :

Mini Tower Computer

product: OptiPlex 380

vendor: Dell Inc.

serial: redacted

width: 64 bits

capabilities:

    SMBIOS version 2.5,

    DMI version 2.5,

    Symmetric Multi-Processing,

    32-bit processes

configuration:

    administrator_password: enabled

    boot: normal

    chassis: mini-tower

    power-on_password: enabled

    uuid: redacted



It should show things like USB and SATA controllers and the devices
connected to them, but it does not.



Regards,

    Joshua Blagden

Bug#883937: fix the build with libical3

[Jeremy Bicha]

On Sat, Dec 9, 2017 at 12:06 PM, Matthias Klose  wrote:
> patch at

Please use the upstream patch at
https://gitlab.gnome.org/GNOME/gnome-todo/commit/6de8adc.patch

Thanks,
Jeremy Bicha

Bug#883956: node-rollup-plugin-commonjs: should declare that it "Enhances: rollup"

[Jonas Smedegaard]

Package: node-rollup-plugin-commonjs
Version: 8.2.4-2
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

node-rollup-plugin-commonjs is a plugin for commonjs - i.e. and
enhancement for that.

Please declare it in the control file, to ease locating the package when
browsing for packages relating to rollup, like this:

  Enhances: rollup

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlosO4cACgkQLHwxRsGg
ASEvUg//dKEblBgPm6wwOEtZ0eFgsdjx3iZb8ZvbiSpEHuG8zHzybuLVBRrp6Ljg
dFUx3aTaoEofJrlGR+QTmzzSMyPKv/B3mzjrNFROwrt8bHZifS2GeUotBmbitvf6
WIWtWPKs80TqiGWy0Jf/zBgMRihewCdYU5+HcYeVuDQchKHliu/QBus+/YDiP8Rl
uDYWTHtv46XRm7Q34O0XpJ23tbfLAITvSG+pkhHYsisAaaFUUP8Ll06kzj4ZHwMK
k0mQSFGC2v9lYzq7ZJgnGPmSQ1z9jX2LP5VMlOWD+My+kVGdJ4upIn8RACKvkSXK
3MzsYlMDuFfTb0mSv/DAYikiLSY0dJoKWj5Woqglmon/mUO3nNLudNQOFToj57/R
4Uc5UYWd8bzoHVZxuiZwZpt2GfmO21QHLcQJnJIwXBXQQMvODOSMYRhcEYjUHonL
5ZBV8G6SLYoBNnhDjr1G5d0zjGn8hZGflAwsjpsWkiOjKfeLEr2CE+sDXZQRS1Sq
ig4VrySdz/eUNDt5tkN908OhWWhiNPl5axO097+P3Cql8jZRkWLep7OJzX8moSlb
jHCsRbPQVAlDdar/u9Az2tyirRxxMxS+x42D2H5vsXwlWzL+5DJgxZRTGUBMJPEQ
gXh7MmMElhVobw2lWmOa2Mi3l2zNfqU5/Od6ibmAf3UyY6v0HYY=
=Ddz5
-END PGP SIGNATURE-

Bug#883954: rollup: wrong homepage - should instead use https://rollupjs.org/

[Jonas Smedegaard]

Package: rollup
Version: 0.47.4-3
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The rollup package lists its Github page as Homepage.

That is wrong: Even that Github page instead promotes as its
homepage this: https://rollupjs.org/

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlosOoEACgkQLHwxRsGg
ASHHtA//bJXe53Px1L8p7Io32yK81DGnLCHco7HHUOTjG8yUiRr5gCnCOzjUKGG2
nLekJFtztUKmkR7Mz1S7xIRUJ7r9JoObU2pNEDyjjArExDfBU3XS9Dw9BbY7ChXE
7Xe1GvT+P3/uW+8DZQ2b3NyV3Hrhlb96HkN7QHFaNR+zReD/vi0Twv9Py6l35cOz
sazaDeA6ZIkxrTY4UWaAYLCtACKq9ch74RrMbpok7Gai7j00PdVJcNmFKNj89GW7
+7nE3OXypryJUgl5aH7qop4qPzzG7iCtVwzYNAnkve3uNi189lIV/FDuIYyY27xh
YXPgS/mQrAgfhlzVs8SoiM6ZZqe508EWZVyI4+j+zGBD37+y/PXKnu/qry3t8Q8S
MWPTS1SSvNibqGVXXrICvPB5FEYVLuXODbfXHwgI46edAaOY7QUR28QVMozD7OlI
qIpwTjGah0piknFAH1XTJlFYC8qhZ4cOpLQ5BNI5CrqCtZNnmZzSfCQpK6RRtAmJ
ybrihD63/iztBknr1dpwHL2Y61v3dvG0J2HTmyrUXY2g3oCW1giF6IaoV2+9ucHE
ImLpa4O/v7Da9zlLRSAWdZe58vyd3puOW2gRoKrcEsJ1fBDASN496SXMlo4W6GNh
OqY4x20Y37ems87hJv3Tv45iwxnqZPcAWzPrYWZLgh6UdoN/zjo=
=OxNF
-END PGP SIGNATURE-

Bug#883953: goldencheetah fails to build with libical3

[Matthias Klose]

Package: src:goldencheetah
Version: 1:3.5~DEV1710-1
Tags: patch sid buster
Severity: serious

goldencheetah fails to build with libical3

patch at
http://launchpadlibrarian.net/348653229/goldencheetah_1%3A3.5~DEV1710-1build1_1%3A3.5~DEV1710-1ubuntu1.diff.gz

Bug#883951: cyrus-imapd fails to build with libical3

[Matthias Klose]

Package: src:cyrus-imapd
Version: 2.5.10-3
Tags: sid buster patch
Severity: serious

cyrus-imapd fails to build with libical3, according to the Fedora packaging
there is a patch for version 3.0.4:

https://src.fedoraproject.org/rpms/cyrus-imapd/blob/master/f/cyrus-imapd.spec

https://github.com/cyrusimap/cyrus-imapd/commit/1966c22fc4249a1157a4d4c1224138ce78653514.patch

Note that the watch file probably needs an update, it still points to 2.5.11 as
a new release.

Bug#883952: stretch-pu: package activity-log-manager/0.8.0-1.2~deb9u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Let's fix the missing dependency on python-zeitgeist, #881438, by
rebuilding the corresponding fixed package from sid.


Andreas
diff -Nru activity-log-manager-0.8.0/debian/changelog 
activity-log-manager-0.8.0/debian/changelog
--- activity-log-manager-0.8.0/debian/changelog 2015-08-18 17:28:36.0 
+0200
+++ activity-log-manager-0.8.0/debian/changelog 2017-12-09 20:04:56.0 
+0100
@@ -1,3 +1,17 @@
+activity-log-manager (0.8.0-1.2~deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sat, 09 Dec 2017 20:04:56 +0100
+
+activity-log-manager (0.8.0-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add dependency against python-zeitgeist (Closes: #881438)
+
+ -- Laurent Bigonville   Sun, 12 Nov 2017 18:05:38 +0100
+
 activity-log-manager (0.8.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru activity-log-manager-0.8.0/debian/control 
activity-log-manager-0.8.0/debian/control
--- activity-log-manager-0.8.0/debian/control   2015-08-18 17:30:06.0 
+0200
+++ activity-log-manager-0.8.0/debian/control   2017-11-12 18:04:24.0 
+0100
@@ -17,7 +17,8 @@
  python,
  zeitgeist-core (>= 0.7~) | zeitgeist (>= 0.7~),
  python-gtk2,
- python-cairo
+ python-cairo,
+ python-zeitgeist
 Description: blacklist configuration user interface for Zeitgeist
  Zeitgeist is a service which logs the user's activities and events (files
  opened, websites visited, conversations held with other people, etc.) and

Bug#742364: Patch to document debian/missing-sources

[Sean Whitton]

control: severity -1 normal
control: tag -1 +patch

Hello,

I am seeking seconds for the following patch:

> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
> index 37c4442..f8f768f 100644
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -686,6 +686,26 @@ even if most environment variables and build paths are 
> varied.  It is
>  intended for this stricter standard to replace the above when it is
>  easier for packages to meet it.
>  
> +Missing sources: ``debian/missing-sources``
> +---
> +
> +Sometimes upstream does not include the source code for some files in
> +the upstream tarball.  In order to satisfy the DFSG for packages in
> +``main`` or ``contrib``, you should either:
> +
> +1. repack the upstream tarball to include those sources; or
> +2. include a copy of the sources in the ``debian/missing-sources``
> +   directory.
> +
> +There is an optional convention to organise the contents of
> +``debian/missing-sources`` in the following way.  For a sourceless
> +file ``foo`` in the subdirectory ``bar`` of the upstream tarball,
> +where the source of ``foo`` has extension ``baz``, the source is to be
> +located at ``debian/missing-sources/bar/foo.baz``.  For example,
> +according to this convention, the C source code of an executable
> +``checksum/util`` is to be located at
> +``debian/missing-sources/checksum/util.c``.
> +
>  .. [#]
> See the file ``upgrading-checklist`` for information about policy
> which has changed between different versions of this document.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#859649: debian-policy: Please add CC0-1.0 to common-licenseso

[Bill Allombert]

On Sat, Dec 09, 2017 at 11:53:51AM -0700, Sean Whitton wrote:
> Hello,
> 
> On Sat, Dec 09 2017, Bill Allombert wrote:
> 
> > See the file tools/license-count in the policy git repo and look up
> > the debian-policy list archive for previous statistics.
> 
> Thanks.
> 
> > The point is that if there are licenses not in common-licenses that
> > are much more common than CC0, it would make more sense to add them
> > rather than CC0.
> 
> I don't think this is a good argument.  For example, it may be that the
> other CC-* licenses are more common than CC0.  But there are complex
> reasons why adding those CC-* licenses to common-licenses will take more
> work.  We shouldn't let that block adding CC0 just because it is not the
> most common CC license.

What work are you referring to ? What I have described is the common
practice for managing common-licenses which was used so far as you can
see in the archive.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#864739: [Pkg-amule-devel] Bug#864739: amule-daemon: amuled --ec-config crashes on fresh installation

[Sandro Tosi]

> Assertion failed: ../src/common/socketiohandler.cpp:Install_Callback:54:
> Assertion 'socket->m_fd != -1' failed. shouldn't be called on invalid socket
> Backtrace follows:
> [3] wxOnAssert(char const*, int, char const*, char const*, char const*) in
> /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7fc1f33cf23a]
> [4] ?? in /usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0[0x7fc1f383e023]
> [5] ?? in /usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0[0x7fc1f3835675]
> [6] ?? in /usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0[0x7fc1f3836ae0]
> [7] wxSocketClient::DoConnect(wxSockAddress const&, wxSockAddress const*,
> bool) in /usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0[0x7fc1f3836d3c]
> [8] wxHTTP::GetInputStream(wxString const&) in
> /usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0[0x7fc1f38270af]
> [9] ?? in amuled[0x56259b0533ae]
> [10] ?? in amuled[0x56259b05419e]
> [11] wxThread::CallEntry() in
> /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7fc1f3521012]
> [12] ?? in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7fc1f35296a3]
> [13] ?? in /lib/x86_64-linux-gnu/libpthread.so.0[0x7fc1f4a46494]
> [14] clone in /lib/x86_64-linux-gnu/libc.so.6[0x7fc1f280daff]
>
> Aborted

can you please install the -dbg package and run that program via gdb?
when it crashed, please run "bt ; bt full ; thread apply all bt" and
attach the full output here - this way I can report the bug upstream

Thanks,

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#883950: debian-policy: allow specifying common licenses with only the identifier

[Mattia Rizzolo]

Package: debian-policy

Nowadays it's common to see stand alone license paragraphs like these:

|License: GPL-2+
| On Debian systems the full text of the GPL-2 can be found in
| /usr/share/common-licenses/GPL-2

or

|License: GPL-2+
| This program is free software; you can redistribute it and/or modify
| it under the terms of the GNU General Public License as published by
| the Free Software Foundation; either version 2 of the License, or
| (at your option) any later version.
| .
| This program is distributed in the hope that it will be useful,
| but WITHOUT ANY WARRANTY; without even the implied warranty of
| MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
| GNU General Public License for more details.
| .
| You should have received a copy of the GNU General Public License along
| with this program; if not, write to the Free Software Foundation, Inc.,
| 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
| .
| On Debian systems, the complete text of the GNU General Public
| License version 2 can be found in `/usr/share/common-licenses/GPL-2'.


First of all, I'd like policy to stop being unclear on this matter, or
state whether the correct form is the former or the latter.

Secondly (which would overcome the first matter as well), I'd like to
propose to just stop wasting time/bytes in dumping such useless
boilerplte in our `debian/copyright`s when a license is available in
/usr/share/common-licenses.
I'm proposing either a new License-File field to be used in stand-alone
license paragraphs, or just whitelist some license identifiers as
"well known" and allow them to not need stand alone license paragraphs
at all (i.e. a file paragraph with 'License: GPL-2+' would be fine
without any extended license specification).

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#881663: Missing build on mips64el and mipsel

[Sylvestre Ledru]

On 09/12/2017 12:16, Emilio Pozuelo Monfort wrote:
> Control: retitle -1 llvm-toolchain-5.0: FTBFS on mips64el: slow tests?
> 
> On Mon, 13 Nov 2017 17:32:43 -0500 Nicholas D Steeves  
> wrote:
>> Package: llvm-toolchain-5.0
>> Version: 1:5.0-4
>> Severity: important
>> Control: block 880669 by -1
>>
>> Dear LLVM maintainers,
>>
>> In #873410 a transition to llvm-5.0-dev was requested for irony-mode.
>> Would you please fix llvm-toolchain-5.0 FTBS (maybe self-tests?) on
>> mips64el and mipsel?
> 
> This is only failing on mips64el on experimental (which will be uploaded to 
> sid
> soon I guess).
> 
> Sylvestre couldn't reproduce this on a porterbox:
> 
> 08:26 < Sylvestre> oh, llvm 5.0 built all night on mips64el to reproduce the
> issue... and no issue on the porterbox :'(
> 
> So maybe this is just the tests being too slow on the buildd, where we have a
> timeout if there's no output on stdout. ISTR some output is not enough, but 
> new
> lines are needed to reset the timer, and the tests just print some progress on
> the same line:
Good idea!

I tried to update that to display it more.
I landed the change in the VCS. Should be part of the next upload!




S

Bug#859649: debian-policy: Please add CC0-1.0 to common-licenseso

[Sean Whitton]

Hello,

On Sat, Dec 09 2017, Bill Allombert wrote:

> See the file tools/license-count in the policy git repo and look up
> the debian-policy list archive for previous statistics.

Thanks.

> The point is that if there are licenses not in common-licenses that
> are much more common than CC0, it would make more sense to add them
> rather than CC0.

I don't think this is a good argument.  For example, it may be that the
other CC-* licenses are more common than CC0.  But there are complex
reasons why adding those CC-* licenses to common-licenses will take more
work.  We shouldn't let that block adding CC0 just because it is not the
most common CC license.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#851506: cpanminus embeds other modules in fatpacked library

[gregor herrmann]

On Sat, 18 Nov 2017 20:16:30 +, Damyan Ivanov wrote:

> -=| Dominique Dumont, 15.01.2017 19:59:44 +0100 |=-

> > Providing cpanminus without fatpack can be done by either:
> > - removing fatpacked part from the cpan tarball
> > - create debian package from upstream git repo (where fatpack
> >   is not yet done, even if this repo contains convenience
> >   copies of the modules).
> 
> What do others think? I am raising the severity to 'serious', but if 
> you disagree, please revert.

Right, fatpacked and minimized modules are most probably a serious
bug, and going the github-route seems sensible.

So I've done this now and pushed some rather drastic changes to our
repo on Alioth.

Please review/improve/revert before I upload.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Rolling Stones: T-and-a


signature.asc
Description: Digital Signature

Bug#851506: Pending fixes for bugs in the cpanminus package

[pkg-perl-maintainers]

tag 851506 + pending
thanks

Some bugs in the cpanminus package are closed in revision
d7e7c1967be57ec7e9796f268a8a6742aefa9d0c in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/cpanminus.git/commit/?id=d7e7c19

Commit message:

Update build machinery to new tarball source and avoid any fatpacking.

- run (patched) maint/build.pl in debian/rules instead of removing fatpacked
  modules after the fact
- update build dependencies
- remove generated files via debian/clean
- update debian/patches/test-load.patch (new modules)

Closes: #851506

Bug#883949: ntp: no info how to fix the access to a local DCF clock blocked by apparmor

[Peter Marschall]

Package: ntp
Version: 1:4.2.8p10+dfsg-5
Severity: normal

Hi,

with one of the recent updates ntp lost acess to my local DCF clock.

It took me quite a while to find out that the correct may to regain
access to the device was to set
@{NTPD_DEVICE}="/dev/ttyUSB[0-9]*"
in
/etc/apparmor.d/tunables/ntpd

Please be so kind to mention the above file and the tunable NTPD_DEVICE
in README.Debian or NEWS.Debian to help people like me with local clocks.

When I googled the issue, the most prominent results were to disable any
SElinux / apparmor. And this is definitely the worst option ;-)

Thanks for maintaining ntp in Debian
Peter


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

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

Versions of packages ntp depends on:
ii  adduser  3.116
ii  dpkg 1.19.0.4
ii  init-system-helpers  1.51
ii  libc62.25-3
ii  libcap2  1:2.25-1.2
ii  libedit2 3.1-20170329-1
ii  libopts251:5.18.12-3
ii  libssl1.11.1.0g-2
ii  lsb-base 9.20170808
ii  netbase  5.4
ii  tzdata   2017c-1

Versions of packages ntp recommends:
ii  perl  5.26.1-3
pn  sntp  

Versions of packages ntp suggests:
ii  ntp-doc  1:4.2.8p10+dfsg-5

-- Configuration Files:
/etc/apparmor.d/tunables/ntpd changed:
@{NTPD_DEVICE}="/dev/ttyUSB[0-9]*"

-- no debconf information

Bug#883922: Charles,your recent order85219

[Charles Ashcom]

Amazon:  You have no order from me. Is this a scam? Ship nothing. Charge me
for nothing. I have not clicked on any links you sent me. Stop this. Donot
send me ways to fix - YOU FIX!

On Sat, Dec 9, 2017 at 11:00 AM, AmazonOffer  wrote:

> we would like to Thankyou
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 09 Dec 2017 15:58:31 + with message-id and
> subject line Bug#883922: fixed in evolution-data-server 3.26.2.1-1.1 has
> caused the Debian Bug report #883922, regarding libical3-dev: libical-dev
> provides should be versioned 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.) -- 883922: https://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=883922 Debian Bug Tracking System Contact
> ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: Matthias Klose 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Sat, 9 Dec 2017 13:23:25 +0100
> Subject: fix dependencies for libical3
> Package: src:evolution-data-server
> Version: 3.26.2.1
> Severity: serious
> Tags: sid buster patch
>
> please fix the (build)dependencies for libical3, by either dropping the
> versioned libical-dev dependency, or by introducing an alternative
> libical3-dev
> dependency.
>
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: 883922-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 09 Dec 2017 15:58:31 +
> Subject: Bug#883922: fixed in evolution-data-server 3.26.2.1-1.1
> Source: evolution-data-server
> Source-Version: 3.26.2.1-1.1
>
> We believe that the bug you reported is fixed in the latest version of
> evolution-data-server, 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 883...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Matthias Klose  (supplier of updated
> evolution-data-server 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, 09 Dec 2017 13:52:27 +0100
> Source: evolution-data-server
> Binary: evolution-data-server evolution-data-server-common
> evolution-data-server-tests evolution-data-server-dev
> evolution-data-server-doc libedataserver-1.2-22 libedataserver1.2-dev
> gir1.2-edataserver-1.2 libedataserverui-1.2-1 libedataserverui1.2-dev
> gir1.2-edataserverui-1.2 libcamel-1.2-60 libcamel1.2-dev gir1.2-camel-1.2
> libebook-1.2-19 libebook1.2-dev gir1.2-ebook-1.2 libedata-book-1.2-25
> libedata-book1.2-dev gir1.2-ebookcontacts-1.2 libebook-contacts-1.2-2
> libebook-contacts1.2-dev libecal-1.2-19 libecal1.2-dev libedata-cal-1.2-28
> libedata-cal1.2-dev libebackend-1.2-10 libebackend1.2-dev
> Architecture: source
> Version: 3.26.2.1-1.1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Evolution Maintainers  lists.alioth.debian.org>
> Changed-By: Matthias Klose 
> Description:
>  evolution-data-server - evolution database backend server
>  evolution-data-server-common - architecture independent files for
> Evolution Data Server
>  evolution-data-server-dev - Development files for evolution-data-server
> (metapackage)
>  evolution-data-server-doc - Documentation files for the Evolution Data
> Server libraries
>  evolution-data-server-tests - Installed tests for the evolution database
> backend server
>  gir1.2-camel-1.2 - GObject introspection for the Camel library
>  gir1.2-ebook-1.2 - GObject introspection for the EBook library
>  gir1.2-ebookcontacts-1.2 - GObject introspection for the EBook Contacts
> library
>  gir1.2-edataserver-1.2 - GObject introspection for the EDataServer library
>  gir1.2-edataserverui-1.2 - GObject introspection for the EDataServerUI
> library
>  libcamel-1.2-60 - Evolution MIME message handling 

Bug#883948: apparmor: xdg-user-dirs should have localized directory names

[Vincas Dargis]

Package: apparmor
Version: 2.11.1-4
Severity: wishlist

Dear Maintainer,

Currently `tunables/xdg-user-dirs` has only english versions of common
user directories:

```
@{XDG_DESKTOP_DIR}="Desktop"
@{XDG_DOWNLOAD_DIR}="Downloads"
@{XDG_TEMPLATES_DIR}="Templates"
...
```

This means that abstractions like `user-download`, `user-write` and similar
woudn't help on non-english desktop systems.

Maybe it would be possible to collect all translations available? Or
that would load profile too mutch?

Or, maybe some sort of hook could be implemented, or task-x-desktop be
used in any way to deploy an include file with appropriate translations?

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

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

Versions of packages apparmor depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  libc6  2.25-3
ii  lsb-base   9.20170808
ii  python33.6.3-2

apparmor recommends no packages.

Versions of packages apparmor suggests:
ii  apparmor-profiles2.11.1-4
ii  apparmor-profiles-extra  1.16
ii  apparmor-utils   2.11.1-4

-- Configuration Files:
/etc/apparmor/parser.conf changed [not included]

-- debconf information excluded