Bug#910575: Bug#910591: ITA: logdata-anomaly-miner -- lightweight tool for log checking, log analysis

[Tobias Frost]

On Thu, Oct 11, 2018 at 10:12:23AM -0400, Boyuan Yang wrote:
> Control: tag -1 - moreinfo
> X-Debbugs-CC: roman.fied...@ait.ac.at
> 
> Hi Markus,
> 
> Wurzenberger Markus  于2018年10月11日周四 上午7:20写道：
> >
> > Hi Boyuan,
> >
> > unfortunately, Roman left our organization. Therefore, there is no 
> > possibility
> > for him to make any confirmations via e-mail. Before he left, he handed me
> > over the logdata- anomaly-miner launchpad project and repository to maintain
> > and further develop it, as you can see here:
> > https://launchpad.net/logdata-anomaly-miner
> > https://git.launchpad.net/logdata-anomaly-miner
> 
> He should have informed the downstream distributions before leaving to
> fully hand over the
> responsibilities... but it seems a little bit late to make such reminder.
> 
> > Please let me know how to handle this situation so that I can keep the
> > logdata-anomaly-miner Debian package up to date.

> I am sending a mail copy to Debian QA/MIA Team since it looks like a
> missing-in-action
>  scenario. Meanwhile, all latter uploads should not remove Roman from
> maintainer list
> unless he sends out a public email declaring the handover of
> maintenance, or the Debian MIA
> Team decides that his package should be orphaned.

From my perspective (and I think this is also the opinion of the MIA
team), it is ok for Markus to take over the package in this case,
as he got the (verbal) ok from the former maintainer and we do not have reasons
to believe that this is not true. IMHO there is no need to formally
orphan it beforehand (and strictly it would not need an ITA either).
(And still, if we find out that Roman would disagrees, he can easily be
re-instatniated as maintainer.)

-- 
tobi

> I don't have enough time recently to review the work; I may examine it
> later or some
> other Debian Developers would review it.
> 
> --
> Thanks,
> Boyuan Yang
> 
> > Regards,
> > Markus Wurzenberger
> >
> > -Original Message-
> > From: Boyuan Yang 
> > Sent: Mittwoch, 10. Oktober 2018 22:10
> > To: 910...@bugs.debian.org; 910...@bugs.debian.org
> > Subject: Bug#910591: ITA: logdata-anomaly-miner -- lightweight tool for log
> > checking, log analysis
> >
> > X-Debbugs-CC: roman.fied...@ait.ac.at markus.wurzenber...@ait.ac.at
> > Control: tag -1 + moreinfo
> >
> > Hi Markus,
> >
> > I noticed your RFS and ITA document. However, it seems that the original
> > maintainer (Roman Fiedler) never submitted the RFA or Orphaning bug to 
> > declare
> > that this package is given up for adoption. I think an acknowledgment from 
> > the
> > original maintainer should be necessary.
> >
> > Dear Roman, could you please send an public email to confirm that you are
> > willing to have Markus taken over the package maintenance?
> >
> > If Markus is no longer able to send emails to make confirmation, that is
> > another situation and needs to be handled differently.


signature.asc
Description: PGP signature

Bug#910844: rust-phf-shared: unsatisifiable dependency

[Ximin Luo]

Control: reopen -1
Control: found -1 0.7.23-1

My apologies, you are correct there is indeed a problem. We uploaded unicase 
version 2 but we should have uploaded unicase version 1. Actually we can just 
patch phf_shared to accept both unicase version 1 >= 1.4 and version 2, I will 
do that imminently.

X

Ximin Luo:
> Control: notfound -1 0.7.23-1
> Control: close -1
> 
> Hi, this is not a bug, it is due to how cargo dependencies work vs how dpkg 
> dependencies work, for details see
> 
> https://github.com/kpcyrd/cargo-debstatus/issues/2
> 
> Furthermore there is also a bug in Britney where some packages might migrate 
> too early, for details see
> 
> https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2018-September/002574.html
> 
> and the follow-ups.
> 
> See also #908364 #908366 #904485.
> 
> X
> 
> Jeremy Bicha:
>> Source: rust-phf-shared
>> Version: 0.7.23-1
>> Severity: serious
>>
>> rust-phf-shared won't migrate to testing because
>> librust-phf-shared+unicase-dev depends on
>> librust-unicase-1+default-dev but that package is not available in
>> Debian.
>>
>> There is a librust-unicase-2+default-dev virtual package though.
>>
>> Thanks,
>> Jeremy Bicha
>>
> 
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#910849: powerline: [INTL:ru] Russian translation of debconf template

[Lev Lamberov]

Source: powerline
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached the Russian debconf translation of powerline.

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.18.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)
LSM: AppArmor: enabled
# Russian translation of powerline debconf template.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the powerline package.
# Lev Lamberov , 2018.
#
msgid ""
msgstr ""
"Project-Id-Version: powerline\n"
"Report-Msgid-Bugs-To: powerl...@packages.debian.org\n"
"POT-Creation-Date: 2018-05-21 06:54+0200\n"
"PO-Revision-Date: 2018-10-07 11:03+0500\n"
"Language-Team: Debian L10n Russian \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.1.1\n"
"Last-Translator: Lev Lamberov \n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && 
n%10<=4 && (n%100<12 || n%100>14) ? 1 : 2);\n"
"Language: ru\n"

#. Type: title
#. Description
#: ../powerline.templates:1001
msgid "powerline: Setup"
msgstr "powerline: настройка"

#. Type: boolean
#. Description
#: ../powerline.templates:2001
msgid "Enable powerline globally?"
msgstr "Включить powerline глобально?"

#. Type: boolean
#. Description
#: ../powerline.templates:2001
msgid "powerline can be enabled globally for all Bash users of this system."
msgstr "powerline можно включить глобально для всех пользователей Bash данной 
системы."

Bug#910837: RFS: mle/1.2-1 [ITP] -- flexible terminal-based text editor (C)

[Mo Zhou]

Hi Adam,

Thanks for this package, the copyright file looks good to me.
However there are still a couple of problems:

1. Can we avoid shipping with embedded code copy[1] of lua, termbox and
   uthash? . lua 5.3 and uthash are already in the archive. termbox needs
   to be packaged.

2. I'd recommend you to create a packaging repo so that the others can
   track the changes about packaging with git. Since you are also the
   upstream author, it's fine if you set the source format as
   "3.0 (native)" and push the debian directory to the upstream git repo.
   A separate git repo following e.g. the gbp-buildpackage workflow is
   also acceptable. No packaging repo is fine too but not encouraged.

3. External tools such as fzf can be leveraged by mle to enhance
   features. That means those packages should be listed in the
   "Recommends" or "Suggests" fields.

Best.

[1] https://wiki.debian.org/EmbeddedCodeCopies

On Thu, Oct 11, 2018 at 08:04:33PM -0400, Adam Saponara wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "mle":
> 
>   Package name: mle
>   Version : 1.2-1
>   Upstream Author : Adam Saponara 
>   URL : https://github.com/adsr/mle
>   License : Apache, Expat, BSD-1-clause
>   Section : editors
> 
> It builds those binary packages:
> 
>   mle - flexible terminal-based text editor (C)
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/mle
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x https://mentors.debian.net/debian/pool/main/m/mle/mle_1.2-1.dsc
> 
> More information about hello can be obtained from https://github.com/adsr/mle.
> 
> Changes since the last upload: -
> 
> Regards,
> 
> Adam
> 

Bug#910847: fusiondirectory: [INTL:ru] Russian translation of debconf template

[Lev Lamberov]

Source: fusiondirectory
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached the Russian debconf translation of fusiondirectory.

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.18.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)
LSM: AppArmor: enabled
# Russian translation of fusiondirectory debconf template
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the fusiondirectory 
package.
# Lev Lamberov , 2018.
#
msgid ""
msgstr ""
"Project-Id-Version: fusiondirectory\n"
"Report-Msgid-Bugs-To: fusiondirect...@packages.debian.org\n"
"POT-Creation-Date: 2018-08-28 17:16+0200\n"
"PO-Revision-Date: 2018-10-12 09:46+0500\n"
"Language-Team: Debian L10n Russian \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.1.1\n"
"Last-Translator: Lev Lamberov \n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<12 || n%100>14) ? 1 : 2);\n"
"Language: ru\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Really perform FusionDirectory major version upgrade?"
msgstr "Выполнить обновление FusionDirectory до новой версии?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"You are about to upgrade FusionDirectory to a new major version. Please "
"consult the UPGRADE documentation first: /usr/share/doc/fusiondirectory/"
"UPGRADE.md.gz"
msgstr ""
"Вы собираетесь выполнить обновление FusionDirectory до новой версии. Для "
"начала ознакомьтесь с файлом UPGRADE: /usr/share/doc/fusiondirectory/"
"UPGRADE.md.gz"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"FusionDirectory comes with tools to migrate from one major version to "
"another. However, as with other LDAP directory setups, exceptional "
"circumstances or wrong data in the LDAP tree may sometimes prevent these "
"tools from migrating everything."
msgstr ""
"FusionDirectory содержит инструменты, позволяющие выполнить переход с "
"одной версии на другую. Однако, как и в случае с другими установками "
"каталогов LDAP, исключительные обстоятельства или неправильные данные в "
"дереве LDAP иногда могут помешать этим инструментам перенести все данные."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"In this case, the directory information tree may even need to be manually "
"adapted outside of FusionDirectory with tools such as ldapmodify or ldapvi."
msgstr ""
"В таком случае может даже потребоваться вручную адаптировать "
"информационное дерево каталог вне FusionDirectory с помощью таких "
"инструментов как ldapmodify или ldapvi."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"If you do not choose to proceed, the upgrade process for FusionDirectory "
"related packages will be canceled."
msgstr ""
"Если вы решите не продолжать, то обновление связанных с FusionDirectory "
"пакетов будет отменено."

#. Type: error
#. Description
#: ../templates:2001
msgid "FusionDirectory upgrade canceled"
msgstr "Обновление FusionDirectory отменено"

#. Type: error
#. Description
#: ../templates:2001
msgid ""
"The upgrade of FusionDirectory has been canceled on user request. The "
"installation process will be aborted."
msgstr ""
"Обновление FusionDirectory было отменено по запросу пользователя. "
"Установка будет прекращена."

Bug#910848: plinth: [INTL:ru] Russian translation of debconf template

[Lev Lamberov]

Package: plinth
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached the Russian debconf translation of plinth.

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.18.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)
LSM: AppArmor: enabled

Versions of packages plinth depends on:
ii  adduser 3.118
pn  apache2 
pn  augeas-tools
ii  avahi-daemon0.7-4+b1
pn  avahi-utils 
pn  batctl  
pn  certbot 
ii  debconf [debconf-2.0]   1.5.69
ii  e2fsprogs   1.44.4-2
pn  fail2ban
pn  firewalld   
pn  flite   
ii  fonts-lato  2.0-2
ii  gettext 0.19.8.1-8
ii  gir1.2-glib-2.0 1.58.0-1
pn  gir1.2-nm-1.0   
pn  gir1.2-udisks-2.0   
ii  javascript-common   11
ii  ldap-utils  2.4.46+dfsg-5
ii  ldapscripts 2.0.8-1
pn  libapache2-mod-auth-pubtkt  
pn  libapache2-mod-gnutls   
pn  libapache2-mod-php  
pn  libjs-bootstrap 
ii  libjs-jquery3.2.1-1
pn  libjs-modernizr 
pn  libnss-ldapd
pn  libpam-ldapd
ii  network-manager 1.12.4-1
pn  node-turbolinks 
pn  nslcd   
pn  ntp 
pn  openssh-server  
ii  openssl 1.1.0h-4
pn  ppp 
pn  pppoe   
ii  python3 3.6.6-1
ii  python3-apt 1.7.0~rc1
pn  python3-augeas  
pn  python3-bootstrapform   
pn  python3-cherrypy3   
pn  python3-configobj   
ii  python3-dbus1.2.8-2+b1
pn  python3-django  
pn  python3-django-axes 
pn  python3-django-captcha  
pn  python3-django-stronghold   
ii  python3-gi  3.30.1-1
pn  python3-openssl 
pn  python3-psutil  
ii  python3-requests2.18.4-2
pn  python3-ruamel.yaml 
pn  python3-yaml
pn  slapd   
ii  sudo1.8.23-2
pn  udiskie 
pn  unattended-upgrades 

plinth recommends no packages.

plinth suggests no packages.
# Russian translation of plinth debconf template.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the plinth package.
# Lev Lamberov .
#
msgid ""
msgstr ""
"Project-Id-Version: plinth\n"
"Report-Msgid-Bugs-To: pli...@packages.debian.org\n"
"POT-Creation-Date: 2018-07-03 16:39+0530\n"
"PO-Revision-Date: 2018-10-07 11:19+0500\n"
"Language-Team: Debian L10n Russian \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.1.1\n"
"Last-Translator: Lev Lamberov \n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<12 || n%100>14) ? 1 : 2);\n"
"Language: ru\n"

#. Type: note
#. Description
#: ../templates:1001
msgid "FreedomBox first wizard secret - ${secret}"
msgstr "Секретная строка мастера настройки FreedomBox - ${secret}"

#. Type: note
#. Description
#: ../templates:1001
msgid ""
"Please save this string. You will be asked to enter this in the first screen "
"after you launch the FreedomBox interface. In case you lose it, you can find "
"it in the file /var/lib/plinth/firstboot-wizard-secret."
msgstr ""
"Сохраните эту строку. Вам будет необходимо ввести её на самом первом экране "
"после запуска интерфейса FreedomBox. Если вы потеряете эту строку, то вы "
"сможете найти её в файле /var/lib/plinth/firstboot-wizard-secret."

Bug#910846: X server "Segmentation fault at address 0x0" when using about:support in Firefox-based browsers.

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: xserver-xorg-video-radeon
Version: 1:18.1.0-1

I am using a standalone AMD HD 7670. "firmware-amd-graphics" is installed and 
loaded during boot.
It seems that whenever I tries to query information about hardware 
acceleration, X segfaults.
"dmesg" does not show any error or warning after segfault.
Sometimes other programs or games trigger it as well, with the same problem 
described in the file Xorg.0.log.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAQBQJbwCXBCRDYtWA5RV10HwAAuiQIAJQ2jdMOx42C2e3u6tMl
gWPQH1duJcPbXwk/SgD6mQBZPFP2+q/nxStgqAEtrihj78DrgefD9tnyt4tu
Z/PAp0g5quf6ds4Apwo4RCXbsxq1aQRe0ATRHidj2h959k6Qi9InH7skxcCO
AYn0GFRNGEtLXiqs3BE5Je8oQ+t5lI71s1DtmzCLtaQo/OKwNQl+T29UO01d
fz4Y9VppJdQLZYP71cPW3MRbW0o+dv7FcURoiU/28GF28941APtDX+M1rDQ/
o4UrKYR1I4Ea4ejroYSOQGZyKCc7c3Ao0z5rTAFTkLnNncp4pfJnHwCK20GO
8KMH6svPEBKMjfxINfI635g=
=SqQz
-END PGP SIGNATURE-

[   303.139] 
X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
[   303.139] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[   303.139] Current Operating System: Linux AVENTHEIM 4.19.0-rc7-amd64 #1 SMP Debian 4.19~rc7-1~exp1 (2018-10-07) x86_64
[   303.139] Kernel command line: auto BOOT_IMAGE=vmlinuz rw root=800 scsi_mod.use_blk_mq=0 elevator=deadline net.ifnames=0 biosdevname=0 pti=off radeon.dpm=1 quiet video=vesafb:ywrap,mtrr:3
[   303.139] Build Date: 10 October 2018  04:23:15PM
[   303.139] xorg-server 2:1.20.1-5 (https://www.debian.org/support) 
[   303.139] Current version of pixman: 0.34.0
[   303.139] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   303.139] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   303.139] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 12 08:03:49 2018
[   303.141] (==) Using config file: "/etc/X11/xorg.conf"
[   303.141] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   303.142] (==) No Layout section.  Using the first Screen section.
[   303.142] (==) No screen section available. Using defaults.
[   303.142] (**) |-->Screen "Default Screen Section" (0)
[   303.142] (**) |   |-->Monitor ""
[   303.143] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[   303.143] (**) |   |-->Device "Card0"
[   303.143] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   303.143] (==) Automatically adding devices
[   303.143] (==) Automatically enabling devices
[   303.143] (==) Automatically adding GPU devices
[   303.143] (==) Max clients allowed: 256, resource mask: 0x1f
[   303.143] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   303.143] 	Entry deleted from font path.
[   303.143] (**) FontPath set to:
	/usr/share/fonts/X11,
	built-ins,
	built-ins
