Bug#889834: Possibility to include desktop translation for next upload?

[Helge Kreutzmann]

Hello maintainers,
would it be possible to include this targetted fix for your next
upload, preferrably before the freeze? Th patch is rather targetted
and should not cause any harm.

Greetings

  Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#915985: gnome-control-center: gnome lock screen feature missing in buster after update

[geo_work]

Package: gnome-control-center
Version: 1:3.30.2-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?after latest update
   * What exactly did you do (or not do) that was effective (or
 ineffective)? searched for lock screen settings in gnome
   * What was the outcome of this action? it was disabled and the button in
upper right near the close button is missing
   * What outcome did you expect instead?

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



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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.45-1
ii  apg2.2.3.dfsg.1-5
ii  colord 1.4.3-3+b1
ii  desktop-file-utils 0.23-4
ii  gnome-control-center-data  1:3.30.2-1
ii  gnome-desktop3-data3.30.2-1
ii  gnome-settings-daemon  3.30.1.2-1
ii  gsettings-desktop-schemas  3.28.1-1
ii  libaccountsservice00.6.45-1
ii  libatk1.0-02.30.0-1
ii  libc6  2.27-8
ii  libcairo-gobject2  1.16.0-1
ii  libcairo2  1.16.0-1
ii  libcanberra-gtk3-0 0.30-6
ii  libcanberra0   0.30-6
ii  libcheese-gtk253.30.0-1
ii  libcheese8 3.30.0-1
ii  libclutter-1.0-0   1.26.2+dfsg-7
ii  libclutter-gtk-1.0-0   1.8.4-3
ii  libcolord-gtk1 0.1.26-2
ii  libcolord2 1.4.3-3+b1
ii  libcups2   2.2.9-2
ii  libfontconfig1 2.13.1-2
ii  libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii  libglib2.0-0   2.58.1-2
ii  libgnome-bluetooth13   3.28.2-2
ii  libgnome-desktop-3-17  3.30.2-1
ii  libgoa-1.0-0b  3.30.0-1
ii  libgoa-backend-1.0-1   3.30.0-1
ii  libgrilo-0.3-0 0.3.7-1
ii  libgtk-3-0 3.24.1-2
ii  libgtop-2.0-11 2.38.0-2
ii  libgudev-1.0-0 232-2
ii  libibus-1.0-5  1.5.19-1
ii  libkrb5-3  1.16.1-1
ii  libmm-glib01.8.2-1
ii  libnm0 1.14.4-4
ii  libnma01.8.18-2
ii  libpango-1.0-0 1.42.4-4
ii  libpangocairo-1.0-01.42.4-4
ii  libpolkit-gobject-1-0  0.105-22
ii  libpulse-mainloop-glib012.2-2
ii  libpulse0  12.2-2
ii  libpwquality1  1.4.0-2
ii  libsecret-1-0  0.18.6-3
ii  libsmbclient   2:4.9.2+dfsg-2
ii  libsoup2.4-1   2.64.1-3
ii  libupower-glib30.99.9-2
ii  libwacom2  0.31-1
ii  libwayland-server0 1.16.0-1
ii  libx11-6   2:1.6.7-1
ii  libxi6 2:1.7.9-1
ii  libxml22.9.4+dfsg1-7+b2

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-5.2+b1
ii  cups-pk-helper0.2.6-1+b1
ii  gkbd-capplet  3.26.0-4
ii  gnome-online-accounts 3.30.0-1
ii  gnome-user-docs   3.30.2-1
ii  gnome-user-share  3.28.0-1
ii  iso-codes 4.1-1
ii  libcanberra-pulse 0.30-6
ii  libnss-myhostname 239-13
ii  mousetweaks   3.12.0-4
ii  network-manager-gnome 1.8.18-2
ii  policykit-1   0.105-22
ii  pulseaudio-module-bluetooth   12.2-2
ii  realmd0.16.3-2
ii  rygel 0.36.2-2
ii  rygel-tracker 0.36.2-2
ii  system-config-printer-common  1.5.11-3

Versions of packages gnome-control-center suggests:
ii  gnome-software   3.30.5-1
ii  gstreamer1.0-pulseaudio  1.14.4-1
pn  libcanberra-gtk-module   
ii  libcanberra-gtk3-module  0.30-6
ii  x11-xserver-utils7.7+8

-- no debconf information

Bug#915978: devscripts: salsa error Unknown command fork

[Xavier]

Le 09/12/2018 à 04:18, Dmitry Bogatov a écrit :
> Package: devscripts
> Version: 2.18.11
> Severity: normal
> 
> Dear Maintainer,
> 
> I installed devscripts/experimental to get `salsa' script and did
> following:
> 
>  $ salsa fork lintian/lintian --verbose
> 
> and got this:
> 
>  salsa error Unknown command fork
>  salsa info: Can't locate Devscripts/Salsa/chechout.pm in @INC (you may need 
> to install the Devscripts::Salsa::chechout module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
> /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
> /usr/share/perl5/Module/Runtime.pm line 314.
>   at /usr/share/perl5/Devscripts/Salsa/fork.pm line 9.
>  Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 314.

Hello,

sorry for this stupid bug introduced during a function rename. Here is
the fix if you want to continue to test:

--- a/usr/share/perl5/Devscripts/Salsa/fork.pm
+++ b/usr/share/perl5/Devscripts/Salsa/fork.pm
@@ -6,7 +6,7 @@ use Devscripts::Output;
 use Dpkg::IPC;
 use Moo::Role;

-with 'Devscripts::Salsa::chechout';
+with 'Devscripts::Salsa::checkout';

 sub fork {
 my ($self, $project) = @_;
@@ -14,7 +14,7 @@ sub fork {
 $self->api->fork_project($project, { namespace => $path });
 my $p = $project;
 $p =~ s#.*/##;
-$self->chechout($p);
+$self->checkout($p);
 chdir $p;
 spawn(
 exec => [
> 
> According to salsa(1) it is valid:
> 
>  fork
> Forks a project in group/user repository and set "upstream" to
> original project. Example:
> 
>   $ salsa fork js-team/node-mongodb --verbose
>   ...
>   salsa.pl info: node-mongodb ready in node-mongodb/
>   $ cd node-mongodb
>   $ git remote --verbose show
>   origin  g...@salsa.debian.org:me/node-mongodb (fetch)
>   origin  g...@salsa.debian.org:me/node-mongodb (push)
>   upstreamg...@salsa.debian.org:js-team/node-mongodb (fetch)
>   upstreamg...@salsa.debian.org:js-team/node-mongodb (push)
> 
> For a group:
> 
>   salsa fork --group js-team user/node-foo
> 
> Oh, and by the way, it is quite unfortunate, that reportbug by default
> insert content of ~/.devscripts into bugreport. It could contain quite
> sensible SALSA_TOKEN. Not sure, whether it is bug in devscripts or
> reportbug.

Sure it's a bug. Report it against devscripts, then if needed we will
reassign it.

Thanks to take time to test salsa !

Cheers,
Xavier

Bug#819909: 819909: leafpad: Cannot display the content of a logfile

[Juhani Numminen]

Followup-For: Bug #819909
Control: found -1 0.8.18.1-5
Control: retitle -1 leafpad: Cannot display UTF-16

On Sun, 3 Apr 2016 21:14:49 +0200 atalantt...@gmail.com wrote:
> Package: leafpad
> Version: 0.8.18.1
> Severity: important
> 
> Hi,
> 
> Leafpad is unable to show the content of the attached logfile created by the 
> Windows(R) software Intel(R) Chipset Device Software 10.1.1.14. It just shows 
> 'ÿþ=' as content.

I observe the same behavior in current leafpad as well.

I'm able to open the file with the Kate editor and when I do so, in the bottom
right of the window it displays "UTF-16LE".

This is what encguess says:

$ encguess *.log
Chipset_20160403204652_0_SetupChipsetx64.msi.logUTF-16

I can also produce a smaller text file that leafpad fails to correctly open:

$ echo Test. | iconv -t UTF16 -o test-utf16.txt


Regards,
Juhani

-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages leafpad depends on:
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1

leafpad recommends no packages.

Versions of packages leafpad suggests:
pn  evince-gtk  

-- no debconf information

Bug#915986: lvm2: Incomplete debian/copyright?

[Chris Lamb]

Source: lvm2
Version: 2.03.01-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Bastian Blank , ftpmas...@debian.org

Hi,

I just ACCEPTed lvm2 from NEW but noticed it was missing attribution 
in debian/copyright for at least Rackable Systems, Rackable Systems,
IBM, etc.

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


Regards,

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

Bug#915830: busybox: cp: failed to access '/var/tmp/mkinitramfs_h8da2B//usr/bin/busybox': Too many levels of symbolic links

[Chris Lamb]

Hi Ben,

> > Any ideas? Sounds very usrmerge related...  Setting severity to
> > "important" as I'm a little worried to reboot. :)

After the aforementioned purge-and-reinstall I rebooted and everything
appears to be fine. :)

> The file copying function it uses knows how to copy symlinks along with
> their targets, but can't cope with a situation like this where the host
> filesystem has a file symlink that parallels the directory symlink in
> the skeleton initramfs.

Whilst you could indeed change this, given that my attempt at usrmerge
failed for reasons unrelated to busybox and/or initramfs generation
(#914716 in molly-guard) the problem — if there was one to begin
with! — is not here and is likely to just mask the underlying problem
anyway.

Thus, we should probably just close this bug.


Regards,

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

Bug#915053: gitlab: Err 500 when go to the project page(any project)

[Dragos Jarca]

Hi

Updated to 11.4.9, but the problem exists.

Seems tat gitlab API not work in all forms described in documentation.

root@omv:/etc/gitlab# curl --header 'PRIVATE-TOKEN: ***' 
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master

alter table ws add column if not exists isactive TINYINT not null default 0;
alter table ws add column if not exists apikey varchar(128);
root@omv:/etc/gitlab# curl 
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master?private_token=***

{"message":"404 Project Not Found"}
root@omv:/etc/gitlab# curl --header '_gitlab_session=*' 
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master

{"message":"404 Project Not Found"}

In web interface _gitlab_session is responsable, and seems not no work.
Strange is that:

https://gitlab.dynamicpuzzle.ro/meteo/meteo/blob/master/db/upd.sql
not work and return ERR 500

and

https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd.sql/raw?ref=master

work and return content of file.

I can work in external git clients, but cannot see thhe project files 
and commits in the web interface.


Dragos Jarca

On 06.12.2018 10:00, Pirate Praveen wrote:

On 12/4/18 10:03 PM, Dragos Jarca wrote:

Yes, tried on different browsers, different os, different browsers on
moile phones, smart tb browser, etc.

I have just uploaded gitlab 11.4.9 to experimental. See if that fixes
the issues.

Bug#915737: open-ath9k-htc-firmware still uses GCC 7

[Oleksij Rempel]

If I see it correctly, there is no way to have (default) gcc-source.
I'll update it to gcc-8-source.

-- 
Regards,
Oleksij



signature.asc
Description: OpenPGP digital signature

Bug#915987: partimage FTBFS with glibc 2.28

[Adrian Bunk]

Source: partimage
Version: 0.6.9-6
Severity: serious
Tags: ftbfs

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

...
misc.cpp: In function 'int checkInodeForDevice(char*, char*)':
misc.cpp:1683:103: error: expected ';' before ')' token
   nRes = mknod(szDevice, S_IFBLK | S_IREAD | S_IWRITE | S_IRGRP | S_IROTH, 
makedev(nMajor, nMinor));

   ^
make[5]: *** [Makefile:537: misc.o] Error 1

Bug#915988: chromium: Maintainer address needs updating

[Adrian Bunk]

Source: chromium
Version: 71.0.3578.80-1
Severity: serious


Source: chromium
Maintainer: Debian Chromium Team 

At some point in the future chromium-browser@ will stop working.

Bug#915989: arbtt: cannot fulfill the build dependencies

[Adrian Bunk]

Source: arbtt
Version: 0.10.0.2-1
Severity: serious

The following packages have unmet dependencies:
 builddeps:arbtt : Depends: libghc-aeson-dev (< 1.3) but 1.3.1.1-3+b1 is to be 
installed
   Depends: libghc-exceptions-dev (< 0.9) but 0.10.0-2+b2 is to 
be installed

Bug#915990: * (caja:5113): WARNING **: 15:31:13.561: Could not inhibit power management: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist

[shirish शिरीष]

Package: caja
Version: 1.20.2-5
Severity: normal

Dear Maintainer,
Could you fix the above.


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

Kernel: Linux 4.18.0-3-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 caja depends on:
ii  caja-common   1.20.2-5
ii  desktop-file-utils0.23-4
ii  gvfs  1.38.1-1
ii  libatk1.0-0   2.30.0-1
ii  libc6 2.28-2
ii  libcairo-gobject2 1.16.0-1
ii  libcairo2 1.16.0-1
ii  libcaja-extension11.20.2-5
ii  libexempi32.4.5-2
ii  libexif12 0.6.21-5
ii  libgail-3-0   3.24.1-2
ii  libgdk-pixbuf2.0-02.38.0+dfsg-6
ii  libglib2.0-0  2.58.1-2
ii  libglib2.0-bin2.58.1-2
ii  libglib2.0-data   2.58.1-2
ii  libgtk-3-03.24.1-2
ii  libice6   2:1.0.9-2
ii  libmate-desktop-2-17  1.20.3-2
ii  libnotify40.7.7-3
ii  libpango-1.0-01.42.4-4
ii  libpangocairo-1.0-0   1.42.4-4
ii  libselinux1   2.8-1+b1
ii  libsm62:1.2.2-1+b3
ii  libstartup-notification0  0.12-5
ii  libx11-6  2:1.6.7-1
ii  libxml2   2.9.4+dfsg1-7+b2
ii  mate-desktop  1.20.3-2
ii  shared-mime-info  1.10-1

Versions of packages caja recommends:
ii  gvfs-backends  1.38.1-1

Versions of packages caja suggests:
ii  engrampa1.20.1-1
ii  gstreamer1.0-tools  1.14.4-1
ii  meld3.18.3-1

-- 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#915991: vzctl FTBFS with glibc 2.28

[Adrian Bunk]

Source: vzctl
Version: 4.9.4-5
Severity: serious
Tags: ftbfs

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

...
config.c: In function 'store_dev':
config.c:1250:10: error: called object 'major' is not a function or function 
pointer
  major = major(res->dev); \
  ^

Bug#915992: ckermit FTBFS with glibc 2.28

[Adrian Bunk]

Source: ckermit
Version: 302-5.3
Severity: serious
Tags: ftbfs buster sid

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

...
In file included from ckucmd.c:41:
ckucmd.c: In function 'cmdconchk':
ckucmd.c:7385:48: error: 'FILE' {aka 'struct _IO_FILE'} has no member named 
'_cnt'
 debug(F101,"cmdconchk stdin->_cnt","",stdin->_cnt);
^~

Bug#915994: spooles FTBFS with multiarchified openmpi >= 3.1.3-3

[Adrian Bunk]

Source: spooles
Version: 2.2-13
Severity: serious
Tags: ftbfs

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

...
In file included from aggListMPI.c:3:
../spoolesMPI.h:6:10: fatal error: mpi.h: No such file or directory
 #include 
  ^~~
compilation terminated.
make[5]: *** [makeG:38: aggListMPI.o] Error 1

Bug#915993: shim-signed: [INTL:it] Italian translation of debconf messages

[Beatrice Torracca]

Package: shim-signed
Severity: wishlist
Tags: patch l10n

Hi.

Please find attached the Italian translation of shim-signed debconf messages
proofread by the Italian localization team.

Please include it in your next upload.

Thanks,
Beatrice
# Italian translation of shim-signed debconf messages
# Copyright (C) 2018, shim-signed package copyright holder
# This file is distributed under the same license as the shim-signed package.
# Beatrice Torracca , 2018.
msgid ""
msgstr ""
"Project-Id-Version: shim-signed\n"
"Report-Msgid-Bugs-To: shim-sig...@packages.debian.org\n"
"POT-Creation-Date: 2018-11-04 08:13+0100\n"
"PO-Revision-Date: 2018-11-09 08:48+0200\n"
"Last-Translator: Beatrice Torracca \n"
"Language-Team: Italian \n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Virtaal 0.7.1\n"

#. Type: text
#. Description
#: ../templates:1001
msgid "Configuring UEFI Secure Boot"
msgstr "Configurazione di Secure Boot (avvio protetto) UEFI"

#. Type: error
#. Description
#: ../templates:2001
msgid "Invalid password"
msgstr "Password non valida"

#. Type: error
#. Description
#: ../templates:2001
msgid ""
"The Secure Boot key you've entered is not valid. The password used must be "
"between 8 and 16 characters."
msgstr ""
"La chiave per il Secure Boot inserita non è valida. La password utilizzata "
"deve contenere da 8 a 16 caratteri."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Disable UEFI Secure Boot?"
msgstr "Disabilitare il Secure Boot UEFI?"

#. Type: boolean
#. Description
#. Type: note
#. Description
#: ../templates:3001 ../templates:5001
msgid ""
"If Secure Boot remains enabled on your system, your system may still boot "
"but any hardware that requires third-party drivers to work correctly may not "
"be usable."
msgstr ""
"Se Secure Boot rimane abilitato sul sistema, questo potrà comunque avviarsi, "
"ma qualsiasi hardware che richiede driver di terze parti per funzionare "
"correttamente potrebbe non essere utilizzabile."

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Enable UEFI Secure Boot?"
msgstr "Abilitare il Secure Boot UEFI?"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"If Secure Boot is enabled on your system, your system may still boot but any "
"hardware that requires third-party drivers to work correctly may not be "
"usable."
msgstr ""
"Se Secure Boot viene abilitato sul sistema, questo potrà comunque avviarsi, "
"ma qualsiasi hardware che richiede driver di terze parti per funzionare "
"correttamente potrebbe non essere utilizzabile."

#. Type: note
#. Description
#: ../templates:5001
msgid "Your system has UEFI Secure Boot enabled"
msgstr "Questo sistema ha il Secure Boot UEFI abilitato"

#. Type: note
#. Description
#: ../templates:5001
msgid "UEFI Secure Boot is not compatible with the use of third-party drivers."
msgstr ""
"Il Secure Boot UEFI non è compatibile con l'uso di driver di terze parti."

#. Type: note
#. Description
#: ../templates:5001
msgid ""
"The system will assist you in toggling UEFI Secure Boot. To ensure that this "
"change is being made by you as an authorized user, and not by an attacker, "
"you must choose a password now and then use the same password after reboot "
"to confirm the change."
msgstr ""
"Il sistema aiuterà nella modifica del Secure Boot UEFI. Per assicurare che "
"questa modifica venga fatta da un utente autorizzato e non da un autore di "
"attacchi, è necessario scegliere una password ora e poi usare la stessa "
"password dopo il riavvio per confermare la modifica."

#. Type: note
#. Description
#: ../templates:5001
msgid ""
"If you choose to proceed but do not confirm the password upon reboot, the "
"Secure Boot configuration will not be changed, and the machine will continue "
"booting as before."
msgstr ""
"Se si sceglie di procedere ma non si conferma la password dopo il riavvio, "
"la configurazione del Secure Boot non verrà modificata e la macchina "
"continuerà ad avviarsi come prima."

#. Type: password
#. Description
#: ../templates:6001
msgid "UEFI Secure Boot password:"
msgstr "Password per Secure Boot UEFI:"

#. Type: password
#. Description
#: ../templates:6001
msgid "Please enter a password for configuring UEFI Secure Boot."
msgstr "Inserire una password per configurare il Secure Boot UEFI."

#. Type: password
#. Description
#: ../templates:6001
msgid ""
"This password will be used after a reboot to confirm authorization for a "
"change to Secure Boot state."
msgstr ""
"Questa password verrà usata dopo il riavvio per confermare l'autorizzazione "
"per una modifica allo stato del Secure Boot."

#. Type: password
#. Description
#: ../templates:7001
msgid "Re-enter password to verify:"
msgstr "Reinserire la password per verifica:"

#. Type: password
#. Description
#: ../templates:7001
msgid ""
"Please enter the same password again to verify that you have typed it 

Bug#915995: nfs-utils FTBFS with glibc 2.28

[Adrian Bunk]

Source: nfs-utils
Version: 1:1.3.4-2.3
Severity: serious
Tags: ftbfs

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

...
device-discovery.c: In function 'bl_add_disk':
device-discovery.c:156:28: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  } else if (dm_is_dm_major(major(dev)))
^
...
libtool: link: gcc -Wall -Wextra -Wstrict-prototypes -pipe 
-D_LARGEFILE64_SOURCE -g -Wall -DPIPEFS_DIR=\"/run/rpc_pipefs\" 
-DGSSD_PIPEFS_DIR=\"/run/rpc_pipefs\" -O2 -Wl,-z -Wl,relro -o blkmapd 
device-discovery.o device-inq.o device-process.o dm-device.o  -ldevmapper 
../../support/nfs/libnfs.a
/usr/bin/ld: device-discovery.o: in function `bl_add_disk':
/build/1st/nfs-utils-1.3.4/utils/blkmapd/device-discovery.c:156: undefined 
reference to `major'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:506: blkmapd] Error 1

Bug#915997: unyaffs FTBFS with glibc 2.28

[Adrian Bunk]

Source: unyaffs
Version: 0.9.6-1
Severity: serious
Tags: ftbfs buster sid

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

...
make V=1 -j1
make[2]: Entering directory '/build/1st/unyaffs-0.9.6'
cc -D_FORTIFY_SOURCE=2 -O2 -Wall -Wl,-z,relro unyaffs.c -o unyaffs
unyaffs.c: In function 'prt_node':
unyaffs.c:360:15: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
   major(oh->yst_rdev),
   ^
unyaffs.c:361:15: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
   minor(oh->yst_rdev));
   ^
   mknod
/usr/bin/ld: /tmp/ccmn6g0d.o: in function `process_chunk':
unyaffs.c:(.text+0x12cf): undefined reference to `minor'
/usr/bin/ld: unyaffs.c:(.text+0x12e1): undefined reference to `major'
/usr/bin/ld: unyaffs.c:(.text+0x1330): undefined reference to `minor'
/usr/bin/ld: unyaffs.c:(.text+0x1342): undefined reference to `major'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:4: unyaffs] Error 1

Bug#915996: kvpm FTBFS with glibc 2.28

[Adrian Bunk]

Source: kvpm
Version: 0.9.10-1.1
Severity: serious
Tags: ftbfs

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

...
/build/1st/kvpm-0.9.10/kvpm/logvol.cpp: In member function 'void 
LogVol::getDeviceNumbers(long unsigned int&, long unsigned int&)':
/build/1st/kvpm-0.9.10/kvpm/logvol.cpp:1147:16: error: 'major' was not declared 
in this scope
 majornum = major(fs.st_rdev);
^
/build/1st/kvpm-0.9.10/kvpm/logvol.cpp:1148:16: error: 'minor' was not declared 
in this scope
 minornum = minor(fs.st_rdev);
^

Bug#915998: tcplay FTBFS with glibc 2.28

[Adrian Bunk]

Source: tcplay
Version: 1.1-5
Severity: serious
Tags: ftbfs

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

...
/build/1st/tcplay-1.1/tcplay.c: In function 'xlate_maj_min':
/build/1st/tcplay-1.1/tcplay.c:1339:14: warning: implicit declaration of 
function 'makedev' [-Wimplicit-function-declaration]
  dev_t dev = makedev(maj, min);
  ^~~
...
/usr/bin/ar qc libtcplay.a  CMakeFiles/tcplay-static.dir/tcplay_api.c.o 
CMakeFiles/tcplay-static.dir/tcplay.c.o CMakeFiles/tcplay-static.dir/crc32.c.o 
CMakeFiles/tcplay-static.dir/safe_mem.c.o CMakeFiles/tcplay-static.dir/io.c.o 
CMakeFiles/tcplay-static.dir/hdr.c.o CMakeFiles/tcplay-static.dir/humanize.c.o 
CMakeFiles/tcplay-static.dir/crypto.c.o 
CMakeFiles/tcplay-static.dir/generic_xts.c.o 
CMakeFiles/tcplay-static.dir/crypto-gcrypt.c.o 
CMakeFiles/tcplay-static.dir/pbkdf2-gcrypt.c.o
/usr/bin/ranlib libtcplay.a
/usr/bin/ld: CMakeFiles/tcplay-bin.dir/tcplay.c.o: in function `xlate_maj_min':
./obj-x86_64-linux-gnu/./tcplay.c:1339: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[4]: Leaving directory '/build/1st/tcplay-1.1/obj-x86_64-linux-gnu'
make[4]: *** [CMakeFiles/tcplay-bin.dir/build.make:237: tcplay] Error 1

Bug#916001: partconf FTBFS with glibc 2.28

[Adrian Bunk]

Source: partconf
Version: 1.51
Severity: serious
Tags: ftbfs

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

...
cc -W -Wall -Os -o find-partitions -DFIND_PARTS_MAIN find-parts.c util.o 
xasprintf.o -lparted
find-parts.c: In function 'is_cdrom':
find-parts.c:129:13: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 switch (major(st.st_rdev)) {
 ^
find-parts.c:137:9: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
 if (minor(st.st_rdev) == 0) {
 ^
 mknod
/usr/bin/ld: /tmp/cc3JcWrE.o: in function `is_cdrom':
find-parts.c:(.text+0x25): undefined reference to `major'
/usr/bin/ld: find-parts.c:(.text+0x3b): undefined reference to `minor'
/usr/bin/ld: find-parts.c:(.text+0x4b): undefined reference to `minor'
/usr/bin/ld: find-parts.c:(.text+0x5e): undefined reference to `major'
/usr/bin/ld: find-parts.c:(.text+0x80): undefined reference to `major'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:12: find-partitions] Error 1

Bug#915898: picard-tools FTBFS: error: module not found: java.xml.bind

[Emmanuel Bourg]

Le 08/12/2018 à 20:04, Andreas Tille a écrit :

> Hmmm,
> 
>   grep -R java.xml.bind
> 
> in the picard-tools source tree does not have any result.

Probably due to this ? :)

https://salsa.debian.org/med-team/picard-tools/commit/9359e09f

Bug#916000: ncbi-blast+: FTBFS - Makefile.flat: No such file or directory

[Andreas Metzler]

Source: ncbi-blast+
Version: 2.7.1-1
Severity: serious
Justification: fails to build from source

Hello,

ncbi-blast+ FTBFS on current sid:

LIBRARIES:  build as dynamic by default
FEATURES:   GCC MT LFS DLL DLL_BUILD unix WinMain Linux
PACKAGES:
  enabled:  Iconv Z BZ2 PCRE MBEDTLS GMP GMP NETTLE NETTLE GNUTLS Boost.Spirit 
Boost.Test.Included LMDB LocalLMDB
  disabled: UUID FUSE LIBUNWIND LocalZ LocalBZ2 LZO LocalPCRE GCRYPT OPENSSL 
KRB5 CURL Sybase DBLib FreeTDS MySQL BerkeleyDB BerkeleyDB++ ODBC PYTHON 
PYTHON25 PYTHON26 PYTHON27 PYTHON3 PERL Boost.Filesystem Boost.Iostreams 
Boost.Program-Options Boost.Regex Boost.System Boost.Test Boost.Thread 
C-Toolkit OpenGL MESA GLUT GLEW wxWidgets wx2.8 Fast-CGI LocalSSS LocalMSGMAIL2 
SSSUTILS LocalNCBILS NCBILS2 SSSDB SP ORBacus ICU EXPAT SABLOT LIBXML LIBXSLT 
LIBEXSLT Xerces Xalan Zorba SQLITE3 SQLITE3ASYNC VDB OECHEM SGE MUPARSER HDF5 
JPEG PNG TIFF GIF UNGIF XPM FreeType FTGL MAGIC MIMETIC GSOAP AVRO Cereal SASL2 
MONGODB MONGODB3 GMOCK LAPACK LIBUV LIBSSH2 CASSANDRA LIBXLSXWRITER GRPC
PROJECTS:
  enabled:  cgi serial objects app algo
  disabled: local_lbsm connext ncbi_crypt bdb dbapi ctools gui gbench

Tools / flags / paths:  
/tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/build/Makefile.mk
Configuration  header:  
/tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/inc/ncbiconf_unix.h

To build everything:  cd /tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/build && 
/usr/bin/make all_r
or simply run /usr/bin/make in the current directory


*** CONFIGURATION SUCCESSFUL ***
make[1]: Leaving directory '/tmp/MODGNU/ncbi-blast+-2.7.1'
   debian/rules override_dh_auto_build-arch
make[1]: Entering directory '/tmp/MODGNU/ncbi-blast+-2.7.1'
cd c++/BUILD/build  && \
make -j5 -f Makefile.flat all_projects="algo/blast/ app/ objmgr/ 
objtools/align_format/ objtools/blast/"
make[2]: Entering directory '/tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/build'
make[2]: warning: -j5 forced in submake: resetting jobserver mode.
make[2]: Makefile.flat: No such file or directory
make[2]: *** No rule to make target 'Makefile.flat'.  Stop.
make[2]: Leaving directory '/tmp/MODGNU/ncbi-blast+-2.7.1/c++/BUILD/build'
make[1]: *** [debian/rules:56: override_dh_auto_build-arch] Error 2
make[1]: Leaving directory '/tmp/MODGNU/ncbi-blast+-2.7.1'
make: *** [debian/rules:129: build-arch] Error 2

Bug#915999: wsjtx needs libqt5multimedia5-plugins

[Christoph Berg]

Package: wsjtx
Version: 1.8.0+repack-1
Severity: normal

Hi,

wsjtx needs libqt5multimedia5-plugins installed or else it will
complain that sound input/output is not available on startup.

https://sourceforge.net/p/wsjt/mailman/message/33765271/

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

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

Versions of packages wsjtx depends on:
ii  libc62.27-8
ii  libfftw3-double3 3.3.8-2
ii  libfftw3-single3 3.3.8-2
ii  libgcc1  1:8.2.0-9
ii  libgfortran5 8.2.0-9
ii  libgomp1 8.2.0-9
ii  libhamlib-utils  3.2-3+b1
ii  libhamlib2   3.2-3+b1
ii  libqt5core5a 5.11.2+dfsg-7
ii  libqt5gui5   5.11.2+dfsg-7
ii  libqt5multimedia55.11.2-2
ii  libqt5network5   5.11.2+dfsg-7
ii  libqt5printsupport5  5.11.2+dfsg-7
ii  libqt5serialport55.11.2-2
ii  libqt5widgets5   5.11.2+dfsg-7
ii  libquadmath0 8.2.0-9
ii  libstdc++6   8.2.0-9
ii  libudev1 239-13
ii  libusb-1.0-0 2:1.0.22-2

Versions of packages wsjtx recommends:
pn  wsjtx-doc  

wsjtx suggests no packages.

-- no debconf information

Christoph

Bug#916003: nfswatch FTBFS with glibc 2.28

[Adrian Bunk]

Source: nfswatch
Version: 4.99.11-4
Severity: serious
Tags: ftbfs

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

...
util.c: In function 'setup_nfs_counters':
util.c:557:27: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
nc->nc_dev.Major = major(st.st_dev);
   ^
util.c:558:27: warning: implicit declaration of function 'minor'; did you mean 
'mknod'? [-Wimplicit-function-declaration]
nc->nc_dev.Minor = minor(st.st_dev);
   ^
   mknod
...
cc -o nfswatch dlpi.o logfile.o netaddr.o nfswatch.o nit.o pfilt.o pktfilter.o 
rpcfilter.o rpcutil.o screen.o snoop.o util.o xdr.o parsenfsfh.o linux.o -lpcap 
-lncurses -lm
/usr/bin/ld: util.o: in function `setup_nfs_counters':
util.c:(.text+0x6d9): undefined reference to `major'
/usr/bin/ld: util.c:(.text+0x6f6): undefined reference to `minor'
/usr/bin/ld: util.c:(.text+0x910): undefined reference to `major'
/usr/bin/ld: util.c:(.text+0x928): undefined reference to `minor'
/usr/bin/ld: util.o: in function `setup_fil_counters':
util.c:(.text+0xa5c): undefined reference to `major'
/usr/bin/ld: util.c:(.text+0xa74): undefined reference to `minor'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:165: nfswatch] Error 1

Bug#916002: xnbd FTBFS with glibc 2.28

[Adrian Bunk]

Source: xnbd
Version: 0.3.0-2
Severity: serious
Tags: ftbfs buster sid

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

...
io.c: In function 'get_disksize':
io.c:155:7: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
   if (major(st.st_rdev) == 259)
   ^
...
/bin/bash ./libtool  --tag=CC   --mode=link gcc  -g -O2 
-ffile-prefix-map=/build/1st/xnbd-0.3.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-Wformat=2 -Wcast-align -Wwrite-strings -Wfloat-equal -Wpointer-arith 
-Wswitch-enum -fstack-protector -fstack-check -lgthread-2.0 -pthread -lglib-2.0 
-Wl,-z,relro -o xnbd-cachestatdump xnbd_cachestatdump.o libxnbd_internal.la 
libtool: link: gcc -g -O2 -ffile-prefix-map=/build/1st/xnbd-0.3.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Wformat=2 -Wcast-align -Wwrite-strings 
-Wfloat-equal -Wpointer-arith -Wswitch-enum -fstack-protector -fstack-check 
-pthread -Wl,-z -Wl,relro -o .libs/xnbd-cachestatdump xnbd_cachestatdump.o  
-lgthread-2.0 -lglib-2.0 ./.libs/libxnbd_internal.so -pthread -Wl,-rpath 
-Wl,/usr/lib/xnbd
/usr/bin/ld: ./.libs/libxnbd_internal.so: undefined reference to `major'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:639: xnbd-cachestatdump] Error 1

Bug#916005: oss4 FTBFS with glibc 2.28

[Adrian Bunk]

Source: oss4
Version: 4.2-build2010-5
Severity: serious
Tags: ftbfs

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

...
ossdetect.c: In function 'create_devlinks':
ossdetect.c:564:31: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
   if (mknod (dev, node_m, makedev (major, minor)) == -1)
   ^~~
cc -O -s -o ../../../target/sbin/ossdetect ./ossdetect.o   
/usr/bin/ld: ./ossdetect.o: in function `main':
ossdetect.c:(.text+0xf2c): undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:34: ../../../target/sbin/ossdetect] Error 1

Bug#916004: makefs FTBFS with glibc 2.28

[Adrian Bunk]

Source: makefs
Version: 20100306-6
Severity: serious
Tags: ftbfs buster sid

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

...
/build/1st/makefs-20100306/builddir/usr.sbin/makefs/nbsrc/sbin/mknod/pack_dev.c:
 In function 'pack_native':
/build/1st/makefs-20100306/builddir/usr.sbin/makefs/nbsrc/sbin/mknod/pack_dev.c:72:9:
 warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
   dev = makedev(numbers[0], numbers[1]);
 ^~~
/build/1st/makefs-20100306/builddir/usr.sbin/makefs/nbsrc/sbin/mknod/pack_dev.c:73:15:
 warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
   if ((u_long)major(dev) != numbers[0])
   ^
...
cc -g -O2 -ffile-prefix-map=/build/1st/makefs-20100306=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wformat 
-Wno-unused-but-set-variable -Wno-unused-result -flto=jobserver -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed  -o makefs cd9660.o ffs.o getid.o makefs.o misc.o 
pack_dev.o spec.o walk.o cd9660_strings.o cd9660_debug.o cd9660_eltorito.o 
cd9660_write.o cd9660_conversion.o iso9660_rrip.o cd9660_archimedes.o 
ffs_alloc.o ffs_balloc.o ffs_bswap.o ffs_subr.o ffs_tables.o ufs_bmap.o buf.o 
mkfs.o pwcache.o strsuftoll.o fparseln.o -lbsd
/usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 124
/tmp/ccuOSmWf.ltrans0.ltrans.o: in function `fparseln':
:(.text+0xbfb7): warning: This function cannot be safely ported, 
use getline(3) instead, as it is supported by GNU and POSIX.1-2008.
/usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 124
/tmp/ccuOSmWf.ltrans0.ltrans.o: in function `pack_native':
:(.text+0x4bb1): undefined reference to `makedev'
/usr/bin/ld: :(.text+0x4bbe): undefined reference to `major'
/usr/bin/ld: :(.text+0x4be6): undefined reference to `minor'
collect2: error: ld returned 1 exit status
*** Error code 1

Bug#916006: udftools FTBFS with glibc 2.28

[Adrian Bunk]

Source: udftools
Version: 2.0-2
Severity: serious
Tags: ftbfs

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

...
main.c: In function 'is_whole_disk':
main.c:170:8: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  maj = major(st.st_rdev);
^
main.c:171:8: warning: implicit declaration of function 'minor'; did you mean 
'mknod'? [-Wimplicit-function-declaration]
  min = minor(st.st_rdev);
^
...
libtool: link: gcc -g -O2 -ffile-prefix-map=/build/1st/udftools-2.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o mkudffs main.o mkudffs.o defaults.o file.o options.o  
../libudffs/.libs/libudffs.a
/usr/bin/ld: main.o: in function `is_whole_disk':
./mkudffs/main.c:170: undefined reference to `major'
/usr/bin/ld: ./mkudffs/main.c:171: undefined reference to `minor'
/usr/bin/ld: main.o: in function `is_removable_disk':
./mkudffs/main.c:231: undefined reference to `minor'
/usr/bin/ld: ./mkudffs/main.c:231: undefined reference to `major'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:381: mkudffs] Error 1

Bug#916007: spacefm FTBFS with glibc 2.28

[Adrian Bunk]

Source: spacefm
Version: 1.0.6-3
Severity: serious
Tags: ftbfs

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

...
../../../src/main.c: In function 'get_inode_tag':
../../../src/main.c:189:42: error: implicit declaration of function 'major' 
[-Werror=implicit-function-declaration]
  major( stat_buf.st_dev ),
  ^
../../../src/main.c:190:42: error: implicit declaration of function 'minor'; 
did you mean 'mknod'? [-Werror=implicit-function-declaration]
  minor( stat_buf.st_dev ),
  ^

Bug#916008: wmhdplop FTBFS with glibc 2.28

[Adrian Bunk]

Source: wmhdplop
Version: 0.9.10-1
Severity: serious
Tags: ftbfs buster sid

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

...
devnames.c: In function 'device_id_from_name':
devnames.c:207:13: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
   *pmajor = major(stat_buf.st_rdev);
 ^
devnames.c:208:13: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
   *pminor = minor(stat_buf.st_rdev);
 ^
...
/usr/bin/ld: wmhdplop-devnames.o: in function `device_id_from_name':
./devnames.c:207: undefined reference to `major'
/usr/bin/ld: ./devnames.c:208: undefined reference to `minor'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:483: wmhdplop] Error 1

Bug#916006: udftools FTBFS with glibc 2.28

[Pali Rohár]

On Sunday 09 December 2018 13:20:49 Adrian Bunk wrote:
> main.c: In function 'is_whole_disk':
> main.c:170:8: warning: implicit declaration of function 'major' 
> [-Wimplicit-function-declaration]
>   maj = major(st.st_rdev);
> ^
> main.c:171:8: warning: implicit declaration of function 'minor'; did you mean 
> 'mknod'? [-Wimplicit-function-declaration]
>   min = minor(st.st_rdev);
> ^

Hi! This problem is already fixed in upstream udftools git repository
and I'm planning to release a new version of udftools in this month,
including new Debian package upload.

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: PGP signature

Bug#916009: sbuild: sbuild-createchroot --setup-only option is unusable due to empty directory checking

[Lukas Schwaighofer]

Package: sbuild
Version: 0.77.1-2
Severity: normal
Tags: patch


Dear Maintainer,

the sbuild-createchroot --setup-only option is designed to perform setup
tasks on an existing chroot.  Thus the check for non-empty directories
introduced in

https://salsa.debian.org/debian/sbuild/commit/53e250cdeb0035663833fa0c8ce80adf96d31c03
needs to be disabled when that option is in use.

I've fixed this for my need with the following change:


diff -u /usr/bin/sbuild-createchroot sbuild-createchroot
--- /usr/bin/sbuild-createchroot»   2018-11-13 16:07:19.0
+0100 +++ sbuild-createchroot»2018-12-09 11:41:56.634681576 +0100
@@ -288,7 +288,7 @@
 # has more entries than just "." and ".." and must thus not be
empty. readdir $dh;
 readdir $dh;
-die "$target is not empty" if (readdir $dh);
+die "$target is not empty" if (readdir $dh and !$conf->get('SETUP_ONLY')); 
} else {
 # Create the target directory in advance so abs_path (which is
buggy) # won't fail.  Remove if abs_path is replaced by something
better.


Thanks
Lukas

Bug#915975: please package and release new version of telegram desktop version 1.4.8

[Коля Гурьев]

Hi,

09.12.2018 01:20, shirish शिरीष пишет:
> Please package and release new version fo telegram-desktop v 1.4.8 .

This is pre-release version of Telegram Desktop and won't be packaged, sorry.

> Also your watchfile needs to be tweaked it seems, see
> https://github.com/telegramdesktop/tdesktop/releases while at t.d.o.
> it says that the latest is 1.4.3 which is obviously wrong.

No, it's correct. 1.4.3 is the latest version available on
desktop.telegram.org. But in changelog[1] only 1.4.0 is mentioned.

 [1]: https://desktop.telegram.org/changelog

Bug#916010: fotoxx FTBFS with glibc 2.28

[Adrian Bunk]

Source: fotoxx
Version: 18.07-1
Severity: serious
Tags: ftbfs

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

...
f.effects.cc: In function 'int anykernel_dialog_event(zdialog*, const char*)':
f.effects.cc:5064:34: error: reference to 'fmul' is ambiguous
  zdialog_fetch(zd,"fmul",fmul);
  //  17.08
  ^~~~
In file included from /usr/include/c++/8/cmath:45,
 from /usr/include/c++/8/math.h:36,
 from zfuncs.h:37,
 from fotoxx.h:30,
 from f.effects.cc:42:
/usr/include/x86_64-linux-gnu/bits/mathcalls-narrow.h:30:20: note: candidates 
are: 'float fmul(double, double)'
 __MATHCALL_NARROW (__MATHCALL_NAME (mul), __MATHCALL_REDIR_NAME (mul), 2);
^~~
f.effects.cc:4919:16: note: 'float anykernel_names::fmul'
float   fmul = 1.0; 
  //  multiplier
^~~~
f.effects.cc:5065:34: error: reference to 'fadd' is ambiguous
  zdialog_fetch(zd,"fadd",fadd);
  ^~~~
In file included from /usr/include/c++/8/cmath:45,
 from /usr/include/c++/8/math.h:36,
 from zfuncs.h:37,
 from fotoxx.h:30,
 from f.effects.cc:42:
/usr/include/x86_64-linux-gnu/bits/mathcalls-narrow.h:24:20: note: candidates 
are: 'float fadd(double, double)'
 __MATHCALL_NARROW (__MATHCALL_NAME (add), __MATHCALL_REDIR_NAME (add), 2);
^~~
f.effects.cc:4920:16: note: 'int anykernel_names::fadd'
int fadd = 0;   
  //  adder
^~~~
f.effects.cc: In function 'void* anykernel_wthread(void*)':
f.effects.cc:5195:11: error: reference to 'fmul' is ambiguous
   if (fmul != 1.0) {   
  //  apply multiplier   17.08
   ^~~~
In file included from /usr/include/c++/8/cmath:45,
 from /usr/include/c++/8/math.h:36,
 from zfuncs.h:37,
 from fotoxx.h:30,
 from f.effects.cc:42:
/usr/include/x86_64-linux-gnu/bits/mathcalls-narrow.h:30:20: note: candidates 
are: 'float fmul(double, double)'
 __MATHCALL_NARROW (__MATHCALL_NAME (mul), __MATHCALL_REDIR_NAME (mul), 2);
^~~
f.effects.cc:4919:16: note: 'float anykernel_names::fmul'
float   fmul = 1.0; 
  //  multiplier
^~~~
f.effects.cc:5196:16: error: reference to 'fmul' is ambiguous
  red = fmul * red;
^~~~
In file included from /usr/include/c++/8/cmath:45,
 from /usr/include/c++/8/math.h:36,
 from zfuncs.h:37,
 from fotoxx.h:30,
 from f.effects.cc:42:
/usr/include/x86_64-linux-gnu/bits/mathcalls-narrow.h:30:20: note: candidates 
are: 'float fmul(double, double)'
 __MATHCALL_NARROW (__MATHCALL_NAME (mul), __MATHCALL_REDIR_NAME (mul), 2);
^~~
f.effects.cc:4919:16: note: 'float anykernel_names::fmul'
float   fmul = 1.0; 
  //  multiplier
^~~~
f.effects.cc:5197:18: error: reference to 'fmul' is ambiguous
  green = fmul * green;
  ^~~~
In file included from /usr/include/c++/8/cmath:45,
 from /usr/include/c++/8/math.h:36,
 from zfuncs.h:37,
 from fotoxx.h:30,
 from f.effects.cc:42:
/usr/include/x86_64-linux-gnu/bits/mathcalls-narrow.h:30:20: note: candidates 
are: 'float fmul(double, double)'
 __MATHCALL_NARROW (__MATHCALL_NAME (mul), __MATHCALL_REDIR_NAME (mul), 2);
^~~
f.effects.cc:4919:16: note: 'float anykernel_names::fmul'
float   fmul = 1.0; 
  //  multiplier
^~~~
f.effects.cc:5198:17: error: reference to 'fmul' is ambiguous
  blue = fmul * blue;
 ^~~~
In file included from /usr/include/c++/8/cmath:45,
 from /usr/include/c++/8/math.h:36,
 from zfuncs.h:37,
 from fotoxx.h:30,
 from f.effects.cc:42:
/usr/include/x86_64-linux-gnu/bits/mathcalls-narrow.h:30:20: note: candidates 
are: 'float fmul(double, double)'
 __MATHCALL_NARROW (__MATHCALL_NAME (mul), __MATHCALL_REDIR_NAME (mul), 2);
^~~
f.effects.cc:4919:16: note: 'float anykernel_names::fmul'
float   fmul = 1.0; 
  //  multiplier
^~~~
f.effects.cc:5201:11: error: reference to 'fadd' is ambi

Bug#916009: sbuild: sbuild-createchroot --setup-only option is unusable due to empty directory checking

[Lukas Schwaighofer]

On Sun, 9 Dec 2018 12:48:30 +0100
Lukas Schwaighofer  wrote:

> I've fixed this for my need with the following change:

I messed up the patch formatting, corrected below.  Sorry for the noise.


--- /usr/bin/sbuild-createchroot2018-11-13 16:07:19.0 +0100
+++ sbuild-createchroot 2018-12-09 11:41:56.634681576 +0100
@@ -288,7 +288,7 @@
 # has more entries than just "." and ".." and must thus not be empty.
 readdir $dh;
 readdir $dh;
-die "$target is not empty" if (readdir $dh);
+die "$target is not empty" if (readdir $dh and !$conf->get('SETUP_ONLY'));
 } else {
 # Create the target directory in advance so abs_path (which is buggy)
 # won't fail.  Remove if abs_path is replaced by something better.
swluk@tank:~$ 

Bug#640509: Bug#905042: Intent to NMU deborphaner (MU preferred)

[Helge Kreutzmann]

Hello Chris,
On Sun, Dec 09, 2018 at 12:58:57PM +0100, Chris Hofstaedtler wrote:
> * Helge Kreutzmann  [181209 08:57]:
> > Hello Chris,
> > hello Carsten,
> > deborphaner has several documentation and translation bugs. Ideally
> > they would be solved in a MU, but if necessary they should be solved
> > in a NMU. If I don't hear back from you I will initiate the following
> > sequence (you can intervene at any time, a MU is preferred!):
> 
> Well, looks like you're going to do an overhaul of the packaging.
> I'd prefer it if you'd join as Uploaders: to the package then.
> For that I've granted you access on salsa just now.

Thanks.

Please note that this is temporary, I only intend to work on it for
one release (and if necessary fixes casused by this).

Are you fine with the proposed changes by me, and if so, do you have
any additional documentation updates/fixes you would like to be
included (before I ask for translation updates)?

Greetings

   Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#640509: Bug#905042: Intent to NMU deborphaner (MU preferred)

[Chris Hofstaedtler]

Hey,

* Helge Kreutzmann  [181209 08:57]:
> Hello Chris,
> hello Carsten,
> deborphaner has several documentation and translation bugs. Ideally
> they would be solved in a MU, but if necessary they should be solved
> in a NMU. If I don't hear back from you I will initiate the following
> sequence (you can intervene at any time, a MU is preferred!):

Well, looks like you're going to do an overhaul of the packaging.
I'd prefer it if you'd join as Uploaders: to the package then.
For that I've granted you access on salsa just now.

Cheers,
Chris

Bug#916012: emacs-gtk crashes when rendering U+2728 SPARKLES

[Daniel Kahn Gillmor]

Package: emacs-gtk
Version: 1:25.2+1-11
Severity: normal
Control: affects -1 + notmuch-emacs

I'm running emacs-gtk under X11.

When i try to open the attached file (sparkles.txt), emacs-gtk crashes
with the following backtrace.  Sorry for it not being well-annotated,
i have emacs-gtk-dbg and emacs-bin-common-dbgsym installed!

I've tried this after clearing my xrdb as well, and the crash still
happens.

Let me know if i can help debug further.

I've marked this bug report as affecting notmuch-emacs because anyone
who sends a mail that contains U+2728 SPARKLES in the subject line
(typically via RFC 2047-encoding) will crash the inbox view.

---
X protocol error: BadLength (poly request too large or internal Xlib length 
error) on protocol request 139
When compiled with GTK, Emacs cannot recover from X disconnects.
This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715
For details, see etc/PROBLEMS.
Fatal error 6: Aborted
(emacs:2822): GLib-WARNING **: 05:31:05.156: g_main_context_prepare() called 
recursively from within a source's check() or prepare() member.

(emacs:2822): GLib-WARNING **: 05:31:05.156: g_main_context_check() called 
recursively from within a source's check() or prepare() member.

Backtrace:
emacs[0x50a52e]
emacs[0x4f0a29]
emacs[0x50a5d3]
emacs[0x4c0b53]
emacs[0x4c4eb9]
emacs[0x4c4f3b]
/usr/lib/x86_64-linux-gnu/libX11.so.6(_XError+0x11a)[0x7fca397fa11a]
/usr/lib/x86_64-linux-gnu/libX11.so.6(+0x43077)[0x7fca397f7077]
/usr/lib/x86_64-linux-gnu/libX11.so.6(+0x4311d)[0x7fca397f711d]
/usr/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x55)[0x7fca397f7a55]
/usr/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x57)[0x7fca397e97b7]
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x68e1d)[0x7fca3a26ee1d]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_prepare+0x1c9)[0x7fca39d69379]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4dd7b)[0x7fca39d69d7b]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_pending+0x27)[0x7fca39d69f17]
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_events_pending+0xd)[0x7fca3a53e31d]
emacs[0x4c14f7]
emacs[0x4f7829]
emacs[0x4f7ec5]
emacs[0x5c7eb7]
emacs[0x57c344]
emacs[0x5cabda]
emacs[0x5cae61]
emacs[0x5cb16c]
emacs[0x44349a]
emacs[0x44b5b0]
emacs[0x451148]
emacs[0x4647a1]
emacs[0x467eeb]
emacs[0x563d6e]
emacs[0x432332]
emacs[0x454639]
emacs[0x4fa45f]
emacs[0x4fde89]
emacs[0x4ff574]
emacs[0x563ce2]
emacs[0x4f0e64]
emacs[0x563c61]
emacs[0x4f0dfb]
emacs[0x4f5557]
emacs[0x4f58a8]
...
Aborted
---

-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages emacs-gtk depends on:
ii  emacs-bin-common   1:25.2+1-11
ii  emacs-common   1:25.2+1-11
ii  libacl12.2.52-3+b1
ii  libasound2 1.1.7-1+b1
ii  libatk1.0-02.30.0-1
ii  libc6  2.27-8
ii  libcairo-gobject2  1.16.0-1
ii  libcairo2  1.16.0-1
ii  libdbus-1-31.12.10-1
ii  libfontconfig1 2.13.1-2
ii  libfreetype6   2.9.1-3
ii  libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii  libgif75.1.4-3
ii  libglib2.0-0   2.58.1-2
ii  libgnutls303.5.19-1+b1
ii  libgomp1   8.2.0-9
ii  libgpm21.20.7-5
ii  libgtk-3-0 3.24.1-2
ii  libice62:1.0.9-2
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libm17n-0  1.8.0-2
ii  libmagickcore-6.q16-6  8:6.9.10.14+dfsg-7
ii  libmagickwand-6.q16-6  8:6.9.10.14+dfsg-7
ii  libotf00.9.13-4
ii  libpango-1.0-0 1.42.4-4
ii  libpangocairo-1.0-01.42.4-4
ii  libpng16-161.6.34-2
ii  librsvg2-2 2.44.9-1
ii  libselinux12.8-1+b1
ii  libsm6 2:1.2.2-1+b3
ii  libtiff5   4.0.10-3
ii  libtinfo6  6.1+20181013-1
ii  libx11-6   2:1.6.7-1
ii  libx11-xcb12:1.6.7-1
ii  libxcb11.13.1-1
ii  libxfixes3 1:5.0.3-1
ii  libxft22.3.2-2
ii  libxinerama1   2:1.1.4-1
ii  libxml22.9.4+dfsg1-7+b2
ii  libxpm41:3.5.12-1
ii  libxrandr2 2:1.5.1-1
ii  libxrender11:0.9.10-1
ii  zlib1g 1:1.2.11.dfsg-1

emacs-gtk recommends no packages.

Versions of packages emacs-gtk suggests:
pn  emacs-common-non-dfsg  

-- no debconf information
✨

Bug#916011: Blank dialog — Can't locate object method "vbox" via package "Gtk3::Dialog"

[martin f krafft]

Package: gscan2pdf
Version: 2.2.1-1
Severity: normal

Gscan2pdf stopped working across an APT upgrade last night. Now only
a dialog window shows up, but it's blank, i.e. no UI elements
whatsoever. --debug log output ends with:

  WARN - *** unhandled exception in callback:
  ***   Can't locate object method "vbox" via package "Gtk3::Dialog" at 
/usr/bin/gscan2pdf line 1583.
  ***  ignoring at 
/usr/lib/x86_64-linux-gnu/perl5/5.28/Glib/Object/Introspection.pm line 67.

I did the same upgrade on another sid machine, but there it keeps
workins, and there is no such error message. I've tried rolling back
the APT upgrade, but still cannot get Gscan2pdf to display a UI to
me beyond the grey background.

All dependencies are the same across the two sid machines. I remain
utterly baffled at this.

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

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

Versions of packages gscan2pdf depends on:
ii  imagemagick8:6.9.10.14+dfsg-7
ii  imagemagick-6.q16 [imagemagick]8:6.9.10.14+dfsg-7
ii  libconfig-general-perl 2.63-1
ii  libdate-calc-perl  6.4-1
ii  libfilesys-df-perl 0.92-6+b4
ii  libgoocanvas2-perl 0.06-1
ii  libgtk3-perl   0.034-2
ii  libgtk3-simplelist-perl0.17-2
ii  libhtml-parser-perl3.72-3+b3
ii  libimage-magick-perl   8:6.9.10.14+dfsg-7
ii  libimage-sane-perl 0.14-1+b3
ii  liblist-moreutils-perl 0.416-1+b4
ii  liblocale-gettext-perl 1.07-3+b4
ii  liblog-log4perl-perl   1.49-1
ii  libossp-uuid-perl [libdata-uuid-perl]  1.6.2-1.5+b7
ii  libpdf-api2-perl   2.033-1
ii  libproc-processtable-perl  0.55-1+b1
ii  libreadonly-perl   2.050-1
ii  librsvg2-common2.44.9-1
ii  libset-intspan-perl1.19-1
ii  libtiff-tools  4.0.10-3
ii  libtry-tiny-perl   0.30-1
ii  sane-utils 1.0.27-3.1

Versions of packages gscan2pdf recommends:
ii  djvulibre-bin  3.5.27.1-10
ii  sane   1.0.14-13+b1
ii  tesseract-ocr  4.0.0-1+b1
ii  unpaper6.1-2+b2
ii  xdg-utils  1.1.3-1

gscan2pdf suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#916013: atop FTBFS with glibc 2.28

[Adrian Bunk]

Source: atop
Version: 2.3.0-1
Severity: serious
Tags: ftbfs

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

...
photosyst.c: In function 'lvmmapname':
photosyst.c:1465:19: error: called object 'major' is not a function or function 
pointer
 dmp->major  = major(statbuf.st_rdev);
   ^
photosyst.c:1420:25: note: declared here
 lvmmapname(unsigned int major, unsigned int minor,
~^
photosyst.c:1466:19: error: called object 'minor' is not a function or function 
pointer
 dmp->minor  = minor(statbuf.st_rdev);
   ^

Bug#640509: Bug#905042: Intent to NMU deborphaner (MU preferred)

[Chris Hofstaedtler]

* Helge Kreutzmann  [181209 13:04]:
> Hello Chris,
> On Sun, Dec 09, 2018 at 12:58:57PM +0100, Chris Hofstaedtler wrote:
> > * Helge Kreutzmann  [181209 08:57]:
> > > Hello Chris,
> > > hello Carsten,
> > > deborphaner has several documentation and translation bugs. Ideally
> > > they would be solved in a MU, but if necessary they should be solved
> > > in a NMU. If I don't hear back from you I will initiate the following
> > > sequence (you can intervene at any time, a MU is preferred!):
> > 
> > Well, looks like you're going to do an overhaul of the packaging.
> > I'd prefer it if you'd join as Uploaders: to the package then.
> > For that I've granted you access on salsa just now.
> 
> Thanks.
> 
> Please note that this is temporary, I only intend to work on it for
> one release (and if necessary fixes casused by this).
> 
> Are you fine with the proposed changes by me, and if so, do you have
> any additional documentation updates/fixes you would like to be
> included (before I ask for translation updates)?

The list looked good. I think there are two bugfixes in git already.
Go ahead.

Chris

Bug#916014: squashfs-tools FTBFS with glibc 2.28

[Adrian Bunk]

Source: squashfs-tools
Version: 1:4.3-6
Severity: serious
Tags: ftbfs

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

...
mksquashfs.c: In function 'create_inode':
mksquashfs.c:989:24: error: called object 'major' is not a function or function 
pointer
   unsigned int major = major(buf->st_rdev);
^
mksquashfs.c:989:16: note: declared here
   unsigned int major = major(buf->st_rdev);
^
mksquashfs.c:990:24: error: called object 'minor' is not a function or function 
pointer
   unsigned int minor = minor(buf->st_rdev);
^
mksquashfs.c:990:16: note: declared here
   unsigned int minor = minor(buf->st_rdev);
^
mksquashfs.c:1013:24: error: called object 'major' is not a function or 
function pointer
   unsigned int major = major(buf->st_rdev);
^
mksquashfs.c:1013:16: note: declared here
   unsigned int major = major(buf->st_rdev);
^
mksquashfs.c:1014:24: error: called object 'minor' is not a function or 
function pointer
   unsigned int minor = minor(buf->st_rdev);
^

Bug#916016: qbittorrent: No search plugins available

[Mark Caglienzi]

Package: qbittorrent
Version: 4.1.4-1
Severity: important

Dear Maintainer(s),
it's since a couple of days that qbittorrent does not have search plugins
available anymore (it used to have a bunch of them)

Searching online, I found that some years ago (maybe I was not even using it at
that time) it had this problem, resolved by fixing a bug wrt newer python
interpreters: https://bugs.launchpad.net/qbittorrent/+bug/846649

I have this python 2.7 version:

$ dpkg -l python2.7 | grep ^ii
ii  python2.7  2.7.15-5 amd64Interactive high-level object-
oriented language (version 2.7)

so 2.7.15-5, despite of the informations that reportbug extracts and adds below 
(that say 2.7.15-3)


If I launch qbittorrent from the terminal, it tells:

$ qbittorrent
Could not parse Nova search engine capabilities, msg:
Error:

so no really useful informations (aka no verbose error message), but there's
definitely a problem with search engine capabilities.

Kind regards,
Mark



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

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

Versions of packages qbittorrent depends on:
ii  geoip-database 20181108-1
ii  libboost-system1.67.0  1.67.0-11
ii  libc6  2.27-8
ii  libgcc11:8.2.0-9
ii  libqt5core5a   5.11.2+dfsg-7
ii  libqt5dbus55.11.2+dfsg-7
ii  libqt5gui5 5.11.2+dfsg-7
ii  libqt5network5 5.11.2+dfsg-7
ii  libqt5widgets5 5.11.2+dfsg-7
ii  libqt5xml5 5.11.2+dfsg-7
ii  libstdc++6 8.2.0-9
ii  libtorrent-rasterbar9  1.1.9-1+b1
ii  python 2.7.15-3
ii  zlib1g 1:1.2.11.dfsg-1

qbittorrent recommends no packages.

Versions of packages qbittorrent suggests:
pn  qbittorrent-dbg  

-- no debconf information


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

Bug#916015: gnome-bluetooth: have to re-pair btmouse after every bt off/on switch because of missing pin database entry.

[Thomas Krutz]

Package: gnome-bluetooth
Version: 3.28.2-2
Severity: important

Dear Maintainer,

i have two microsoft sculpt comfort mouses - one of which cannot reconnect 
after bt on/off switch

after some debugging it seems that this is due to missing pin-code-database.xml 
entry.

as it turns out, the same was already added to upstream 3 months ago:

https://gitlab.gnome.org/GNOME/gnome-bluetooth/commit/907fd7542c8c9d2b4cc2e3d78127c56bf4f3218b

adding the new device oui fixes my problem.

br
 Thomas

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

Kernel: Linux 4.18.0-3-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-bluetooth depends on:
ii  bluez 5.50-1
ii  bluez-obexd   5.50-1
ii  libc6 2.27-8
ii  libglib2.0-0  2.58.1-2
ii  libgnome-bluetooth13  3.28.2-2
ii  libgtk-3-03.24.1-2
ii  udev  239-13

Versions of packages gnome-bluetooth recommends:
ii  gnome-control-center  1:3.30.2-1
ii  gvfs-backends 1.38.1-1

gnome-bluetooth suggests no packages.

-- no debconf information

Bug#916018: xfce4-diskperf-plugin FTBFS with glibc 2.28

[Adrian Bunk]

Source: xfce4-diskperf-plugin
Version: 2.6.1-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xfce4-diskperf-plugin.html

...
devperf.c: In function 'DevGetPerfData1':
devperf.c:65:32: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 const int   iMajorNo = major(p_iDevice),
^
devperf.c:66:13: warning: implicit declaration of function 'minor' 
[-Wimplicit-function-declaration]
  iMinorNo = minor(p_iDevice);
 ^
devperf.c:69:21: error: 'major' redeclared as different kind of symbol
 unsigned intmajor, minor, rsect, wsect, ruse, wuse, use;
 ^
devperf.c:65:32: note: previous implicit declaration of 'major' was here
 const int   iMajorNo = major(p_iDevice),
^
devperf.c:69:28: error: 'minor' redeclared as different kind of symbol
 unsigned intmajor, minor, rsect, wsect, ruse, wuse, use;
^
devperf.c:66:13: note: previous implicit declaration of 'minor' was here
  iMinorNo = minor(p_iDevice);
 ^

Bug#916019: zfs-fuse FTBFS with glibc 2.28

[Adrian Bunk]

Source: zfs-fuse
Version: 0.7.0-18
Severity: serious
Tags: ftbfs

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

...
lib/libsolcompat/getmntany.c: In function 'getextmntent':
lib/libsolcompat/getmntany.c:89:19: warning: implicit declaration of function 
'major' [-Wimplicit-function-declaration]
   mp->mnt_major = major(st.st_dev);
   ^
lib/libsolcompat/getmntany.c:90:19: warning: implicit declaration of function 
'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration]
   mp->mnt_minor = minor(st.st_dev);
   ^
...
gcc -o cmd/zdb/zdb -pipe -Wall -ggdb cmd/zdb/zdb.o cmd/zdb/zdb_il.o 
cmd/zdb/ptrace.o lib/libavl/libavl.a lib/libnvpair/libnvpair-user.a 
lib/libumem/libumem.a lib/libzfs/libzfs.a lib/libzpool/libzpool-user.a 
lib/libzfscommon/libzfscommon-user.a lib/libuutil/libuutil.a 
lib/libsolcompat/libsolcompat.a -lrt -lpthread -ldl -lz -lm -laio -lcrypto
/usr/bin/ld: lib/libsolcompat/libsolcompat.a(getmntany.o): in function 
`getextmntent':
/build/1st/zfs-fuse-0.7.0/src/lib/libsolcompat/getmntany.c:89: undefined 
reference to `major'
/usr/bin/ld: /build/1st/zfs-fuse-0.7.0/src/lib/libsolcompat/getmntany.c:90: 
undefined reference to `minor'
collect2: error: ld returned 1 exit status
scons: *** [cmd/zdb/zdb] Error 1

Bug#916017: pax FTBFS with glibc 2.28

[Adrian Bunk]

Source: pax
Version: 1:20171021-2
Severity: serious
Tags: ftbfs

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

...
cpio.c: In function 'vcpio_wr':
pax.h:261:18: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 #define MAJOR(x) major(x)
  ^
cpio.c:777:53: note: in expansion of macro 'MAJOR'
  t_major = (anonarch & ANON_INODES) ? 0UL : (u_long)MAJOR(arcn->sb.st_dev);
 ^
pax.h:262:18: warning: implicit declaration of function 'minor'; did you mean 
'mknod'? [-Wimplicit-function-declaration]
 #define MINOR(x) minor(x)
  ^
cpio.c:778:53: note: in expansion of macro 'MINOR'
  t_minor = (anonarch & ANON_INODES) ? 0UL : (u_long)MINOR(arcn->sb.st_dev);
 ^
In file included from gen_subs.c:55:
gen_subs.c: In function 'ls_list':
pax.h:261:18: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 #define MAJOR(x) major(x)
  ^
gen_subs.c:123:50: note: in expansion of macro 'MAJOR'
   (void)fprintf(fp, "%4lu,%4lu ", (unsigned long)MAJOR(sbp->st_rdev),
  ^
...
/usr/bin/ld: /tmp/cc4cCtFm.o: in function `vcpio_rd':
./cpio.c:628: undefined reference to `makedev'
/usr/bin/ld: ./cpio.c:631: undefined reference to `makedev'
/usr/bin/ld: /tmp/cc4cCtFm.o: in function `vcpio_wr':
./cpio.c:777: undefined reference to `major'
/usr/bin/ld: ./cpio.c:778: undefined reference to `minor'
/usr/bin/ld: ./cpio.c:850: undefined reference to `major'
/usr/bin/ld: ./cpio.c:852: undefined reference to `minor'
/usr/bin/ld: /tmp/ccSVOR4l.o: in function `ls_list':
./gen_subs.c:124: undefined reference to `minor'
/usr/bin/ld: ./gen_subs.c:123: undefined reference to `major'
/usr/bin/ld: /tmp/cc0rXSax.o: in function `ustar_rd':
./tar.c:842: undefined reference to `makedev'
/usr/bin/ld: /tmp/cc0rXSax.o: in function `ustar_wr':
./tar.c:992: undefined reference to `major'
/usr/bin/ld: ./tar.c:994: undefined reference to `minor'
collect2: error: ld returned 1 exit status
make: *** [debian/rules:55: debian/.build_stamp] Error 1

Bug#916020: smp-utils FTBFS with glibc 2.28

[Adrian Bunk]

Source: smp-utils
Version: 0.98-1
Severity: serious
Tags: ftbfs buster sid

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

...
smp_lin_bsg.c: In function 'open_lin_bsg_device':
smp_lin_bsg.c:230:21: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
 makedev(maj, min));
 ^~~
...
smp_mptctl_io.c: In function 'chk_mpt_device':
smp_mptctl_io.c:66:52: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 if ((S_ISCHR(st.st_mode)) && (MPT_DEV_MAJOR == major(st.st_rdev))) {
^
smp_mptctl_io.c:67:31: warning: implicit declaration of function 'minor'; did 
you mean 'mknod'? [-Wimplicit-function-declaration]
 if ((MPT_DEV_MINOR == minor(st.st_rdev)) ||
   ^
...
smp_aac_io.c: In function 'chk_aac_device':
smp_aac_io.c:90:35: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
 if(mknod(dev_name,S_IFCHR,makedev(aacDevMjr,aacDevMnr))) {
   ^~~
smp_aac_io.c:101:53: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 if ((S_ISCHR(st.st_mode)) && (aacDevMjr ==(int) major(st.st_rdev))) {
 ^
smp_aac_io.c:102:33: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
 if ((aacDevMnr == (int) minor(st.st_rdev)))

...
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I ../include 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -W -g -O2 
-ffile-prefix-map=/build/1st/smp-utils-0.98=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o smp_conf_general.o smp_conf_general.c
/bin/bash ../libtool  --tag=CC   --mode=link gcc -I ../include 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -W -g -O2 
-ffile-prefix-map=/build/1st/smp-utils-0.98=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -o smp_conf_general 
smp_conf_general.o ../lib/libsmputils1.la  
libtool: link: gcc -I ../include -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 
-Wall -W -g -O2 -ffile-prefix-map=/build/1st/smp-utils-0.98=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o .libs/smp_conf_general smp_conf_general.o  
../lib/.libs/libsmputils1.so
/usr/bin/ld: ../lib/.libs/libsmputils1.so: undefined reference to `minor'
/usr/bin/ld: ../lib/.libs/libsmputils1.so: undefined reference to `major'
/usr/bin/ld: ../lib/.libs/libsmputils1.so: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:564: smp_conf_general] Error 1

Bug#914160: qcontrol: Job dev-input-by\x2dpath-platform\x2dgpio_keys\x2devent.device/start failed with result 'timeout'

[Ian Campbell]

On Tue, 2018-11-20 at 02:46 +0100, Bernhard Übelacker wrote:
> Package: qcontrol
> Version: 0.5.6-1
> Severity: important

Thank you for your report.

> Therefore I made following change and qcontrol started up
> successfully, as far as I can see:
> root@qnap-119p-ii:~# nano /lib/systemd/system/qcontrold.service
> -Requires=dev-input-by\x2dpath-platform\x2dgpio_keys\x2devent.device
> -After=dev-input-by\x2dpath-platform\x2dgpio_keys\x2devent.device
> +#Requires=dev-input-by\x2dpath-platform\x2dgpio_keys\x2devent.device
> +#After=dev-input-by\x2dpath-platform\x2dgpio_keys\x2devent.device
> 
> root@qnap-119p-ii:~# systemctl daemon-reload
> 
> root@qnap-119p-ii:~# invoke-rc.d qcontrold start

I think what you've done here is remove a (broken) dependency on the
device, which has opened up a race which you happen to be now winning
(i.e. the device happens to be present even though the package is not
longer explicitly waiting for it).

> I assume "dev-input-by\x2dpath-platform\x2dgpio_keys\x2devent.device"
> is just a systemd notation to "/dev/input/by-path/platform-gpio_keys-event",
> like used in /etc/qcontrol.conf ?

Correct.

> This path is a symlink to the actual device file:
> root@qnap-119p-ii:~# ls -lisah 
> /dev/input/by-path/platform-gpio_keys-event /dev/input/event0 
> 5496 0 lrwxrwxrwx 1 root root   9 Nov 20 01:39 
> /dev/input/by-path/platform-gpio_keys-event -> ../event0
> 5311 0 crw-rw 1 root input 13, 64 Nov 20 01:39 /dev/input/event0
> 
> And following this notation waiting directly for the device I assume
> works:
> systemctl start dev-input-event0.device
> 
> But following takes 90 seconds and responds with a failure:
> systemctl start dev-input-by\x2dpath-
> platform\x2dgpio_keys\x2devent.device
> Job for dev-input-byx2dpath-platformx2dgpio_keysx2devent.device
> timed out.
> 
> Some searching mentioned also a possibly missing TAG+="systemd" in the udev 
> rule,
> which made no difference as far as I can say.

What exactly did you try here? I would expect that correctly adding
this tag should have worked (and for this bug to therefore be a
duplicate of #912376).

> Maybe /dev/input/by-path/platform-gpio_keys-event would be still better,
> because that path stays the same after rmmod gpio_keys && modprobe gpio_keys.

Correct, we want to keep using the symlink for this reason, also
because plugging in any input device would cause the numbers to change
as well. Not that there is much cause to plugin e.g. a keyboard or
mouse etc, but you never know...

> But there is still the problem to tell systemd to wait for
> the symlink to the device file.

Indeed. I'm going to (speculatively) merge this with #912376 which I
intend to fix with the upload of 0.5.6-2 very shortly (hopefully today)
since I believe this should fix the issue you are seeing too. If not
then please reopen this bug (or ping me to do so).

Thanks,
Ian.

Bug#914544: xss-lock: Fails to run locker with -n and cycle time 0

[Ian Campbell]

Control: tag -1 +help

Thanks for you report.

On Sat, 2018-11-24 at 18:26 +0200, Teemu Ikonen wrote:
> I think the correct behaviour in the case of cycle time = 0 would be
> to run the notification and locker commands one after the other.

I suppose when cycle time = 0 the XCB_SCREENSAVER_STATE_CYCLE case in
screensaver_event_cb() is never called (only XCB_SCREENSAVER_STATE_ON
is)? Are you able to debug that to confirm which events you are
actually seeing?

The docs say:

   -n cmd, --notifier=cmd
   Run *cmd* when the screen saver activates because of user
   inactivity. Shell-style quoting is supported. The notifier is
   killed when X signals user activity or when the locker is
   started. The locker is started after the first screen saver
   cycle, as set with ``xset s TIMEOUT CYCLE``.

   This can be used to run a countdown or (on laptops) dim the
   screen before locking. For an example, see the script
   *@CMAKE_INSTALL_PREFIX@/share/doc/xss-lock/dim-screen.sh*.

So I believe the correct fix would be to skip the notifier if the cycle
time is zero since "The locker is started after the first screen saver
cycle". In that case a cycle time of 0 would imply to me that the
locker should be started immediately, skipping the notifier. That would
also seem to be implied by the lack of a XCB_SCREENSAVER_STATE_CYCLE
event in this case.

Looking at [0] and all the related interfaces though I don't see how to
spot the case when cycle time is 0 (neither statically nor it changing
dynamically).

Unfortunately upstream seems to have been moribund and I'm not find any
active forks (nor any inactive ones with a relevant looking fix). If
you can come up with a plausible & tested patch I'd be happy to take a
look with a view to applying but I do not have the time to become
upstream for this software.

In the meantime I'm afraid I would take the view that using the -n with
cycle time = 0 (either explicitly or implicitly via something like
xfce4-power-manager messing with it) is not supported, so if you want
to use xfce4-power-manager then you should not use the -n option,
sorry. I suppose I could clarify the documentation on this point.

Ian.

[0] 
https://xcb.freedesktop.org/manual/structxcb__screensaver__notify__event__t.html
 

Bug#904034: Finally got qcontrol working in Stretch

[Ian Campbell]

On Thu, 2018-07-19 at 04:58 +1000, Paul "TBBle" Hampson wrote:
> Just in case this bug report was unexpected, I've gotten a local
> backport build working.

Excellent thanks, sorry for completely missing this bug when you filed
it.

> However, I had to take a couple of extra steps to get it fully
> operational.
> 
> I created /etc/udev/rules.d/70-gpio_keys-for-systemd.rules:
> ACTION=="remove", GOTO="gpio_keys_end"
> SUBSYSTEM=="input", KERNEL=="event*", SUBSYSTEMS=="platform",
> DRIVERS=="gpio-keys", TAG+="systemd"
> LABEL="gpio_keys_end"

This is #912376 which I'm hoping to fix with an upload of 0.5.6-2
today.

Given that I'm planning to hold off on the upload to stretch-backports
until that version makes it into testing/buster.

Ian.

Bug#916021: lintian: Please check for references to build directory

[Dmitry Bogatov]

Package: lintian
Version: 2.5.116
Severity: wishlist

Dear Maintainer,

please add check, that files in binary packages do not refer to build
directory. See (#915511) for example.

I believe the following strings should raise warning:

 /build/{name}
 /build/{name}-{version}
 $PWD

Bug#916023: lintian: Please check if architecture could be "all" instead of "any"

[Dmitry Bogatov]

Package: lintian
Version: 2.5.116
Severity: wishlist

Dear Maintainer,

please add check, that binary package could have "Architecture: all"
instead of "any". See #915976 for example.

I believe checking that none of files in package have ELF magic is quite
reliable.

Bug#916022: python-hug binary-any FTBFS

[Adrian Bunk]

Source: python-hug
Version: 2.4.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=python-hug&suite=sid

...
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.0 /usr/local/share/perl/5.28.0 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 11) line 
1.
BEGIN failed--compilation aborted at (eval 11) line 1.

make: *** [debian/rules:11: clean] Error 2


The binary-any (dpkg-buildpackage -B) build seems to require
packages that are only in Build-Depends-Indep.

Bug#916024: pocl FTBFS: symbol differences

[Adrian Bunk]

Source: pocl
Version: 1.1-7
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/pocl-1.1'
dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libpocl2/DEBIAN/symbols doesn't match 
completely debian/libpocl2.symbols
--- debian/libpocl2.symbols (libpocl2_1.1-7_amd64)
+++ dpkg-gensymbolskKdcOb   2018-12-05 11:31:25.885362758 -1200
@@ -29,7 +29,7 @@
 #MISSING: 0.13-3~llvm3.8# 
_ZN21WorkItemAliasAnalysis5aliasERKN4llvm14MemoryLocationES3_@Base 0.13
  _ZN21WorkItemAliasAnalysis6anchorEv@Base 0.13-3~llvm3.8
  _ZN4llvm11TypeBuilderINS_13_pocl_contextELb1EE12size_t_widthE@Base 0.10
-#MISSING: 0.11# 
(optional=templinst)_ZN4llvm15SmallVectorImplIPN4pocl14ParallelRegionEEaSERKS4_@Base
 0.10
+#MISSING: 1.1-7# 
(optional=templinst)_ZN4llvm15SmallVectorImplIPN4pocl14ParallelRegionEEaSERKS4_@Base
 0.10
  
(optional=templinst)_ZN4llvm15callDefaultCtorI17BreakConstantGEPsEEPNS_4PassEv@Base
 0.10
  
(optional=templinst)_ZN4llvm15callDefaultCtorI21WorkItemAliasAnalysisEEPNS_4PassEv@Base
 0.13
  
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl12LoopBarriersEEEPNS_4PassEv@Base
 0.10
@@ -38,7 +38,7 @@
  
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl14AllocasToEntryEEEPNS_4PassEv@Base
 0.10
  
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl14IsolateRegionsEEEPNS_4PassEv@Base
 0.10
  
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl18RemoveBarrierCallsEEEPNS_4PassEv@Base
 0.14
-#MISSING: 0.14-4~llvm3.9# 
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl19TargetAddressSpacesEEEPNS_4PassEv@Base
 0.10
+#MISSING: 1.1-7# 
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl19TargetAddressSpacesEEEPNS_4PassEv@Base
 0.10
  
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl19WorkitemReplicationEEEPNS_4PassEv@Base
 0.10
  
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl20CanonicalizeBarriersEEEPNS_4PassEv@Base
 0.10
  
(optional=templinst)_ZN4llvm15callDefaultCtorIN4pocl20ImplicitLoopBarriersEEEPNS_4PassEv@Base
 0.10
@@ -268,7 +268,7 @@
  
(optional=templinst)_ZNSt6vectorIPN4llvm10BasicBlockESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
  
(optional=templinst)_ZNSt6vectorIPN4llvm10BasicBlockESaIS2_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS2_S4_EERS7_@Base
 0.10
  
(optional=templinst)_ZNSt6vectorIPN4llvm11InstructionESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
-#MISSING: 0.14-4~llvm3.9# 
(optional=templinst)_ZNSt6vectorIPN4llvm12MemIntrinsicESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
+#MISSING: 1.1-7# 
(optional=templinst)_ZNSt6vectorIPN4llvm12MemIntrinsicESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
  
(optional=templinst)_ZNSt6vectorIPN4llvm4TypeESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base
 1.0
  
(optional=templinst)_ZNSt6vectorIPN4llvm4TypeESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
  
(optional=templinst)_ZNSt6vectorIPN4llvm5ValueESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base
 0.10
@@ -278,13 +278,13 @@
  
(optional=templinst)_ZNSt6vectorIPN4llvm8ConstantESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base
 0.10
  
(optional=templinst)_ZNSt6vectorIPN4llvm8ConstantESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
  
(optional=templinst)_ZNSt6vectorIPN4llvm8FunctionESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.14
-#MISSING: 0.14-4~llvm3.9# 
(optional=templinst)_ZNSt6vectorIPN4llvm8FunctionESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
-#MISSING: 0.14-7~llvm4.0# 
(optional=templinst)_ZNSt7__cxx1110_List_baseISt4pairIPvSt10unique_ptrIN4llvm6detail21AnalysisResultConceptINS4_8FunctionEEESt14default_deleteIS8_EEESaISC_EE8_M_clearEv@Base
 0.13-3~llvm3.8
+#MISSING: 1.1-7# 
(optional=templinst)_ZNSt6vectorIPN4llvm8FunctionESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
+#MISSING: 1.1-7# 
(optional=templinst)_ZNSt7__cxx1110_List_baseISt4pairIPvSt10unique_ptrIN4llvm6detail21AnalysisResultConceptINS4_8FunctionEEESt14default_deleteIS8_EEESaISC_EE8_M_clearEv@Base
 0.13-3~llvm3.8
  
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 1.1-6~llvm6.0+gcc8
  
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base

Bug#916025: rust-cbindgen FTBFS: unresolved import `syn::synom`

[Adrian Bunk]

Source: rust-cbindgen
Version: 0.6.7-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=rust-cbindgen&suite=sid

...
   Compiling cbindgen v0.6.7 (/<>)
 Running `rustc --crate-name cbindgen src/lib.rs --color never --crate-type 
lib --emit=dep-info,link -C debuginfo=2 -C metadata=957c334fa4d9b1e5 -C 
extra-filename=-957c334fa4d9b1e5 --out-dir 
/<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
x86_64-unknown-linux-gnu -C 
incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental 
-L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
dependency=/<>/target/debug/deps --extern 
clap=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libclap-72727f6e266f4efd.rlib
 --extern 
log=/<>/target/x86_64-unknown-linux-gnu/debug/deps/liblog-1db24efd55deb73f.rlib
 --extern 
serde=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libserde-ee27fd985dcf4aeb.rlib
 --extern 
serde_derive=/<>/target/debug/deps/libserde_derive-65443369b791243e.so
 --extern 
serde_json=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libserde_json-3018054f2ce7a8a8.rlib
 --extern 
syn=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libsyn-2ed2a35b5bd90da4.rlib
 --extern 
tempfile=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libtempfile-915e1c7ae4a3fd9f.rlib
 --extern 
toml=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libtoml-44787d338df8c300.rlib
 -C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C 
link-arg=-Wl,-z,relro --remap-path-prefix 
/<>=/usr/share/cargo/registry/cbindgen-0.6.7`
error[E0432]: unresolved import `syn::synom`
  --> src/bindgen/error.rs:10:14
   |
10 | pub use syn::synom::ParseError;
   |  ^ Could not find `synom` in `syn`

error[E0609]: no field `is_sugared_doc` on type `&syn::Attribute`
   --> src/bindgen/ir/cfg.rs:111:21
|
111 | if attr.is_sugared_doc {
| ^^

error[E0609]: no field `is_sugared_doc` on type `&syn::Attribute`
  --> src/bindgen/ir/documentation.rs:39:44
   |
39 | let line = if attr.is_sugared_doc {
   |^^

error[E0609]: no field `is_sugared_doc` on type `&syn::Attribute`
  --> src/bindgen/ir/repr.rs:58:25
   |
58 | if attr.is_sugared_doc || attr.style != 
syn::AttrStyle::Outer {
   | ^^

error[E0609]: no field `is_sugared_doc` on type `&syn::Attribute`
   --> src/bindgen/parser.rs:345:41
|
345 | if attr.is_sugared_doc {
| ^^

error: aborting due to 5 previous errors

Some errors occurred: E0432, E0609.
For more information about an error, try `rustc --explain E0432`.
error: Could not compile `cbindgen`.

Caused by:
  process didn't exit successfully: `rustc --crate-name cbindgen src/lib.rs 
--color never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C 
metadata=957c334fa4d9b1e5 -C extra-filename=-957c334fa4d9b1e5 --out-dir 
/<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
x86_64-unknown-linux-gnu -C 
incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental 
-L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
dependency=/<>/target/debug/deps --extern 
clap=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libclap-72727f6e266f4efd.rlib
 --extern 
log=/<>/target/x86_64-unknown-linux-gnu/debug/deps/liblog-1db24efd55deb73f.rlib
 --extern 
serde=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libserde-ee27fd985dcf4aeb.rlib
 --extern 
serde_derive=/<>/target/debug/deps/libserde_derive-65443369b791243e.so
 --extern 
serde_json=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libserde_json-3018054f2ce7a8a8.rlib
 --extern 
syn=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libsyn-2ed2a35b5bd90da4.rlib
 --extern 
tempfile=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libtempfile-915e1c7ae4a3fd9f.rlib
 --extern 
toml=/<>/target/x86_64-unknown-linux-gnu/debug/deps/libtoml-44787d338df8c300.rlib
 -C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C 
link-arg=-Wl,-z,relro --remap-path-prefix 
/<>=/usr/share/cargo/registry/cbindgen-0.6.7` (exit code: 1)
debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j4', 
'--target', 'x86_64-unknown-linux-gnu'],) {}
dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101
make: *** [debian/rules:3: build-arch] Error 25

Bug#916026: bootchart2 FTBFS with glibc 2.28

[Adrian Bunk]

Source: bootchart2
Version: 0.14.4-3
Severity: serious
Tags: ftbfs buster sid

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

...
collector/collector.c: In function 'enter_environment':
collector/collector.c:633:47: warning: implicit declaration of function 
'makedev' [-Wimplicit-function-declaration]
  if (mknod (TMPFS_PATH "/kmsg", S_IFCHR|0666, makedev(1, 11)) < 0) {
   ^~~
...
cc -g -Wall -O0  -pthread -Icollector -o bootchart-collector 
collector/collector.o collector/output.o collector/tasks.o 
collector/tasks-netlink.o collector/dump.o
/usr/bin/ld: collector/collector.o: in function `enter_environment':
/build/1st/bootchart2-0.14.4/collector/collector.c:633: undefined reference to 
`makedev'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:39: bootchart-collector] Error 1

Bug#916027: cfengine3 FTBFS with glibc 2.28

[Adrian Bunk]

Source: cfengine3
Version: 3.10.2-4
Severity: serious
Tags: ftbfs

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

...
evalfunction.c: In function 'FnCallFileStatDetails':
evalfunction.c:3929:60: error: implicit declaration of function 'minor'; did 
you mean 'mknod'? [-Werror=implicit-function-declaration]
 snprintf(buffer, CF_MAXVARSIZE, "%ju", (uintmax_t) 
minor(statbuf.st_dev) );
^
mknod
evalfunction.c:3937:60: error: implicit declaration of function 'major' 
[-Werror=implicit-function-declaration]
 snprintf(buffer, CF_MAXVARSIZE, "%ju", (uintmax_t) 
major(statbuf.st_dev) );
^

Bug#601718: Fixed

[Xavier]

Control: tags -1 + pending

Hello,

the following code shows that bug is fixed at least with version ≥ 4.

  use JSON;
  $obj1 = {
a => 1,
b => {
  c => 32
}
  };
  $ex = '{"a":"1","b":{"c":"32"}}';
  my $obj2 = decode_json($ex);
  my $dump1 = encode_json($obj1);
  my $dump2 = encode_json($obj2);
  use Data::Dumper;
  print Dumper($dump1,$dump2);

Result:

  $VAR1 = '{"b":{"c":32},"a":1}';
  $VAR2 = '{"a":"1","b":{"c":"32"}}';

Cheers,
Xavier

Bug#909406: [regression] GCC-8 failed to compile Julia on armhf while GCC-7 worked.

[Matthias Klose]

On 23.09.18 06:18, Mo Zhou wrote:
> Package: gcc-8
> Version: 8.2.0-7
> Severity: important
> 
> This happend on our buildd and Ubuntu buildfarm, and I reproduced it in my
> qemu-armhf chroot:
> 
>   qemu: Unsupported syscall: 385
>   Invalid Thumb instruction at 0xff5ef780: 0xee4c, 0x000e
>   
>   signal (4): Illegal instruction
>   in expression starting at no file:0
>   unknown function (ip: 0xff5ef77f)
>   true_main at ./ui/./ui/repl.c:103
>   main at ./ui/./ui/repl.c:233
>   __libc_start_main at /lib/arm-linux-gnueabihf/libc.so.6 (unknown line)
>   _start at /home/lumin/packages/julia.pkg/julia/usr/bin/julia (unknown line)
>   Allocations: 36838 (Pool: 36838; Big: 0); GC: 0
>   qemu: uncaught target signal 4 (Illegal instruction) - core dumped
>   Illegal instruction
> 
> Source to reproduce:
>   https://salsa.debian.org/julia-team/julia
>   - tag: debian/1.0.0-3
> 
> In order to reproduce the armhf build failure, just revert this commit
> https://salsa.debian.org/julia-team/julia/commit/b89c05c87f27d23513cb3f90cd534f775daea289

please can you recheck with 8.2.0-11 or -12? Also could you recheck on the armhf
porter boxes once these gcc versions are installable?

Bug#916013: atop FTBFS with glibc 2.28

[Marc Haber]

On Sun, Dec 09, 2018 at 02:12:53PM +0200, Adrian Bunk wrote:
> photosyst.c: In function 'lvmmapname':
> photosyst.c:1465:19: error: called object 'major' is not a function or 
> function pointer
>  dmp->major  = major(statbuf.st_rdev);
>^
> photosyst.c:1420:25: note: declared here
>  lvmmapname(unsigned int major, unsigned int minor,
> ~^
> photosyst.c:1466:19: error: called object 'minor' is not a function or 
> function pointer
>  dmp->minor  = minor(statbuf.st_rdev);
>^

This is upstream issue #37, fixed upstream. Waiting for a new release,
will upload a locally patched package if upstream doesn't release in
time. For the mean time, I can confirm that a git checkout compiles fine
in Debian unstable.

Greetings
Marc

Bug#916028: cltl: solving some upgrade issues

[Andreas Beckmann]

Package: cltl
Version: 1.0.29
Severity: important
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

attached you can find a patch to fix some upgrading issues (upgrading
from the 1.0.26 in wheezy to buster) that I noticed while running
piuparts on contrib locally.

  * preinst: Disable buggy postrm code on upgrades from (<< 1.0.27) that would
delete files from the newly unpacked package.  (Cf. #700670)
  * Clean up the obsolete conffile /etc/emacs/site-start.d/60cltl.el on
upgrade.
  * Use /var/cache/cltl as download location.


Andreas
diff -Nru cltl-1.0.29/debian/changelog cltl-1.0.30/debian/changelog
--- cltl-1.0.29/debian/changelog2018-04-14 10:15:35.0 +0200
+++ cltl-1.0.30/debian/changelog2018-12-08 23:59:44.0 +0100
@@ -1,3 +1,14 @@
+cltl (1.0.30) UNRELEASED; urgency=medium
+
+  [ Andreas Beckmann ]
+  * preinst: Disable buggy postrm code on upgrades from (<< 1.0.27) that would
+delete files from the newly unpacked package.  (Cf. #700670)
+  * Clean up the obsolete conffile /etc/emacs/site-start.d/60cltl.el on
+upgrade.
+  * Use /var/cache/cltl as download location.
+
+ -- Andreas Beckmann   Sat, 08 Dec 2018 23:59:44 +0100
+
 cltl (1.0.29) unstable; urgency=medium
 
   * Team upload.
diff -Nru cltl-1.0.29/debian/cltl.maintscript 
cltl-1.0.30/debian/cltl.maintscript
--- cltl-1.0.29/debian/cltl.maintscript 1970-01-01 01:00:00.0 +0100
+++ cltl-1.0.30/debian/cltl.maintscript 2018-12-08 23:59:44.0 +0100
@@ -0,0 +1 @@
+rm_conffile /etc/emacs/site-start.d/60cltl.el 1.0.30~
diff -Nru cltl-1.0.29/debian/postinst cltl-1.0.30/debian/postinst
--- cltl-1.0.29/debian/postinst 2018-04-14 10:03:54.0 +0200
+++ cltl-1.0.30/debian/postinst 2018-12-08 23:59:44.0 +0100
@@ -23,7 +23,7 @@
 
 INDEX=/usr/share/doc/cltl/cltl2.html
 
URL=http://www-2.cs.cmu.edu/afs/cs.cmu.edu/project/ai-repository/ai/lang/lisp/doc/cltl/cltl_ht.tgz
-FILE_DIR=/root/tmp
+FILE_DIR=/var/cache/cltl
 FILE=${FILE_DIR}/cltl_ht.tgz
 DOCDIR=/usr/share/doc/cltl
 
diff -Nru cltl-1.0.29/debian/postrm cltl-1.0.30/debian/postrm
--- cltl-1.0.29/debian/postrm   1970-01-01 01:00:00.0 +0100
+++ cltl-1.0.30/debian/postrm   2018-12-08 23:59:44.0 +0100
@@ -0,0 +1,9 @@
+#!/bin/sh
+set -e
+
+if [ "$1" = "purge" ];
+then
+   rm -rf /var/cache/cltl
+fi
+
+#DEBHELPER#
diff -Nru cltl-1.0.29/debian/preinst cltl-1.0.30/debian/preinst
--- cltl-1.0.29/debian/preinst  1970-01-01 01:00:00.0 +0100
+++ cltl-1.0.30/debian/preinst  2018-12-08 23:59:44.0 +0100
@@ -0,0 +1,14 @@
+#!/bin/sh
+set -e
+
+# work around "#700670 - 'old-postrm upgrade' removes /usr/share/doc/cltl/*
+#   after the new package was unpacked"
+# by disabling the offending line
+if dpkg --compare-versions "$2" lt-nl "1.0.27" ; then
+   if [ -f /var/lib/dpkg/info/cltl.postrm ]; then
+   echo "Disabling buggy code in old postrm script..."
+   sed -ir '8{\%^rm -rf /usr/share/doc/cltl/\*\s*$%{s/^/#/}}' 
/var/lib/dpkg/info/cltl.postrm
+   fi
+fi
+
+#DEBHELPER#

Bug#916029: RM: pycra -- RoQA, unmaintained, dead-upstream

[Tobias Frost]

Package: src:pycra
Severity: serious

Dear maintainer,

pycra seems to be unmaintained with the last upload 10 (!) years ago,
despite it has several bugs reported against it. Additionally, upstream
disappeared and there seems to be better alternatives available.

In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600782#28 the
upstream author indicates 2010 that "At the moment I'm not even using
pyCA myself anymore.", indicating the dead-upstream thing. (the
reference in the mail is no longer there, the domain has been grabbed
by some domain grabber and now has advertisiment for gambling)

There are no r-depends on the pacakge and popcon is low.

This makes me wonder if we should retire this package.

If you don't think so, just close this bug.

If you also think so, just reassign it to the ftp.debian.org pseudo
package.

If there is no answer, I will reassing the bug in exactly 3 months.

Thanks!

tobi



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

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

Bug#897760: gltron: ftbfs with GCC-8

[Markus Koschany]

Control: tags -1 pending patch

Dear maintainer,

I've uploaded a new revision of gltron versioned as 0.70final-12.2. I
think it is best to remove the -Werror flag which treats warnings as
errors and causes a FTBFS whenever GCC becomes more strict. Unless there
is someone who fixes those warnings, it is simpler to ignore them for
now. Please find attached the debdiff.

Regards,

Markus
diff -Nru gltron-0.70final/debian/changelog gltron-0.70final/debian/changelog
--- gltron-0.70final/debian/changelog   2015-07-09 13:53:25.0 +0200
+++ gltron-0.70final/debian/changelog   2018-12-09 14:32:28.0 +0100
@@ -1,3 +1,11 @@
+gltron (0.70final-12.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add no-Werror.patch and do not treat warnings as errors anymore.
+(Closes: #897760)
+
+ -- Markus Koschany   Sun, 09 Dec 2018 14:32:28 +0100
+
 gltron (0.70final-12.1) unstable; urgency=medium
 
   * Non maintainer upload.
diff -Nru gltron-0.70final/debian/patches/no-Werror.patch 
gltron-0.70final/debian/patches/no-Werror.patch
--- gltron-0.70final/debian/patches/no-Werror.patch 1970-01-01 
01:00:00.0 +0100
+++ gltron-0.70final/debian/patches/no-Werror.patch 2018-12-09 
14:32:28.0 +0100
@@ -0,0 +1,27 @@
+From: Markus Koschany 
+Date: Sun, 9 Dec 2018 14:30:34 +0100
+Subject: no Werror
+
+Remove -Werror flag and do not treat warnings as errors anymore. This is a
+useful development flag but will cause a FTBFS whenever GCC becomes more
+strict.
+
+Bug-Debian: https://bugs.debian.org/897760
+Forwarded: no
+---
+ configure.in | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.in b/configure.in
+index 86af0cb..82e5a4e 100644
+--- a/configure.in
 b/configure.in
+@@ -23,7 +23,7 @@ AC_ARG_ENABLE(warn,
+ AC_HELP_STRING([--enable-warn],[Enable compiler warnings @<:@default=on@:>@]),
+   enable_warn=$enableval, enable_warn=yes)
+ if test "x$enable_warn" = xyes; then
+-  CFLAGS="$CFLAGS -Wall -Werror"
++  CFLAGS="$CFLAGS -Wall"
+ fi
+ 
+ AC_ARG_ENABLE(debug,
diff -Nru gltron-0.70final/debian/patches/series 
gltron-0.70final/debian/patches/series
--- gltron-0.70final/debian/patches/series  2015-07-09 13:44:40.0 
+0200
+++ gltron-0.70final/debian/patches/series  2018-12-09 14:32:28.0 
+0100
@@ -9,3 +9,4 @@
 fix-prototypes.patch
 automake-error.patch
 gcc5.diff
+no-Werror.patch


signature.asc
Description: OpenPGP digital signature

Bug#916030: moria: FTBFS on mips64el

[Markus Koschany]

Package: moria
Version: 5.7.10+20181022-1
Severity: serious

Dear maintainer,

moria fails to build from source on mips64el. This prevents the
package migration to testing. According to the build log the error is
caused by

src/ui_io.cpp:521:31: error: cast from 'int*' to 'fd_set*' increases required 
alignment of target type [-Werror=cast-align]

Another way to work around this problem is to remove the -Werror flag
which is useful for development but causes FTBFS whenever GCC becomes
more strict.

Regards,

Markus

Bug#916011: Blank dialog — Can't locate object method "vbox" via package "Gtk3::Dialog"

[martin f krafft]

Turns out there was an old session, and once I removed that, the
problem went away. I have not been able to reproduce this using
another crashed session.

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#916031: Runs unpaper multiple times unnecessarily

[martin f krafft]

Package: gscan2pdf
Version: 2.2.1-1
Severity: normal

After a scan of 44 pages, gscan2pdf has been running unpaper across
all of them multiple times. At the bottom of the screen, I am told

  "Process 83 of 125 (unpaper)"

and when the next page loads, *both* numbers are incremented:

  "Process 84 of 126 (unpaper)"

Once the last page is reached, it starts again from the beginning,
except with page 2 the second time, and page 3 the third time, and
then it appears to have completed

And in fact, if I scan just 4 pages, unpaper is run 4+3+2 times.
I've attached the debug log of this session.

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

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

Versions of packages gscan2pdf depends on:
ii  imagemagick8:6.9.10.14+dfsg-7
ii  imagemagick-6.q16 [imagemagick]8:6.9.10.14+dfsg-7
ii  libconfig-general-perl 2.63-1
ii  libdate-calc-perl  6.4-1
ii  libfilesys-df-perl 0.92-6+b4
ii  libgoocanvas2-perl 0.06-1
ii  libgtk3-perl   0.034-2
ii  libgtk3-simplelist-perl0.17-2
ii  libhtml-parser-perl3.72-3+b3
ii  libimage-magick-perl   8:6.9.10.14+dfsg-7
ii  libimage-sane-perl 0.14-1+b3
ii  liblist-moreutils-perl 0.416-1+b4
ii  liblocale-gettext-perl 1.07-3+b4
ii  liblog-log4perl-perl   1.49-1
ii  libossp-uuid-perl [libdata-uuid-perl]  1.6.2-1.5+b7
ii  libpdf-api2-perl   2.033-1
ii  libproc-processtable-perl  0.55-1+b1
ii  libreadonly-perl   2.050-1
ii  librsvg2-common2.44.9-1
ii  libset-intspan-perl1.19-1
ii  libtiff-tools  4.0.10-3
ii  libtry-tiny-perl   0.30-1
ii  sane-utils 1.0.27-3.1

Versions of packages gscan2pdf recommends:
ii  djvulibre-bin  3.5.27.1-10
ii  sane   1.0.14-13+b1
ii  tesseract-ocr  4.0.0-1+b1
ii  unpaper6.1-2+b2
ii  xdg-utils  1.1.3-1

gscan2pdf suggests no packages.

-- no debconf information

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


gscan2pdf.debuglog.xz
Description: application/xz


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#916033: alex4 FTBFS with allegro4.4 2:4.4.2-13

[Adrian Bunk]

Source: alex4
Version: 1.1-7
Severity: serious
Tags: ftbfs buster sid

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

...
shooter.c: In function 's_update_object':
shooter.c:503:26: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
  ^~~~
  fixmul
shooter.c:503:46: warning: implicit declaration of function 'fsin'; did you 
mean 'fixsin'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
  ^~~~
  fixsin
shooter.c:508:46: warning: implicit declaration of function 'fcos'; did you 
mean 'feof'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fcos(itofix(o->t;
  ^~~~
  feof
main.c: In function 'draw_custom_ending':
main.c:1215:23: warning: implicit declaration of function 'fcos'; did you mean 
'feof'? [-Wimplicit-function-declaration]
  r = 70 + fixtoi(20 * fcos(itofix(game_count >> 1)) + 20 * 
fsin(itofix((int)(game_count / 2.7))) );
   ^~~~
   feof
main.c:1215:60: warning: implicit declaration of function 'fsin'; did you mean 
'fixsin'? [-Wimplicit-function-declaration]
  r = 70 + fixtoi(20 * fcos(itofix(game_count >> 1)) + 20 * 
fsin(itofix((int)(game_count / 2.7))) );
^~~~
fixsin
...
cc -Wl,-z,relro -Wl,-z,now -o alex4 actor.o edit.o map.o player.o shooter.o 
unix.o bullet.o hisc.o options.o script.o timer.o control.o main.o particle.o 
scroller.o token.o -laldmb -ldumb `allegro-config --libs`
/usr/bin/ld: shooter.o: undefined reference to symbol 'fmul@@GLIBC_2.28'
/usr/bin/ld: //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:12: alex4] Error 1

Bug#916035: kraptor FTBFS with allegro4.4 2:4.4.2-13

[Adrian Bunk]

Source: kraptor
Version: 0.0.20040403+ds-1
Severity: serious
Tags: ftbfs

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

...
src/explos.c: In function 'dibujar_explosion':
src/explos.c:129:20: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
   x2 -= fixtoi(fmul(itofix(tmp->spr->w), tmp->r))/2;
^~~~
...
src/enemigo.c: In function 'agregar_disparo_ene':
src/enemigo.c:498:24: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
nueva->dy = fmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 
3)) );
^~~~
...
gcc obj/linux/azar.o obj/linux/bomba.o obj/linux/captura.o obj/linux/cinema.o 
obj/linux/clima.o obj/linux/combo.o obj/linux/config.o obj/linux/data.o 
obj/linux/datafind.o obj/linux/enemigo.o obj/linux/error.o obj/linux/explos.o 
obj/linux/filedata.o obj/linux/game.o obj/linux/global.o obj/linux/guiprocs.o 
obj/linux/guitrans.o obj/linux/humo.o obj/linux/ia.o obj/linux/joymnu.o 
obj/linux/jugador.o obj/linux/kfbuffer.o obj/linux/krstring.o obj/linux/main.o 
obj/linux/mapa.o obj/linux/menu.o obj/linux/partic.o obj/linux/pmask.o 
obj/linux/premio.o obj/linux/rvideo.o obj/linux/savedlg.o obj/linux/shopping.o 
obj/linux/sombras.o obj/linux/sonido.o obj/linux/wordwrap.o -o 
bin/kraptor_linux.bin -laldmb -ldumb `allegro-config --libs` `dpkg-buildflags 
--get LDFLAGS`
/usr/bin/ld: obj/linux/enemigo.o: undefined reference to symbol 
'fmul@@GLIBC_2.28'
/usr/bin/ld: //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status

Bug#905254: Status of libphp-phpmailer

[Chris Lamb]

Chris Lamb wrote:

> >   However, the git does not seem to have been moved to salsa.
> 
> I fixed a number of CVEs recently and I would love to push my changes
> to suitable branches. Can the PEAR maintainers please migrate this
> repo ASAP?

Gentle ping on this folks? :)



Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb 🍥 Debian Project Leader (2017—)
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#916034: sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64

[Andreas Beckmann]

Package: sl-modem-dkms
Version: 2.9.11~20110321-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 2.9.11~20110321-12

Hi,

sl-modem-dkms fails to build a module for 4.18.0-3-amd64 and 4.9.0-8-amd64

Selecting previously unselected package sl-modem-dkms.
(Reading database ... 33401 files and directories currently installed.)
Preparing to unpack .../sl-modem-dkms_2.9.11~20110321-13_amd64.deb ...
Unpacking sl-modem-dkms (2.9.11~20110321-13) ...
Setting up sl-modem-dkms (2.9.11~20110321-13) ...
Loading new sl-modem-2.9.11~20110321 DKMS files...
grep: /lib/modules/4.9.0-6-amd64/build/.config: No such file or directory
It is likely that 4.9.0-6-amd64 belongs to a chroot's host
Building for 4.18.0-3-amd64
Building initial module for 4.18.0-3-amd64
Error!  Build of slusb.ko failed for: 4.18.0-3-amd64 (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ for more information.
dpkg: error processing package sl-modem-dkms (--configure):
 installed sl-modem-dkms package post-installation script subprocess returned 
error exit status 7
Errors were encountered while processing:
 sl-modem-dkms

# cat /var/lib/dkms/sl-modem/2.9.11~20110321/build/make.log 
DKMS make.log for sl-modem-2.9.11~20110321 for kernel 4.18.0-3-amd64 (x86_64)
Sun Dec  9 13:53:21 UTC 2018
make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
doing %.o: %.c
cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB 
`test -f /lib/modules/4.18.0-3-amd64/build/include/linux/modversions.h && echo 
-DMODVERSIONS --include 
/lib/modules/4.18.0-3-amd64/build/include/linux/modversions.h 
-I/lib/modules/4.18.0-3-amd64/build/include`  -I. -I./../modem   -o 
old_st7554.o -c old_st7554.c
old_st7554.c:49:10: fatal error: linux/init.h: No such file or directory
 #include 
  ^~
compilation terminated.
make: *** [Makefile:129: old_st7554.o] Error 1
make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
make: Entering directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'
make modules -C /lib/modules/4.18.0-3-amd64/build 
SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem
make[1]: Entering directory '/usr/src/linux-headers-4.18.0-3-amd64'
  CC [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.mod.o
  LD [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.18.0-3-amd64'
make: Leaving directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'

# cat /var/lib/dkms/sl-modem/2.9.11~20110321/build/make.log 
DKMS make.log for sl-modem-2.9.11~20110321 for kernel 4.9.0-8-amd64 (x86_64)
Sun Dec  9 14:02:25 UTC 2018
make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
doing %.o: %.c
cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB 
`test -f /lib/modules/4.9.0-8-amd64/build/include/linux/modversions.h && echo 
-DMODVERSIONS --include 
/lib/modules/4.9.0-8-amd64/build/include/linux/modversions.h 
-I/lib/modules/4.9.0-8-amd64/build/include`  -I. -I./../modem   -o old_st7554.o 
-c old_st7554.c
old_st7554.c:48:26: fatal error: linux/module.h: No such file or directory
 #include 
  ^
compilation terminated.
Makefile:128: recipe for target 'old_st7554.o' failed
make: *** [old_st7554.o] Error 1
make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
make: Entering directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'
make modules -C /lib/modules/4.9.0-8-amd64/build 
SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem
make[1]: Entering directory '/usr/src/linux-headers-4.9.0-8-amd64'
  CC [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.mod.o
  LD [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.9.0-8-amd64'
make: Leaving directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'


Andreas

Bug#915954: inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)

[Benoît Sibaud]

Hi,

same issue here. Deterministic (always fails at boot with -3, and works with 
-2).

below, kernel log of 4.18.0-2 and 4.18.0-3 (with something wrong in 
i915_request_alloc)

kernel log of 4.18.0-2 (the WORKING one) follows:

[0.00] Linux version 4.18.0-2-amd64 (debian-ker...@lists.debian.org) 
(gcc version 7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.10-2 (2018-11-02)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-2-amd64 
root=/dev/mapper/anthra-root ro
[0.00] Disabled fast string operations
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e4000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xaf78] usable
[0.00] BIOS-e820: [mem 0xaf79-0xaf79dfff] ACPI data
[0.00] BIOS-e820: [mem 0xaf79e000-0xaf7d] ACPI NVS
[0.00] BIOS-e820: [mem 0xaf7e-0xaf7f] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xffb0-0x] reserved
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.4 present.
[0.00] DMI: System manufacturer System Product Name/P5B-VM, BIOS 0901   
 07/03/2007
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] last_pfn = 0xaf790 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-D uncachable
[0.00]   E-E write-through
[0.00]   F-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0BC00 mask FFC00 uncachable
[0.00]   1 base 0C000 mask FC000 uncachable
[0.00]   2 base 0 mask F write-back
[0.00]   3 base 1 mask F8000 write-back
[0.00]   4 base 0AF80 mask FFF80 uncachable
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.00] e820: update [mem 0xaf80-0xafff] usable ==> reserved
[0.00] e820: update [mem 0xbc00-0x] usable ==> reserved
[0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at 
[(ptrval)]
[0.00] Base memory trampoline at [(ptrval)] 99000 size 24576
[0.00] BRK [0x5344b000, 0x5344bfff] PGTABLE
[0.00] BRK [0x5344c000, 0x5344cfff] PGTABLE
[0.00] BRK [0x5344d000, 0x5344dfff] PGTABLE
[0.00] BRK [0x5344e000, 0x5344efff] PGTABLE
[0.00] BRK [0x5344f000, 0x5344] PGTABLE
[0.00] BRK [0x5345, 0x53450fff] PGTABLE
[0.00] RAMDISK: [mem 0x34e27000-0x3670afff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000FA950 24 (v02 ACPIAM)
[0.00] ACPI: XSDT 0xAF790100 54 (v01 MSTEST OEMXSDT  
07000703 MSFT 0097)
[0.00] ACPI: FACP 0xAF790290 F4 (v03 MSTEST OEMFACP  
07000703 MSFT 0097)
[0.00] ACPI: DSDT 0xAF7905C0 007C09 (v01 A0518  A0518000 
 INTL 20060113)
[0.00] ACPI: FACS 0xAF79E000 40
[0.00] ACPI: FACS 0xAF79E000 40
[0.00] ACPI: APIC 0xAF790390 6C (v01 MSTEST OEMAPIC  
07000703 MSFT 0097)
[0.00] ACPI: MCFG 0xAF790400 3C (v01 MSTEST OEMMCFG  
07000703 MSFT 0097)
[0.00] ACPI: OEMB 0xAF79E040 7B (v01 MSTEST AMI_OEM  
07000703 MSFT 0097)
[0.00] ACPI: HPET 0xAF7981D0 38 (v01 MSTEST OEMHPET  
07000703 MSFT 0097)
[0.00] ACPI: GSCI 0xAF79E0C0 002024 (v01 MSTEST GMCHSCI  
07000703 MSFT 0097)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] No NUMA configuration found
[0.00] Faking a node at [mem 0x-0xaf78]
[0.00] NODE_DATA(0) allocated [mem 0xaf78b000-0xaf78]
[0.00] tsc: Fast TSC calibration using PIT
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x1000-0x00ff]
[0.00]   DMA32[mem 0x0100-0xaf78]
[0.00]   Normal   empty
[0.00]   Device   empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x1000-0x0009efff]
[0.00]   node   0: [mem 0x0010-0xaf78]
[0.00] Reserved but unavailable: 2258 pages
[0.00] Initm

Bug#916032: RFA: caffe-contrib -- Fast, open framework for Deep Learning

[Mo Zhou]

Package: wnpp
Severity: normal

See #915186

Bug#916037: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Adrian Bunk]

Source: liquidwar
Version: 5.6.4-5
Severity: serious
Tags: ftbfs buster sid

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

...
distor.c: In function 'create_wave_line':
distor.c:197:15: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
   cycle_tmp = fsqrt (fsqrt (cycle_tmp)) / 2;
   ^
   fixsqrt
distor.c:206:8: warning: implicit declaration of function 'fsin'; did you mean 
'fixsin'? [-Wimplicit-function-declaration]
   f0 = fsin (cycle_coef + freq_coef * period2);
^~~~
fixsin
distor.c:207:22: warning: implicit declaration of function 'fcos'; did you mean 
'fixcos'? [-Wimplicit-function-declaration]
   fp0x0 = (PI_1024 * fcos (cycle_coef + freq_coef * period2)) / 1024;
  ^~~~
...
fighter.c: In function 'move_fighters':
fighter.c:338:6: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
  fsqrt (fsqrt (1 << (LW_CONFIG_CURRENT_RULES.fighter_attack
  ^
...
palette.c: In function 'sqrt255':
palette.c:91:12: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
   result = fsqrt (i * 256) / 256;
^
...
Linking liquidwar (target=default, debug=no, static=no, asm=no)
/usr/bin/ld: random.o: in function `lw_random_generate_map':
random.c:(.text+0x34): warning: the use of `tmpnam' is dangerous, better use 
`mkstemp'
/usr/bin/ld: distor.o: in function `create_wave_line.constprop.0':
distor.c:(.text+0xc6): undefined reference to `fsqrt'
/usr/bin/ld: distor.c:(.text+0xcf): undefined reference to `fsqrt'
/usr/bin/ld: distor.c:(.text+0x130): undefined reference to `fsin'
/usr/bin/ld: distor.c:(.text+0x13e): undefined reference to `fcos'
/usr/bin/ld: distor.c:(.text+0x24e): undefined reference to `fcos'
/usr/bin/ld: fighter.o: in function `move_fighters':
fighter.c:(.text+0x46d): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x476): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x4a5): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x4ae): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x554): undefined reference to `fsqrt'
/usr/bin/ld: fighter.o:fighter.c:(.text+0x55d): more undefined references to 
`fsqrt' follow
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:245: liquidwar] Error 1

Bug#916036: gnome-software: Bump the Suggest on fwupd to a Recommend?

[Paul van Tilburg]

Package: gnome-software
Version: 3.30.5-1
Severity: wishlist

Dear GNOME team,

Now that LVFS has matured over the last year (both programming as well as
support wise), I wonder if it is possible or time to bump the Suggest on
fwupd to a Recommend?  Are there any points in favour of against this? 
Or is this never likely to happen?

Over the year, I have had to explain to people to install this manually
when they wondered how I got this nice BIOS software updates and
integration in the GNOME desktop.  Another point in favour would be that
people will have not forget their important security updates fixed in their
laptops.

Kind regards,
Paul


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

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

Versions of packages gnome-software depends on:
ii  appstream0.12.3-1
ii  apt-config-icons 0.12.3-1
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-1
ii  gnome-software-common3.30.5-1
ii  gsettings-desktop-schemas3.28.1-1
ii  libappstream-glib8   0.7.12-1
ii  libatk1.0-0  2.30.0-1
ii  libc62.27-8
ii  libcairo21.16.0-1
ii  libfwupd21.1.4-1
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libglib2.0-0 2.58.1-2
ii  libgnome-desktop-3-173.30.2-1
ii  libgspell-1-11.6.1-1
ii  libgtk-3-0   3.24.1-2
ii  libgtk3-perl 0.034-2
ii  libgudev-1.0-0   232-2
ii  libjson-glib-1.0-0   1.4.4-1
ii  libpackagekit-glib2-18   1.1.11-1
ii  libpolkit-gobject-1-00.105-22
ii  libsecret-1-00.18.6-3
ii  libsoup2.4-1 2.64.1-3
ii  packagekit   1.1.11-1
ii  software-properties-gtk  0.96.20.2-1

gnome-software recommends no packages.

Versions of packages gnome-software suggests:
pn  apt-config-icons-hidpi 
ii  fwupd  1.1.4-1
ii  gnome-software-plugin-flatpak  3.30.5-1
pn  gnome-software-plugin-snap 

-- no debconf information

Bug#915423: xfce4-session: reproducible build (usrmerge): embeds path of rm found via PATH

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, 2018-12-03 at 20:02 +0100, Ansgar Burchardt wrote:
> Source: xfce4-session
> Version: 4.12.1-6
> Severity: normal
> Tags: patch
> User: m...@linux.it
> Usertags: usrmerge
> Control: user reproducible-bui...@lists.alioth.debian.org
> Control: usertag -1 + environment
> 
> Dear Maintainer,
> 
> According to reproducible build tests xfce4-session gets built
> differently on a merged-usr system vs a non-merged system.
> 
> The package embeds the full path of rm. Since PATH defaults to
> /usr/bin before /bin, the first will be used on a usrmerged system
> where they're both essentially the same thing, but /usr/bin/rm does
> not exist on non-merged systems.
> 
> The attached patch passes `RM=/bin/rm` to explicitly set the path.

Hi,

I didn't follow recent discussions on usrmerge, but are we sure explicitly
adding snippets like this to every relevant package is the right way to fix
that? It looks a bit hacky to me (also couldn't that be done in debhelper or
something?).

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlwNIswACgkQ3rYcyPpX
RFsi2AgA35yWi7pUVlmyDz18S+2bvZkVd5yojUko+U2UKrODkThR67iC3bAQJPUf
hXgvMPtSyoHrFPuaQYexWuhU5Hobn3D7P6mrAxwYVLjfsdTbbyYdvtEtfI2RIj6Q
DvXvRtFOjm1QRB3nKugDj8FQRZt54Uu+K6ovreiUs86ZZ0TH3vSUh516dlUZns59
cr/FC9pTJDQxUqZ7VhbUWkUoN/bxLYqIPAhgLwpkCBLcBKnzmiCNxgHLceU56odF
3gAVM9xqNVJ2/Vo5gbbjlTaQBF+Eg8tozEIjxSxCgvJWWYq5t8ralfYSKKG2Bwx0
geTiA1Rj9n5tuaYIQwbjms8J2xoyJA==
=GRJS
-END PGP SIGNATURE-

Bug#916026: bootchart2 FTBFS with glibc 2.28

[Riccardo Magliocchetti]

Il 09/12/18 14:10, Adrian Bunk ha scritto:

Source: bootchart2
Version: 0.14.4-3
Severity: serious
Tags: ftbfs buster sid

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

...
collector/collector.c: In function 'enter_environment':
collector/collector.c:633:47: warning: implicit declaration of function 
'makedev' [-Wimplicit-function-declaration]
   if (mknod (TMPFS_PATH "/kmsg", S_IFCHR|0666, makedev(1, 11)) < 0) {
^~~
...
cc -g -Wall -O0  -pthread -Icollector -o bootchart-collector 
collector/collector.o collector/output.o collector/tasks.o 
collector/tasks-netlink.o collector/dump.o
/usr/bin/ld: collector/collector.o: in function `enter_environment':
/build/1st/bootchart2-0.14.4/collector/collector.c:633: undefined reference to 
`makedev'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:39: bootchart-collector] Error 1



This has already been fixed upstream here:

commit add58c3b57064afd6f7d2fd5f09006d28a3e770e
Author: Mike Frysinger 
Date:   Thu Apr 21 00:19:32 2016 -0400

include sys/sysmacros.h for major/minor/makedev

These funcs are defined in the sys/sysmacros.h header, not sys/types.h.
Linux C libraries are updating to drop the implicit include, so we need
to include it explicitly.

diff --git a/collector/collector.c b/collector/collector.c
index cfdcb26..2f3ce6b 100644
--- a/collector/collector.c
+++ b/collector/collector.c
@@ -33,6 +33,7 @@
 #include "common.h"

 #include 
+#include 
 #include 
 #include 
 #include 


--
Riccardo Magliocchetti
@rmistaken

http://menodizero.it

Bug#915017: Different shown keybindings in full nano and nano-udeb

[Benno Schulenberg]

Hi Steve,

Op 04-12-18 om 03:03 schreef Steve McIntyre:
> I'm seeing this difference in the two help lines at the bottom.  [...]

Okay: the udeb version shows "^S Save" and "^Q Where Was" at the end
of the two help lines.

First, how realistic or probable is it that nowadays someone would
install Debian while connected with a terminal over a serial line?

Second, is it possible to detect that the current terminal is using
a real serial line?  If yes, then nano could suppress the showing of
^S and ^Q in that case.

> The script debian/rules is responsible for building three different
> versions from a single source tree:
> 
>   https://salsa.debian.org/debian/nano/blob/master/debian/rules

If I understand the rules script well, a udeb version is identical
to a tiny version (also in the installation part, they just remove
all documentation in a different way).

>   CONFFLAGS_tiny = \
>--enable-tiny \
>--disable-speller \
>--disable-justify \
>--disable-tabcomp \
>--disable-nls \
>--disable-wrapping \
>--with-slang
> 
> Hmmm. I'm pondering if it's just the --disable-wrapping and
> --disable-speller that are causing the differences here...

No, the --disable-speller and --disable-wrapping and --disable-justify
and --disable-tabcomp are superfluous here: they are all comprised in
--enable-tiny.  The flags could thus be reduced to just: --enable-tiny
--disable-nls --with-slang.

If detection of a serial line is not possible, then maybe I could
suppress the showing of ^S and ^Q when --with-slang is used.  The
--with-slang option is used probably only by Debian, because its use
severely handicaps nano's keyboard handling.  If it is possible to
use ncurses, nobody should be using --with-slang.

(In fact, it would be better if the flags for the tiny version did
not include --with-slang.  It would still build a small binary, but
would be able to understand things like .  Only the
udeb version should use --with-slang, *if* the installation environment
does not provide ncurses.)

Benno

Bug#916038: dash: preinst script failure

[Guillaume Charifi]

Package: dash
Version: 0.5.8-2.10
Severity: important
Tags: patch upstream

Dear Maintainer,

Dash installation fails if the copy destination does not exist.
Patch here: https://salsa.debian.org/debian/dash/merge_requests/1



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

Kernel: Linux 4.19.2-041902-generic (SMP w/16 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr_CA:fr_CA (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dash depends on:
ii  debianutils  4.8.6
ii  dpkg 1.19.0.5ubuntu5
ii  libc62.28-0ubuntu1

dash recommends no packages.

dash suggests no packages.

-- debconf information:
* dash/sh: true

Bug#908204: git-buildpackage: cannot use gbp push without tagging a release

[Tong Sun]

> On Sun, Sep 09, 2018 at 10:45:35PM +0900, Norbert Preining wrote:
> > Hi Guido,
> >
> > > See the man page.
> >
> > Ok, was that always like this? I faintly remember (but without
> > screenshot to prove it) that I could gbp push stuff even without a
> > tagged debian release!?
> >
> It pushes everything *except* for the tip of your packaging branch (that
> is any tags needed, upstream and pristine tar.
> >
> > > not up to date. If this does not happen it's a bug but pushing non
> > > uptodate debian packaging branch is not the focus.

Hi Guido,

I'm trying to figure out the implication of your answer and solution
for this problem.

So let me summarize up the conclusion first,

gbp pushes up-to-date content of everything (that is any tags needed,
upstream and pristine tar) *except* for the tip of the packaging
branch, because "pushing non
uptodate debian packaging branch is not the focus"

> > Maybe I am the only developer on this earth that uses two computers and
> > prefers to push/pull, but I was more than once beaten by a not pushed
> > pristine-tar branch...
> Don't think so.

Does that implies that people can gbp push stuff even without a tagged
debian release!?

> > ? I don't get what you want to say? I want gbp push to push the branches
> > that are normally used by gbp (master/upstream/pristine-tar) and push
> > any tag from gbp tag that isn't up there.
> And it does that, see this test:
> 
> https://github.com/agx/git-buildpackage/blob/master/tests/component/deb/test_push.py#L106

"And it does that" -- Does that implies that gbp will push all the branches
that are normally used by gbp (master/upstream/pristine-tar) and push
any tag from gbp tag that isn't up there.

I took a look at the test:
 
https://github.com/agx/git-buildpackage/blob/master/tests/component/deb/test_push.py#L106

But can't figure out whether my implication-guess is right or not
because I don't understand those Python code. Any how,

If I want gbp to push _latest_ content of everything (including all the branches
that are normally used by gbp (master/upstream/pristine-tar) and any
tag from gbp tag that isn't up there), what shall I do?

If gbp somehow not able to do that currently, is there any workaround
to make it happen? E.g., if I have to tag a debian release, then how
exactly should I tag it so that it is acceptable by gbp?

Please help

Thanks

Bug#907159: mudlet: FTBFS in buster/sid (invalid use of incomplete type 'class QTabBar')

[Markus Koschany]

Control: tags -1 patch pending

Dear maintainer,

I've uploaded a new revision of mudlet versioned as 1:3.7.1-1.1.

To fix this issue I had to patch src/TCommandLine.cpp and add the
missing include for QTabBar. I also had to export CCACHE_DIR because
otherwise the build would fail on my system (pbuilder setup). Please
find attached the debdiff.

Regards,

Markus
diff -Nru mudlet-3.7.1/debian/changelog mudlet-3.7.1/debian/changelog
--- mudlet-3.7.1/debian/changelog   2017-12-24 07:49:23.0 +0100
+++ mudlet-3.7.1/debian/changelog   2018-12-09 15:12:05.0 +0100
@@ -1,3 +1,13 @@
+mudlet (1:3.7.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Export CCACHE_DIR in debian/rules to prevent a FTBFS because of
+a non-writable cache directory.
+  * QTabBar-include.patch: Fix FTBFS by adding the missing include for QTabBar.
+(Closes: #907159)
+
+ -- Markus Koschany   Sun, 09 Dec 2018 15:12:05 +0100
+
 mudlet (1:3.7.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru mudlet-3.7.1/debian/patches/QTabBar-include.patch 
mudlet-3.7.1/debian/patches/QTabBar-include.patch
--- mudlet-3.7.1/debian/patches/QTabBar-include.patch   1970-01-01 
01:00:00.0 +0100
+++ mudlet-3.7.1/debian/patches/QTabBar-include.patch   2018-12-09 
15:12:05.0 +0100
@@ -0,0 +1,22 @@
+From: Markus Koschany 
+Date: Sun, 9 Dec 2018 15:11:33 +0100
+Subject: QTabBar include
+
+Bug-Debian: https://bugs.debian.org/907159
+Forwarded: no
+---
+ src/TCommandLine.cpp | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/TCommandLine.cpp b/src/TCommandLine.cpp
+index 416e9ad..3a69da2 100644
+--- a/src/TCommandLine.cpp
 b/src/TCommandLine.cpp
+@@ -34,6 +34,7 @@
+ #include 
+ #include 
+ #include "post_guard.h"
++#include 
+ 
+ 
+ TCommandLine::TCommandLine(Host* pHost, TConsole* pConsole, QWidget* parent)
diff -Nru mudlet-3.7.1/debian/patches/series mudlet-3.7.1/debian/patches/series
--- mudlet-3.7.1/debian/patches/series  2017-12-24 07:49:23.0 +0100
+++ mudlet-3.7.1/debian/patches/series  2018-12-09 15:11:55.0 +0100
@@ -1,3 +1,4 @@
 project_file
 qrc_removedups
 freebsd_ifdef
+QTabBar-include.patch
diff -Nru mudlet-3.7.1/debian/rules mudlet-3.7.1/debian/rules
--- mudlet-3.7.1/debian/rules   2017-12-24 07:49:23.0 +0100
+++ mudlet-3.7.1/debian/rules   2018-12-09 15:01:48.0 +0100
@@ -9,6 +9,7 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 export QT_SELECT=5
+export CCACHE_DIR := $(CURDIR)/debian/ccache
 
 PACKAGE=mudlet
 SRC_VERSION:=$(shell dpkg-parsechangelog | sed -ne 's/^Version: 
\(\([0-9]\+\):\)\?\(.*\)-.*/\3/p')


signature.asc
Description: OpenPGP digital signature

Bug#916033: alex4 FTBFS with allegro4.4 2:4.4.2-13

[Andreas Ronnquist]

This patch fixes this problem for alex4. (I am the cause of the problem,
and I'll post patches to the other allegro4.4-related failures too).

-- Andreas Rönnquist
gus...@debian.org
--- a/src/shooter.c
+++ b/src/shooter.c
@@ -500,12 +500,12 @@
 			break;
 		case SM_SIN_WAVE:
 			o->x += o->vx;
-			o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
+			o->y = o->d2 + fixtoi(fixmul(ftofix(o->vy), fixsin(itofix(o->t;
 			o->t += o->d1;
 			break;
 		case SM_COS_WAVE:
 			o->x += o->vx;
-			o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fcos(itofix(o->t;
+			o->y = o->d2 + fixtoi(fixmul(ftofix(o->vy), fixcos(itofix(o->t;
 			o->t += o->d1;
 			break;
 		case SM_BOSS_1:
@@ -516,8 +516,8 @@
 o->tx = o->x;
 			}
 			else {
-o->y = o->ty + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
-o->x = o->tx - fixtoi(10 * fsin(itofix(o->t >> 1)));
+o->y = o->ty + fixtoi(fixmul(ftofix(o->vy), fixsin(itofix(o->t;
+o->x = o->tx - fixtoi(10 * fixsin(itofix(o->t >> 1)));
 o->t ++;
 			}
 			break;
@@ -573,7 +573,7 @@
 		else if (o->image == ENEMY15) {
 			int i;
 			for(i = 0; i < 256; i += 32)
-s_make_enemy_bullet((int)o->x + o->bw / 2, (int)o->y + o->bh, fixtof(1 * fcos(itofix(i - 6))), fixtof(1 * fsin(itofix(i - 6;
+s_make_enemy_bullet((int)o->x + o->bw / 2, (int)o->y + o->bh, fixtof(1 * fixcos(itofix(i - 6))), fixtof(1 * fixsin(itofix(i - 6;
 			o->fire_counter = 200 + rand()%50;
 		}
 	
--- a/src/main.c
+++ b/src/main.c
@@ -1212,9 +1212,9 @@
 
 	blit(data[INTRO_BG].dat, bmp, 0, 0, 0, 0, 160, 120);
 
-	r = 70 + fixtoi(20 * fcos(itofix(game_count >> 1)) + 20 * fsin(itofix((int)(game_count / 2.7))) );
+	r = 70 + fixtoi(20 * fixcos(itofix(game_count >> 1)) + 20 * fixsin(itofix((int)(game_count / 2.7))) );
 	for(i = 0; i < 256; i += 32) 
-		draw_sprite(bmp, head, 80 - head->w/2 + fixtoi(r * fcos(itofix(game_count + i))), 60 - head->h/2 + fixtoi(r * fsin(itofix(game_count + i;
+		draw_sprite(bmp, head, 80 - head->w/2 + fixtoi(r * fixcos(itofix(game_count + i))), 60 - head->h/2 + fixtoi(r * fixsin(itofix(game_count + i;
 
 	draw_sprite_h_flip(bmp, data[ALEX].dat, 60, 40);
 	draw_sprite(bmp, data[LOLA].dat, 84, 40);
@@ -2545,7 +2545,7 @@
 	textout_ex(bmp, data[THE_FONT].dat, "QUIT", x+1, y+1, 1, -1);
 	textout_ex(bmp, data[THE_FONT].dat, "QUIT", x, y, 4, -1);
 
-	draw_sprite(bmp, data[POINTER].dat, x - 25 + fixtoi(3 * fcos(itofix(tick << 2))), 44 + menu_choice * step);
+	draw_sprite(bmp, data[POINTER].dat, x - 25 + fixtoi(3 * fixcos(itofix(tick << 2))), 44 + menu_choice * step);
 }
 
 

Bug#916008: wmhdplop FTBFS with glibc 2.28

[Andreas Metzler]

On 2018-12-09 Adrian Bunk  wrote:
> Source: wmhdplop
> Version: 0.9.10-1
[...]

> devnames.c: In function 'device_id_from_name':
> devnames.c:207:13: warning: implicit declaration of function 'major' 
> [-Wimplicit-function-declaration]
>*pmajor = major(stat_buf.st_rdev);
>  ^
[...]

Seems to miss a 
#include 

cu Andreas

Bug#916040: AMDGPU: UVD stalls when encoding and decoding videos, freeze screen.

[Kyuma Ohta]

Package: src:linux
Version: 4.19.5-1~exp1
Severity: important

Dear Maintainer,

When encoding video via FFMPEG/VAAPI, *and* start to decoding another video via 
VAAPI,
sometimes stall decoding.
Then, freeze screen(s), not recoverible.Need to re-boot.

When happens this problem, kernel messaged below log:
Dec  9 23:37:37 melchior kernel: [630983.109621] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring uvd timeout, signaled seq=16226, emitted seq=16229
Dec  9 23:37:37 melchior kernel: [630983.109634] amdgpu :01:00.0:GPU reset 
begin!

This issue was happend at least before kernel 4.17.

Regards,
Ohta.

-- Package-specific info:
** Version:
Linux version 4.19.0-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.2.0 (Debian 8.2.0-10)) #1 SMP Debian 4.19.5-1~exp1 (2018-11-27)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-trunk-amd64 
root=UUID=040b41b0-26fe-4064-af0a-3619f3112096 ro video=1280x768 
systemd.debug-shell amdgpu.si_support=1 radeon.si_support=0 amdgpu.deep_color=1 
amdgpu.gpu_recovery=1 iommu=pt video=1280x768 systemd.debug-shell iommu=pt

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: To Be Filled By O.E.M.
product_name: To Be Filled By O.E.M.
product_version: To Be Filled By O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: P2.70
board_vendor: ASRock
board_name: 990FX Extreme4
board_version: 

** Loaded modules:
ipt_MASQUERADE(E)
nf_conntrack_netlink(E)
xfrm_user(E)
xfrm_algo(E)
nft_counter(E)
nft_chain_nat_ipv4(E)
nf_nat_ipv4(E)
xt_addrtype(E)
nft_compat(E)
nf_tables(E)
nfnetlink(E)
xt_conntrack(E)
nf_nat(E)
nf_conntrack(E)
nf_defrag_ipv6(E)
nf_defrag_ipv4(E)
br_netfilter(E)
bridge(E)
stp(E)
llc(E)
pci_stub(E)
vboxpci(OE)
vboxnetadp(OE)
vboxnetflt(OE)
vboxdrv(OE)
lttng_probe_writeback(OE)
lttng_probe_workqueue(OE)
lttng_probe_v4l2(OE)
lttng_probe_vmscan(OE)
lttng_probe_udp(OE)
lttng_probe_timer(OE)
lttng_probe_sunrpc(OE)
lttng_probe_statedump(OE)
lttng_probe_sock(OE)
lttng_probe_skb(OE)
lttng_probe_signal(OE)
lttng_probe_scsi(OE)
lttng_probe_sched(OE)
lttng_probe_regulator(OE)
lttng_probe_rcu(OE)
lttng_probe_random(OE)
lttng_probe_printk(OE)
lttng_probe_power(OE)
lttng_probe_net(OE)
lttng_probe_napi(OE)
lttng_probe_module(OE)
lttng_probe_kvm(OE)
lttng_probe_kmem(OE)
lttng_probe_jbd2(OE)
lttng_probe_irq(OE)
lttng_probe_gpio(OE)
lttng_probe_compaction(OE)
lttng_probe_block(OE)
lttng_probe_asoc(OE)
lttng_ring_buffer_metadata_mmap_client(OE)
lttng_ring_buffer_client_mmap_overwrite(OE)
lttng_ring_buffer_client_mmap_discard(OE)
lttng_ring_buffer_metadata_client(OE)
lttng_ring_buffer_client_overwrite(OE)
lttng_ring_buffer_client_discard(OE)
lttng_tracer(OE)
ipmi_devintf(E)
lttng_statedump(OE)
lttng_kprobes(OE)
cpufreq_conservative(E)
cpufreq_powersave(E)
ipmi_msghandler(E)
lttng_clock(OE)
cpufreq_userspace(E)
lttng_lib_ring_buffer(OE)
lttng_kretprobes(OE)
binfmt_misc(E)
jfs(E)
xfs(E)
nls_ascii(E)
nls_cp437(E)
crc32c_generic(E)
vfat(E)
fat(E)
edac_mce_amd(E)
kvm_amd(E)
ccp(E)
rng_core(E)
kvm(E)
irqbypass(E)
ftdi_sio(E)
crct10dif_pclmul(E)
crc32_pclmul(E)
ghash_clmulni_intel(E)
usbserial(E)
joydev(E)
pktcdvd(E)
snd_hda_codec_realtek(E)
snd_hda_codec_generic(E)
mxl301rf(E)
efi_pstore(E)
qm1d1c0042(E)
efivars(E)
tc90522(E)
snd_hda_codec_hdmi(E)
earth_pt3(E)
fam15h_power(E)
snd_hda_intel(E)
dvb_core(E)
snd_hda_codec(E)
k10temp(E)
snd_hda_core(E)
sg(E)
sp5100_tco(E)
pcc_cpufreq(E)
evdev(E)
acpi_cpufreq(E)
cuse(E)
fuse(E)
w83627ehf(E)
hwmon_vid(E)
w83627hf_wdt(E)
snd_usb_audio(E)
snd_usbmidi_lib(E)
snd_hwdep(E)
snd_rawmidi(E)
snd_seq_device(E)
snd_dummy(E)
snd_pcm(E)
snd_timer(E)
snd(E)
soundcore(E)
loop(E)
i2c_dev(E)
parport_pc(E)
ppdev(E)
lp(E)
parport(E)
vhba(OE)
efivarfs(E)
ip_tables(E)
x_tables(E)
autofs4(E)
overlay(E)
ext4(E)
crc16(E)
mbcache(E)
jbd2(E)
fscrypto(E)
btrfs(E)
zstd_decompress(E)
zstd_compress(E)
xxhash(E)
raid10(E)
raid456(E)
async_raid6_recov(E)
async_memcpy(E)
async_pq(E)
async_xor(E)
async_tx(E)
xor(E)
raid6_pq(E)
libcrc32c(E)
raid1(E)
raid0(E)
multipath(E)
linear(E)
md_mod(E)
hid_generic(E)
usbhid(E)
hid(E)
uas(E)
usb_storage(E)
sr_mod(E)
cdrom(E)
sd_mod(E)
ohci_pci(E)
amdkfd(E)
crc32c_intel(E)
mxm_wmi(E)
ata_generic(E)
amdgpu(E)
chash(E)
gpu_sched(E)
i2c_algo_bit(E)
ttm(E)
pata_atiixp(E)
aesni_intel(E)
ahci(E)
xhci_pci(E)
aes_x86_64(E)
ohci_hcd(E)
ehci_pci(E)
libahci(E)
crypto_simd(E)
drm_kms_helper(E)
xhci_hcd(E)
ehci_hcd(E)
cryptd(E)
glue_helper(E)
libata(E)
tg3(E)
i2c_piix4(E)
usbcore(E)
libphy(E)
drm(E)
scsi_mod(E)
usb_common(E)
floppy(E)
wmi(E)
button(E)

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 
Host Bridge [1002:5a14] (rev 02)
Subsystem: ASRock Incorporation RD9x0/RX980 Host Bridge [1849:5a14]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- 

Bug#916037: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Andreas Ronnquist]

tags 916037 + patch
thanks

Patch attached to fix this build error (Which I am the cause of).

/Andreas
gus...@debian.org
--- a/src/distor.c
+++ b/src/distor.c
@@ -194,7 +194,7 @@
   cycle_tmp /= 2;
   speed--;
 }
-  cycle_tmp = fsqrt (fsqrt (cycle_tmp)) / 2;
+  cycle_tmp = fixsqrt (fixsqrt (cycle_tmp)) / 2;
   cycle_tmp /= SCREEN_W;
   cycle_tmp *= period;
   if (cycle_tmp <= 0)
@@ -203,8 +203,8 @@
 }
   cycle_coef = sens * 256 * (itofix (GLOBAL_TICKER % cycle_tmp) / cycle_tmp);
 
-  f0 = fsin (cycle_coef + freq_coef * period2);
-  fp0x0 = (PI_1024 * fcos (cycle_coef + freq_coef * period2)) / 1024;
+  f0 = fixsin (cycle_coef + freq_coef * period2);
+  fp0x0 = (PI_1024 * fixcos (cycle_coef + freq_coef * period2)) / 1024;
 
   alphax03 = (ampli_cst / 256) * ((fp0x0 - 2 * f0) / 256);
   betax02 = (ampli_cst / 256) * ((-fp0x0 + 3 * f0) / 256);
@@ -217,7 +217,7 @@
 }
   for (i = period2; i < real_length - period2; ++i)
 {
-  temp = ((ampli_cos) / 256) * (fcos (cycle_coef + freq_coef * i) / 256);
+  temp = ((ampli_cos) / 256) * (fixcos (cycle_coef + freq_coef * i) / 256);
   buffer2[i] = temp / WAVE_SIZE_SCALE;
 }
 
--- a/src/fighter.c
+++ b/src/fighter.c
@@ -335,7 +335,7 @@
   coef += 256;
 
   attack[i] = (coef *
-		   fsqrt (fsqrt (1 << (LW_CONFIG_CURRENT_RULES.fighter_attack
+		   fixsqrt (fixsqrt (1 << (LW_CONFIG_CURRENT_RULES.fighter_attack
    + cpu_influence[i] / (256 * 8);
   if (attack[i] >= MAX_FIGHTER_HEALTH)
 	attack[i] = MAX_FIGHTER_HEALTH - 1;
@@ -343,7 +343,7 @@
 	attack[i] = 1;
 
   defense[i] = (coef *
-		fsqrt (fsqrt
+		fixsqrt (fixsqrt
 			   (1 <<
 			(LW_CONFIG_CURRENT_RULES.fighter_defense +
 			 cpu_influence[i] / (256 * 256);
@@ -353,7 +353,7 @@
 	defense[i] = 1;
 
   new_health[i] = (coef *
-		   fsqrt (fsqrt
+		   fixsqrt (fixsqrt
 			  (1 <<
 			   (LW_CONFIG_CURRENT_RULES.fighter_new_health +
 cpu_influence[i] / (256 * 4);
--- a/src/palette.c
+++ b/src/palette.c
@@ -88,7 +88,7 @@
 {
   int result;
 
-  result = fsqrt (i * 256) / 256;
+  result = fixsqrt (i * 256) / 256;
   if (result > 255)
 result = 255;
 

Bug#916041: libc-client2007e: add SNI support

[Ed Spiridonov]

Package: libc-client2007e
Version: 8:2007f~dfsg-5
Severity: important
Tags: patch

Dear Maintainer,

When used with openssl 1.1.1 this library cannot work with Google IMAP servers
because Google wants SNI request if client supports TLS 1.3.

This breaks simple php script:
$hostname = '{imap.googlemail.com:993/imap/ssl}INBOX';
$username = '...';
$password = '...';
$inbox = imap_open($hostname, $username, $password) or die(imap_last_error());


More information here:
https://mta.openssl.org/pipermail/openssl-project/2018-April/000628.html
https://mta.openssl.org/pipermail/openssl-project/2018-April/000635.html


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (450, 'stable'), (150, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0 (SMP w/2 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/bash
Init: sysvinit (via /sbin/init)

Versions of packages libc-client2007e depends on:
ii  libc6 2.24-11+deb9u1
ii  libcom-err2   1.44.4-2
ii  libgssapi-krb5-2  1.15-1+deb9u1
ii  libk5crypto3  1.15-1+deb9u1
ii  libkrb5-3 1.15-1+deb9u1
ii  libpam-modules1.1.8-3.6
ii  libpam0g  1.1.8-3.6
ii  libssl1.1 1.1.1-2+0~20181105132527.5+stretch~1.gbp90eb86
ii  mlock 8:2007f~dfsg-5

libc-client2007e recommends no packages.

Versions of packages libc-client2007e suggests:
pn  uw-mailutils  

-- no debconf information
Add SNI support for openssl 1.1.1Index: 
uw-imap-2007f~dfsg/src/osdep/unix/ssl_unix.c
===
--- uw-imap-2007f~dfsg.orig/src/osdep/unix/ssl_unix.c
+++ uw-imap-2007f~dfsg/src/osdep/unix/ssl_unix.c
@@ -266,6 +266,9 @@ static char *ssl_start_work (SSLSTREAM *
/* create connection */
   if (!(stream->con = (SSL *) SSL_new (stream->context)))
 return "SSL connection failed";
+#if OPENSSL_VERSION_NUMBER >= 0x10101000
+  SSL_set_tlsext_host_name(stream->con,host);
+#endif
   bio = BIO_new_socket (stream->tcpstream->tcpsi,BIO_NOCLOSE);
   SSL_set_bio (stream->con,bio,bio);
   SSL_set_connect_state (stream->con);

Bug#916042: lxde: leafpad is not fit for default editor

[Juhani Numminen]

Package: lxde
Version: 10
Severity: normal
X-Debbugs-Cc: kretc...@gmail.com, sfkrys...@gmail.com, and...@rep.kiev.ua

Hi,

The metapackage lxde currently depends on "leafpad | mousepad" which
in practice makes leafpad the default text editor for lxde. I think
leafpad is not suitable to be a default editor because of its 
long-standing bugs:

- UTF-8 mishandling
https://bugs.debian.org/913838
https://bugs.launchpad.net/ubuntu/+bug/800059
- data loss when used with ssh/sftp/samba
https://bugs.debian.org/890416
https://bugs.launchpad.net/ubuntu/+bug/708829
- middle click paste not working
https://bugs.debian.org/511827
- UTF-16 encoded file not displayed
https://bugs.debian.org/819909
- last line of selection is not indented
https://bugs.launchpad.net/ubuntu/+bug/1460311

I think any of those is not a problem for the two alternative editors,
mousepad and featherpad. Please consider dropping the dependency
on leafpad from lxde.


Thanks,

--
Juhani

Bug#916043: qemu-user-static: qemu-arm-static running armel dash breaks globbing

[Ian Campbell]

Package: qemu-user-static
Version: 1:2.12+dfsg-3+b1
Severity: normal

Dear Maintainer,

While working on a new qcontrol package, using a cross-schroot via
qemu-arm-static on an amd64 host, I noticed that globs did not appear to be
expanded when running dash. It appears to relate to libc 2.28-2 but only when
running under qemu-arm-static:

ijc@dagon:dash-bug$ curl -LOJ 
"http://ftp.uk.debian.org/debian/pool/main/d/dash/dash_0.5.10.2-1_armel.deb";
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
100  105k  100  105k0 0  1074k  0 --:--:-- --:--:-- --:--:-- 
1074k
ijc@dagon:dash-bug$ curl -LOJ 
"http://ftp.uk.debian.org/debian/pool/main/g/glibc/libc6_2.28-2_armel.deb";
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
100 2340k  100 2340k0 0  5454k  0 --:--:-- --:--:-- --:--:-- 
5454k
ijc@dagon:dash-bug$ curl -LOJ 
"http://ftp.uk.debian.org/debian/pool/main/g/glibc/libc6_2.27-8_armel.deb";
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
100 2371k  100 2371k0 0  5305k  0 --:--:-- --:--:-- --:--:-- 
5293k
ijc@dagon:dash-bug$ dpkg-deb -x libc6_2.27-8_armel.deb 2.27-8
ijc@dagon:dash-bug$ dpkg-deb -x dash_0.5.10.2-1_armel.deb 2.27-8
ijc@dagon:dash-bug$ dpkg-deb -x libc6_2.28-2_armel.deb 2.28-2
ijc@dagon:dash-bug$ dpkg-deb -x dash_0.5.10.2-1_armel.deb 2.28-2
ijc@dagon:dash-bug$ dpkg -l qemu-user-static
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description

+++-===---
ii  qemu-user-static1:2.12+dfsg-3+b1 amd64QEMU user 
mode emulation binaries (static version)
ijc@dagon:dash-bug$ mkdir 2.27-8/usr/bin/ 2.28-2/usr/bin
ijc@dagon:dash-bug$ cp /usr/bin/qemu-arm-static 2.27-8/usr/bin/
ijc@dagon:dash-bug$ cp /usr/bin/qemu-arm-static 2.28-2/usr/bin/
ijc@dagon:dash-bug$ sudo chroot 2.27-8/ dash -c 'echo *'
bin etc lib usr
ijc@dagon:dash-bug$ sudo chroot 2.28-2/ dash -c 'echo *'
*
ijc@dagon:dash-bug$ uname -a
Linux dagon 4.17.0-1-amd64 #1 SMP Debian 4.17.8-1 (2018-07-20) x86_64 
GNU/Linux

However I cannot reproduce on my qnap (armel):

root@qnap:~/dash-bug# curl -LOJ 
"http://ftp.uk.debian.org/debian/pool/main/d/dash/dash_0.5.10.2-1_armel.deb";
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
100  105k  100  105k0 0  1012k  0 --:--:-- --:--:-- --:--:-- 
1012k
root@qnap:~/dash-bug# curl -LOJ 
"http://ftp.uk.debian.org/debian/pool/main/g/glibc/libc6_2.28-2_armel.deb";
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
100 2340k  100 2340k0 0  3720k  0 --:--:-- --:--:-- --:--:-- 
3720k
root@qnap:~/dash-bug# curl -LOJ 
"http://ftp.uk.debian.org/debian/pool/main/g/glibc/libc6_2.27-8_armel.deb";
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
100 2371k  100 2371k0 0  3676k  0 --:--:-- --:--:-- --:--:-- 
3676k
root@qnap:~/dash-bug# dpkg-deb -x libc6_2.27-8_armel.deb 2.27-8
root@qnap:~/dash-bug# dpkg-deb -x dash_0.5.10.2-1_armel.deb 2.27-8
root@qnap:~/dash-bug# dpkg-deb -x libc6_2.28-2_armel.deb 2.28-2
root@qnap:~/dash-bug# dpkg-deb -x dash_0.5.10.2-1_armel.deb 2.28-2
root@qnap:~/dash-bug# chroot 2.27-8/ dash -c 'echo *'
bin etc lib usr
root@qnap:~/dash-bug# chroot 2.28-2/ dash -c 'echo *'
bin etc lib usr
root@qnap:~/dash-bug# uname -a
Linux qnap 4.18.0-3-marvell #1 Debian 4.18.20-2 (2018-11-23) armv5tel 
GNU/Linux

Nor on abel.debian.org (armel porter box, but with armhf kernel so not
necessarily a good data point):

(sid_armel-dchroot)ijc@abel:/$ apt policy dash libc6
dash:
  Installed: 0.5.10.2-1
  Candidate: 0.5.10.2-1
  Version table:
 *** 0.5.10.2-1 500
500 http://ftp.uk.debian.org/debian sid/main armel Packages
100 /var/lib/dpkg/status
libc6:
  Installed: 2.28-2
  Candidate: 2.28-2
  Version table:
 *** 2.28-2 500
500 http://ftp.uk.debian.org/debian sid/main armel Packages
100 /var/l

Bug#916035: kraptor FTBFS with allegro4.4 2:4.4.2-13

[Andreas Ronnquist]

tags 916035 + patch
thanks

Attached patch to fix building with fixmul instead of fmul. (I am the
cause of the problem with my allegro4.4 upload)

thanks
-- Andreas Rönnquist
gus...@debian.org
--- a/src/explos.c
+++ b/src/explos.c
@@ -126,10 +126,10 @@
  while (tmp) {
 
   x2 = fixtoi(tmp->x)-x;
-  x2 -= fixtoi(fmul(itofix(tmp->spr->w), tmp->r))/2;
+  x2 -= fixtoi(fixmul(itofix(tmp->spr->w), tmp->r))/2;
 
   y2 = fixtoi(tmp->y)-y;
-  y2 -= fixtoi(fmul(itofix(tmp->spr->h), tmp->r))/2;
+  y2 -= fixtoi(fixmul(itofix(tmp->spr->h), tmp->r))/2;
 
   /* dibujar */
   rotate_scaled_sprite(bmp, tmp->spr, x2, y2, itofix(tmp->rot), tmp->r);
--- a/src/enemigo.c
+++ b/src/enemigo.c
@@ -495,7 +495,7 @@
nueva->dx = ftofix((float)rand_ex(-fixtof(arma_ene[ene->arma_actual].vx)*10.0, fixtof(arma_ene[ene->arma_actual].vx)*10.0) / 10.0);
if (rand()%100 < 10)  nueva->dx = 0;
 
-   nueva->dy = fmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 3)) );
+   nueva->dy = fixmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 3)) );
break;
 
case 2: /* abanico triple */
@@ -527,7 +527,7 @@
if (rand()%100 < 15) // cada tanto, al azar
   {
nueva->dx = ftofix((float)rand_ex(-150, 150) / 10.0);
-   nueva->dy = fmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 3)) );
+   nueva->dy = fixmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 3)) );
   }
 
break;

Bug#799626: RFP: beancount -- command line double-entry bookkeeping system

[Martin Michlmayr]

Is there any update on this ITP?

Is the delay because of the test failures mentioned by Zack?

-- 
Martin Michlmayr
https://www.cyrius.com/

Bug#915603: Your mail

[Andreas Beckmann]

On Wed, 05 Dec 2018 12:21:05 -0700 Ted Percival  wrote:
> So the solution might just be to add the versioned Build-Depends: g++ (>= 4:7)
> and rebuild to get the old symbols back into the library, rather than bumping
> the soname.

That reminds me of https://bugs.debian.org/911090 where

On 2018-10-22 15:13, Matthias Klose wrote:
> The compat symbol was in GCC 7, and then removed in GCC 8.

So, yes, best do a proper transition ... unless you can easily enumerate
the affected packages and add Breaks against them.

How many more of these time bombs do we have lingering in our packages?


Andreas

Bug#901185: [Debconf-devel] Bug#901185: me too

[Luca Boccassi]

On Tue, 12 Jun 2018 06:22:09 +0100 Colin Watson 
wrote:
> On Mon, Jun 11, 2018 at 08:52:11PM +0200, Andreas Metzler wrote:
> > On 2018-06-11 Colin Watson  wrote:
> > > On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> > > > yes, resetting IFS to its default value in confmodule helps.
> > 
> > > Thanks.  For completeness, could you try this variant patch?  If
shells
> > > are going to be unreliable about setting IFS in this way, then
I'd
> > > rather just separate out the assignments altogether.
> > [snip]
> > 
> > Yes, this variant of the patch also works.
> > 
> > Thanks to your handholding we now have a minimal reproducer for the
> > issue:
> 
> Thanks.  Now that you have a reproducer that doesn't involve debconf
and
> so I won't be interfering with debugging, I've uploaded debconf
1.5.67
> with that confmodule patch.  I know it's a bash5 bug and will
hopefully
> be fixed, but we might as well be conservative in debconf when it's
easy
> to do so.
> 
> -- 
> Colin Watson   [cjwatson@debian.o
rg]

Hi,

FYI, this was fixed in bash 5.0 beta1:

$ ./bash --version
GNU bash, version 5.0.0(1)-beta (x86_64-pc-linux-gnu)
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ ./bash -o posix -c 'v=ok; v=bug read x 

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

Bug#916044: git-buildpackage: Please correct "was build" grammatical errors

[Chris Lamb]

Source: git-buildpackage
Version: 0.9.10+nmu1
Severity: minor
Tags: patch

Hi,

The attached patch fixes a number of "was build" grammatical mistakes.
(It also includes a correction for a "pristine-tar" typo.)


Best wishes,

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

Bug#916044: git-buildpackage: Please correct "was build" grammatical errors

[Guido Günther]

Hi,
On Sun, Dec 09, 2018 at 05:06:36PM +0100, Chris Lamb wrote:
> Source: git-buildpackage
> Version: 0.9.10+nmu1
> Severity: minor
> Tags: patch
> 
> Hi,
> 
> The attached patch fixes a number of "was build" grammatical mistakes.
> (It also includes a correction for a "pristine-tar" typo.)

No patch attached.
 -- Guido

Bug#916000: ncbi-blast+: FTBFS - Makefile.flat: No such file or directory

[Aaron M. Ucko]

Andreas Metzler  writes:

> ncbi-blast+ FTBFS on current sid:

Thanks for the report!  It looks like ncbi-blast+ needs another round of
formal patches for compatibility with current Boost.  The following
upstream changes should collectively take care of it:

https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision&revision=79910
https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision&revision=79926
https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision&revision=79928
https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision&revision=79929

Olivier, will you have time to integrate these changes, or should I?

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#851783: GNUCash crashes when asking for a report, if talkplugin for chrome is installed

[Bertrand Marc]

Hi Sergio,

Do you still face this issue? I cannot reproduce neither on stable (version 
2.15) nor unstable (version 3.3).

Cheers,
Bertrand

Bug#916045: x2goserver: [INTL:de] Updated German debconf translation

[Chris Leick]

Package: x2goserver
Version: 4.1.0.3-2
Severity: wishlist
Tags: l10n patch



Hi,

please find attached the newest German translation.

Kind regards,
Chris


de.po.gz
Description: application/gzip

Bug#916044: git-buildpackage: Please correct "was build" grammatical errors

[Chris Lamb]

Chris Lamb wrote:

> The attached patch fixes a number of "was build" grammatical mistakes.
> (It also includes a correction for a "pristine-tar" typo.)

Actually attaching patch...


Regards,

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

Bug#916046: libsqlite3-0 might need Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~)

[Adrian Bunk]

Package: libsqlite3-0
Version: 3.26.0-1
Severity: serious
Control: block -1 by 915938

  Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~)
(assuming #915938 will be fixed in version 0.11.0-4)
might be correct to prevent people using testing or stretch-backports
to end up using a problematic combination of packages.