[   303.143] (**) ModulePath set to "/usr/lib/xorg/modules"
[   303.144] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   303.144] (II) Loader magic: 0x5627644f5e20
[   303.144] (II) Module ABI versions:
[   303.144] 	X.Org ANSI C Emulation: 0.4
[   303.144] 	X.Org Video Driver: 24.0
[   303.144] 	X.Org XInput driver : 24.1
[   303.144] 	X.Org Server Extension : 10.0
[   303.144] (++) using VT number 1

[   303.145] (EE) systemd-logind: failed to get session: The name org.freedesktop.login1 was not provided by any .service files
[   303.145] (II) xfree86: Adding drm device (/dev/dri/card0)
[   303.148] (--) PCI:*(1@0:0:0) 1002:675b:174b:7670 rev 0, Mem @ 0xe000/268435456, 0xf7e2/131072, I/O @ 0xe000/256, BIOS @ 0x/131072
[   303.148] (II) LoadModule: "glx"
[   303.149] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   303.161] (II) Module glx: vendor="X.Org Foundation"
[   303.161] 	compiled for 1.20.1, module version = 1.0.0
[   303.161] 	ABI class: X.Org Server Extension, version 10.0
[   303.161] (II) LoadModule: "radeon"
[   303.161] (II) Loading 

Bug#910631: lightdm: first login hangs waiting for user-generated entropy

[Dr. Julius]

Hi,

The issue still persists using the 4.17 kernel.

Regards,
Jules.

Bug#910844: rust-phf-shared: unsatisifiable dependency

[Ximin Luo]

Control: notfound -1 0.7.23-1
Control: close -1

Hi, this is not a bug, it is due to how cargo dependencies work vs how dpkg 
dependencies work, for details see

https://github.com/kpcyrd/cargo-debstatus/issues/2

Furthermore there is also a bug in Britney where some packages might migrate 
too early, for details see

https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2018-September/002574.html

and the follow-ups.

See also #908364 #908366 #904485.

X

Jeremy Bicha:
> Source: rust-phf-shared
> Version: 0.7.23-1
> Severity: serious
> 
> rust-phf-shared won't migrate to testing because
> librust-phf-shared+unicase-dev depends on
> librust-unicase-1+default-dev but that package is not available in
> Debian.
> 
> There is a librust-unicase-2+default-dev virtual package though.
> 
> Thanks,
> Jeremy Bicha
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#910845: RFS: jag/0.3.5-3 -- arcade and puzzle 2D game

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "jag"

 * Package name: jag
   Version : 0.3.5-3
   Upstream Author : Carlos Donizete Froes 
 * URL : https://gitlab.com/coringao/jag/wikis
 * License : GPL-3+
   Section : games

  It builds those binary packages:

  jag - arcade and puzzle 2D game
  jag-data - arcade and puzzle 2D game (data file)

  To access further information about this package, please visit the following 
URL:

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

  Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/j/jag/jag_0.3.5-3.dsc

  More information about JAG can be obtained from 
https://gitlab.com/coringao/jag.

  Changes since the last upload:

  jag (0.3.5-3) unstable; urgency=medium

  * debian/control:
+ Declare compliance with Debian Policy: 4.2.1
  * Updated debian/watch

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Bug#910844: rust-phf-shared: unsatisifiable dependency

[Jeremy Bicha]

Source: rust-phf-shared
Version: 0.7.23-1
Severity: serious

rust-phf-shared won't migrate to testing because
librust-phf-shared+unicase-dev depends on
librust-unicase-1+default-dev but that package is not available in
Debian.

There is a librust-unicase-2+default-dev virtual package though.

Thanks,
Jeremy Bicha

Bug#858191: linssid: missing root privileges to run "iw wlan0 scan"

[Eriberto Mota]

Hi Alf,

Em dom, 19 de mar de 2017 às 13:06, Alf  escreveu:
>
> Package: linssid
> Version: 2.9-3
> Severity: important
> Tags: security
>
> Dear Maintainer,
>
> Just installing linssid in Stretch results in beeing unfunctional.
> The installer creates an entry in the Applications-Menu which just is
> unable to start linssid.
>
> A (dirty) workaround is to start the application comletely as root from
> the command line. However this is a unnecessary security risk as the
> whole graphical stuff does not need the root privileges, it is just the
> command "iw wlan0 scan" to contol the wifi-device. Running it this way
> also spams the home directory of root with its configuration settings
> and logging.
>
> To demonstrate how it should work, and as version 2.7-1 under Jessie
> does, I downloaded the original package linssid_2.9-1_amd64.deb from
> SourceForge, installed the necessary dependencies (libboost-regex1.58
> and libicu55) from Debian-snapshots and it works as expected. At start
> it requests the root-PW once (popup window) and runs
> "sudo iw wlan0 scan" to scan the device.
>
> Of course this requires the user starting linssid, to be member of group
> "sudo" and to modify /etc/sudoers to ask the root-PW, i.e like this:
> Defaultsenv_reset, targetpw, timestamp_timeout=0

Thanks for your message.

I just uploaded linssid 3.6 that uses policykit to gain root
permission. So, the execution from menu is fixed. However, the rights
over iw command only is not solved by this new scenary. But I think
this is the best solution because sudo is a bit insecure IMHO (I am a
specialist in computer forensics and sudo forgets/keeps the root
password in RAM after execute the binary).

Can I close this bug?

Regards,

Eriberto

Bug#908468: stretch-pu: package weboob/1.2-1

[Duck]

Quack,

Any news about this?

\_o<


On 9/10/18 5:15 PM, Marc Dequènes (duck) wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: pu
> Tags: stretch
> Severity: normal
> 
> 
> Quack,
> 
> This update has been made to:
>   - fix #905299 to remove insults
>   - add a warning in the package description about the naming
> 
> See attached debdiff.
> 
> I plan to do the same for Jessie if you agree on this one.
> 
> Regards.
> \_o<
> 



signature.asc
Description: OpenPGP digital signature

Bug#899012: python-weboob: Recommends python-gdata which it does not use

[Duck]

Quack,

It seems neither of us had any time to work on this, I'm sorry. I won't
have time until a few weeks, so feel free to NMU. Please update the git
repository accordingly (it is in the 'debian' group, ex collab-maint).

Regards.
\_o<



signature.asc
Description: OpenPGP digital signature

Bug#910154: [Pkg-deepin-devel] Bug#910154: deepin-icon-theme: broken symlinks: /usr/share/icons/deepin/places/16/folder-bookmark.svg, /usr/share/icons/deepin/devices/16/phone{, -apple-iphone}.svg

[Yanhao Mo]

Control: tag + confirmed

On Wed 10/03 12:08, Andreas Beckmann wrote:
> Package: deepin-icon-theme
> Version: 15.12.59-3
> Severity: normal
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
> 
> From the attached log (scroll to the bottom...):
> 
> 0m58.4s ERROR: FAIL: Broken symlinks:
>   /usr/share/icons/deepin/places/16/folder-bookmark.svg -> 
> deepin/places/16/user-bookmarks-symbolic.svg (deepin-icon-theme)
>   /usr/share/icons/deepin/devices/16/phone.svg -> android-device.svg 
> (deepin-icon-theme)
>   /usr/share/icons/deepin/devices/16/phone-apple-iphone.svg -> ios-device.svg 
> (deepin-icon-theme)
> 
> 
> cheers,
> 
> Andreas

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#908553: can't reproduce

[Bdale Garbee]

tags 908553 +unreproducible 
severity 908553 normal
thanks

I've been unable to reproduce this problem, and am in fact a nearly-daily
user of pcb-rnd.

If the problem is persistent for you, I'm going to need to know more about
your system config, how you're invoking pcb-rnd, etc, to be able to usefully
pursue this.

Bdale

Bug#910843: jaxb: Rebuilding from source gives broken dependencies

[Daniel Schepler]

Source: jaxb
Version: 2.3.0.1-5
Severity: important

To reproduce the error I'm seeing, run this in a pbuilder login session:

adduser pbuildd
echo 'deb-src http://deb.debian.org/debian sid main' >
/etc/apt/source.list.d/debian-src.list
apt update
apt install eatmydata fakeroot
cd /build
mkdir dtd-parser
cd dtd-parser
eatmydata apt build-dep dtd-parser
chown -R pbuildd:pbuildd .
su pbuildd -c "apt source -b dtd-parser"
eatmydata apt install ./*.deb
cd ..
mkdir jaxb
cd jaxb
eatmydata apt build-dep jaxb
chown -R pbuildd:pbuildd .
su pbuildd -c "apt source -b jaxb"
eatmydata apt install ./*.deb

With which I get the error:

The following packages have unmet dependencies:
libjaxb-java : Depends: libdtd-parser-java (>= 1.2-SNAPSHOT) but
1.2~svn20110404-1 is to be installed
E: Unable to correct problems, you have held broken packages.

(I don't really know anything about how the dependency generation
works, so I don't really have any idea if this is a bug in src:jaxb,
src:dtd-parser, or maybe even in one of the build tools.)
-- 
Daniel Schepler

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Samuel Thibault, le ven. 12 oct. 2018 03:27:47 +0200, a ecrit:
> Samuel Thibault, le ven. 12 oct. 2018 03:02:32 +0200, a ecrit:
> > Samuel Thibault, le ven. 12 oct. 2018 00:55:47 +0200, a ecrit:
> > > Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> > > > To be sure, I have installed a VM from scratch with stretch (default
> > > > install, just not the graphical desktop task), created a chroot with
> > > > pbuilder there, and ran in it, and got the issue there too...
> > 
> > (actually I can't reproduce the issue with the stretch VM, I guess I
> > read wrongly previously)
> > 
> > > Doing the same with a VM with buster, I don't get the issue... I'll now
> > > be able to check what differences there can be in the chroots.
> > 
> > I dugged more and more... It seems the issue is... that my box hostname
> > is "function"...
> 
> Mmm, no, I have changed the hostname of my new "function" VM back to
> something else than "function" and I still have the issue there.
> 
> I have checked the chroot's dpkg -l, the environment, / is ext4 with
> relatime in both case, the kernel is the same, I even used -cpu host
> -smp 4 to expose the same CPU. What else?

I'm thinking... My chroots have a lib -> usr/lib symlink. Could it be
that python somehow gets lost between /lib/python* and /usr/lib/python*,
and dependending on e.g. inode number or directory order, we could have
one way or the other?

Right now I have two VMs with almost the same chroot (differences
notably lie in .pyc files), one works, the other doesn't. When I mount
the chroot of one on the other, the chroot behavior holds (i.e. the
failing chroot keeps failing on the VM which produced a working chroot).

Samuel

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Samuel Thibault, le ven. 12 oct. 2018 03:02:32 +0200, a ecrit:
> Samuel Thibault, le ven. 12 oct. 2018 00:55:47 +0200, a ecrit:
> > Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> > > To be sure, I have installed a VM from scratch with stretch (default
> > > install, just not the graphical desktop task), created a chroot with
> > > pbuilder there, and ran in it, and got the issue there too...
> 
> (actually I can't reproduce the issue with the stretch VM, I guess I
> read wrongly previously)
> 
> > Doing the same with a VM with buster, I don't get the issue... I'll now
> > be able to check what differences there can be in the chroots.
> 
> I dugged more and more... It seems the issue is... that my box hostname
> is "function"...

Mmm, no, I have changed the hostname of my new "function" VM back to
something else than "function" and I still have the issue there.

I have checked the chroot's dpkg -l, the environment, / is ext4 with
relatime in both case, the kernel is the same, I even used -cpu host
-smp 4 to expose the same CPU. What else?

Samuel

Bug#910783: Remove doc-base recommendation

[Russ Allbery]

Stuart Prescott  writes:

> In counterpoint, I'll add to that 4169 packages register 5318 sets of
> documents in doc-base. To me, that says that we've got a lot of packages
> who are advertising their documentation this way.

I wish I had some feel for how many people were actually using doc-base as
a client, though.  How many users actually run the tools and use them to
find documentation, and is it successful for them?

I dutifully provide doc-base registrations for all the documentation in
all of my packages, but I think in all the time I've been using Debian
I've only run the tool as a user maybe twice, and then only to check
whether my package documentation showed up.  So the fact that my packages
all have doc-base registrations doesn't indicate those registrations are
useful, necessarily.

> At the user-support BoF at the last DebConf, we also discussed how we
> could leverage doc-base files better to make documentation more easily
> discoverable. That is work-in-progress.

That sort of thing would be really cool.

-- 
Russ Allbery (r...@debian.org)   

Bug#910842: Update debugging documentation

[積丹尼 Dan Jacobson]

Package: chromium
Version: 69.0.3497.92-1
File: /usr/share/doc/chromium/README.Debian

Please revise debugging documentation.

/usr/share/doc/chromium/README.Debian mentions debugging. But it is out
of date. One cannot find such packages mentioned anymore,
http://wiki.debian.org/Chromium/Debugging is even more out of date.
In https://bugs.chromium.org/p/chromium/issues/detail?id=886921 we see
people can no longer debug crashes anymore.

Bug#905458: pari: enable OpenPGP verification of upstream source with uscan

[John Scott]

Package: src:pari
Followup-For: Bug #905458

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

> Is there a way to point to a key in the Debian keyring instead of
> copying the full key?

I'm afraid not (yet), but that would be convenient.

> Why does your patch change the version to 4 ?
> Why does your patch remove 'debian uupdate' ?

I have limited experience packaging, but after reviewing the
documentation I believe that the version 2 standard for the
watchfile is very old, and in fact I can't find reference to
its syntax on the man page (though it does have v3). The current
syntax is well-documented though, so I've upgraded the version.

I also believe that, in version 4 of the syntax, the
'debian uupdate' is the default when fetching one upstream
source file and it's not necessary here.

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

Kernel: Linux 4.18.0-1-amd64 (SMP w/2 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)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAXEkn09uX7g8Tv8W3qerYfa4vJcFAlu/9FcACgkQ3qerYfa4
vJfu/Qf+L0tCg8OvqfLMEP2D619wFm3CnP8ESyVx1tkwcGXJ8utB2JPdTt112XjZ
fGLts3V8b3N0aXS4RdUqtZEACxnXkCTmNUCiVqzPeOfBkG9Y/xmBCgVXB/6Dx+kE
OcretHM7u1K0scRGYs6pLP5/3MF5cu5ljVInqewVKxcGc2cn5KrlfzsZjAyQ+0BJ
r+T9Unojtggwxp3rBFdfzcevkjTapJXu0D6fZgg6CAIo/TMD2+g/mpQW8Ce8cFTC
OKwuHuF34bW+NKz2rNw25ZKHuaauSWCf20Q7pGLNgIp//ebfgioPkbJQUOt78wCV
J7V+fgUT8sYOdxbr1DK+1zy/VRAnHA==
=DuiX
-END PGP SIGNATURE-

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Samuel Thibault, le ven. 12 oct. 2018 00:55:47 +0200, a ecrit:
> Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> > To be sure, I have installed a VM from scratch with stretch (default
> > install, just not the graphical desktop task), created a chroot with
> > pbuilder there, and ran in it, and got the issue there too...

(actually I can't reproduce the issue with the stretch VM, I guess I
read wrongly previously)

> Doing the same with a VM with buster, I don't get the issue... I'll now
> be able to check what differences there can be in the chroots.

I dugged more and more... It seems the issue is... that my box hostname
is "function"...

I have just installed that new laptop, I knew that that hostname could
pose problem, I didn't think it'd be so soon :)

Samuel

Bug#910841: xml-core: more elts

[Joseph Herlant]

Another element to keep in mind when working on that one is what is
explained in https://lists.debian.org/debian-qa/2015/08/msg00015.html

Bug#910783: Remove doc-base recommendation

[Stuart Prescott]

> lintian has an I: possible-documentation-but-no-doc-base-registration tag,
> with 1872 emitted currently:
> https://lintian.debian.org/tags/possible-documentation-> 
> but-no-doc-base-registration.html

In counterpoint, I'll add to that 4169 packages register 5318 sets of 
documents in doc-base. To me, that says that we've got a lot of packages who 
are advertising their documentation this way.

At the user-support BoF at the last DebConf, we also discussed how we could 
leverage doc-base files better to make documentation more easily 
discoverable. That is work-in-progress.

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#910841: xml-core: review how the catalogs updates are handled

[Joseph Herlant]

Package: xml-core
Version: 0.18
Severity: wishlist

This is a follow-up on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660687#15 as it
makes more sense in its own bug report rather than on the ITA bug
report.

The following content was from Daniel Leidert, previous maintainer of
the package:

It is more or less a similar bug to #477751. Every package update
re-installs all entries to /etc/xml/catalog and /etc/xml/$package.xml.
But this is a policy violation. Changes done to the above files are not
preserved. Further we create and manipulate the system catalog by a
self-written tool. IMO the rewrite must finish in

- shipping the /etc/xml/$package.xml file instead of creating it (so
dh_installxmlcatalogs will simply put a file into etc/xml/)

- and registering it with the system catalog by the nextCatalog entry
instead of putting delegate* entries in the system catalog directly
(this should be done in a way, that is compatible with using the
xmlcatalog tool from libxml)

- if a user decides he wants to unregister a catalog, he can simply
remove the relevant nextCatalog [1] entry in /etc/xml/catalog - and this
change must be preserved during package updates.

[1] 
https://www.oasis-open.org/committees/entity/spec-2001-08-06.html#s.nextcatalog

Bug#910840: coq: upgrade to new upstream version 8.6.1+

[John Scott]

Source: coq
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

My interest in upgrading Coq is to satisfy the requirements
to build CompCert. If there is any obstacle to doing so, I'd
love to help out whatever way I can.

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

Kernel: Linux 4.18.0-1-amd64 (SMP w/2 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)
LSM: AppArmor: enabled

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAXEkn09uX7g8Tv8W3qerYfa4vJcFAlu/7y8ACgkQ3qerYfa4
vJcARAf+NsyX5/bC4w/NNXx7c0pUQN1DL2qIn1fo5QOVFPuUfStXmhsdCHpLgpau
8K/W7/vPM5AHN6wHXWIX7W93FxD6cOF+xLMO4nSOc7t50KjUpw3v/44FMCTuKsyc
dJrrr6pKSQU/0jiWGA9RhlExU0fhTi8ruF9O0v77AIgp3nWihNqoHEm3snEGvk/U
sh9VjyAJ7HKh0LYW3Qn5cb3vTx95/TOea/7+VI9HGga4iuC33vQuP95DQDa3ztY0
LG/8Yl0NOQO0Ia9yb9wpEdQ62QbgNZhOHHMQNi739XRrkzLJjweTn50ZXgz8l2+N
Kvw34EKw/bwY3HYJfuaW2slvArRwtw==
=Kcxd
-END PGP SIGNATURE-

Bug#910783: Remove doc-base recommendation

[Sean Whitton]

Hello,

On Thu 11 Oct 2018 at 01:04PM +0100, Ian Jackson wrote:

> The problem with doc-base is not that it is a bad idea, it's that it's
> not comprehensive enough.
>
> I suggest that instead of abandoning it, we should bump the lintian
> message to a warning.

I'm not a Lintian maintainer, but I think I can safely say that we
definitely do not have project consensus for doing that.  It would be
considered a bug by a lot of people.

(I know that you treat Lintian warnings as less urgent than most other
people do, so I can understand why you would take bumping the severity
of the tag to be less related to the project consensus on the value of
doc-base.)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#910783: Remove doc-base recommendation

[Sean Whitton]

Hello Andrey,

On Thu 11 Oct 2018 at 12:57PM +0500, Andrey Rahmatullin wrote:

> It seems to me that the consensus is that doc-base is not actually useful and
> so 9.10. Registering Documents using doc-base can be dropped.

We shouldn't drop it because then the doc-base registrations in existing
packages would be undocumented.

Instead, if there is indeed consensus, we should change it so that it
no longer says that doc-base registration is recommended.

> lintian has an I: possible-documentation-but-no-doc-base-registration tag, 
> with
> 1872 emitted currently: 
> https://lintian.debian.org/tags/possible-documentation-
> but-no-doc-base-registration.html

If we make the change, Lintian should probably stop emitting the tag.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#910838: xml-core: add unit tests

[Joseph Herlant]

Package: xml-core
Version: 0.18
Severity: whishlist

It would be nice to have some unit tests on this package.
It's pretty widely used and unit tests would prevent from some
unexpected bugs after a given change.

Bug#910707: s-s-d: please implement service readiness protocol

[Michael Biebl]

Am 12.10.18 um 02:09 schrieb Michael Biebl:
> Am 11.10.18 um 22:59 schrieb Guillem Jover:
>> I've switched the socket to be on /tmp so that non-root users can use
>> it too. I've got some code to generate a tempdir to hold the socket,
>> but meh, that's ugly. 
> 
> Hm, not sure if using /tmp is a good idea.
> We want to use it in udev, i.e. during early boot where /tmp might not
> be writable yet. /run sounds like a much better choice for this case.

See attached screenshot from a VM where /etc/init.d/udev tries to use
--notify-await


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?


signature.asc
Description: OpenPGP digital signature

Bug#660687: ITA: xml-core -- XML infrastructure and XML catalog file support

[Joseph Herlant]

Control: retitle 660687 ITA: xml-core -- XML infrastructure and XML
catalog file support

Hi,

Based on the lack of answer I'm guessing you didn't have the time to
look at it so I'm going to go ahead and work on the package in the
next few weeks.
Let me know if you still want to adopt it, I can help or let you do
it, whatever you think is best.
In the meantime I'll file some bugs and prepare a new version.

Thanks
Joseph

Bug#910707: s-s-d: please implement service readiness protocol

[Michael Biebl]

Am 11.10.18 um 22:59 schrieb Guillem Jover:
> I've switched the socket to be on /tmp so that non-root users can use
> it too. I've got some code to generate a tempdir to hold the socket,
> but meh, that's ugly. 

Hm, not sure if using /tmp is a good idea.
We want to use it in udev, i.e. during early boot where /tmp might not
be writable yet. /run sounds like a much better choice for this case.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#910837: RFS: mle/1.2-1 [ITP] -- flexible terminal-based text editor (C)

[Adam Saponara]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "mle":

  Package name: mle
  Version : 1.2-1
  Upstream Author : Adam Saponara 
  URL : https://github.com/adsr/mle
  License : Apache, Expat, BSD-1-clause
  Section : editors

It builds those binary packages:

  mle - flexible terminal-based text editor (C)

To access further information about this package, please visit the following 
URL:

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

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/m/mle/mle_1.2-1.dsc

More information about hello can be obtained from https://github.com/adsr/mle.

Changes since the last upload: -

Regards,

Adam

Bug#863455: firefoxdriver: switch to geckodriver?

[Paul Wise]

On Thu, 2018-10-11 at 20:00 +0200, Sascha Girrulat wrote:

> we will try to integrate the geckodriver in the near future. But this
> will not result in a removal of the firefoxdriver because the
> geckodriver is needed by this package too. The Package contains the
> extension which will be injected as firefox start. That's mainly the
> content of this package.
> 
> The geckodriver has to be builded out of the firefox stuff.

It sounds like you are saying that Selenium cannot work with Firefox
without the non-free firefoxdriver stuff even if geckodriver is
available, is that true? It would be nice if Mozilla fixed this.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#910836: libeclipse-e4-ui-services-java: unsatisfiable dep on libeclipse-e4-core-di-services-java

[Jeremy Bicha]

Package: libeclipse-e4-ui-services-java
Version: 1.3.0+eclipse4.7.3-2
Severity: serious

libeclipse-e4-ui-services-java has an unsatisifiable dependency on
libeclipse-e4-core-di-services-java

I'm wondering if that's a typo and it should depend on
libeclipse-e4-ui-services-java

I looked at
https://salsa.debian.org/java-team/eclipse-platform-ui/commit/df00f1b0

Thanks,
Jeremy Bicha

Bug#910835: libgnutls30: elinks errors with SSL error with 3.6.4-2 libgnutls28 on any https website

[Dimitri John Ledkov]

Package: libgnutls30
Version: 3.6.4-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

I've tried upgrading libgnutls30 and squid autopkgtest surfaced the
following bug:

# The below works correctly and dumps a text
# representation of the google homepage
$ elinks -dump https://google.com

$ sudo apt install libgnutls30/experimental

$ elinks -dump https://google.com
ELinks: SSL error

I'm not sure why... Either elinks is buggy and need changes, or maybe
libgnutls30 is buggy, or if it's not buggy maybe it needs to declare
breaks on elinks.

Hopefully you can investigate this further, or like clone/reassign to
elinks package.

Regards,

Dimitri.

-BEGIN PGP SIGNATURE-

iQFEBAEBCgAuFiEEdzyZ69ChEXIhenw/ysLYuc0spfkFAlu/0rgQHHhub3hAdWJ1
bnR1LmNvbQAKCRDKwti5zSyl+XniB/4jLfZhEIed2ItKSeRfNVm0WKGJqKT9z2xQ
YT91+6BDV1AUEnTkGW3ThsKFgEKlzYEeBuQa6iE/L9YiBO9b8EggKHWd8x425ZOx
gMjRPt3BKAucqCpwy8ISwnBzxeMt4rB4SZ9KfzSbDbVCH+6uyR2ioZS67knb19lO
gAii4tSnoyHLBwh6vmZP5ngkxKjfrqHujYOlW5eLgSkbs4yIrfdDQX0vzJn8Nv8E
KJDz5Qd/1iN3mQFOC/kiVurk+ENKNyYaSc4/oW/utpRMvEfpDxIhOskmfexTDOKb
LaT8LPxBPAbvRTeQ7arPHLC/lhcBx70Hj3o9bxz+jiKyBGz438x7
=FNFV
-END PGP SIGNATURE-

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> To be sure, I have installed a VM from scratch with stretch (default
> install, just not the graphical desktop task), created a chroot with
> pbuilder there, and ran in it, and got the issue there too...

Doing the same with a VM with buster, I don't get the issue... I'll now
be able to check what differences there can be in the chroots.

Samuel

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Samuel Thibault, le ven. 12 oct. 2018 00:38:39 +0200, a ecrit:
> To be sure, I have installed a VM from scratch with stretch (default
> install, just not the graphical desktop task)

Not completely default actually, I installed in french.

Samuel

Bug#909822: mkchromecast: Should probably depend on pulseaudio-utils

[Ruben Undheim]

Hi Muammar,

> The package suggests mkchromecast-pulseaudio:
> 
> 
> Taking a closer look at the description of Mkchromecast there is the
> following text:
> 
> ```
>  mkchromecast can cast using either pulseaudio or ALSA. The respective
> dependencies can be pulled by mkchromecast-pulseaudio and
> mkchromecast-alsa dependency packages respectively. For more
>  information, please read the README.Debian file shipped in this package.
> ```
> 
> I think this bug should be closed. Let me know what you think.

You are right. It looks quite solid. I must admit I filed the bug in a hurry
after being annoyed when I did not get it to work immediately - but rather
quickly found out what single piece was missing (without looking at the
documentation). Then I spent the time afterwards enjoying the music via my big
loudspeakers over mkchromecast - and forgot completely about the bug.


Feel free to close the bug.

Thanks. and sorry for wasting your time.. :(

Best regards
Ruben

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Samuel Thibault, le jeu. 11 oct. 2018 19:02:10 +0200, a ecrit:
> Emilio Pozuelo Monfort, le jeu. 11 oct. 2018 18:33:10 +0200, a ecrit:
> > Weird. I just did:
> > 
> > sudo cowbuilder --update
> > debcheckout sphinxbase
> > cd sphinxbase
> > pdebuild
> > 
> > And it was fine. No idea what we're doing differently.
> 
> Ok. I have run it on a chroot on the barriere porter machine, and it was
> fine too. I'll see what is different on my system.

Mmm...

To be sure, I have installed a VM from scratch with stretch (default
install, just not the graphical desktop task), created a chroot with
pbuilder there, and ran in it, and got the issue there too...

Yes, debian/python-sphinxbase.install does contain

debian/tmp/usr/lib/python2*

without usr/lib.

Samuel

Bug#910834: python-hiredis FTBFS, inporterror when running testsuite.

[peter green]

package: python-hiredis
version: 0.2.0-3
severity: serious

python-hiredis failed to build during the re-build for libhiredis0.14, this 
failure does not seem to be architecture specific


Traceback (most recent call last):
   File "/<>/test.py", line 4, in 
 import test
   File "/<>/test/__init__.py", line 12, in 
 from . import reader
   File "/<>/test/reader.py", line 3, in 
 import hiredis
   File "/<>/.pybuild/cpython2_2.7_hiredis/build/hiredis/__init__.py", 
line 1, in 
 from .hiredis import Reader, HiredisError, ProtocolError, ReplyError
ImportError: 
/<>/.pybuild/cpython2_2.7_hiredis/build/hiredis/hiredis.so: 
undefined symbol: redisReplyReaderGetError
E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: 
BUILDDIR=/<>/.pybuild/cpython2_2.7_hiredis/build python2.7 
/<>/test.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
"--test-args=BUILDDIR={build_dir} {interpreter} {dir}/test.py" returned exit 
code 13


https://buildd.debian.org/status/package.php?p=python-hiredis=unstable

Bug#910702: gnome-shell-pomdoro: Please Build-Depends on gjs

[Joseph Herlant]

On Thu, Oct 11, 2018 at 3:02 PM Jeremy Bicha  wrote:
> Would it be ok if I uploaded to Debian from your git repo if we do need it?

I have absolutely no problems with that. :)
I'm done with my changes for now. Feel free to cut the release
whenever you need it.

Joseph

Bug#910702: gnome-shell-pomdoro: Please Build-Depends on gjs

[Jeremy Bicha]

On Thu, Oct 11, 2018 at 4:57 PM Joseph Herlant  wrote:
> I can't upload for now because my key didn't make the keyring update
> yet, so I have to wait until the end of the month for that upload.
> I have a few other updates to make anyway, so unless it's pressing,
> I'll wait a bit for the upload.

We got approval to do the gjs transition with the s390x removal. I'm
not sure how exactly that is going to work: we may want to upload
gnome-shell-pomodoro then to complete the transition.

Would it be ok if I uploaded to Debian from your git repo if we do need it?

https://bugs.debian.org/906016

Thanks,
Jeremy Bicha

Bug#910634: spice: diff for NMU version 0.14.0-1.2

[Salvatore Bonaccorso]

Control: tags 910634 + patch
Control: tags 910634 + pending

Dear maintainer,

I've prepared an NMU for spice (versioned as 0.14.0-1.2) and
uploaded it. Attached is the debdiff. The testsuite keys were
generated following https://www.spice-space.org/spice-user-manual.html
.

Regards,
Salvatore
diff -Nru spice-0.14.0/debian/changelog spice-0.14.0/debian/changelog
--- spice-0.14.0/debian/changelog	2018-09-15 09:15:28.0 +0200
+++ spice-0.14.0/debian/changelog	2018-10-11 23:41:48.0 +0200
@@ -1,3 +1,10 @@
+spice (0.14.0-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * tests/pki: Use CA/certificate with 2048 bit RSA keys (Closes: #910634)
+
+ -- Salvatore Bonaccorso   Thu, 11 Oct 2018 23:41:48 +0200
+
 spice (0.14.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru spice-0.14.0/debian/patches/refresh-tests-pki-keys.patch spice-0.14.0/debian/patches/refresh-tests-pki-keys.patch
--- spice-0.14.0/debian/patches/refresh-tests-pki-keys.patch	1970-01-01 01:00:00.0 +0100
+++ spice-0.14.0/debian/patches/refresh-tests-pki-keys.patch	2018-10-11 23:41:48.0 +0200
@@ -0,0 +1,131 @@
+Description: tests/pki: Use CA/certificate with 2048 bit RSA keys
+ The testsuite contains only 1024 bit RSA keys generated/refreshed
+ in the upstream commit
+ https://cgit.freedesktop.org/spice/spice/commit/server/tests/pki?id=7b5e294a363e1500ab1a5b143da1602c9fed0547
+ .
+ In openssl/1.1.1-1 /etc/ssl/openssl.cnf contains
+ .
+   CipherString = DEFAULT@SECLEVEL=2
+ .
+ This level is responsible to not accept the 80 bits used in
+ the certificate in this test, while we need at least 112 bits.
+ .
+ Generate new certificates following the instructions from
+ https://www.spice-space.org/spice-user-manual.html .
+Origin: vendor
+Bug: https://gitlab.freedesktop.org/spice/spice/issues/27
+Bug-Debian: https://bugs.debian.org/910634
+Forwarded: no
+Author: Salvatore Bonaccorso 
+Last-Update: 2018-10-11
+
+--- a/server/tests/pki/ca-cert.pem
 b/server/tests/pki/ca-cert.pem
+@@ -1,15 +1,21 @@
+ -BEGIN CERTIFICATE-
+-MIICUjCCAbugAwIBAgIJAKM/WOQQB3iqMA0GCSqGSIb3DQEBCwUAMEIxCzAJBgNV
+-BAYTAlhYMRUwEwYDVQQHDAxEZWZhdWx0IENpdHkxHDAaBgNVBAoME0RlZmF1bHQg
+-Q29tcGFueSBMdGQwHhcNMTcwMzIzMTA0MDEwWhcNNDcwMzE2MTA0MDEwWjBCMQsw
+-CQYDVQQGEwJYWDEVMBMGA1UEBwwMRGVmYXVsdCBDaXR5MRwwGgYDVQQKDBNEZWZh
+-dWx0IENvbXBhbnkgTHRkMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZXCWk
+-OuMVr45sAE9a7RM1K2brRdwzjdEqy1OV0dhqymL9YG/iygGp4HqwkLvLqEewq1bD
+-sCcIbRlOidmBv9+uhy2zU9tBzaAptB7Vb6lAAa0PHlUQnQskVcPCwsK7RxwWw0/J
+-pfld8qDAY1t8qM6mSy9Kuyk0X4FOvcuVQKCmiQIDAQABo1AwTjAdBgNVHQ4EFgQU
+-eCFCqTxHPsa+7B0vcCZyxEgCnBwwHwYDVR0jBBgwFoAUeCFCqTxHPsa+7B0vcCZy
+-xEgCnBwwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQsFAAOBgQBr+TeJqQH+SlAp
+-GcA90SkGnqcEJSijjF9qcgmL0F5Z/yCBDaZa6F3wh/rXNZB2rKfQGW6Mem9KS8cm
+-lui4A1pomMZBWQMwUYP02UF1fHg76RCG7PMhBZR2GkqHqHWfZBfFigdIWKFrm5fq
+-92l4opvf97dSiOF9x1JLPUeoOOJL8A==
++MIIDZTCCAk2gAwIBAgIUP4OBTjXwyIOome7Rw5J1P442Rk8wDQYJKoZIhvcNAQEL
++BQAwQjELMAkGA1UEBhMCWFgxFTATBgNVBAcMDERlZmF1bHQgQ2l0eTEcMBoGA1UE
++CgwTRGVmYXVsdCBDb21wYW55IEx0ZDAeFw0xODEwMTEyMTM3NTRaFw00ODEwMDMy
++MTM3NTRaMEIxCzAJBgNVBAYTAlhYMRUwEwYDVQQHDAxEZWZhdWx0IENpdHkxHDAa
++BgNVBAoME0RlZmF1bHQgQ29tcGFueSBMdGQwggEiMA0GCSqGSIb3DQEBAQUAA4IB
++DwAwggEKAoIBAQClmeuCqQM4Xc0iW4+qqc7HmNG6jXSh/5+s8Dh1eydQMvfrthT5
+++EQSSq+aUyT8bK4xVelJOQbqWBnMh56sZgd4L/vk0eer9QMl1rqR3roTAGc9STuJ
++8GddiAMzaYJ/sGaU2xL//sa3dTCr9qKe/JhBCCzFIJVgnP48WvoKfSdiu5IRF5WY
++OAEpXNu8a7IE5w0gnNro73r4cOJ/MhReMDKsB3nRiCFKnGsQjwknjRVI7TiAWhd4
++g+l6+4kuwLP+nhumDT8LhL+gDKIEHKCZHScD2jfF1f8JPKbXUmkW0FNZ2b8dsdwv
++R6RBgVNWZdbSZt7nT+NeRDxd19bNMqf/2yknAgMBAAGjUzBRMB0GA1UdDgQWBBT1
++sI07A1i84f/13iwxnTci4N6NgzAfBgNVHSMEGDAWgBT1sI07A1i84f/13iwxnTci
++4N6NgzAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQBWnDlRWTBb
++zBVVFRhsBo+nI4Oc8g5anTj4Tqaemc+g3dVy2WYnln3S8ZZDJrF0VevCGPeQ6mrC
++zxGwFDWExqBuMvXMKgiOff8THXPZuDpaObM9iZCtNCbvcPaW4dvXhPgm8mdUFdkI
++lFfXw7zmIaPOEY+aTLc5BShB0RVnqdaNubFrepXU+vWFfjUPHIudxr/IHvlpzfZQ
++Cmlqf5qe6i4aVMAhYWt2Z6oGHIIq+0V3IgOr/mZMkg/VC7LX7MOKBtLdeHqTnf0R
++aYQc+J120F9zE51A0xK1/u5inMDcSmODV9nzzYyZ6NyLSZlyC7l3NbNL4M4ZUn4M
++uN4ROAAxfc6v
+ -END CERTIFICATE-
+--- a/server/tests/pki/server-cert.pem
 b/server/tests/pki/server-cert.pem
+@@ -1,13 +1,18 @@
+ -BEGIN CERTIFICATE-
+-MIIB8zCCAVwCAQEwDQYJKoZIhvcNAQELBQAwQjELMAkGA1UEBhMCWFgxFTATBgNV
++MIIC+DCCAeACAQEwDQYJKoZIhvcNAQELBQAwQjELMAkGA1UEBhMCWFgxFTATBgNV
+ BAcMDERlZmF1bHQgQ2l0eTEcMBoGA1UECgwTRGVmYXVsdCBDb21wYW55IEx0ZDAe
+-Fw0xNzAzMjMxMDQwNDVaFw00NzAzMTYxMDQwNDVaMEIxCzAJBgNVBAYTAlhYMRUw
++Fw0xODEwMTEyMTM3NTZaFw00ODEwMDMyMTM3NTZaMEIxCzAJBgNVBAYTAlhYMRUw
+ EwYDVQQHDAxEZWZhdWx0IENpdHkxHDAaBgNVBAoME0RlZmF1bHQgQ29tcGFueSBM
+-dGQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMXDPMZLse8CuEwJKMkvEdmB
+-wK+33T0jOMkUJPt8LseLCjXmYOir2gWrsnP5fgxpwx/Xxb61ivwhAtC2mFcy3xXp
+-RNkDHk3F2XpGwD0Msj9tR9DYidyRz/rN1BRth5ZLm0TvjmwWcBb7qWICIVTLsp6z
+-XuM/erA3E00s7VANBlaPAgMBAAEwDQYJKoZIhvcNAQELBQADgYEA2Om01Qav2OQc

Bug#910786: opensc: No longer recognizes Yubikey NEO after upgrade to 0.16.0-3+deb9u1

[Hilko Bengen]

Hi,

after some digging and testing, I come to the conclusion that the the
immediate cause for the breakage I reported is the change made to the
piv_general_io() function (src/libopensc/card-piv.c, expanded for
context): Because rbuflen is set to zero, sc_asn1_read_tag will never
read/parse an ASN.1 tag.

Reverting this single change seems to fix my problems, however this
leaves the clear possibility for overflowing receive buffers that are
passed into the function, this has so far only worked by accident...

Cheers,
-Hilko

@@ -525,15 +525,16 @@ static int piv_general_io(sc_card_t *card, int ins, int 
p1, int p2,
rbuflen = 0;  /* in case rseplen < 3  i.e. not parseable */
if ( recvbuflen && recvbuf && apdu.resplen > 3) {
*recvbuflen = 0;
/* we should have all the tag data, so we have to tell 
sc_asn1_find_tag
 * the buffer is bigger, so it will not produce "ASN1.tag too 
long!" */
 
body = rbuf;
-   if (sc_asn1_read_tag(, 0x, _out, _out, 
) !=  SC_SUCCESS)   {
+   if (sc_asn1_read_tag(, rbuflen, _out, _out, 
) !=  SC_SUCCESS
+   || body == NULL)  {
/* only early beta cards had this problem */
sc_debug(card->ctx, SC_LOG_DEBUG_NORMAL, "* 
received buffer tag MISSING ");
body = rbuf;
/* some readers/cards might return 6c 00 */
if (apdu.sw1 == 0x61  || apdu.sw2 == 0x6c )
bodylen = 12000;
else

Bug#910790: [Pkg-raspi-maintainers] Bug#910790: Acknowledgement (new initrd file was not found)

[Matthias Luescher]

Hi

Here is my proposal to fix the issue:
https://salsa.debian.org/lueschem-guest/raspi3-firmware/commit/58d7fec1a6e695371f0ed15b82560421e82f0d94

Best regards
Matthias

Am Do., 11. Okt. 2018 um 12:45 Uhr schrieb Santiago Garcia Mantinan <
ma...@debian.org>:

> Hi again!
>
> After that install of the kernel I tried a reinstall via...
> # apt-get install --reinstall linux-image-4.18.0-2-arm64
> Lendo as listas de paquetes... Feito
> Construindo a árbore de dependencias
> Lendo a información do estado... Feito
> 0 anovados, 0 instalados, 1 reinstalados, Vanse retirar 0 e deixar 51
> sen anovar.
> Ten que recibir 0 B/36,5 MB de arquivos.
> Despois desta operación ocuparanse 0 B de disco adicionais.
> (A ler a base de datos ... 31785 files and directories currently
> installed.)
> Preparing to unpack .../linux-image-4.18.0-2-arm64_4.18.10-2_arm64.deb ...
> Unpacking linux-image-4.18.0-2-arm64 (4.18.10-2) over (4.18.10-2) ...
> A configurar linux-image-4.18.0-2-arm64 (4.18.10-2) ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.18.0-2-arm64
> raspi3-firmware: deferring update via initramfs-tools (hook will be
> called later by the kernel
>
> What I saw there was that the propagation to /boot/firmware had been
> done by raspi3-firmware before the update-initramfs had built the new
> initrd and later the new initrd is not propagated to firmware, so I
> ended up with an older -2 initrd on the firmware dir.
>
> Regards.
> --
> Manty/BestiaTester -> http://manty.net
>
> ___
> Pkg-raspi-maintainers mailing list
> pkg-raspi-maintain...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-raspi-maintainers
>

Bug#910531: kdepim-runtime: Authenticating to gmail using "Gmail" authentication type (oauth, kgapi?) leads to segfault

[Alexander Kernozhitsky]

Just tested it now, GMail auth works fine.

Is the bug still present for you?

-- 
Alexander Kernozhitsky

Bug#910707: s-s-d: please implement service readiness protocol

[Guillem Jover]

On Thu, 2018-10-11 at 01:46:02 +0200, Michael Biebl wrote:
> A quick test with /lib/systemd/systemd-udevd suggests that this is not
> quite working yet.
> 
> One thing I noticed is that NOTIFY_SOCKET is not set.
> And even if I manually set that via
> export NOTIFY_SOCKET=/run/s-s-d-channel.id.notify
> a test script using systemd-notify [1] yields
> 
> Failed to notify init system: Connection refused

Ok, I've force pushed to that branch a version that should work, at
least it does for me locally. :)

I've switched the socket to be on /tmp so that non-root users can use
it too. I've got some code to generate a tempdir to hold the socket,
but meh, that's ugly. I'm also undecided whether the timeout should
exit non-zero, I might want to make that configurable, and perhaps
default to non-failure. I think I'll also add support for ERRNO+STATUS
and probably also the new EXTEND_TIMEOUT_USEC.

Thanks,
Guillem

Bug#908834: please build libzstd udeb so that btrfs-progs can use zstd in Debian Installer

[Cyril Brulebois]

Hi,

And thanks for checking with us (explicit Cc's welcome, by the way).

Alex Mestiashvili  (2018-10-11):
> On 10/09/2018 07:39 PM, Nicholas D Steeves wrote:
> > Control: retitle -1 please build libzstd udeb so that btrfs-progs can use 
> > zstd in Debian Installer
> > Control: reassign -1 src:libzstd/ 1.3.5+dfsg-1
> 
> Done, dropped zstd-udeb.
> 
> > Please read what Cyril (Debian Installer Team) wrote at these bugs in
> > case these questions have already been answered:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898410
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886968
> 
> Thank you, that was useful.
> 
> I've updated the libzstd repository[0].
> 
> @Kibi, could you please review that?
> 
> basically I just call dh_makeshlibs with -V'libzstd1 (>=1.3.5)' as there
> are new symbols introduced in this version.

From a quick look at debian/control:
> Package: libzstd1-udeb
> Architecture: any
> Multi-Arch: same

This field isn't needed for d-i.

> Section: debian-installer
> Depends: ${misc:Depends},
>  ${shlibs:Depends}
> Package-Type: udeb
> Description: fast lossless compression algorithm
>  Zstd, short for Zstandard, is a fast lossless compression algorithm, 
> targeting
>  real-time compression scenarios at zlib-level compression ratio.
>  .
>  This package contains the shared library.
>  .
>  This is a minimal package for debian-installer.

FWIW: A single-line description is sufficient in a d-i context.


From a quick look at debian/rules, a real issue:
> override_dh_makeshlibs:
> dh_makeshlibs -plibzstd1 -V'libzstd1 (>=1.3.5)' 
> --add-udeb=libzstd-udeb

You're passing libzstd-udeb to --add-udeb, while the actual package is
called libzstd1-udeb, so the generated shlibs file (see DEBIAN/shlibs in
your build tree) will point to a package that doesn't exist, generating
dependencies that can be satisfied for udebs using symbols from libzstd.

[I'm used to seeing a space after '>=' but apparently having no space
seems supported as well:
(sid-amd64-devel)kibi@armor:~/hack/libzstd$ grep '>=' 
/var/lib/dpkg/info/*shlibs | grep -v '>= '
/var/lib/dpkg/info/libgcrypt20:amd64.shlibs:libgcrypt 20 libgcrypt20 (>=1.8.0-0)
/var/lib/dpkg/info/libgcrypt20:amd64.shlibs:udeb: libgcrypt 20 libgcrypt20-udeb 
(>=1.8.0-0)
/var/lib/dpkg/info/libprocps6:amd64.shlibs:libprocps 6 libprocps6 (>=2:3.3.13-1)
/var/lib/dpkg/info/libprocps7:amd64.shlibs:libprocps 7 libprocps7 (>=2:3.3.15-1)
/var/lib/dpkg/info/libtasn1-6:amd64.shlibs:libtasn1 6 libtasn1-6 (>=4.7-0)
]

Other than that, the resulting udeb after a binary build looks OK to me.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#898084: Please migrate to libsrtp2 in Buster

[Bernhard Schmidt]

Control: tags -1 patch
Control: forward -1 https://bugs.kde.org/show_bug.cgi?id=399678

On Sun, May 06, 2018 at 11:55:14PM +0200, Bernhard Schmidt wrote:

> I haven't seen any upstream work on this and it seems to be entangled with the
> mediastreamer2 FTBFS (also in libjingle). I'm filing this bug so we don't
> forget about it.

Filed it upstream and minutes later got a reply that archlinux has a
patch for it.

https://git.archlinux.org/svntogit/packages.git/tree/trunk/kopete-srtp2.patch?h=packages/kopete

Bernhard

Bug#909822: mkchromecast: Should probably depend on pulseaudio-utils

[Muammar El Khatib]

Hi Ruben,

On Sat, Sep 29, 2018 at 3:33 AM Ruben Undheim
 wrote:
>
> Package: mkchromecast
> Version: 0.3.8.1-1
> Severity: normal
>
> Dear Maintainer,
>
> I get an error saying 'pactl' cannot be found when
> starting. Solved it by installing pulseaudio-utils.
>

The package suggests mkchromecast-pulseaudio:


```
Package: mkchromecast-pulseaudio
Version: 0.3.8.1-1
State: not installed
Priority: optional
Section: sound
Maintainer: Muammar El Khatib 
Architecture: all
Uncompressed Size: 16.4 k
Depends: pavucontrol, pulseaudio-utils, pulseaudio, mkchromecast
Description: Pulseaudio dependencies to cast with mkchromecast
 This dependency package contains an informational list of packages
which are considered essential for using mkchromecast together with
pulseaudio sound server. This package also depends on
 the packages on that list.
Homepage: http://mkchromecast.com
Tags: admin::hardware, role::plugin, works-with::audio
```

Taking a closer look at the description of Mkchromecast there is the
following text:

```
 mkchromecast can cast using either pulseaudio or ALSA. The respective
dependencies can be pulled by mkchromecast-pulseaudio and
mkchromecast-alsa dependency packages respectively. For more
 information, please read the README.Debian file shipped in this package.
```

I think this bug should be closed. Let me know what you think.

Best,

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

Bug#910822: golang-docker-credential-helpers: headless gnome-keyring failure

[Nye Liu]

Sorry, missed the rest of the log:

Oct 11 20:07:15  dbus-daemon[29865]: [session uid=1012 pid=29865] 
Activating service name='org.gnome.keyring.SystemPrompter' requested by 
':1.34' (uid=1012 pid=1611 comm="/usr/bin/gnome-keyring-daemon --start 
--foreground")
Oct 11 20:07:15  org.gnome.keyring.SystemPrompter[29865]: Unable to 
init server: Could not connect: Connection refused

Oct 11 20:07:15  gcr-prompter[1783]: cannot open display:
Oct 11 20:07:15  dbus-daemon[29865]: [session uid=1012 pid=29865] 
Activated service 'org.gnome.keyring.SystemPrompter' failed: Process 
org.gnome.keyring.SystemPrompter exited with status 1
Oct 11 20:07:15  gnome-keyring-daemon[1611]: couldn't initialize 
prompt: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: 
Process org.gnome.keyring.SystemPrompter exited with status 1
Oct 11 20:07:15  gnome-keyring-d[1611]: couldn't initialize prompt: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.keyring.SystemPrompter exited with status 1

Bug#910822: golang-docker-credential-helpers: headless gnome-keyring failure

[Nye Liu]

Likely due to gnome-keyring needing d-bus to have a DISPLAY:

gnome-keyring-daemon[1611]: couldn't initialize prompt: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.keyring.SystemPrompter exited with status 1


This is fundamentally broken with respect to headless systems.

Bug#910833: mozjs52: Please build with "--disable-pie" on powerpcspe

[John Paul Adrian Glaubitz]

Source: mozjs52
Version: 52.9.1-1
Severity: normal
User: debian-powe...@lists.debian.org
Usertags: powerpcspe

Hello!

On powerpcspe, the mozjs52 build fails with:

checking for --noexecstack option to as... yes
checking for -z noexecstack option to ld... yes
checking for -z text option to ld... yes
checking for --build-id option to ld... yes
checking for PIE support... no
configure: error: --enable-pie requires PIE support from the linker.
ERROR: old-configure failed
make[1]: *** [debian/rules:77: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:53: binary-arch] Error 2

For powerpcspe, we haven't enabled PIE in the toolchain. Hence,
please disable PIE on powerpcspe the same way it has been disabled
for sh4.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#902025: Any news on the emacs 26 front ?

[Rob Browning]

Emmanuel Charpentier  writes:

> an no news since...
>
> Is there any hope to get emacs 26.1 as, say, stockings filler ? Or as
> turkey stuffing ?

I'd certainly hope so, but right now we're blocked on some copyright
questions, in particular with respect to some of the unicode.org files
that Emacs includes.  I've contacted them, and my understanding is that
they're looking in to it, but we haven't heard back yet.

Once that's resolved, the remaining work shouldn't take too long.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#877019: ITP: nix -- Purely functional package manager

[Kai Harries]

Raju Devidas  writes:

> On Wed, 27 Sep 2017 20:05:06 + Kai Harries 
> wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Kai Harries 
>>
>> * Package name : nix
>> Version : 1.1.15
>> Upstream Author : Eelco Dolstra 
>> * URL : https://nixos.org/nix/
>> * License : LGPL v2.1
>> Programming Lang: C++, Shell, C, Perl
>> Description : Purely functional package manager
>>
>> A powerful package manager for Linux and other Unix systems that
>> makes package management reliable and reproducible. Nix provides
>> atomic upgrades and rollbacks, side-by-side installation of multiple
>> versions of a package, multi-user package management and easy setup of
>> build environments.
>>
>> I personally use it to install software that is not part of Debian or
>> software that I need in a newer version.
>>
>> My packaging efforts can be found here [1].
>>
>> I am looking for a sponsor.
>>
>> [1] https://github.com/KaiHa/nix-debian/releases
>>
> Have you made any progress on this?
> I discovered the package manager today and I think it would be great to
> have it in Debian.

Regarding getting nix included into Debian, no. First this [1] must be
solved. But the packaging itself should work, you can build a Debian
package yourself by cloning the repository [2] and following the
instructions in the README.

[1] https://github.com/KaiHa/nix-debian/issues/2
[2] https://github.com/KaiHa/nix-debian

Bug#910811: [Pkg-xen-devel] Bug#910811: xenstore-utils: upgrade error: xenstore-utils_4.11.1 unpack error with '/usr/share/man/man1/xenstore-chmod.1.gz'

[Hans van Kranenburg]

Control: tags -1 pending

Hi Diederik,

On 10/11/2018 06:25 PM, Diederik de Haas wrote:
> Package: xenstore-utils
> Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-2
> Severity: normal
> 
> while doing 'aptitude safe-upgrade' with today's updates, I got the
> following error:
> 
> Unpacking xenstore-utils (4.11.1~pre.20180911.5acdd26fdc+dfsg-2) over 
> (4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-NA96TI/4-xenstore-utils_4.11.1~pre.20180911.5acdd26fdc+dfsg-2_amd64.deb
>  (--unpack):
>  trying to overwrite '/usr/share/man/man1/xenstore-chmod.1.gz', which is also 
> in package xen-utils-common 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9
> Preparing to unpack 
> .../5-xen-utils-common_4.11.1~pre.20180911.5acdd26fdc+dfsg-2_amd64.deb ...
> Unpacking xen-utils-common (4.11.1~pre.20180911.5acdd26fdc+dfsg-2) over 
> (4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) ...
> Errors were encountered while processing:
>  
> /tmp/apt-dpkg-install-NA96TI/4-xenstore-utils_4.11.1~pre.20180911.5acdd26fdc+dfsg-2_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Doing another 'aptitude safe-upgrade' directly thereafter succeeded,
> hence (only) severity normal.
> 
> My guess would be a missing breaks/replaces issue.

Thanks for testing.

The fix is...

https://salsa.debian.org/xen-team/debian-xen/commit/61a40bf45edb1c63a000ac69bdc69a1dc3ff0845

...which will be in the next package upload RSN:

https://alioth-lists.debian.net/pipermail/pkg-xen-devel/2018-October/007394.html

If you want to follow progress around Xen in Debian Unstable, I can
recommend to subscribe to the related mailing list:

https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-xen-devel

Testing feedback is much appreciated, and knowing about known issues
might save you time. :)

Have fun,
Regards,
Hans van Kranenburg


> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
> (101, 'experimental'), (1, 'experimental-debug')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.18.0-2-amd64 (SMP w/16 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)
> LSM: AppArmor: enabled
> 
> Versions of packages xenstore-utils depends on:
> ii  libc62.27-6
> ii  libxenstore3.0   4.11.1~pre.20180911.5acdd26fdc+dfsg-2
> ii  libxentoolcore1  4.11.1~pre.20180911.5acdd26fdc+dfsg-2
> 
> xenstore-utils recommends no packages.
> 
> Versions of packages xenstore-utils suggests:
> pn  xen-doc  
> 
> -- no debconf information
> 
> ___
> Pkg-xen-devel mailing list
> pkg-xen-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-xen-devel
> 

Bug#910830: Downloading: gives up too soon on broken internet connection

[David Lawyer]

Package: aptitude
Version: 0.8.11-3
Severity: normal

Dear Maintainer,
I have a free dial-up connection to the inernet and do long (like
overnight) unattended downloads.  When the connection is lost my wvdial
program redials and a few minutes later reestablises a connection of my
computer with the internet.  But unfortunatly, by this time aptitude has
given up downloading and fails to utilize the restored connection.  Then
my computer spends hours doing nothing (unattended).  When a connection is
lost, aptititude should wait several minutes before giving up downloading.

My isp (Southern California Freenet) only provides surplus bandwidth free
and if it gets congested will drop non-paying users like me.  Thus
restoring broken connections is essential. Since not all other users
redial there is usually surplus bandwidth to use after freeloaders are
dropped so usually redialing works fine.  But aptitude stops working.

-- Package-specific info:
Terminal: linux
$DISPLAY not set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.11
Compiler: g++ 8.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.1
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20180714
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-gate.so.1 (0xb7f46000)
libapt-pkg.so.5.0 => /usr/lib/i386-linux-gnu/libapt-pkg.so.5.0 
(0xb78f)
libncursesw.so.6 => /lib/i386-linux-gnu/libncursesw.so.6 (0xb78ae000)
libtinfo.so.6 => /lib/i386-linux-gnu/libtinfo.so.6 (0xb7886000)
libsigc-2.0.so.0 => /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 
(0xb787e000)
libcwidget.so.3 => /usr/lib/i386-linux-gnu/libcwidget.so.3 (0xb7771000)
libsqlite3.so.0 => /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xb764c000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/i386-linux-gnu/libboost_iostreams.so.1.62.0 (0xb763)
libboost_system.so.1.62.0 => 
/usr/lib/i386-linux-gnu/libboost_system.so.1.62.0 (0xb762b000)
libxapian.so.30 => /usr/lib/i386-linux-gnu/sse2/libxapian.so.30 
(0xb73ea000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb73ca000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb7249000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb7146000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb7128000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb6f4e000)
libresolv.so.2 => /lib/i386-linux-gnu/libresolv.so.2 (0xb6f35000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb6f16000)
libbz2.so.1.0 => /lib/i386-linux-gnu/libbz2.so.1.0 (0xb6f03000)
liblzma.so.5 => /lib/i386-linux-gnu/liblzma.so.5 (0xb6ed7000)
liblz4.so.1 => /usr/lib/i386-linux-gnu/liblz4.so.1 (0xb6eb8000)
libzstd.so.1 => /usr/lib/i386-linux-gnu/libzstd.so.1 (0xb6e1f000)
libudev.so.1 => /lib/i386-linux-gnu/libudev.so.1 (0xb6dfd000)
/lib/ld-linux.so.2 (0xb7f48000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb6df5000)
librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb6deb000)
libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xb6de1000)

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

Kernel: Linux 4.18.0-1-686-pae (SMP w/2 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/bash
Init: systemd (via /run/systemd/system)

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.11-3
ii  libapt-pkg5.0 1.6.4
ii  libboost-iostreams1.62.0  1.62.0+dfsg-10
ii  libboost-system1.62.0 1.62.0+dfsg-10
ii  libc6 2.27-6
ii  libcwidget3v5 0.5.17-11
ii  libgcc1   1:8.2.0-6
ii  libncursesw6  6.1+20180714-1
ii  libsigc++-2.0-0v5 2.10.0-2.1
ii  libsqlite3-0  3.24.0-1
ii  libstdc++68.2.0-6
ii  libtinfo6 6.1+20180714-1
ii  libxapian30   1.4.7-2

Versions of packages aptitude recommends:
pn  libparse-debianchangelog-perl  
ii  sensible-utils 0.0.12

Versions of packages aptitude suggests:
pn  apt-xapian-index
ii  aptitude-doc-en [aptitude-doc]  0.8.11-3
pn  debtags 
pn  tasksel 

-- no debconf information

Bug#902025: Any news on the emacs 26 front ?

[Emmanuel Charpentier]

On Sept 10, we were told :

> I do, and have been working on it, but haven't found enough time to
> finish the DFSG split yet, after I found some additional files that 
> are probably going to have to be removed from main, and which may 
> require some adaptation in the code/build-infrastructure.

an no news since...

Is there any hope to get emacs 26.1 as, say, stockings filler ? Or as
turkey stuffing ?

--
Emmanuel Charpentier

Bug#908161: Please enable building a riscv64 kernel image

[Karsten Merker]

Control: tags 908161 + patch

On Tue, Sep 18, 2018 at 08:57:01PM +0200, Karsten Merker wrote:
> On Sat, Sep 08, 2018 at 11:15:36PM +0100, Ben Hutchings wrote:
> 
> [Building a linux-image-*-riscv64 binary package]
> 
> > The addition of riscv will have to wait until it has support
> > for an initramfs.
> > 
> > Is this commit sufficient to make booting with an initramfs work:
> > 
> > commit cdc7274029ca5984350a057a2399aaa340d3be2d
> > Author: Guenter Roeck 
> > Date:   Tue Aug 28 17:33:46 2018 -0700
> > 
> > riscv: Do not overwrite initrd_start and initrd_end
> > 
> > or are more changes needed?
> 
> Hello,
> 
> just a short status update: the aforementioned patch has been
> included in the upstream 4.19-rc4 release and I can confirm
> that the initramfs support for riscv64 works with 4.19-rc4.
> 
> The other major issue in this bug (unversioned symbols breaking
> the package build) is still unresolved; I'll report back as soon
> as I have received feedback from the upstream RISC-V architecture
> maintainer.

Hello,

all previously mentioned issues have been addressed in
the meantime:

- The broken initrd support has been fixed upstream in kernel
  4.19-rc4.

- The symbol version issue has been fixed upstream in kernel
  4.19-rc6.

- The riscv64 kernel config has been modularized as far as
  possible and all redundant entries have been removed.

- Headings have been added to the kernel config.

Attached is a new patch, alternatively it is available as a merge
request on salsa as suggested earlier in the discussion:

  https://salsa.debian.org/kernel-team/linux/merge_requests/66

The resulting kernel has been successfully tested on a qemu
"virt" board:

[0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020
[0.00] Linux version 4.19.0-rc7-riscv64 
(debian-ker...@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-7)) #1 SMP 
Debian 4.19~rc7-1~exp2 (2018-10-08)
[0.00] bootconsole [early0] enabled
[0.00] Initial ramdisk at: 0x(ptrval) (43521258 bytes)
[0.00] Zone ranges:
[0.00]   DMA32[mem 0x8020-0x]
[0.00]   Normal   [mem 0x0001-0x2fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x8020-0x0002]
[0.00] Initmem setup node 0 [mem 0x8020-0x0002]
[0.00] On node 0 totalpages: 2620928
[0.00]   DMA32 zone: 8184 pages used for memmap
[0.00]   DMA32 zone: 0 pages reserved
[0.00]   DMA32 zone: 523776 pages, LIFO batch:63
[0.00]   Normal zone: 32768 pages used for memmap
[0.00]   Normal zone: 2097152 pages, LIFO batch:63
[0.00] software IO TLB: mapped [mem 0xfbfff000-0xf000] (64MB)
[0.00] elf_hwcap is 0x112d
[0.00] percpu: Embedded 19 pages/cpu @(ptrval) s39384 r8192 
d30248 u77824
[0.00] pcpu-alloc: s39384 r8192 d30248 u77824 alloc=19*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 2579976
[0.00] Kernel command line: console=ttyS0 ro root=/dev/vda
[0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 
bytes)
[0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 
bytes)
[0.00] Sorting __ex_table...
[0.00] Memory: 10178016K/10483712K available (4955K kernel code, 504K 
rwdata, 1633K rodata, 446K init, 934K bss, 305696K reserved, 0K cma-reserved)
[0.00] random: get_random_u64 called from 
__kmem_cache_create+0x46/0x55c with crng_init=0
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] ftrace: allocating 21055 entries in 83 pages
[0.00] rcu: Hierarchical RCU implementation.
[0.00] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[0.00] NR_IRQS: 0, nr_irqs: 0, preallocated irqs: 0
[0.00] plic: mapped 10 interrupts to 4 (out of 8) handlers.
[0.00] clocksource: riscv_clocksource: mask: 0x 
max_cycles: 0x24e6a1710, max_idle_ns: 440795202120 ns
[0.004000] Console: colour dummy device 80x25
[0.008000] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 20.00 BogoMIPS (lpj=4)
[0.012000] pid_max: default: 32768 minimum: 301
[0.016000] Security Framework initialized
[0.016000] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.02] AppArmor: AppArmor initialized
[0.024000] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
[0.028000] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 
bytes)
[0.072000] rcu: Hierarchical SRCU implementation.
[0.092000] smp: Bringing up secondary CPUs ...
[0.112000] smp: Brought up 1 node, 4 CPUs
[0.16] 

Bug#910829: some upstream errors seen via --verbose mode via torbrowser-launcher.

[shirish शिरीष]

Package: torbrowser-launcher
Version: 0.2.9-6
Severity: normal

Dear Maintainer,

I saw a few errors on the CLI while using torbrowser-launcher.

First is, it's not known in reportbug which version of torbrowser was
actually used. It was Torbrowser 8.0.2

I did see probably upstream errors which probably upstream has to solve -

Fontconfig warning:
"/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf",
line 85: unknown element "blank"

JavaScript error: resource://gre/modules/ExtensionContent.jsm, line
489: TypeError: Argument 1 of PrecompiledScript.executeInGlobal is not
an object.
JavaScript error: resource://gre/modules/ExtensionContent.jsm, line
489: TypeError: Argument 1 of PrecompiledScript.executeInGlobal is not
an object.
date time [notice] Catching signal TERM, exiting cleanly.
JavaScript error: resource://gre/modules/ExtensionPageChild.jsm, line
191: TypeError: this.contentWindow is null
JavaScript error: resource://gre/modules/ExtensionPageChild.jsm, line
191: TypeError: this.contentWindow is null
JavaScript error: chrome://torbutton/content/tor-circuit-display.js,
line 436: TypeError: myController is null

Would be nice if the above issues can be fixed.


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

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

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg 2.2.10-3
ii  libdbus-glib-1-2  0.110-3
ii  python2.7.15-3
ii  python-gtk2   2.24.0-5.1+b1
ii  python-lzma   0.5.3-3.1
ii  python-parsley1.2-1
ii  python-psutil 5.4.6-1+b1
ii  python-twisted18.7.0-3
ii  python-txsocksx   1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor   2.13-8
pn  python-pygame  

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#909537: [devscripts] Files-Excluded-module-hyphen does not work

[Xavier]

mk-origtargz uses Dpkg::Control::HashCore to read debian/copyright.
Manpage says: "The fields names are case insensitive and are always
capitalized" according to RFC822.
That is the problem...

Bug#910828: RFP: node-pretty-quick -- Runs Prettier on your changed files

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-pretty-quick
  Version : ea58162d4f
  Upstream Author : Lucas Azzola ( @lucasazz...@twitter.com )
* URL : https://notabug.org/themusicgod1/pretty-quick
* License : expat
  Programming Lang: javascript
  Description : Runs Prettier on your changed files

Supports Git and Mercurial source control managers.  See #879665 for
details on Prettier.  Prerequisite for meteor-dapp-wallet (#908151).

Bug#910826: javatools: test failure on Ubuntu 18.10

[Jeremy Bicha]

Source: javatools
Version: 0.70

javatools fails to build on Ubuntu 18.10 but it builds in unstable.

If I'm reading the build log correctly, it looks like the test failure
is only because of a line break in the tested manifest. Could you make
the test less sensitive so that it doesn't fail for something as minor
as that?

Build log

https://launchpad.net/ubuntu/+source/javatools/0.70/+build/15530318

Thanks,
Jeremy Bicha

Bug#910827: Doing update on torbrowser-launcher 0.2.9-6 resulted in not finding profile

[shirish शिरीष]

Package: torbrowser-launcher
Version: 0.2.9-6
Severity: normal

Dear Maintainer,
I was using torbrowser-launcher and updated it to torbrowser 8.0.2 .
When the torbrowser restarted it gave me a message stating it could
not find my profile.

While I was able to workaround the issue by using -

~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/start-tor-browser
--verbose

and in a way forcing/seeing that it got correctly updated. After this
I was able to launch using torbrowser-launcher normally as I always do
via

$ $ torbrowser-launcher

I have no clue why I had to use the workaround, please fix so it
doesn't happen again. Many users wouldn't even know what to do.

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

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

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg 2.2.10-3
ii  libdbus-glib-1-2  0.110-3
ii  python2.7.15-3
ii  python-gtk2   2.24.0-5.1+b1
ii  python-lzma   0.5.3-3.1
ii  python-parsley1.2-1
ii  python-psutil 5.4.6-1+b1
ii  python-twisted18.7.0-3
ii  python-txsocksx   1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor   2.13-8
pn  python-pygame  

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#910825: transition: libtidy

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 11/10/2018 20:41, Boyuan Yang wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-CC: tidy-ht...@packages.debian.org
> 
> Hello all,
> 
> I want to start a transition from libtidy5 to libtidy5.6. You may find
> current version of
> tidy-html5 (5.2) and the one in experimental (5.6) [2] at the package
> tracker page. [1]
> 
> I have rebuilt all the reverse dependencies on amd64 and here is the result:
> 
> 2018/10/11 14:12:47 Build results:
> 2018/10/11 14:12:47 PASSED: libextractor
> 2018/10/11 14:12:47 PASSED: libjpfcodegen-java
> 2018/10/11 14:12:47 PASSED: gitmagic
> 2018/10/11 14:12:47 PASSED: psi-plus
> 2018/10/11 14:12:47 PASSED: lprng-doc
> 2018/10/11 14:12:47 PASSED: pumpa
> 2018/10/11 14:12:47 PASSED: php7.2
> 2018/10/11 14:12:47 PASSED: kde-baseapps
> 2018/10/11 14:12:47 PASSED: qmtest
> 2018/10/11 14:12:47 PASSED: elementtidy
> 2018/10/11 14:12:47 PASSED: php7.3
> 2018/10/11 14:12:47 PASSED: konqueror
> 2018/10/11 14:12:47 PASSED: ruby-kramdown
> 2018/10/11 14:12:47 PASSED: prayer
> 2018/10/11 14:12:47 PASSED: xqilla
> 2018/10/11 14:12:47 PASSED: mcl
> 2018/10/11 14:12:47 PASSED: libhtml-tidy-perl
> 2018/10/11 14:12:47 PASSED: ddccontrol
> 2018/10/11 14:12:47 PASSED: abiword
> 2018/10/11 14:12:47 PASSED: intercal
> 2018/10/11 14:12:47 PASSED: mp4h
> 2018/10/11 14:12:47 PASSED: cgit
> 2018/10/11 14:12:47 PASSED: libopkele
> 2018/10/11 14:12:47 PASSED: mathomatic
> 2018/10/11 14:12:47 PASSED: libparse-debianchangelog-perl
> 2018/10/11 14:12:47 PASSED: edbrowse
> 2018/10/11 14:12:47 PASSED: python-tidylib
> 2018/10/11 14:12:47 PASSED: libapache2-mod-auth-openid
> 2018/10/11 14:12:47 FAILED: ball (see buildlogs/ball_1.4.3~beta1-4)
> 2018/10/11 14:12:47 FAILED: doc-linux-fr (see 
> buildlogs/doc-linux-fr_2013.01-3)
> 2018/10/11 14:12:47 FAILED: cmucl (see buildlogs/cmucl_21c-4)
> 
> 3 packages currently FTBFS:
> 
> * ball: Under-maintained, already FTBFS before this transition, not in testing
> * doc-linux-fr: Under-maintained, already FTBFS before this
> transition, not in testing
> * cmucl: The maintainer only allowed the package to be built on i386,
> not for amd64
> 
> As a result, I believe this transition would be reasonable and I am
> requesting a transition slot.
> (I'm not sure if the auto-libtidy tracker would appear later; if not,
> please create a slot manually.)

The tracker is https://release.debian.org/transitions/html/auto-tidy-html5.html

Please go ahead.

Emilio

Bug#910823: docker-compose: remove broken dependency on golang-docker-credential-helpers or fix golang-docker-credential-helpers

[Nye Liu]

The current recommended workaround is here:

https://github.com/docker/docker-credential-helpers/issues/105#issuecomment-420480401

sudo apt-get remove golang-docker-credential-helpers
docker login

sudo apt-get install docker-compose

This is not at all reasonable.

Bug#910824: RFP: node-beefy -- a local development server designed to work with browserify

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-beefy
  Version : 2.1.8
  Upstream Author : Chris Dickinson 
* URL : https://notabug.org/themusicgod1/beefy
* License : Expat/MIT
  Programming Lang: javascript
  Description : a local development server designed to work with browserify

beefy can live reload your browser when your code changes (if you want).  It 
works with whatever 
version of browserify or watchify; globally installed or locally installed to 
node_modules/.
It will spit compile errors out into the browser so you don't have that 1-2 
seconds of 
cognitive dissonance and profound ennui that follows refreshing the page only 
to get a 
blank screen.  It will spit out a default index.html for missing routes so you 
don't need to 
even muck about with HTML to get started serves up static files with grace and 
aplomb 
(and also appropriate mimetypes). It is designed to fall away gracefully, as 
your project 
gets bigger.

node-beefy is a building prerequisite of eslint ( #743404 ).

Bug#910825: transition: libtidy

[Boyuan Yang]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-CC: tidy-ht...@packages.debian.org

Hello all,

I want to start a transition from libtidy5 to libtidy5.6. You may find
current version of
tidy-html5 (5.2) and the one in experimental (5.6) [2] at the package
tracker page. [1]

I have rebuilt all the reverse dependencies on amd64 and here is the result:

2018/10/11 14:12:47 Build results:
2018/10/11 14:12:47 PASSED: libextractor
2018/10/11 14:12:47 PASSED: libjpfcodegen-java
2018/10/11 14:12:47 PASSED: gitmagic
2018/10/11 14:12:47 PASSED: psi-plus
2018/10/11 14:12:47 PASSED: lprng-doc
2018/10/11 14:12:47 PASSED: pumpa
2018/10/11 14:12:47 PASSED: php7.2
2018/10/11 14:12:47 PASSED: kde-baseapps
2018/10/11 14:12:47 PASSED: qmtest
2018/10/11 14:12:47 PASSED: elementtidy
2018/10/11 14:12:47 PASSED: php7.3
2018/10/11 14:12:47 PASSED: konqueror
2018/10/11 14:12:47 PASSED: ruby-kramdown
2018/10/11 14:12:47 PASSED: prayer
2018/10/11 14:12:47 PASSED: xqilla
2018/10/11 14:12:47 PASSED: mcl
2018/10/11 14:12:47 PASSED: libhtml-tidy-perl
2018/10/11 14:12:47 PASSED: ddccontrol
2018/10/11 14:12:47 PASSED: abiword
2018/10/11 14:12:47 PASSED: intercal
2018/10/11 14:12:47 PASSED: mp4h
2018/10/11 14:12:47 PASSED: cgit
2018/10/11 14:12:47 PASSED: libopkele
2018/10/11 14:12:47 PASSED: mathomatic
2018/10/11 14:12:47 PASSED: libparse-debianchangelog-perl
2018/10/11 14:12:47 PASSED: edbrowse
2018/10/11 14:12:47 PASSED: python-tidylib
2018/10/11 14:12:47 PASSED: libapache2-mod-auth-openid
2018/10/11 14:12:47 FAILED: ball (see buildlogs/ball_1.4.3~beta1-4)
2018/10/11 14:12:47 FAILED: doc-linux-fr (see buildlogs/doc-linux-fr_2013.01-3)
2018/10/11 14:12:47 FAILED: cmucl (see buildlogs/cmucl_21c-4)

3 packages currently FTBFS:

* ball: Under-maintained, already FTBFS before this transition, not in testing
* doc-linux-fr: Under-maintained, already FTBFS before this
transition, not in testing
* cmucl: The maintainer only allowed the package to be built on i386,
not for amd64

As a result, I believe this transition would be reasonable and I am
requesting a transition slot.
(I'm not sure if the auto-libtidy tracker would appear later; if not,
please create a slot manually.)

Thanks!
Boyuan Yang

---

Ben file:

title = "libtidy";
is_affected = .depends ~ "libtidy5" | .depends ~ "libtidy5.6";
is_good = .depends ~ "libtidy5.6";
is_bad = .depends ~ "libtidy5";

---


[1] https://tracker.debian.org/pkg/tidy-html5
[2] https://tracker.debian.org/news/994768

Bug#910823: docker-compose: remove broken dependency on golang-docker-credential-helpers or fix golang-docker-credential-helpers

[Nye Liu]

Package: docker-compose
Version: 1.21.0-3
Severity: normal

docker-compose installs golang-docker-credential-helpers, which breaks `docker 
login`

https://github.com/docker/compose/issues/6023

https://github.com/docker/docker-credential-helpers/issues/105

https://github.com/docker/docker-credential-helpers/issues/60

https://stackoverflow.com/questions/51222996/docker-login-fails-on-a-server-with-no-x11-installed

https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1796119

The python3-docker package requires python3-dockerpycreds, which requires 
golang-docker-credential-helpers.

Upstream docker-compose does NOT require golang-docker-credential-helpers.

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

Kernel: Linux 4.15.13-x86_64-linode106 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages docker-compose depends on:
ii  python3  3.6.6-1
ii  python3-cached-property  1.4.0-1
ii  python3-distutils3.6.6-1
ii  python3-docker   3.4.1-2
ii  python3-dockerpty0.4.1-1
ii  python3-docopt   0.6.2-2
ii  python3-jsonschema   2.6.0-4
ii  python3-requests 2.18.4-2
ii  python3-six  1.11.0-2
ii  python3-texttable1.4.0-1
ii  python3-websocket0.53.0-1
ii  python3-yaml 3.12-1+b2

Versions of packages docker-compose recommends:
pn  docker.io  

docker-compose suggests no packages.

-- no debconf information

Bug#910805: stretch-pu: package dnsruby/1.54-2

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Thu, 2018-10-11 at 15:51 +0200, Santiago Ruano Rincón wrote:
> I'd like to propose the attached dnsruby NMU to fix two bugs:
> 
> #908887: include latest DNS trust anchor (KSK-2017)
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908887

The metadata for that bug suggests that it also affects the package in
unstable - is that correct?

> #910754: dnsruby: warning: constant ::TimeoutError is deprecated
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910754

That bug has no version information at all. :-( Does it also affect the
package in unstable?

Regards,

Adam

Bug#909302: metacity: Should present at-spi elements for the decorations

[Dmitry Shachnev]

On Thu, Oct 11, 2018 at 08:28:25PM +0200, Samuel Thibault wrote:
> We will see directly with upstream, yes. We just keep the Debian users
> informed of the bug handling and when it eventually gets fixed in
> Debian.

Ok, thanks, looking forward to it!

--
Dmitry Shachnev

Bug#910822: Subject: golang-docker-credential-helpers: headless gnome-keyring failure

[Nye Liu]

Package: golang-docker-credential-helpers
Version: 0.6.1-1
Severity: important

The docker-compose package automatically installs 
golang-docker-credential-helpers, which causes docker login problems on 
headless machines:


On docker login:

1) without gnome-keyring installed:

Remote error from secret service: 
org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.secrets was not provided by any .service files
Error saving credentials: error storing credentials - err: exit status 
1, out: `The name org.freedesktop.secrets was not provided by any 
.service files`



2) with gnome-keyring installed:

Remote error from secret service: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
?org.freedesktop.Secret.Collection? on object at path 
/org/freedesktop/secrets/collection/login
Error saving credentials: error storing credentials - err: exit status 
1, out: `No such interface “org.freedesktop.Secret.Collection” on object 
at path /org/freedesktop/secrets/collection/login`


See also

https://github.com/docker/compose/issues/6023

https://github.com/docker/docker-credential-helpers/issues/105

https://github.com/docker/docker-credential-helpers/issues/60

https://stackoverflow.com/questions/51222996/docker-login-fails-on-a-server-with-no-x11-installed

https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1796119

Bug#909302: metacity: Should present at-spi elements for the decorations

[Samuel Thibault]

Hello,

Dmitry Shachnev, le jeu. 11 oct. 2018 21:26:32 +0300, a ecrit:
> On Fri, Sep 21, 2018 at 12:00:50PM +0200, Samuel Thibault wrote:
> > While using a screen reader such as Orca in mouse review mode ("Speak
> > object under mouse" option in its general preference panel), it would be
> > useful to have it able to read the window decorations rendered by metacity.
> > Basically, it means metacity exposing to at-spi some Accessible objects
> > corresponding to the different decoration elements (notably the title bar
> > and the buttons), so that Orca can know where they are and their content.
> 
> I see you assigned this bug to b...@hypra.fr, so do I understand it correctly
> that you are going to work on this?

Yes.

> In this case, can you please propose a merge request directly to upstream?

We will see directly with upstream, yes. We just keep the Debian users
informed of the bug handling and when it eventually gets fixed in
Debian.

Samuel

Bug#909302: metacity: Should present at-spi elements for the decorations

[Dmitry Shachnev]

Control: tags -1 + moreinfo

Hi Samuel!

On Fri, Sep 21, 2018 at 12:00:50PM +0200, Samuel Thibault wrote:
> Package: metacity
> Version: 1:3.30.0-2
> Severity: wishlist
> Tags: a11y
> Owner: b...@hypra.fr
> User: b...@hypra.fr
> Usertags: hypra
> Forwarded: https://gitlab.gnome.org/GNOME/metacity/issues/1
>
> As reported to upstream:
>
> While using a screen reader such as Orca in mouse review mode ("Speak
> object under mouse" option in its general preference panel), it would be
> useful to have it able to read the window decorations rendered by metacity.
> Basically, it means metacity exposing to at-spi some Accessible objects
> corresponding to the different decoration elements (notably the title bar
> and the buttons), so that Orca can know where they are and their content.

I see you assigned this bug to b...@hypra.fr, so do I understand it correctly
that you are going to work on this?

In this case, can you please propose a merge request directly to upstream?

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#910240: Bug #910240 in python-django marked as pending

[Chris Lamb]

Dear Raphael

> This fixes it in unstable, but the bug report has been filed against
> stable so it's probably worth a stable update as well?

Filed as #910821.
 
> Also can we add some supplementary build-dependencies so that this gets tested
> as part of the regular test suite?

Done.


Regards,

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

Bug#910821: stretch-pu: package python-django/1:1.10.7-2+deb9u3

[Chris Lamb]

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

Dear stable release managers,

Please consider python-django (1:1.10.7-2+deb9u3) for stretch:
  
  python-django (1:1.10.7-2+deb9u3) stretch; urgency=medium
  
* Default to supporting Spatialite >= 4.2. (Closes: #910240)


The full diff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/changelog b/debian/changelog
index 17c90124e..b1c56f7c5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-django (1:1.10.7-2+deb9u3) stretch; urgency=medium
+
+  * Default to supporting Spatialite >= 4.2. (Closes: #910240)
+
+ -- Chris Lamb   Thu, 11 Oct 2018 18:47:12 +0100
+
 python-django (1:1.10.7-2+deb9u2) stretch-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff --git a/debian/patches/0006-Default-to-supporting-Spatialite-4.2.patch 
b/debian/patches/0006-Default-to-supporting-Spatialite-4.2.patch
new file mode 100644
index 0..6c92929a2
--- /dev/null
+++ b/debian/patches/0006-Default-to-supporting-Spatialite-4.2.patch
@@ -0,0 +1,28 @@
+From: Chris Lamb 
+Date: Thu, 4 Oct 2018 09:58:58 +0100
+Subject: Default to supporting Spatialite 4.2
+
+See, for example:
+
+  https://www.gaia-gis.it/fossil/libspatialite/wiki?name=mod_spatialite
+
+... and:
+
+  
https://docs.djangoproject.com/en/2.1/ref/contrib/gis/install/spatialite/#installing-spatialite
+---
+ django/contrib/gis/db/backends/spatialite/base.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/django/contrib/gis/db/backends/spatialite/base.py 
b/django/contrib/gis/db/backends/spatialite/base.py
+index 1f03868..6d0d631 100644
+--- a/django/contrib/gis/db/backends/spatialite/base.py
 b/django/contrib/gis/db/backends/spatialite/base.py
+@@ -35,7 +35,7 @@ class DatabaseWrapper(SQLiteDatabaseWrapper):
+ # cannot be found by `ctypes.util.find_library`), then it may be set
+ # manually in the settings via the `SPATIALITE_LIBRARY_PATH` setting.
+ self.spatialite_lib = getattr(settings, 'SPATIALITE_LIBRARY_PATH',
+-  find_library('spatialite'))
++  'mod_spatialite')
+ if not self.spatialite_lib:
+ raise ImproperlyConfigured('Unable to locate the SpatiaLite 
library. '
+'Make sure it is in your library path, 
or set '
diff --git a/debian/patches/series b/debian/patches/series
index 0b2048f8f..6ccbb746a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -7,3 +7,4 @@ fix-test-middleware-classes-headers.patch
 0014-CVE-2018-7537.patch
 0015-CVE-2018-14574.patch
 0016-CVE-2017-12794.patch
+0006-Default-to-supporting-Spatialite-4.2.patch

Bug#910820: gnome-font-viewer: Invalid MIME type defined in desktop file

[Michel Le Bihan]

Package: gnome-font-viewer
Version: 3.30.0-1
Severity: normal

When running update-desktop-database, I'm getting this error:

michel@debian:~$ sudo update-desktop-database
Error in file "/usr/share/applications/org.gnome.font-viewer.desktop":
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
Error in file "/usr/share/applications/org.gnome.font-viewer.desktop":
"font/otf" is an invalid MIME type ("font" is an unregistered media type)

I had to fix the issue manually by removing the invalid MIME types. That's why
debsums reported that this file has been changed.



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

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

Versions of packages gnome-font-viewer depends on:
ii  libc6  2.27-6
ii  libcairo-gobject2  1.15.12-1
ii  libcairo2  1.15.12-1
ii  libfontconfig1 2.13.1-1
ii  libfreetype6   2.8.1-2
ii  libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii  libglib2.0-0   2.58.1-2
ii  libgnome-desktop-3-17  3.30.1-1
ii  libgtk-3-0 3.24.1-2
ii  libharfbuzz0b  1.9.0-1
ii  libpango-1.0-0 1.42.4-3
ii  libpangocairo-1.0-01.42.4-3

gnome-font-viewer recommends no packages.

gnome-font-viewer suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/applications/org.gnome.font-viewer.desktop 
(from gnome-font-viewer package)

Bug#910819: dpkg: ../../src/packages.c:245: process_queue: Assertion `dependtry <= 4' failed

[Holger Levsen]

Package: dpkg
Version: 1.18.25
Severity: important

Dear Guillem,

on June 28th 2018 was the last successful test of
https://jenkins.debian.net/job/chroot-installation_stretch_install_education-mathematics_upgrade_to_buster/
which tests the installation of the education-mathmatics meta-package on
a clean stretch install (in a chroot) and then upgrades this chroot to
buster. Since July 7th 2018 this test is failing...

As I read
https://jenkins.debian.net/job/chroot-installation_stretch_install_education-mathematics_upgrade_to_buster/35/consoleFull
the upgrade is done using dpkg 1.8.25, however I'm not fully sure the
bug is coming from dpkg...

The failure is (happening when upgrading packages to buster):

Setting up kalgebra (4:17.08.3-2) ...
dpkg: ../../src/packages.c:245: process_queue: Assertion `dependtry <= 4' 
failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly

Feedback much appreciated as I'm lost here. Also maybe this bug should
have severity 'serious' as it breaks upgrades to Buster?!?


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#910731: kaddressbook: crashes at startup

[Bernhard Übelacker]

Hello Francesco,

> Unfortunately, the 17.12.3-1 version is no more available in the
> archive, apart from the hurd architecture.  So I will wait for a newer
> version (I am not going to compile it myself).

If one needs old package versions you have a look at
snapshot.debian.org [1].

As far as I see you might get away with just installing
the two packages [2] and [3] manually.

[1] http://snapshot.debian.org/package/kontactinterface/
[2] 
http://snapshot.debian.org/archive/debian/20180401T155009Z/pool/main/k/kontactinterface/libkf5kontactinterface-data_17.12.3-1_all.deb
[3] 
http://snapshot.debian.org/archive/debian/20180401T155009Z/pool/main/k/kontactinterface/libkf5kontactinterface5_17.12.3-1_amd64.deb

(I have not tested it, I am not using that part of KDE.)

Kind regards,
Bernhard

Bug#910818: ITP: conttest -- A helper script for continuous testing written in Python

[Sascha Girrulat]

Package: wnpp
Severity: wishlist
Owner: Sascha Girrulat 

* Package name: conttest
  Version : 0.0.2 
  Upstream Author : John Jacobsen 
* URL : https://github.com/eigenhombre/continuous-testing-helper
* License : EPL
  Programming Lang: Python
  Description : A helper script for continuous testing written in Python

Continuous testing helper, adapted from [1], but which makes no
assumption about what tests you might want to run continuously while
developing. For more information, see this blog post[2].

Any command supplied to the script will be run once and then repeated
any time a file in the current working directory changes, except for
files excluded using .conttest-excludes as described below.

Note that ANY command you supply the script will be run, so be careful.
You have been warned!

[1] https://github.com/brunobord/tdaemon/blob/master/tdaemon.py
[2] http://zerolib.com/continuous-testing.html

Bug#910812: [Design-devel] Bug#910812: design-desktop-graphics: depends on gimp and mypaint which are not co-installable (see #894757)

[Mattia Rizzolo]

On Thu, Oct 11, 2018 at 07:08:29PM +0200, Jonas Smedegaard wrote:
> Quoting Holger Levsen (2018-10-11 18:36:03)
> > libmypaint-common and mypaint-data have become not co-installable in 
> > sid with libmypaint 1.3.0-2 on April 3rd 2018. gimp depends on 
> > libmypaint-1.3.0, which depends on libmypaint-common and 
> > design-desktop-graphics depends on gimp and mypaint and thus is 
> > uninstallable.
> 
> Thanks for reporting! I'll address that ASAP. :-)

Please don't act rashly and check out
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906144
and the already closed
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894757

:)
(note that I haven't kept up with the situation, so I don't know if
somebody is going to do something, so it might need some prodding in the
right direction).


-- 
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#910817: RM: php-phpdocumentor-reflection/experimental -- ROM; Useless in Debian

[David Prévot]

Package: ftp.debian.org
Severity: normal

Hi,

As per #904345 (removal from unstable), please also remove
php-phpdocumentor-reflection from experimental.

Thanks in advance

Regards

David

Bug#910815: RM: php-hamcrest/experimental -- ROM; Useless in Debian

[David Prévot]

Package: ftp.debian.org
Severity: normal

Hi,

As per #904354 (removal from unstable), please remove php-hamcrest from
experimental too.

Regards

David

Bug#910816: RM: php-kdyby-events/experimental -- ROP; Useless in Debian

[David Prévot]

Package: ftp.debian.org
Severity: normal

Hi,

As per #904469 (removal from unstable), pleas also remove php-kdyby-events
from experimental.

Thanks in advandce

Regards

David

Bug#910814: reportbug-gtk: Please set reportbug-gtk to Priority: optional

[Chris Boot]

Package: reportbug-gtk
Version: 7.5.0
Severity: normal

Hi,

reportbug-gtk is currently Priority: standard, so new installations will
always receive it as long as the "standard system utilities" option is
selected in the Debian Installer, even if no desktop is selected. That
means that all the GTK dependencies are also pulled in.

Removing the (useless on a system without a desktop) reportbug-gtk
package allows for a much smaller default system installation, so please
consider making it Priority: optional. It may be a good idea to replace
it as a Recommends in task-desktop, perhaps.

Thanks,
Chris

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

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

Versions of packages reportbug-gtk depends on:
pn  gir1.2-gtk-3.0 
pn  gir1.2-vte-2.91
ii  python3-gi 3.30.1-1
pn  python3-gi-cairo   
pn  python3-gtkspellcheck  
ii  reportbug  7.5.0

reportbug-gtk recommends no packages.

reportbug-gtk suggests no packages.

Bug#910812: [Design-devel] Bug#910812: design-desktop-graphics: depends on gimp and mypaint which are not co-installable (see #894757)

[Jonas Smedegaard]

Quoting Holger Levsen (2018-10-11 18:36:03)
> libmypaint-common and mypaint-data have become not co-installable in 
> sid with libmypaint 1.3.0-2 on April 3rd 2018. gimp depends on 
> libmypaint-1.3.0, which depends on libmypaint-common and 
> design-desktop-graphics depends on gimp and mypaint and thus is 
> uninstallable.

Thanks for reporting! I'll address that ASAP. :-)

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#910813: doc-linux-fr: FTBFS, latex error "Package inputenc Error: Invalid UTF-8 byte sequence"

[Boyuan Yang]

Source: doc-linux-fr
Version: 2013.01-3
Severity: serious

Hi David,

After fixing #880786, doc-linux-fr would still FTBFS due to LaTeX error.
Example source repo can be found at
https://salsa.debian.org/debian/doc-linux-fr .

 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cd fcol-faq && make
make[2]: Entering directory '/<>/fcol-faq'
sed -e 's/%ISOent;/%TeXent;/' < faq-fcol.xml > faq-fcol-LaTeX.xml
xsltproc --catalogs --nonet --novalid to_tex.xsl faq-fcol-LaTeX.xml >
faq-fcol.tex
Variable $SGML_CATALOG_FILES not set
latex faq-fcol.tex ;
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live
2019/dev/Debian) (preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./faq-fcol.tex
LaTeX2e <2018-04-01> patch level 5
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size11.clo))
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
(/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def)
(/usr/share/texlive/texmf-dist/tex/generic/babel-french/frenchb.ldf

Package babel-french Warning: Option `frenchb' for Babel is *deprecated*,
(babel-french)it might be removed sooner or later. Please
(babel-french)use `french' instead; reported on input line 35.

(/usr/share/texlive/texmf-dist/tex/generic/babel-french/french.ldf
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
(/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def)
(/usr/share/texlive/texmf-dist/tex/latex/carlisle/scalefnt.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/times.sty)
(/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty))
(/usr/share/texlive/texmf-dist/tex/latex/relsize/relsize.sty)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/latex/moreverb/moreverb.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty))
(/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
No file faq-fcol.aux.
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd)
*geometry* driver: auto-detecting
*geometry* detected driver: dvips

! Package inputenc Error: Invalid UTF-8 byte sequence.

See the inputenc package documentation for explanation.
Type  H   for immediate help.
 ...

l.27   \maketitle

?
! Emergency stop.
 ...

l.27   \maketitle

No pages of output.
Transcript written on faq-fcol.log.
make[2]: *** [Makefile:30: faq-fcol.dvi] Error 1
make[2]: Leaving directory '/<>/fcol-faq'
make[1]: *** [debian/rules:120: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:161: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


==

Besides, I'm wondering if doc-linux-fr is still relavent for future
Debian releases.
Is it okay that we eventually remove it from Debian archive?

--
Thanks,
Boyuan Yang

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Emilio Pozuelo Monfort, le jeu. 11 oct. 2018 18:33:10 +0200, a ecrit:
> Weird. I just did:
> 
> sudo cowbuilder --update
> debcheckout sphinxbase
> cd sphinxbase
> pdebuild
> 
> And it was fine. No idea what we're doing differently.

Ok. I have run it on a chroot on the barriere porter machine, and it was
fine too. I'll see what is different on my system.

Samuel

Bug#910812: design-desktop-graphics: depends on gimp and mypaint which are not co-installable (see #894757)

[Holger Levsen]

Package: design-desktop-graphics
Version: 3.0.8
Severity: serious

Dear Maintainer,

libmypaint-common and mypaint-data have become not co-installable in sid with
libmypaint 1.3.0-2 on April 3rd 2018. gimp depends on libmypaint-1.3.0,
which depends on libmypaint-common and design-desktop-graphics depends
on gimp and mypaint and thus is uninstallable.


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Emilio Pozuelo Monfort]

On 11/10/2018 14:03, Samuel Thibault wrote:
> Emilio Pozuelo Monfort, le jeu. 11 oct. 2018 10:08:45 +0200, a ecrit:
>> On 11/10/2018 03:21, Samuel Thibault wrote:
>>> Samuel Thibault, le mer. 10 oct. 2018 18:33:18 +0200, a ecrit:
 Emilio Pozuelo Monfort, le mer. 10 oct. 2018 18:27:18 +0200, a ecrit:
> debian/tmp/usr/lib/python3* usr/lib
>
> That is causing both the python3.6/ and python3.7/ contents to be moved to
> usr/lib,

 D'oh!

 Thanks for the fix, I have pushed it to our tree.
>>>
>>> Mmm, we still have an issue:
>>>
>>> W: python3-sphinxbase: python-module-in-wrong-location 
>>> usr/lib/python3.6/site-packages/sphinxbase/ 
>>> usr/lib/python3/dist-packages/sphinxbase/
>>> W: python3-sphinxbase: python-module-in-wrong-location 
>>> usr/lib/python3.6/site-packages/sphinxbase/_sphinxbase.so 
>>> usr/lib/python3/dist-packages/sphinxbase/_sphinxbase.so
>>>
>>> These are indeed completely bogus.
>>
>> That's weird. I don't get those lintian warnings (lintian 2.5.108) and I 
>> don't
>> have any files in /usr/lib/python3.6 either. Those are the old warnings that 
>> you
>> get without my debdiff, which my changes should fix. Are you somehow running
>> lintian on the old changes, or did you forget to apply my diff?
> 
> I checked it again, it's all correct. I can use this to reproduce it:
> 
> $ pbuilder create  # clean sid chroot
> $ wget 
> http://ftp.debian.org/debian/pool/main/s/sphinxbase/sphinxbase_0.8+5prealpha+1.orig.tar.gz
> $ debcheckout sphinxbase   # to get latest git
> $ cd sphinxbase
> $ pdebuild --debbuildopts --check-command=lintian -- --extrapackages lintian

Weird. I just did:

sudo cowbuilder --update
debcheckout sphinxbase
cd sphinxbase
pdebuild

And it was fine. No idea what we're doing differently.

Emilio

Bug#910811: xenstore-utils: upgrade error: xenstore-utils_4.11.1 unpack error with '/usr/share/man/man1/xenstore-chmod.1.gz'

[Diederik de Haas]

Package: xenstore-utils
Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-2
Severity: normal

while doing 'aptitude safe-upgrade' with today's updates, I got the
following error:

Unpacking xenstore-utils (4.11.1~pre.20180911.5acdd26fdc+dfsg-2) over 
(4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-NA96TI/4-xenstore-utils_4.11.1~pre.20180911.5acdd26fdc+dfsg-2_amd64.deb
 (--unpack):
 trying to overwrite '/usr/share/man/man1/xenstore-chmod.1.gz', which is also 
in package xen-utils-common 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9
Preparing to unpack 
.../5-xen-utils-common_4.11.1~pre.20180911.5acdd26fdc+dfsg-2_amd64.deb ...
Unpacking xen-utils-common (4.11.1~pre.20180911.5acdd26fdc+dfsg-2) over 
(4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) ...
Errors were encountered while processing:
 
/tmp/apt-dpkg-install-NA96TI/4-xenstore-utils_4.11.1~pre.20180911.5acdd26fdc+dfsg-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Doing another 'aptitude safe-upgrade' directly thereafter succeeded,
hence (only) severity normal.

My guess would be a missing breaks/replaces issue.

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/16 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)
LSM: AppArmor: enabled

Versions of packages xenstore-utils depends on:
ii  libc62.27-6
ii  libxenstore3.0   4.11.1~pre.20180911.5acdd26fdc+dfsg-2
ii  libxentoolcore1  4.11.1~pre.20180911.5acdd26fdc+dfsg-2

xenstore-utils recommends no packages.

Versions of packages xenstore-utils suggests:
pn  xen-doc  

-- no debconf information

Bug#910808: sagemath: Sage crashes on startup, seems to be compiled against wrong libsingular version

[Rann Bar-On]

That does the trick. Should it be a dependency, then?

-- 
Rann Bar-On
105L/218 Instructor
Dept of Mathematics
Duke University

Pronouns: he/him/his

On Thu, 2018-10-11 at 17:38 +0200, Tobias Hansen wrote:
> Hi,
> 
> please update libpynac18 to 0.7.22-3.
> 
> Best,
> Tobias
> 
> On 10/11/2018 05:19 PM, Rann Bar-On wrote:
> > Package: sagemath
> > Version: 8.3-3
> > Severity: grave
> > Justification: renders package unusable
> > 
> > Dear Maintainer,
> > 
> > The relevant output from the crash report:
> > 
> > ImportError: libsingular-factory-4.1.0.so: cannot open shared
> > object file: No such file or directory
> > 
> > I believe, given the dependencies of sagemath 8.3, that it should
> > be compiled against libsingular 4.1.1, not 4.1.0
> > 
> > Thanks!
> >
> >
> > -- System Information:
> > Debian Release: buster/sid
> >   APT prefers testing
> >   APT policy: (800, 'testing'), (750, 'unstable'), (500, 'unstable-
> > debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500,
> > 'proposed-updates'), (500, 'oldstable-updates'), (500, 'stable'),
> > (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 4.18.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)
> > LSM: AppArmor: enabled
> > 
> > Versions of packages sagemath depends on:
> > ii  cysignals-tools  1.6.7+ds-4
> > ii  cython   0.28.4-1
> > ii  ecl  16.1.2-4+b1
> > ii  eclib-tools  20171002-1+b3
> > ii  f2c  20160102-1
> > ii  fflas-ffpack 2.3.2-3
> > ii  flintqs  1:1.0-3
> > ii  gap-core 4r8p8-3
> > ii  gfan 0.6.2-2
> > ii  gmp-ecm  7.0.4+ds-3
> > ii  ipython  5.5.0-1
> > ii  iso-codes4.1-1
> > ii  jmol 14.6.4+2016.11.05+
> > dfsg1-3.1
> > ii  lcalc1.23+dfsg-7
> > ii  less 487-0.1+b1
> > ii  libatlas3-base [liblapack.so.3]  3.10.3-7+b1
> > ii  libblas3 [libblas.so.3]  3.8.0-1+b1
> > ii  libbrial-groebner3   1.2.0-2
> > ii  libbrial31.2.0-2
> > ii  libc62.27-6
> > ii  libcdd-tools 094h-1+b1
> > ii  libcliquer1  1.21-2
> > ii  libec3   20171002-1+b3
> > ii  libecm1  7.0.4+ds-3
> > ii  libflint-2.5.2   2.5.2-18
> > ii  libflint-arb21:2.14.0-4
> > ii  libgap-sage-
> > 44.8.8+3+20160327g69a66f0+dsx-1
> > ii  libgcc1  1:8.2.0-7
> > ii  libgd3   2.2.5-4
> > ii  libgivaro9   4.0.4-2
> > ii  libglpk404.65-2
> > ii  libgmp10 2:6.1.2+dfsg-3
> > ii  libgmpxx4ldbl2:6.1.2+dfsg-3
> > ii  libgsl23 2.5+dfsg-5
> > ii  libgslcblas0 2.5+dfsg-5
> > ii  libiml0  1.0.4-1+b2
> > ii  libjs-mathjax2.7.4+dfsg-1
> > ii  libjs-three  80+dfsg2-2
> > ii  liblapack3 [liblapack.so.3]  3.8.0-1+b1
> > ii  liblfunction01.23+dfsg-7
> > ii  liblinbox-1.5.2-01.5.2-2
> > ii  liblinboxsage-1.5.2-01.5.2-2
> > ii  liblrcalc1   1.2-2+b1
> > ii  libm4ri-0.0.20140914 20140914-2+b1
> > ii  libm4rie-0.0.2015090820150908-2
> > ii  libmpc3  1.1.0-1
> > ii  libmpfi0 1.5.3+ds-2
> > ii  libmpfr6 4.0.1-1
> > ii  libntl35 10.5.0-2
> > ii  libpari-gmp-tls6 2.11.0-1
> > ii  libplanarity03.0.0.5-3
> > ii  libpng16-16  1.6.34-2
> > ii  libppl14 1:1.2-3
> > ii  libpynac18  

Bug#910810: /bin/su: su to root does not set $PATH according to id -u being 0 in /etc/profile

[Arthur Marsh]

Package: util-linux
Version: 2.32.1-0.1
Severity: important
File: /bin/su

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

upgrading util-linux, when did su to root, /usr/sbin wasn't in PATH like
happened with earlier util-linux.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

tried running 

. /etc/profile

after su to root

   * What was the outcome of this action?

. /etc/profile set the correct PATH

   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.19.0-rc7+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages util-linux depends on:
ii  fdisk  2.32.1-0.1
ii  libaudit1  1:2.8.4-2
ii  libblkid1  2.32.1-0.1
ii  libc6  2.27-6
ii  libmount1  2.32.1-0.1
ii  libpam0g   1.1.8-3.8
ii  libselinux12.8-1+b1
ii  libsmartcols1  2.32.1-0.1
ii  libsystemd0239-10
ii  libtinfo6  6.1+20180714-1
pn  libudev1   
ii  libuuid1   2.32.1-0.1
ii  login  1:4.5-1.1
ii  zlib1g 1:1.2.11.dfsg-1

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  4.1-2
ii  kbd 2.0.4-4
ii  util-linux-locales  2.32.1-0.1

-- debconf information:
  util-linux/noauto-with-nonzero-passnum:

Bug#910809: ferm: IP tables output with --remote --slow is not reproducible

[Eric Cooper]

Package: ferm
Version: 2.4-1
Severity: normal


The output from "ferm --remote --slow" differs from run to run on the
same input file. As far as I can see, it's generating the "iptables
-P" commands in some non-deterministic order.

For example, this input file

table filter {
chain INPUT {
policy DROP;
mod state state (ESTABLISHED RELATED) ACCEPT;
}
chain FORWARD policy DROP;
chain OUTPUT policy ACCEPT;
}

generates different orderings each time it is run.

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

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

Versions of packages ferm depends on:
ii  debconf  1.5.69
ii  init-system-helpers  1.54
ii  iptables 1.6.2-1.1
ii  lsb-base 9.20170808
ii  perl 5.26.2-7

Versions of packages ferm recommends:
ii  libnet-dns-perl  1.17-1

ferm suggests no packages.

-- Configuration Files:
/etc/ferm/ferm.conf [Errno 13] Permission denied: '/etc/ferm/ferm.conf'

-- debconf information excluded

Bug#910808: sagemath: Sage crashes on startup, seems to be compiled against wrong libsingular version

[Tobias Hansen]

It's not a bug in sagemath. The problem is that the singular library package 
was not renamed even though the library name changed.
However this is only a problem for people who somehow do partial updates.

Best,
Tobias

On 10/11/2018 05:44 PM, Rann Bar-On wrote:
> That does the trick. Should it be a dependency, then?
>

Bug#710117: new version, desktop file

[Gürkan Myczko]

Hello Josue and Markus

I've prepared a new upstream version of greed, and added the desktop 
file.

Feel free to use:

http://phd-sid.ethz.ch/debian/greed/greed_4.2-1.dsc

Best,

Bug#910808: sagemath: Sage crashes on startup, seems to be compiled against wrong libsingular version

[Tobias Hansen]

Hi,

please update libpynac18 to 0.7.22-3.

Best,
Tobias

On 10/11/2018 05:19 PM, Rann Bar-On wrote:
> Package: sagemath
> Version: 8.3-3
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> The relevant output from the crash report:
>
> ImportError: libsingular-factory-4.1.0.so: cannot open shared object file: No 
> such file or directory
>
> I believe, given the dependencies of sagemath 8.3, that it should be compiled 
> against libsingular 4.1.1, not 4.1.0
>
> Thanks!
>   
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (800, 'testing'), (750, 'unstable'), (500, 'unstable-debug'), 
> (500, 'testing-debug'), (500, 'stable-updates'), (500, 'proposed-updates'), 
> (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (1, 
> 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.18.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)
> LSM: AppArmor: enabled
>
> Versions of packages sagemath depends on:
> ii  cysignals-tools  1.6.7+ds-4
> ii  cython   0.28.4-1
> ii  ecl  16.1.2-4+b1
> ii  eclib-tools  20171002-1+b3
> ii  f2c  20160102-1
> ii  fflas-ffpack 2.3.2-3
> ii  flintqs  1:1.0-3
> ii  gap-core 4r8p8-3
> ii  gfan 0.6.2-2
> ii  gmp-ecm  7.0.4+ds-3
> ii  ipython  5.5.0-1
> ii  iso-codes4.1-1
> ii  jmol 14.6.4+2016.11.05+dfsg1-3.1
> ii  lcalc1.23+dfsg-7
> ii  less 487-0.1+b1
> ii  libatlas3-base [liblapack.so.3]  3.10.3-7+b1
> ii  libblas3 [libblas.so.3]  3.8.0-1+b1
> ii  libbrial-groebner3   1.2.0-2
> ii  libbrial31.2.0-2
> ii  libc62.27-6
> ii  libcdd-tools 094h-1+b1
> ii  libcliquer1  1.21-2
> ii  libec3   20171002-1+b3
> ii  libecm1  7.0.4+ds-3
> ii  libflint-2.5.2   2.5.2-18
> ii  libflint-arb21:2.14.0-4
> ii  libgap-sage-4
> 4.8.8+3+20160327g69a66f0+dsx-1
> ii  libgcc1  1:8.2.0-7
> ii  libgd3   2.2.5-4
> ii  libgivaro9   4.0.4-2
> ii  libglpk404.65-2
> ii  libgmp10 2:6.1.2+dfsg-3
> ii  libgmpxx4ldbl2:6.1.2+dfsg-3
> ii  libgsl23 2.5+dfsg-5
> ii  libgslcblas0 2.5+dfsg-5
> ii  libiml0  1.0.4-1+b2
> ii  libjs-mathjax2.7.4+dfsg-1
> ii  libjs-three  80+dfsg2-2
> ii  liblapack3 [liblapack.so.3]  3.8.0-1+b1
> ii  liblfunction01.23+dfsg-7
> ii  liblinbox-1.5.2-01.5.2-2
> ii  liblinboxsage-1.5.2-01.5.2-2
> ii  liblrcalc1   1.2-2+b1
> ii  libm4ri-0.0.20140914 20140914-2+b1
> ii  libm4rie-0.0.2015090820150908-2
> ii  libmpc3  1.1.0-1
> ii  libmpfi0 1.5.3+ds-2
> ii  libmpfr6 4.0.1-1
> ii  libntl35 10.5.0-2
> ii  libpari-gmp-tls6 2.11.0-1
> ii  libplanarity03.0.0.5-3
> ii  libpng16-16  1.6.34-2
> ii  libppl14 1:1.2-3
> ii  libpynac18   0.7.22-2
> ii  libratpoints-2.1.3   1:2.1.3-1+b2
> ii  libreadline7 7.0-5
> ii  librw0   0.8+ds-1
> ii  libsingular4 1:4.1.1-p2+ds-2
> ii  libstdc++6   8.2.0-7
> ii  libsymmetrica2   2.0+ds-5
> ii  

Bug#910807: webext-ublock-origin: Does not work with firefox

[Markus Koschany]

Control: tags -1 confirmed pending

Am 11.10.18 um 16:24 schrieb Eugen Dedu:
> Package: webext-ublock-origin
> Version: 1.17.0+dfsg-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After upgrading to 1.17.0+dfsg-1 version, the package does not work with
> firefox anymore: it is not shown in Tools->Add-ons, and there is no icon
> at the right of the URL bar.
> 
> Regards,
> Eugen Dedu

Thanks for reporting. I placed a boolean value in quotation marks after
I tested the patch to fix #909493 and apparently Firefox doesn't like
incorrect json and refused to load the addon's manifest.json file. Fix
is pending.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature