Bug#941060: chromium: When will the upgrade to v77 reach debian?

[jim_p]

Package: chromium
Followup-For: Bug #941060

It's a real shame that chromium's built in mechanism had to be triggered in
order for the typical debian users to understand how far behind debian's
chromium is.
I had opened this bug report 1+ month ago and yet the "advocates" of this bad
situation said that the devs need time etc. Time is up as it seems and the
package needs to be updated asap!

Of course, as I have read in other bug reports and on reddit, there are
workarounds to this, but the real issue remains: chromium on debian is not
updated as regularly as it used to and that is a major security issue.

As I said above, I moved to chrome the next day 78 became available, so this is
the last bug report on chromium I open and reply to. Last time I had chrome on
my systems, google was still offering it as a 32bit package and firefox was on
3.x! Shame.

p.s. Debian pts MUST get a "flag as out of date" button. Or a better way to
"wake up" the maintainers who keep their packages unmaintained for more than a
period of time after which issues arise.



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

Kernel: Linux 5.3.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ERROR: ld.so: object 
'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared 
object file): ignored.
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
UTF-8), LANGUAGE=en_US:en (charmap=ERROR: ld.so: object 'libgtk3-nocsd.so.0' 
from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
pn  chromium-common  
ii  libasound2   1.1.8-2
ii  libatk-bridge2.0-0   2.34.1-1
ii  libatk1.0-0  2.34.1-1
ii  libatomic1   9.2.1-8
ii  libatspi2.0-02.34.0-3
ii  libavcodec58 10:4.2.1-dmo6
ii  libavformat5810:4.2.1-dmo6
ii  libavutil56  10:4.2.1-dmo6
ii  libc62.29-2
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcups2 2.3.0-5
ii  libdbus-1-3  1.12.16-2
ii  libdrm2  2.4.99-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.9-1
ii  libflac8 1.3.3-1
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.10.1-2
ii  libgcc1  1:9.2.1-8
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-1
ii  libglib2.0-0 2.62.2-1
ii  libgtk-3-0   3.24.12-1
ii  libharfbuzz0b2.6.2-1
ii  libicu63 63.2-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjsoncpp1  1.7.4-3+b1
ii  liblcms2-2   2.9-3+b1
pn  libminizip1  
ii  libnspr4 2:4.23-1
ii  libnss3  2:3.47-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3-1+b1
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpci3  1:3.6.2-2
ii  libpng16-16  1.6.37-1
ii  libpulse013.0-2
pn  libre2-5 
ii  libsnappy1v5 1.1.7-1+b1
ii  libstdc++6   9.2.1-8
ii  libvpx6  1.8.1-dmo1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.6.8-1
ii  libx11-xcb1  2:1.6.8-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.2.0-2
ii  libxdamage1  1:1.1.5-1
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2.1
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

Versions of packages chromium recommends:
pn  chromium-sandbox  

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Bug#667701: cdrom-detect: Need a simple retry or delay to mount USB flash drives

[Karthik Rengasamy]

This problem still persists in Debian buster.
I am using unattended installation using pressed file.
Whenever the mount failed the auto-installation stops and pops up a dialog box.
To retry without human intervention, I made some code changes to the 
cdrom-detect.postinst script.
The below is the script file 
https://salsa.debian.org/installer-team/cdrom-detect/blob/master/debian/cdrom-detect.postinst
 

 from the actual repo.
In my case we are trying to mount the iso from CD /dev/sr0.
After trying to mount the CD and if it failed (line #114), the script is 
looking for usb-partition and if there are no usb-partitions then the retry was 
never called.
The retry condition is looking for a non-empty devices list (line #141), but 
the usb-partition overrides the devices list value to empty string 
(Line #121), because we do not have any usb-partition.
Hence I changed the script by commenting the usb-partitions device list. Now 
the retry worked successfully.

This bug can be easily fixed by changing the variable name ‘devices' to 
something else from line number 121 to 130 in above script.




On Fri, 06 Apr 2012 01:00:36 +0200 =?ISO-8859-15?Q?J=F6rg_Ludwig?= 
 wrote:
> Package: cdrom-detect
> Version: 1.38
> Severity: normal
> Tags: d-i
> 
> *** Please type your report below this line ***
> We install Debian from USB flash drive. After loading of the Linux 
> kernel we immediately get an error saying no CD-ROM could be found. When 
> we abort the CD-ROM detection, go back to the Debian Installer menu and 
> try again it works without any problem.
> 
> The syslog shows that cdrom-detect finishes before the USB flash drive 
> is initialized by the kernel:
> 
> Apr  5 21:46:23 cdrom-detect: Searching for Debian installation media...
> Apr  5 21:46:23 cdrom-detect: Devices: '/dev/sr0'
> Apr  5 21:46:23 cdrom-detect: CD-ROM mount failed: device=/dev/sr0 
> fstype=iso9660
> Apr  5 21:46:26 kernel: [8.161655] usb-storage: device scan complete
> Apr  5 21:46:26 kernel: [8.163255] scsi 4:0:0:0: Direct-Access 
> Kingston DataTraveler G3  PMAP PQ: 0 ANSI: 0 CCS
> Apr  5 21:46:26 kernel: [8.163571] sd 4:0:0:0: Attached scsi generic 
> sg3 type 0
> Apr  5 21:46:26 kernel: [8.164354] sd 4:0:0:0: [sdc] 7612032 
> 512-byte logical blocks: (3.89 GB/3.62 GiB)
> Apr  5 21:46:26 kernel: [8.164856] sd 4:0:0:0: [sdc] Write Protect 
> is off
> Apr  5 21:46:26 kernel: [8.164861] sd 4:0:0:0: [sdc] Mode Sense: 23 
> 00 00 00
> Apr  5 21:46:26 kernel: [8.164864] sd 4:0:0:0: [sdc] Assuming drive 
> cache: write through
> Apr  5 21:46:26 kernel: [8.167472] sd 4:0:0:0: [sdc] Assuming drive 
> cache: write through
> Apr  5 21:46:26 kernel: [8.167477]  sdc: sdc1
> Apr  5 21:46:26 kernel: [8.169955] sd 4:0:0:0: [sdc] Assuming drive 
> cache: write through
> Apr  5 21:46:26 kernel: [8.169957] sd 4:0:0:0: [sdc] Attached SCSI 
> removable disk
> 
> 
> -- System Information:
> Debian Release: 6.0.4
>APT prefers stable-updates
>APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: i386 (x86_64)
> 
> Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> 
> 

Bug#943812: libsopt-dev: missing dependency on libopenmpi-dev

[Helmut Grohne]

Package: libsopt-dev
Version: 3.0.1-7
Severity: serious
Justification: missing required dependency
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:purify

The headers shipped in libsopt-dev #include , but they fail
depending on an mpi implementation. This is a bug.

Moreover, /usr/share/cmake/sopt/SoptCPPTargets.cmake declares an
imported library "sopt" whose INTERFACE_INCLUDE_DIRECTORIES contain
/usr/lib/arm-linux-gnueabi/openmpi/include/openmpi. Any use of this
target fails at the cmake level unless libopenmpi-dev is installed. Here
is an example of how it breaks purify.

| CMake Error in cpp/purify/CMakeLists.txt:
|   Imported target "sopt" includes non-existent path
|
| "/usr/lib/arm-linux-gnueabi/openmpi/include/openmpi"
|
|   in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:
|
|   * The path was deleted, renamed, or moved to another location.
|
|   * An install or uninstall procedure did not complete successfully.
|
|   * The installation package was faulty and references files it does not
|   provide.

A quick glimpse at the package also suggests that libeigen3-dev very
likely should also be a dependency.

Helmut

Bug#943811: perl:any is possible the following way and I suggest doing this

[mdasoh kyaeppd]

Package: perl
Version: 5.30.0-8
Severity: important

Having seen perl:any wane in use, I suggest bringing it back with the following 
measures:
in perl's control stanza:
Provides: perl:any (= 5.30.0-8)
in perl-base's control stanza:
Multi-Arch: foreign
Provides: perl-base:any (= 5.30.0-8), perlapi-5.30.0:any
in a package's control stanza which currently Depends: perl:any
Multi-Arch: foreign
Depends: perl:any (>= 5.30.0-8), perlapi-5.30.0:any

I have it working this way locally
please respond with your thoughts or opinions.

sincerely,
- Mdasoh Kyaeppd.



Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Versions of packages perl depends on:
ii  dpkg   1.19.7
ii  libperl5.305.30.0-8
ii  perl-base  5.30.0-8
ii  perl-modules-5.30  5.30.0-9

Versions of packages perl recommends:
ii  netbase  5.4

Versions of packages perl suggests:
ii  libb-debug-perl1.26-1
ii  liblocale-codes-perl   3.61-1
ii  libterm-readline-gnu-perl  1.36-2+b1
ii  make   4.2.1-1.1
pn  perl-doc   

-- no debconf information
- (snip) -

Bug#921136: lintian: hardening-no-fortify-functions possible false positive

[Olly Betts]

On Tue, Oct 29, 2019 at 11:05:02PM -0400, Scott Talbert wrote:
> On Wed, 30 Oct 2019, Olly Betts wrote:
> 
> > The same issue applies to memcpy() which is why it's deliberately from
> > lintian's list:
> > 
> > https://sources.debian.org/src/lintian/2.31.0/data/binaries/hardened-functions/?hl=6#L6
> > 
> > Presumably wmemcpy() is simply much less widely used than memcpy(), and
> > that's the only reason it's not also omitted already.
> 
> Thanks for the details, Olly.  So, what you're saying is that wmemcpy should
> be excluded from hardened-functions?

Yes.  Probably wmemset and wmemmove should be too.  The history of
this seems to be in #673112 (don't be misled by the bug title!)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673112#67 suggests
that perhaps recvfrom, recv and read ought to be as well.

The whole approach seems a bit flawed though - the
hardening-no-fortify-functions description says:

| Either there are no potentially unfortified functions called by any
| routines, all unfortified calls have already been fully validated at
| compile-time, or the package was not built with the default Debian
| compiler flags defined by dpkg-buildflags

One of the first two cases seems to often be true for a lot of C++
code.

I thought I read ages ago about an idea to record the hardening flags as
notes in the compiled files, which seemed a much more satisfactory
approach, but I guess nothing ever came of it.

Cheers,
Olly

Bug#921136: lintian: hardening-no-fortify-functions possible false positive

[Scott Talbert]

On Wed, 30 Oct 2019, Olly Betts wrote:


The same issue applies to memcpy() which is why it's deliberately from
lintian's list:

https://sources.debian.org/src/lintian/2.31.0/data/binaries/hardened-functions/?hl=6#L6

Presumably wmemcpy() is simply much less widely used than memcpy(), and
that's the only reason it's not also omitted already.


Thanks for the details, Olly.  So, what you're saying is that wmemcpy 
should be excluded from hardened-functions?


Thanks,
Scott

Bug#943744: caja: Cannot move file to Trash, do you want to delete immediately?

[scott092707]

Having done some investigating, I find that in 4 previous distros I have 
installed (all Lubuntu),
none has had root:root as owners of  ~/.local/share/Trash

Since the contents of the files directory in that folder in my current Debian 
install are files
that would originally have been in a sub-directory of a system directory, they 
would have had to 
be trashed from a sudo-invoked FM; it is at least possible that the trashing 
caused ownership
to change to root:root.

However...

Most of the files I trash are in my personal directories, in my data partition, 
and would (should)
end up in the /data/.Trash-1000  trash, which as you can see, is owned by me.

Unless Caja was trying to trash the files by copying them from the data 
partition to the system
partition trash folder, I cannot see how it had difficulty trashing them.

Can anyone enlighten me?

Bug#824185: codeblocks: please build with squirrel3 package

[David Prévot]

Control: tag -1 = help

Hi Fabian,

On Fri, May 13, 2016 at 03:24:22PM +0200, Fabian Wolff wrote:

> codeblocks uses Squirrel [1] as a scripting language. A copy of it is
> included in codeblocks' source code, and it is compiled and linked
> into some executable within the codeblocks package.

They are actually using an old (2.2.5, compared to 3.1 in Debian)
version of Squirrel.

> Please add a patch to compile and link codeblocks against the Squirrel
> package to avoid this kind of redundancy for future releases.

Any help in the patching part would be welcome (maybe even appreciated
upstream).

Regards

David


signature.asc
Description: PGP signature

Bug#943730: marked as done (RFS: cowsay/3.03+dfsg2-7 [ITA] -- configurable talking cow)

[Paul Wise]

On Wed, Oct 30, 2019 at 5:03 AM Stephen Kitt wrote:

> I’ve pushed that to the games-team repository, and tagged the release. Please
> register a guest account on Salsa if you don’t already have one:
> https://signup.salsa.debian.org/
> Then you’ll be able to request access to the cowsay repository and/or the
> games team on https://salsa.debian.org/games-team

Why not use the existing cowsay repository?

https://salsa.debian.org/debian/cowsay

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#943556: ITP: roc-roct-thunk-interface -- Radeon Open Compute Thunk Interface

[Mo Zhou]

Hi,

I've added you to the ROCm team on salsa.

roct-thunk-interface packaging is already available
here: 
https://salsa.debian.org/rocm-team/roc-roct-thunk-interface

Could you please help me test it? I don't have amd
hardware to do the test. Several other libraries were
packaged as well.

Does it work with the amdgpu.ko shipped linux package?
Or we have to package the dkms kernel module?

On 2019-10-29 21:31, Timo Aaltonen wrote:
> On 26.10.2019 16.42, Mo Zhou wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Mo Zhou 
>> X-Debbugs-Cc: debian-de...@lists.debian.org
>>
>> * Package name: roc-roct-thunk-interface
>>   Version : 2.9.0
>>   Upstream Author : AMD
>> * URL :
>> https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface
>> * License : MIT/X11 and BSD-2
>>   Programming Lang: C
>>   Description : Radeon Open Compute Thunk Interface
>>
>> Will be maintained under ROCm team.
>>
> 
> dupe of 933766, but you keep this one

Bug#943810: -d won't stop journalctl messages

[積丹尼 Dan Jacobson]

Package: isc-dhcp-server
Version: 4.4.1-2
Severity: wishlist
File: /usr/share/man/man8/dhcpd.8.gz

Man page says:

-d  Send log messages to the standard error descriptor. This can be useful
for debugging, and also at sites where a complete log of all dhcp
activity must be kept but syslogd is not reliable or otherwise cannot be
used. Normally, dhcpd will log all output using the syslog(3) function
with the log facility set to LOG_DAEMON. Note that -d implies -f (the
daemon will not fork itself into the background).

But it should also say:
"Using -d won't stop messages also going to journalctl though."
"You just get an extra copy of them on STDERR."

Proof:
# journalctl -f &
# dhcpd -f -d -cf /dev/null xyz

Bug#943809: ITP: ruby-chunky-png -- Pure ruby library for read/write, chunk-level access to PNG files

[Samyak Jain]

Package: wnpp
Severity: wishlist
Owner: Samyak Jain 

* Package name: ruby-chunky-png
  Version : 1.3.11
  Upstream Author : 2010-2019, Willem van Bergen 
* URL : https://github.com/wvanbergen/chunky_png
* License : Expat
  Programming Lang: Ruby
  Description : Pure ruby library for read/write, chunk-level
access to PNG files

This pure Ruby library can read and write PNG images without depending
 on an external image library, like RMagick. It tries to be memory
 efficient and reasonably fast.
 .
 It supports reading and writing all PNG variants that are defined in the
 specification, with one limitation: only 8-bit color depth is supported.
 It supports all transparency, interlacing and filtering options the PNG
 specifications allows. It can also read and write textual metadata from
 PNG files. Low-level read/write access to PNG chunks is also possible.
 .
 This library supports simple drawing on the image canvas and simple
 operations like alpha composition and cropping. Finally, it can import
 from and export to RMagick for interoperability.
 .
 Also, have a look at OilyPNG at http://github.com/wvanbergen/oily_png.
 OilyPNG is a drop in mixin module that implements some of the
 ChunkyPNG algorithms in C, which provides a massive speed boost to
 encoding and decoding.

It is a dependency for diaspora and hence needs to be packaged.

Thanks,
Samyak Jain

Bug#943804: error message says missing subnet declaration for down interface

[積丹尼 Dan Jacobson]

Package: isc-dhcp-server
Version: 4.4.1-2
Severity: minor

This error message is wrong:

No subnet declaration for wlp2s0b1 (no IPv4 addresses).
** Ignoring requests on wlp2s0b1.  If this is not what
   you want, please write a subnet declaration
   in your dhcpd.conf file for the network segment
   to which interface wlp2s0b1 is attached. **

Proof:
$ make dhcpd #will produce this message
$ make w r dhcpd #will not produce this message, and work fine.

The error is the interface is not up, not that the dhcpd.conf needs to
be changed!

W=wlp2s0b1
I=192.168.1
E=bla
w:
rfkill unblock wifi
ip link set $W down
iw $W set type ibss
ip link set $W up
: ip link show $W
iw $W ibss join $E 2462
r:
ip address flush dev $W
ip addr add $I/24 broadcast + dev $W
dhcp:/tmp/dhcpd.conf
dhcpd -f -d -cf $? $W
/tmp/dhcpd.conf:Makefile
> $@ echo subnet $I.0 netmask 255.255.255.0 { range $I.10 $I.250\; }

Bug#943803: mention if max-lease-time is minutes, seconds, or hours

[積丹尼 Dan Jacobson]

Package: isc-dhcp-server
Version: 4.4.1-2
Severity: wishlist
File: /usr/share/man/man5/dhcpd.conf.5.gz

On man dhcpd.conf: true, analyzing
   max-lease-time 28800;
$ expr 28800 / 60 / 60
8

reveals it is probably in seconds, but it would be best to mention on
the man page.

Yes there are some indirect hints.

(The dhcpd man page is much clearer.)

Bug#943805: Document proper way to stop the daemon

[積丹尼 Dan Jacobson]

Package: isc-dhcp-server
Version: 4.4.1-2
Severity: wishlist
File: /usr/share/man/man8/dhcpd.8.gz

The dhcpd man page says tons about how to start it,
but not one peep about how one should stop it.
Sure, kill(1) perhaps, but one wonders what indeed the authors had in mind.

Bug#943808: Document why devices disappear from the list upon block

[積丹尼 Dan Jacobson]

Package: rfkill
Version: 2.34-0.1

Odd, blocking sometimes means zapping?

# rfkill
ID TYPE  DEVICE SOFT  HARD
 0 wlan  ideapad_wlan  unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 bluetooth hci0  unblocked unblocked
 3 wlan  phy0blocked unblocked
# rfkill block bluetooth
# rfkill
ID TYPE  DEVICE SOFT  HARD
 0 wlan  ideapad_wlan  unblocked unblocked
 1 bluetooth ideapad_bluetooth   blocked unblocked
 3 wlan  phy0blocked unblocked

Perhaps mention what is going on on the man page.

Bug#943807: ^C on -f ends so abruptly that there isn't even a message

[積丹尼 Dan Jacobson]

Package: isc-dhcp-server
Version: 4.4.1-2
Severity: minor

# dhcpd -f -d -cf /tmp/dhcpd.conf wlp2s0b1
...
Config file: /tmp/dhcpd.conf
Database file: /var/lib/dhcp/dhcpd.leases
PID file: /var/run/dhcpd.pid
Wrote 0 leases to leases file.
Listening on LPF/wlp2s0b1/08:3e:8e:aa:65:d1/192.168.1.0/24
Sending on   LPF/wlp2s0b1/08:3e:8e:aa:65:d1/192.168.1.0/24
Sending on   Socket/fallback/fallback-net
Server starting service.

OK that's great.

However if one then hits ^C.

1. There is not even a peep. No message that the service is ending. Not
on STDERR, not in journalctl.

(2. The service indeed ends (pidof dhcpd finds none), however the pid
files aren't cleaned up. Perhaps do that.)

Same problem with hangup,
# killall -1 dhcpd

I'm saying that there are tons of messages saying it is starting, but
not even one saying it is ending.

Bug#943806: Mention what is the new output format

[積丹尼 Dan Jacobson]

Package: rfkill
Version: 2.34-0.1
Severity: minor
File: /usr/share/man/man8/rfkill.8.gz

We read

   The command "list" output format is deprecated and maintained for
   backward compatibility only. The new output format is the default
   when no command is specified or when the option --output is used.

OK, but shouldn't the man page mention what the "new output format" is?

Bug#943725: calibre: Error when connecting Kobo

[Norbert Preining]

forwarded 943725 https://bugs.launchpad.net/calibre/+bug/1850571
thanks

On Mon, 28 Oct 2019, Remi Vanicat wrote:
> '<' not supported between instances of 'NoneType' and 'NoneType'

Confirmed, same with my Kobo. Forwarded to upstream.

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#943623: Any idea how to fix this?

[Shmerl]

This issue currently breaks building Mesa master with llvm10 snapshot from
http://apt.llvm.org/unstable (in Debian testing).

Bug#943802: piglit: Please add completions/bash/piglit from source

[Witold Baryluk]

Package: piglit
Version: 0~git20180515-62ef6b0db-1
Severity: normal

Dear Maintainer,

piglit sources do have completions/bash/piglit which should be installed
into /etc/bash_completion.d/piglit to enable piglit bash completion.

Thank you.



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages piglit depends on:
ii  libc62.29-2
ii  libdrm-intel12.4.99-1
ii  libdrm2  2.4.99-1
ii  libegl1  1.1.0-1+b1
ii  libgbm1  19.2.1-1
ii  libgcc1  1:9.2.1-15
ii  libgl1   1.1.0-1+b1
ii  libstdc++6   9.2.1-15
ii  libwaffle-1-01.6.0-2
ii  libwayland-client0   1.17.0-1
ii  libwayland-egl1  1.17.0-1
ii  libx11-6 2:1.6.8-1
ii  libxcb-dri2-01.13.1-2
ii  libxcb1  1.13.1-2
ii  libxkbcommon00.8.4-1
ii  ocl-icd-libopencl1 [libopencl1]  2.2.12-2
ii  python3  3.7.5-1
ii  python3-mako 1.0.7+ds1-1
ii  python3-six  1.12.0-2

piglit recommends no packages.

piglit suggests no packages.

-- no debconf information

Bug#943801: speedtest-cli: Depends on python-pkg-resources, blocking removal of Python 2.

[Aaron Howell]

Package: speedtest-cli
Version: 2.1.2-1
Severity: normal

Debian is aiming to remove Python 2 from the next major distribution release. 
While speedtest-cli is packaged against python 3 and runs correctly, it 
continues to declare a dependency on python-pkg-resources as well as 
python3-pkg-resources, blocking the removal of Python 2 from systems where it 
is installed.
Please remove the dependency on python-pkg-resources.


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

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

Versions of packages speedtest-cli depends on:
ii  ca-certificates20190110
pn  python-pkg-resources   
ii  python33.7.5-2
ii  python3-pkg-resources  41.4.0-1

speedtest-cli recommends no packages.

speedtest-cli suggests no packages.

-- no debconf information

Bug#921136: lintian: hardening-no-fortify-functions possible false positive

[Olly Betts]

Control: tags -1 -moreinfo

On Sat, Feb 16, 2019 at 12:26:36AM +0100, Chris Lamb wrote:
> I will thus leave this bug as "moreinfo" awaiting input from others.

What's presumably happening here is that the size of the destination
buffer and size of the copy are known, so it's clear at compile time
that the compile can't overflow.

E.g.:

$ cat wmemcpy-test.cc
#include 

wchar_t buf[10];
void f(const wchar_t* p, int n) {
#ifdef FIXED_LENGTH
(void)n;
wmemcpy(buf, p, 6);
#else
wmemcpy(buf, p, n);
#endif
}
$ g++ -Wall -W -D_FORTIFY_SOURCE=2 -O2 -S wmemcpy-test.cc -o -
.file   "wmemcpy-test.cc"
.text
.p2align 4
.globl  _Z1fPKwi
.type   _Z1fPKwi, @function
_Z1fPKwi:
.LFB26:
.cfi_startproc
movslq  %esi, %rdx
movl$10, %ecx
movq%rdi, %rsi
leaqbuf(%rip), %rdi
jmp __wmemcpy_chk@PLT
.cfi_endproc
.LFE26:
.size   _Z1fPKwi, .-_Z1fPKwi
.globl  buf
.bss
.align 32
.type   buf, @object
.size   buf, 40
buf:
.zero   40
.ident  "GCC: (Debian 9.2.1-8) 9.2.1 20190909"
.section.note.GNU-stack,"",@progbits

But if the lengths are both known:

$ g++ -Wall -W -D_FORTIFY_SOURCE=2 -DFIXED_LENGTH -O2 -S wmemcpy-test.cc -o -
.file   "wmemcpy-test.cc"
.text
.p2align 4
.globl  _Z1fPKwi
.type   _Z1fPKwi, @function
_Z1fPKwi:
.LFB26:
.cfi_startproc
movq%rdi, %rsi
movl$6, %edx
leaqbuf(%rip), %rdi
jmp wmemcpy@PLT
.cfi_endproc
.LFE26:
.size   _Z1fPKwi, .-_Z1fPKwi
.globl  buf
.bss
.align 32
.type   buf, @object
.size   buf, 40
buf:
.zero   40
.ident  "GCC: (Debian 9.2.1-8) 9.2.1 20190909"
.section.note.GNU-stack,"",@progbits

The key difference here is:

<   jmp __wmemcpy_chk@PLT
---
>   jmp wmemcpy@PLT

The same issue applies to memcpy() which is why it's deliberately from
lintian's list:

https://sources.debian.org/src/lintian/2.31.0/data/binaries/hardened-functions/?hl=6#L6
 

Presumably wmemcpy() is simply much less widely used than memcpy(), and
that's the only reason it's not also omitted already.

Cheers,
Olly

Bug#943800: nmu: haveged_1.9.8-1

[Nicolas Braud-Santoni]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

nmu haveged_1.9.8-1 . amd64 . unstable . -m "Rebuild on buildd for transition 
to testing"

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAl243fsRHG5pY29vQGRl
Ymlhbi5vcmcACgkQ5vmO4pLV7MutfxAAkEeNig/0fuYbHBtoWbdAwtKLbQ9zexJ/
YmNEmcHeOd0/0SnZnl2tXOqNj6C4p/kQZNokytMI74qbIxLcixyL0wWfBADx3mmS
inEZxepZN2Romu/ACcEzEGYdxbBVNRCFeiC12vTzdijBRw5RiCfc8/BxWUWlRzoW
8ROR7BaTsWhEAUM4QMS6yCKh0bTDQknW9oOXPza4FVKjGu/fDbJHhOlPqNJlpol3
EgGcNFRrlrC5MzrfUBRY5yqh3x3D+1Yp+57Wjk9J15tRP9PKor0C0Cu2y9cyiERv
aSZPE/VifInXHZXUQmUHxu8ZKdMpgfwNGUXGZ9ZBpVXYYMvE9/G7oH5f0G90SSNp
Ua9kJinXVlbWVU1/sERec2gOAJvTnXjCoSqhE1tnU71tR2MaCLlpvtyWJOtUisEN
GWKPX8VvLWcrsROvUIuH+pyLTn/WoMc4YC0X+Xs/julPhcWeyS2HxbqaOJ2ytJo7
u78N/QWvVLaeaANp+iX6xeCALGxRE5IDfZ65JZ31l/2IHhSUuwXt7ZJ5Qu3aooZA
acrBeHGeEvDCatmrlozIuYLVp11Hx8eTfOFQtyzFfEUAsNrjLk528Bx6WoOLMTnZ
v/EmtSlpHay4GLeLxQFUGclonCZSiNNZkLr17df0ECXwE5V9WsixjvMNcj+Eplci
bCjaDx7jE4Q=
=H6bk
-END PGP SIGNATURE-

Bug#943799: piglit: Please add waffle-utils to Recommends

[Witold Baryluk]

Package: piglit
Version: 0~git20180515-62ef6b0db-1
Severity: normal

Dear Maintainer,

wflinfo is needed to run quick and all test sets.



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages piglit depends on:
ii  libc62.29-2
ii  libdrm-intel12.4.99-1
ii  libdrm2  2.4.99-1
ii  libegl1  1.1.0-1+b1
ii  libgbm1  19.2.1-1
ii  libgcc1  1:9.2.1-15
ii  libgl1   1.1.0-1+b1
ii  libstdc++6   9.2.1-15
ii  libwaffle-1-01.6.0-2
ii  libwayland-client0   1.17.0-1
ii  libwayland-egl1  1.17.0-1
ii  libx11-6 2:1.6.8-1
ii  libxcb-dri2-01.13.1-2
ii  libxcb1  1.13.1-2
ii  libxkbcommon00.8.4-1
ii  ocl-icd-libopencl1 [libopencl1]  2.2.12-2
ii  python3  3.7.5-1
ii  python3-mako 1.0.7+ds1-1
ii  python3-six  1.12.0-2

piglit recommends no packages.

piglit suggests no packages.

-- no debconf information

Bug#943798: ld.so: old Arm ABI detection patch causing problems, time to remove?

[Steve McIntyre]

On Wed, Oct 30, 2019 at 12:17:20AM +, Steve McIntyre wrote:
>Source: glibc
>Version: 2.28-10
>Severity: important
>
>Hi folks,
>
>It looks like my old Arm ABI detection patch for ld.so is causing
>problems for people using LLVM. I've been contacted by a developer,
>referring to a mailing list thread:
>
>  https://lists.llvm.org/pipermail/llvm-dev/2019-October/135993.html

Forgot to add: there's an llvm-objcopy patch under discussion here:

  https://reviews.llvm.org/D69188

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Is there anybody out there?

Bug#943798: ld.so: old Arm ABI detection patch causing problems, time to remove?

[Steve McIntyre]

Source: glibc
Version: 2.28-10
Severity: important

Hi folks,

It looks like my old Arm ABI detection patch for ld.so is causing
problems for people using LLVM. I've been contacted by a developer,
referring to a mailing list thread:

  https://lists.llvm.org/pipermail/llvm-dev/2019-October/135993.html

It looks like the LLVM version of strip is more aggressive than the
GNU binutils version, and this is causing problems - it's stripping
the .ARM.attributes data and that's causing problems with our extra
checks for the Tag_ABI_VFP_args setting. Whether that's a valid thing
to do or not is an argument for another day, I think... However,
checking with the bzip2 binaries that the reporter provided I can see
that they have the right ABI flag in the ELF header but we're still
running the extra ABI check:

(sid-armhf)steve@mjolnir:~/abi$ LD_PRELOAD=./libbz2.so.all ./bzip2 
ERROR: ld.so: object './libbz2.so.all' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
bzip2: I won't write compressed data to a terminal.
bzip2: For help, type: `bzip2 --help'.

(sid-armhf)steve@mjolnir:~/abi$ readelf -a libbz2.so.all | grep "^  Flags"
  Flags: 0x5000400, Version5 EABI, hard-float ABI

I think this is wrong, and I can't think of why I didn't find this
earlier when I was working in this area. :-/

So: I think we have two sensible options:

1. I find time now to fix up ld.so to only do the extra check here if
   we think it's needed

OR

2. Just remove the patch for extra check here - it was always the plan
   that this would go away after a while once people were unlikely to
   still be running binaries from the pre ELF-header toolchains.

Checking history, I can see that the binutils changes for those ELF
header changes landed in Debian back in Nov 2012. (Wow, time
flies!). Given that, I'd now be strongly in favour of just dropping the
patch in

debian/patches/arm/unsubmitted-ldso-abi-check.diff

as it's now safely obsolete. What do others think?

-- System Information:
Debian Release: 10.1
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#802937: firmware-linux-nonfree: radeon tahiti firmware fails to load

[Giuseppe V]

Package: firmware-amd-graphics
Followup-For: Bug #802937

Dear Maintainer,

I installed this package and when I reboot the machine, I got a blue tinted
screen. After trying everything, I tested the gamma and when  I reset it, the
screen retourned at normal colors. However, many icons and images are still in
low quality than before.

My GPU is a Sapphire Vapor-X R9 280X

Apparently, logs shows no errors:

DMESG:

[1.124900] [drm] radeon kernel modesetting enabled.
[1.124932] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 0:
0xe000 -> 0xefff
[1.124933] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 2:
0xf000 -> 0xf003
[1.124934] radeon :01:00.0: vgaarb: deactivate vga console
[1.126929] radeon :01:00.0: VRAM: 3072M 0x -
0xBFFF (3072M used)
[1.126929] radeon :01:00.0: GTT: 2048M 0xC000 -
0x00013FFF
[1.126979] [drm] radeon: 3072M of VRAM memory ready
[1.126979] [drm] radeon: 2048M of GTT memory ready.
[1.127008] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_pfp.bin
[1.127016] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_me.bin
[1.127024] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_ce.bin
[1.127032] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_rlc.bin
[1.127044] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_mc.bin
[1.127058] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_smc.bin
[1.131828] [drm] radeon: dpm initialized
[1.131866] radeon :01:00.0: firmware: direct-loading firmware
radeon/TAHITI_uvd.bin
[1.131887] radeon :01:00.0: firmware: direct-loading firmware
radeon/TAHITI_vce.bin
[1.141253] radeon :01:00.0: WB enabled
[1.141255] radeon :01:00.0: fence driver on ring 0 use gpu addr
0xcc00 and cpu addr 0xc77d13af
[1.141255] radeon :01:00.0: fence driver on ring 1 use gpu addr
0xcc04 and cpu addr 0x4d8e6bbe
[1.141256] radeon :01:00.0: fence driver on ring 2 use gpu addr
0xcc08 and cpu addr 0x22eaff4f
[1.141257] radeon :01:00.0: fence driver on ring 3 use gpu addr
0xcc0c and cpu addr 0x2f3acd6b
[1.141257] radeon :01:00.0: fence driver on ring 4 use gpu addr
0xcc10 and cpu addr 0x963f94c9
[1.141449] radeon :01:00.0: fence driver on ring 5 use gpu addr
0x00075a18 and cpu addr 0x568a4f9f
[1.161386] radeon :01:00.0: fence driver on ring 6 use gpu addr
0xcc18 and cpu addr 0xa913cb9c
[1.161386] radeon :01:00.0: fence driver on ring 7 use gpu addr
0xcc1c and cpu addr 0xf32f8e7d
[1.161389] radeon :01:00.0: radeon: MSI limited to 32-bit
[1.161419] radeon :01:00.0: radeon: using MSI.
[1.161433] [drm] radeon: irq initialized.
[3.412783] fbcon: radeondrmfb (fb0) is primary device
[3.455999] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[3.471042] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on
minor 0
[   22.538983] radeon_dp_aux_transfer_native: 158 callbacks suppressed

Thank you for the help




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

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

firmware-amd-graphics depends on no packages.

firmware-amd-graphics recommends no packages.

Versions of packages firmware-amd-graphics suggests:
ii  initramfs-tools  0.135

Bug#943796: gcc-9: FTBFS on hppa - ld cannot find -latomic

[Matthias Klose]

On 29.10.19 23:26, John David Anglin wrote:

/usr/bin/hppa-linux-gnu-ld: cannot find -latomic
collect2: error: ld returned 1 exit status


yes, fixed in the VCS

Bug#943526: [Pkg-javascript-devel] Bug#943526: Bug#943526: Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Jonas Smedegaard]

Quoting Julien Puydt (2019-10-29 22:11:34)
> Le mardi 29 octobre 2019 à 12:45 +0100, Xavier a écrit :
> > Control: reassign -1 node-typescript
> > 
> > Le 29/10/2019 à 08:29, Julien Puydt a écrit :
> > > Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit :
> > > > Hi JS team,
> > > > 
> > > > why did node-typescript have such link ?
> > > > 
> > > >   /usr/share/nodejs/tslib -> typescript/lib
> > > > 
> > > > This creates this conflict.
> > > > 
> > > 
> > > Well, isn't node-typescript supposed to provide that lib?
> > > 
> > > JP
> > 
> > When installing using `npm install typescript`, there is no
> > "node_modules/tslib", so there is no reason to provide such link IMO.
> > 
> 
> Would that break anything if node-typescript didn't provide the link?
> 
> I don't remember why I added it, but I most certainly didn't add it
> just like this...

Well, did you write a sensible commit message to go along with your 
change?

If not then I think we wil never know (at least I cannot read your 
mind).


 - Jonas

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

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


signature.asc
Description: signature

Bug#943668: Getting "Can't update Chromium" notifications

[Tomasz]

Package: chromium
Version: 76.0.3809.100-1~deb10u1
Followup-For: Bug #943668

Dear Maintainer,

Cuurent chromum browser build pops up a notification saying

"Can't update Chromium. Chromium couldn't update to the latest version, so 
you're missing out on latest features and seurity fixes" 

Can you please address this as it is very distracying.

Tomasz


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

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

Versions of packages chromium depends on:
ii  chromium-common  76.0.3809.100-1~deb10u1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.3.0-6
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.4-1~deb10u1
ii  libavformat587:4.1.4-1~deb10u1
ii  libavutil56  7:4.1.4-1~deb10u1
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcups2 2.2.10-6+deb10u1
ii  libdbus-1-3  1.12.16-1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-2+deb10u1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u1
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.1-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1+deb10u1
ii  libopenjp2-7 2.3.0-2
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-7~deb10u1
ii  libpangocairo-1.0-0  1.42.4-7~deb10u1
ii  libpci3  1:3.5.2-1
ii  libpng16-16  1.6.36-6
ii  libpulse012.2-4+deb10u1
ii  libre2-5 20190101+dfsg-2
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.3.0-6
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2.1~deb10u1
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  76.0.3809.100-1~deb10u1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox 76.0.3809.100-1~deb10u1
ii  fonts-liberation 1:1.07.4-9
ii  libgl1-mesa-dri  18.3.6-2
ii  libu2f-udev  1.1.9-1
ii  notification-daemon  3.20.0-4
ii  upower   0.99.10-1

Versions of packages chromium-sandbox depends on:
ii  libatomic1  8.3.0-6
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libstdc++6  8.3.0-6

-- no debconf information

Bug#943797: netcfg: surprising behavior on bogus wifi password

[Samuel Thibault]

Package: netcfg
Version: 1.160
Severity: normal

Hello,

* start d-i
* get wireless board detected
* choose an ESSID among the list proposed by netcfg
* type a password which is not the proper password

Result: netcfg prompts for a manual ESSID without even making the
prefilled value the ESSID that was chosen among the list.

This is surprising, I was about to type the password again before
realizing that it's the ESSID which is being asked.

Expected result: either (by preference order):
- netcfg should prompt for the password again (that's really what I
  would have expected)
- netcfg should get back the the ESSID list (and one can choose "manual
  selection" there)
- netcfg should prompt for manual ESSID, but at the very least prefill
  it with what was chosen previously.

Samuel

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
X-Favorit-Cartoon: Calvin and Hobbes
 -+- Mail header of Wim van Dorst -+-

Bug#943796: gcc-9: FTBFS on hppa - ld cannot find -latomic

[John David Anglin]

Source: gcc-9
Version: 9.2.1-15
Severity: normal

Dear Maintainer,

The build failed with the following error:

make[6]: Entering directory '/<>/build/hppa-linux-gnu/libgnatvsn'
/bin/mkdir -p '/<>/debian/tmp/usr/lib/ada/adalib/gnatvsn'
/usr/bin/install -c -m 444 .libs/*.ali 
'/<>/debian/tmp/usr/lib/ada/adalib/gnatvsn'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib'
 /bin/bash ./libtool   --mode=install /usr/bin/install -c   libgnatvsn.la 
'/<>/debian/tmp/usr/lib'
libtool: install: warning: relinking `libgnatvsn.la'
libtool: install: (cd /<>/build/hppa-linux-gnu/libgnatvsn; 
/bin/bash /<>/build/hppa-linux-gnu/libgnatvsn/libtool  --tag CC 
--mode=relink /<>/build/./gcc/xgcc -B/<>/build/./gcc/ 
-B/usr/hppa-linux-gnu/bin/ -B/usr/hppa-linux-gnu/lib/ -isystem 
/usr/hppa-linux-gnu/include -isystem /usr/hppa-linux-gnu/sys-include -isystem 
/<>/build/sys-include -fchecking=1 -mdisable-indexing -g -O2 
-version-info 9 -Wl,--no-allow-shlib-undefined -Wl,--no-copy-dt-needed-entries 
-Wl,--no-undefined -Wl,-z,relro -o libgnatvsn.la -rpath /usr/lib 
libgnatvsn_la-link.lo libgnatvsn_la-version.lo -L../libada/adalib -lgnat-9 
aspects.lo atree.lo binderr.lo butil.lo casing.lo csets.lo debug.lo einfo.lo 
elists.lo fname.lo get_scos.lo gnatvsn.lo krunch.lo lib.lo namet.lo nlists.lo 
opt.lo output.lo put_scos.lo repinfo.lo repinfo-input.lo scans.lo scos.lo 
sem_aux.lo sinfo.lo sinput.lo sinput-c.lo stand.lo stringt.lo table.lo 
tempdir.lo tree_in.lo tree_io.lo types.lo uintp.lo uname.lo urealp.lo 
widechar.lo xutil.lo snames.lo alloc.lo hostparm.lo rident.lo 
.././libatomic/libatomic.la -inst-prefix-dir /<>/debian/tmp)
libtool: relink: /<>/build/./gcc/xgcc 
-B/<>/build/./gcc/ -B/usr/hppa-linux-gnu/bin/ 
-B/usr/hppa-linux-gnu/lib/ -isystem /usr/hppa-linux-gnu/include -isystem 
/usr/hppa-linux-gnu/sys-include -isystem /<>/build/sys-include   
-fchecking=1 -shared  -fPIC -DPIC  .libs/libgnatvsn_la-link.o 
.libs/libgnatvsn_la-version.o .libs/aspects.o .libs/atree.o .libs/binderr.o 
.libs/butil.o .libs/casing.o .libs/csets.o .libs/debug.o .libs/einfo.o 
.libs/elists.o .libs/fname.o .libs/get_scos.o .libs/gnatvsn.o .libs/krunch.o 
.libs/lib.o .libs/namet.o .libs/nlists.o .libs/opt.o .libs/output.o 
.libs/put_scos.o .libs/repinfo.o .libs/repinfo-input.o .libs/scans.o 
.libs/scos.o .libs/sem_aux.o .libs/sinfo.o .libs/sinput.o .libs/sinput-c.o 
.libs/stand.o .libs/stringt.o .libs/table.o .libs/tempdir.o .libs/tree_in.o 
.libs/tree_io.o .libs/types.o .libs/uintp.o .libs/uname.o .libs/urealp.o 
.libs/widechar.o .libs/xutil.o .libs/snames.o .libs/alloc.o .libs/hostparm.o 
.libs/rident.o   -L/<>/build/hppa-linux-gnu/libada/adalib -lgnat-9 
-L/<>/debian/tmp/usr/lib -L/usr/lib -latomic  -mdisable-indexing 
-Wl,--no-allow-shlib-undefined -Wl,--no-copy-dt-needed-entries 
-Wl,--no-undefined -Wl,-z -Wl,relro   -pthread -Wl,-soname -Wl,libgnatvsn.so.9 
-o .libs/libgnatvsn.so.9.0.0
/usr/bin/hppa-linux-gnu-ld: cannot find -latomic
collect2: error: ld returned 1 exit status
libtool: install: error: relink `libgnatvsn.la' with the above command before 
installing it
make[6]: *** [Makefile:552: install-libLTLIBRARIES] Error 1

The hppa architecture has a non empty libatomic that needs to be linked
against for atomic support.

Full log is here:
https://buildd.debian.org/status/fetch.php?pkg=gcc-9&arch=hppa&ver=9.2.1-15&stamp=1572353329&raw=0

Regards,
Dave Anglin


-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

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

-- no debconf information

Bug#943724: lintian: internal error in Lintian::files::empty_package::_set_is_dummy

[Thorsten Glaser]

Package: lintian
Version: 2.31.0
Followup-For: Bug #943724

I’ve just hit this as well, but only in cowbuilder; I cannot seem
to reproduce it outside of the chroot. Perhaps a missing dependency
(or (recursive) Recommends) that’s installed outside but not inside?

N: Processing binary package fonts-campania (version 2.009-1, arch all) ...
[…]
Usage: Lintian::files::empty_package::_set_is_dummy(self, newvalue) at 
/usr/share/lintian/checks/files/empty-package.pm line 42.
internal error: cannot run files check on package 
binary:fonts-campania/2.009-1/all
warning: skipping check of binary:fonts-campania/2.009-1/all
N: Finished processing group campania/2.009-1

Both the host system and the cowbuilder chroot are freshly dist-upgraded sid.

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

Kernel: Linux 5.3.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages lintian depends on:
ii  binutils 2.33.1-2
ii  bzip21.0.8-2
ii  diffstat 1.62-1+b1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.37-6
ii  gettext  0.19.8.1-9
ii  gpg  2.2.17-3
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b2
ii  libarchive-zip-perl  1.67-1
ii  libberkeleydb-perl   0.62-1+b1
ii  libcapture-tiny-perl 0.48-1
ii  libcgi-pm-perl   4.44-1
ii  libclass-accessor-perl   0.51-1
ii  libclone-perl0.41-1+b2
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.74-1
ii  libipc-run-perl  20180523.0-1
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmldbm-perl2.05-2
ii  libmoo-perl  2.003004-2
ii  libpath-tiny-perl0.108-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3000-2
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.004004-1
ii  liburi-perl  1.76-1
ii  libxml-simple-perl   2.25-1
ii  libyaml-libyaml-perl 0.80+repack-2+b1
ii  man-db   2.9.0-1
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.0-9
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
ii  binutils-multiarch 2.33.1-2
ii  libhtml-parser-perl3.72-3+b4
pn  libtext-template-perl  

-- no debconf information

Bug#943795: installation-reports: Does not automatically load firmware from ext4 stick

[Samuel Thibault]

Package: installation-reports
Severity: normal

Hello,

While trying to debug something about wifi during d-i, I actually had
an issue: I had put the content of my /lib/firmware directory on a USB
stick, which happened to be formatted as ext4. d-i was not able to read
from it, even if the ext4-modules udeb was loaded. I had to type
"modprobe ext4" by hand to get firmware files loaded from the stick.

Samuel

-- Package-specific info:

Boot method: USB stick
Image version: debian-10.1.0-amd64-netinst.iso
Date: 

Machine: DELL XPS 13 9370
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Booted with 2 USB sticks: one with the d-i netinst image, the other one
formatted as ext4 with the content of /lib/firmware copied to it.

Let it discover network devices, tell it to indeed load firmware from
removable media. It doesn't find anything.

Workaround:

right after the udeb module loading step, switch to VT2 to run
"modprobe ext4" there, go back to VT1. When telling it to load firmware
from removable media, it does find them.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20180610"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux function 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5914] 
(rev 08)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:5917] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation 
Skylake Processor Thermal Subsystem [8086:1903] (rev 08)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP 
USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:15.0 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:15.1 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Sunrise 
Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation Device [8086:9d12] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI 
Express Root Port #5 [8086:9d14] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI 
Express Root Port #9 [8086:9d18] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d4e] 
(rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise 
Point-LP PMC [8086:9d21] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d71] 
(rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus 
[8086:9d23] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07e6]
lspci -knn: 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. 
RTS525A PCI E

Bug#938804: libvtk6.3 still depends on libpython2.7

[Aleksey Kliger]

Package: libvtk6.3
Version: 6.3.0+dfsg2-4
Followup-For: Bug #938804



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

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

Versions of packages libvtk6.3 depends on:
ii  libavcodec587:4.1.4-1+b3
ii  libavformat58   7:4.1.4-1+b3
ii  libavutil56 7:4.1.4-1+b3
ii  libc6   2.29-2
ii  libexpat1   2.2.9-1
ii  libfontconfig1  2.13.1-2+b1
ii  libfreetype62.10.1-2
ii  libgcc1 1:9.2.1-8
ii  libgdal20 [gdal-abi-2-4-0]  2.4.2+dfsg-2
ii  libgl1  1.1.0-1+b1
ii  libgl2ps1.4 1.4.0+dfsg1-2
ii  libhdf5-openmpi-103 1.10.4+repack-10
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  libjsoncpp1 1.7.4-3+b1
ii  libmariadb3 1:10.3.18-1
ii  libnetcdf-c++4  4.2-11+b1
ii  libnetcdf13 1:4.6.2-1+b1
ii  libodbc12.3.6-0.1+b1
ii  libogg0 1.3.2-1+b1
ii  libopenmpi3 3.1.3-11
ii  libpng16-16 1.6.37-1
ii  libpq5  12.0-1+b1
ii  libpython2.72.7.17-1
ii  libsqlite3-03.30.1-1
ii  libstdc++6  9.2.1-8
ii  libswscale5 7:4.1.4-1+b3
ii  libtheora0  1.1.1+dfsg.1-15
ii  libtiff54.0.10+git191003-1
ii  libx11-62:1.6.8-1
ii  libxml2 2.9.4+dfsg1-7+b3
ii  libxt6  1:1.1.5-1+b3
ii  zlib1g  1:1.2.11.dfsg-1+b1

libvtk6.3 recommends no packages.

Versions of packages libvtk6.3 suggests:
pn  mpi-default-bin  

-- no debconf information

Bug#943794: nvidia driver debain buster unresolved dependencies

[hardkorek]

Package: nvidia-driver


Version: 418.74-1


root@dionizos:/home/korek/Pobrane/DaVinci_Resolve_16.1_Linux# apt-get
install nvidia-driver
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności   
Odczyt informacji o stanie... Gotowe
Nie udało się zainstalować niektórych pakietów. Może to oznaczać,
że zażądano niemożliwej sytuacji lub użyto dystrybucji niestabilnej,
w której niektóre pakiety nie zostały jeszcze utworzone lub
przeniesione
z katalogu Incoming ("Przychodzące").
Następujące informacje mogą pomóc rozwiązać sytuację:

Następujące pakiety mają niespełnione zależności:
 nvidia-driver : Wymaga: nvidia-driver-libs (= 418.74-1) ale nie
zostanie zainstalowany lub
 nvidia-driver-libs-nonglvnd (= 418.74-1) ale
nie zostanie zainstalowany
E: Nie udało się naprawić problemów, zatrzymano uszkodzone pakiety.

I have configured bumblebee with noveaou. Need to switch to nvidia so
trying to install nvidia-driver according to a wiki(no entry for buster
right now so I'm assuming that newest one should work). 

My repositories are standard:
deb http://deb.debian.org/debian/ buster main contrib non-free
deb-src http://deb.debian.org/debian/ buster main contrib non-free

deb http://security.debian.org/debian-security buster/updates main
contrib non-free
deb-src http://security.debian.org/debian-security buster/updates main
contrib non-free

# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ buster-updates main contrib non-free
deb-src http://deb.debian.org/debian/ buster-updates main contrib non-
free

deb https://download.virtualbox.org/virtualbox/debian buster contrib
non-free


sources.list.d:
root@dionizos:/home/korek/Pobrane/DaVinci_Resolve_16.1_Linux# cat
/etc/apt/sources.list.d/megasync.list 
deb https://mega.nz/linux/MEGAsync/Debian_10.0/ ./
root@dionizos:/home/korek/Pobrane/DaVinci_Resolve_16.1_Linux# cat
/etc/apt/sources.list.d/signal-xenial.list 
deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
root@dionizos:/home/korek/Pobrane/DaVinci_Resolve_16.1_Linux# cat
/etc/apt/sources.list.d/vscode.list 
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be
lost.
deb [arch=amd64] http://packages.microsoft.com/repos/vscode stable main


no pinning configured

Bug#943556: ITP: roc-roct-thunk-interface -- Radeon Open Compute Thunk Interface

[Timo Aaltonen]

On 26.10.2019 16.42, Mo Zhou wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Mo Zhou 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: roc-roct-thunk-interface
>   Version : 2.9.0
>   Upstream Author : AMD
> * URL :
> https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface
> * License : MIT/X11 and BSD-2
>   Programming Lang: C
>   Description : Radeon Open Compute Thunk Interface
> 
> Will be maintained under ROCm team.
> 

dupe of 933766, but you keep this one


-- 
t

Bug#928525: Confirming

[gi1242+debianbugs]

Confirming I have this problem too. My /etc/sshguard/sshguard.conf has

LOGREADER="LANG=C /bin/journalctl -afb -p info -n1 -o cat SYSLOG_FACILITY=4 
SYSLOG_FACILITY=10"

The example provided by upstream has

LOGREADER="LANG=C journalctl -afb -p info -n1 -t sshd -t sendmail -o cat"

Changing it to this makes the problem go away. (Since I use postfix, I
used  "-t postfix/smtpd" instead of sendmail.)

GI

-- 
My wife told me I had to stop acting like a flamingo. So I had to put my
foot down.

Bug#943526: [Pkg-javascript-devel] Bug#943526: Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib

[Julien Puydt]

Le mardi 29 octobre 2019 à 12:45 +0100, Xavier a écrit :
> Control: reassign -1 node-typescript
> 
> Le 29/10/2019 à 08:29, Julien Puydt a écrit :
> > Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit :
> > > Hi JS team,
> > > 
> > > why did node-typescript have such link ?
> > > 
> > >   /usr/share/nodejs/tslib -> typescript/lib
> > > 
> > > This creates this conflict.
> > > 
> > 
> > Well, isn't node-typescript supposed to provide that lib?
> > 
> > JP
> 
> When installing using `npm install typescript`, there is no
> "node_modules/tslib", so there is no reason to provide such link IMO.
> 

Would that break anything if node-typescript didn't provide the link?

I don't remember why I added it, but I most certainly didn't add it
just like this...

JP

Bug#943793: libvncserver: CVE-2019-15681

[Salvatore Bonaccorso]

Source: libvncserver
Version: 0.9.11+dfsg-1.3
Severity: grave
Tags: security upstream
Control: found -1 0.9.11+dfsg-1.3~deb9u1

Hi,

The following vulnerability was published for libvncserver, severity
is choosen to be rather on safe side and issue has not been fully
checked/investigated for impact/attack vector.

CVE-2019-15681[0]:
| LibVNC commit before d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a contains
| a memory leak (CWE-655) in VNC server code, which allow an attacker to
| read stack memory and can be abused for information disclosure.
| Combined with another vulnerability, it can be used to leak stack
| memory and bypass ASLR. This attack appear to be exploitable via
| network connectivity. These vulnerabilities have been fixed in commit
| d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-15681
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15681

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#943792: ldc: Manual page for ldc(1) and ldc2(1) missed some flags documentation

[Witold Baryluk]

Package: ldc
Version: 1:1.17.0-2
Severity: normal

I noticed that ldc(1) and ldc2(1) manpages do miss some documentation for some 
flags:

Looking at ldc2 --help and at https://wiki.dlang.org/Using_LDC

there are some important flags that are missing in man page.

For example '-shared', '-betterC' and '-sanitize=' ones. But there are few more.

Also I noticed man page is quite old:

December 2009

   based on DMD v1.051 and llvm 2.6 (Wed Dec  2 17:39:53 2009)
   Copyright (c) 1999-2009 by Digital Mars and Tomas Lindquist Olsen
   written by Walter Bright and Tomas Lindquist Olsen D Language
   Documentation: http://www.digitalmars.com/d/1.0/index.html
   LDC Homepage: http://www.dsource.org/projects/ldc

That is quite not correct for current version of ldc.

PS. It also misses some new lines in that section.


Thank you.





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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages ldc depends on:
ii  libc6  2.29-2
ii  libgcc11:9.2.1-15
ii  libllvm8   1:8.0.1-3+b1
ii  libphobos2-ldc-shared-dev  1:1.17.0-2
ii  libstdc++6 9.2.1-15
ii  zlib1g 1:1.2.11.dfsg-1+b1

ldc recommends no packages.

ldc suggests no packages.

-- no debconf information

Bug#943605: libdate-holidays-de-perl 2.00-2+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 943605 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: libdate-holidays-de-perl
Version: 2.00-2+deb10u1

Explanation: mark International Childrens Day (Sep 20th) as a holiday in 
Thuringia from 2019 onwards

Bug#943606: libdate-holidays-de-perl 1.9-1+deb9u4 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 943606 = stretch pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: libdate-holidays-de-perl
Version: 1.9-1+deb9u4

Explanation: mark International Childrens Day (Sep 20th) as a holiday in 
Thuringia from 2019 onwards

Bug#943352: python-werkzeug 0.11.15+dfsg1-1+deb9u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 943352 = stretch pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: python-werkzeug
Version: 0.11.15+dfsg1-1+deb9u1

Explanation: ensure Docker containers have unique debugger PINs [CVE-2019-14806]

Bug#943339: python-werkzeug 0.14.1+dfsg1-4+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 943339 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: python-werkzeug
Version: 0.14.1+dfsg1-4+deb10u1

Explanation: ensure Docker containers have unique debugger PINs [CVE-2019-14806]

Bug#939354: capistrano 3.11.0-3+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 939354 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: capistrano
Version: 3.11.0-3+deb10u1

Explanation: fix failure to remove old releases when there were too many

Bug#942024: openjpeg2 2.1.2-1.1+deb9u4 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 942024 = stretch pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: openjpeg2
Version: 2.1.2-1.1+deb9u4

Explanation: fix heap overflow [CVE-2018-21010], integer overflow 
[CVE-2018-20847] and division by zero [CVE-2016-9112]

Bug#942524: graphite-web 1.1.4-3+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 942524 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: graphite-web
Version: 1.1.4-3+deb10u1

Explanation: remove unused "send_email" function [CVE-2017-18638]; avoid hourly 
error in cron with no whisper database

Bug#942356: spf-engine 2.9.1-0+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 942356 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: spf-engine
Version: 2.9.1-0+deb10u1

Explanation: new upstream stable release; fix sysvinit support

Bug#942177: dkimpy-milter 1.0.2-1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 942177 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: dkimpy-milter
Version: 1.0.2-1

Explanation: new upstream stable release; fix sysvinit support; catch more 
ascii encoding errors to improve resilience against bad data; fix message 
extraction so that signing in the same pass through the milter as verifying 
works correctly

Bug#942209: cron 3.0pl1-134+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 942209 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: cron
Version: 3.0pl1-134+deb10u1

Explanation: stop using obsolete SELinux API

Bug#943791: general: laptop HP 15_bw0xx does not power-off properly

[Christian Quentin]

Package: general
Severity: normal

Dear Maintainer,

* when I ask Debian to stop (from Gnome), the shutdown sequence seems to follow
the usual steps, the a blank screen appears.The screen is not completely off.
The PC does not power-off.
* As the PC does not stop, I have to press the power button 10 seconds which
does not seem to be the best way to stop a computer.
* I would expect the shutdown sequence to power-off the computer completely.
* Hint : shutting down Windows 10 (also present on this computer) works fine.

Best regards and thanks for the fabulous work you do



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

Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#934927: transition: libgit2

[Paul Gevers]

Hi,

On Sat, 12 Oct 2019 17:30:27 +0200 Emilio Pozuelo Monfort
 wrote:> With only libgit-raw-perl and julia
remaining, which aren't key packages have
> one and none (resp) rdeps, and with all the time that has passed since their
> bugs were reported with no action from the maintainers so far, I think we can 
> go
> ahead with this and have those removed from testing if necessary.

Is there any intent to start the libgit2 transition soon? If not, I'd
like to start an other transition, but I don't want the two to intermix.

Paul

Bug#941018: ibus 1.5.21-1 does not work with qt5 applications

[Gunnar Hjalmarsson]

On 2019-10-27 16:32, Boyuan Yang wrote:

While we are waiting for the response of glib upstream (no response
from glib authors yet), I'd like to mention that current ibus in both
stable-security and Testing/Sid are already broken. With next stable
point release, we would break everyone's ibus whenever they are using
Debian 10. As pointed out in
https://lists.debian.org/debian-input-method/2019/10/msg00047.html ,
there are already some bug reports against qt5-based software.


Simon's glib MR has now been reviewed and committed upstream.

--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Bug#943787: mailutils: Please rebuild package with source-only upload

[Jordi Mallach]

El dt. 29 de 10 de 2019 a les 15:50 -0400, en/na Boyuan Yang va
escriure:
> Your latest upload for package mailutils in Debian (1:3.7-1) will
> never
> migrate to testing since this upload contains maintainer-built binary
> package
> (.deb files). Please make another source-only upload and solve this
> issue.

Ugh. I had to upload binaries because NEW. :|

> You may find more information about source-only upload at h
> ttps://wiki.debian.org/SourceOnlyUpload .
> 
> Please let me know if there's any issues.

Jordi

Bug#943790: www.debian.org: packages.debian.org partitions architectures into debports incorrectly

[Witold Baryluk]

Package: www.debian.org
Severity: normal

I just noticed this bug:

https://packages.debian.org/search?keywords=libatomic-ops-dev  - WRONG

https://packages.debian.org/sid/libatomic-ops-dev  - CORRECT

See attached screenshot.

Thanks.



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Bug#943788: postgresql-common/README.Debian: pg_upgradecluster, again suggests to drop active cluster

[Thorsten Glaser]

Package: postgresql-common
Version: 208
Severity: normal

As with every PostgreSQL major version upgrade, the README.Debian(.gz)
from postgresql-common, symlinked in /usr/share/doc/postgresql-12/,
suggests to drop the active (11) cluster, instead of the newly created
empty (12) one.

│Then drop the default 11 cluster that was just created:
│
│  pg_dropcluster 11 main --stop
│
│And then upgrade the 9.6 cluster to the latest installed version (e. g. 11):
│
│  pg_upgradecluster 9.6 main

May I suggest to not symlink the README but instead generate it
for each PostgreSQL server package, so that this doesn’t happen
again? This must be the forth or so time I report this bug…

-- System Information:
Debian Release: bullseye/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), 
(100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages postgresql-common depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.73
ii  lsb-base  11.1.0
ii  perl  5.30.0-9
ii  postgresql-client-common  208
ii  procps2:3.3.15-2
ii  ssl-cert  1.0.39
ii  ucf   3.0038+nmu1

Versions of packages postgresql-common recommends:
ii  e2fsprogs  1.45.4-1
ii  logrotate  3.15.1-1

Versions of packages postgresql-common suggests:
ii  libjson-perl  4.02000-1

-- Configuration Files:
/etc/sysctl.d/30-postgresql-shm.conf changed:
kernel.shmmax=268435456


-- debconf information:
  postgresql-common/catversion-bump:
  postgresql-common/ssl: true
* postgresql-common/obsolete-major:

Bug#943789: seafile-gui depends on seafile-daemon <= 7.0.2-1 while unstable has 7.0.2-1+b1

[Paul Gevers]

Package: seafile-gui
Version: 7.0.2-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

The source package seafile is part of the nettle transition and got rebuild as
part of it. However the binNMU-ed packages aren't migrating to testing because
it would make seafile-gui uninstallable in testing as seafile-gui has this in
its Depends field:
 seafile-daemon (>= ${source:Upstream-Version}),
 seafile-daemon (<= ${source:Version}),

This relation isn't fullfiled anymore in unstable, making your package
uninstallable. Please fix your Depends relation to be binNMU safe.

Paul

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

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

Versions of packages seafile-gui depends on:
ii  libc62.29-2
ii  libgcc1  1:9.2.1-8
ii  libglib2.0-0 2.62.1-1
ii  libjansson4  2.12-1
ii  libqt5core5a 5.11.3+dfsg1-4
ii  libqt5dbus5  5.11.3+dfsg1-4
ii  libqt5gui5   5.11.3+dfsg1-4
ii  libqt5network5   5.11.3+dfsg1-4
ii  libqt5webenginewidgets5  5.11.3+dfsg-2+b1
ii  libqt5widgets5   5.11.3+dfsg1-4
pn  libquazip5-1 
pn  libseafile0  
pn  libsearpc1   
ii  libsqlite3-0 3.30.1-1
ii  libstdc++6   9.2.1-8
pn  seafile-daemon   

seafile-gui recommends no packages.

Versions of packages seafile-gui suggests:
pn  seafile-cli  

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl24mWkACgkQnFyZ6wW9
dQqDJwgAiysi3vD5oBdLTdlNqDfGjz5TvWc6F9wU67YZTfdeOfmAAj6aljLPWw5F
K3GnQkHqS28V0wkAqqAP4pF6X98W7b51d8lkZDNpuiB2xZniOYERQXWe3gQrXKu3
8bQJ/487u4LesEtW5+ruT/oJJPQ/Sk8c0VsHA8hJdT9xl4o5teJVA7NSJ+dv7poj
qVzBhhBg9laBxOmEeb1VMQJ6bzTJxPU1v63eR8CiNdac4J3Ngi0gNLB5edvBrXR3
s1fwDXEi9hbA5tH/FgTaeg5h40cZoWBE4sZ5Avs8e4wSwLcfIBceskB/YFQHpnZ/
pmIEh/0F4cLKe8hRFqPGWBMoR5Upeg==
=BLKr
-END PGP SIGNATURE-

Bug#943787: mailutils: Please rebuild package with source-only upload

[Boyuan Yang]

Package: mailutils
Version: 1:3.7-1
Severity: important
X-Debbugs-CC: jo...@debian.org

Dear mailutils maintainer,

Your latest upload for package mailutils in Debian (1:3.7-1) will never
migrate to testing since this upload contains maintainer-built binary package
(.deb files). Please make another source-only upload and solve this issue.

You may find more information about source-only upload at h
ttps://wiki.debian.org/SourceOnlyUpload .

Please let me know if there's any issues.

-- 
Best,
Boyuan Yang


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

Bug#943786: lmfit-py: failing tests with python3.8

[Steve Langasek]

Source: lmfit-py
Version: 0.9.14-1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Dear maintainers,

The lmfit-py package fails to build from source in Ubuntu focal, because
Ubuntu has begun the transition to python3.8 and lmfit-py 0.9.14 is not
source-compatible with python3.8:

[...]
 ERRORS 
_ ERROR at setup of test_algebraic_constraints _

@pytest.fixture
def minimizer():
"""Return the Minimizer object."""
def residual(pars, x, sigma=None, data=None):
"""Define objective function."""
yg = gaussian(x, pars['amp_g'], pars['cen_g'], pars['wid_g'])
yl = lorentzian(x, pars['amp_l'], pars['cen_l'], pars['wid_l'])

model = yg + yl + pars['line_off'] + x * pars['line_slope']

if data is None:
return model
if sigma is None:
return model - data
return (model-data) / sigma

# generate synthetic data
n = 601
xmin = 0.
xmax = 20.0
x = np.linspace(xmin, xmax, n)

data = (gaussian(x, 21, 8.1, 1.2) + lorentzian(x, 10, 9.6, 2.4) +
np.random.normal(scale=0.23, size=n) + x*0.5)

# create initial Parameters
pars = Parameters()
pars.add(name='amp_g', value=10)
pars.add(name='cen_g', value=9)
pars.add(name='wid_g', value=1)
pars.add(name='amp_tot', value=20)
pars.add(name='amp_l', expr='amp_tot - amp_g')
>   pars.add(name='cen_l', expr='1.5+cen_g')

tests/test_algebraic_constraint.py:41: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
lmfit/parameter.py:361: in add
self.__setitem__(name, Parameter(value=value, name=name, vary=vary,
lmfit/parameter.py:132: in __setitem__
self._asteval.symtable[key] = par.value
lmfit/parameter.py:823: in value
return self._getval()
lmfit/parameter.py:805: in _getval
check_ast_errors(self._expr_eval)
lmfit/parameter.py:25: in check_ast_errors
expr_eval.raise_exception(None)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = , node = None
exc = , msg = ''
expr = <_ast.Module object at 0x7fe2428fa4f0>, lineno = None

def raise_exception(self, node, exc=None, msg='', expr=None,
lineno=None):
"""Add an exception."""
if self.error is None:
self.error = []
if expr is None:
expr = self.expr
if len(self.error) > 0 and not isinstance(node, ast.Module):
msg = '%s' % msg
err = ExceptionHolder(node, exc=exc, msg=msg, expr=expr, lineno=lineno)
self._interrupt = ast.Break()
self.error.append(err)
if self.error_msg is None:
self.error_msg = "%s in expr='%s'" % (msg, self.expr)
elif len(msg) > 0:
self.error_msg = "%s\n %s" % (self.error_msg, msg)
if exc is None:
try:
exc = self.error[0].exc
except:
exc = RuntimeError
>   raise exc(self.error_msg)
E   NotImplementedError: 'Constant' not supported in expr='<_ast.Module 
object at 0x7fe2428fa4f0>'

/usr/lib/python3/dist-packages/asteval/asteval.py:248: NotImplementedError
 Captured stderr setup -
NotImplementedError
   <_ast.Module object at 0x7fe2428fa4f0>
'Constant' not supported
[...]

  (https://launchpad.net/ubuntu/+source/lmfit-py/0.9.14-1/+build/17990659)

Debian has not yet started the transition to python3.8 - the version of
python3-defaults that adds python3.8 as supported is currently in
experimental - but this will eventually become a serious bug in Debian as
well once that transition begins.

For the moment I have worked around the failure in Ubuntu by changing the
packaging to test only against the current version of python3 and not
against all supported versions, but this is a very short-term fix given that
python3.8 will become the default in the next 6 months.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#943785: ITP: python-pyjsparser -- Fast JavaScript parser written in Python

[Peter Wienemann]

Package: wnpp
Severity: wishlist
Owner: Peter Wienemann 

  Package name: python-pyjsparser
  Version : 2.7.1
  Upstream Author : Piotr Dabkowski 
  URL : https://github.com/PiotrDabkowski/pyjsparser
  License : MIT
  Programming Lang: Python
  Description : Fast JavaScript parser written in Python

pyjsparser is a fast JavaScript parser written in Python.

It is a dependency of python-js2py (see #943783).

This package will be team-maintained by the Debian Python Modules
Team.

Bug#941141: codeblocks: Should codeblocks be removed from Debian?

[Olly Betts]

On Tue, Oct 29, 2019 at 07:53:28AM -1000, David Prévot wrote:
> On Thu, Oct 24, 2019 at 02:45:22PM +1300, Olly Betts wrote:
> > This package seems to have an active upstream and a user base
> > in Debian so I'd much rather see it return to a usable state than remove
> > it.
> 
> I recently started to use this package, and am interrested to see it
> working (hopefully with less crashes). I’ve just built the last upstream
> release with wxwidgets3.0-gtk3 and I’m currently running and testing it.

That's really great news - thanks for taking this on David.

This package seems a candidate for salvaging if you're up for taking
over as maintainer - it significantly exceeds the criteria listed:

https://wiki.debian.org/PackageSalvaging

Cheers,
Olly

Bug#942349: ublock-origin 1.22.2+dfsg-1~deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 942349 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: ublock-origin
Version: 1.22.2+dfsg-1~deb10u1

Explanation: new upstream version, compatible with Firefox ESR68 

Bug#943564: ublock-origin 1.22.2+dfsg-1~deb9u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 943564 = stretch pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: ublock-origin
Version: 1.22.2+dfsg-1~deb9u1

Explanation: new upstream version, compatible with Firefox ESR68

Bug#943784: French locale doesn't work

[Louis-Philippe Véronneau]

Package: membernator
Version: 1.1.0-1
Severity: normal

On a Buster system installed with a fr_CA.UTF-8 locale, membernator
still uses the default English locale.

I've checked and there is indeed a file in
/usr/share/locale/fr/LC_MESSAGES/membernator.mo

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#943783: ITP: python-js2py -- JavaScript to Python translator

[Peter Wienemann]

Package: wnpp
Severity: wishlist
Owner: Peter Wienemann 

  Package name: python-js2py
  Version : 0.66
  Upstream Author : Piotr Dabkowski 
  URL : https://github.com/PiotrDabkowski/Js2Py
  License : MIT
  Programming Lang: Python
  Description : JavaScript to Python translator

Js2Py provides a JavaScript to Python translator and a JavaScript
interpreter written in Python.

It is a dependency of python-lark-parser (see #941657).

This package will be team-maintained by the Debian Python Modules
Team.

Bug#941141: codeblocks: Should codeblocks be removed from Debian?

[Scott Talbert]

Control: close -1

On Tue, 29 Oct 2019, David Prévot wrote:


I think it's time to remove the codeblocks package:

[…]

* codeblocks is a major release behind upstream
* There are multiple open bug reports about frequent crashes

[…]

It's now been over 4 weeks with no objections.


Err, wait a little bit please ;).


The wxwidgets3.0-gtk3 transition is almost complete

[…]


This package seems to have an active upstream and a user base
in Debian so I'd much rather see it return to a usable state than remove
it.


I recently started to use this package, and am interrested to see it
working (hopefully with less crashes). I’ve just built the last upstream
release with wxwidgets3.0-gtk3 and I’m currently running and testing it.

I’ve pushed the repository to [Salsa], and I’m confident I’ll be able to
upload it soon (there are over 100,000 lines of code changed, so I need
some time to review it anyway).

Salsa: https://salsa.debian.org/debian/codeblocks


Sounds like there is demand to keep this package, so closing this bug.

The wxWidgets transition is complete anyway - the GTK2 packages have been 
removed.


Scott

Bug#943782: vdr-plugin-epgsearch: Wish to backport unstable to buster.

[Jari Fredriksson]

Package: vdr-plugin-epgsearch
Version: 2.2.0+git20170817-2+b1
Severity: wishlist

Dear Maintainer,

I'm running Debian Buster (as Raspbian) in my VDR box and the the 
vdr-plugin-epgsearch in Buster is unusable
as it crashes the vdr when there is a timer collision. This was patched in 
upstream and the patched version
is uncluded in Debian unstable.

I would like to have unstable vdr-plugin-epgsearch backported to stable to make 
it happen in Raspbian.

I do know that you do not maintain Raspbian, but that is not relevant. Raspbian 
is a straight Debian derivative
and it will get everything from Debian stable in a rapid fashion.

Pleas :)

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

Kernel: Linux 4.19.75-v7l+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
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)

Versions of packages vdr-plugin-epgsearch depends on:
ii  libc6   2.28-10+rpi1
ii  libgcc1 1:8.3.0-6+rpi1
ii  libstdc++6  8.3.0-6+rpi1
ii  sendemail   1.56-5
ii  vdr [vdr-abi-2.4.0-debian]  2.4.0-1+b1

vdr-plugin-epgsearch recommends no packages.

vdr-plugin-epgsearch suggests no packages.

-- no debconf information

Bug#943781: akregator: fails to update feeds

[Leos Pohl]

Package: akregator
Version: 4:18.08.3-2
Severity: important

Dear Maintainer,

Tested for feed from http://rss.sciencedirect.com/publication/science/00191035 
When this feed is added to a clean configuration, it is read. When
akregator is then run another day, feed is not updated, while the source
rss is updated. Manual update does not help. Purging does not help since
it does not delete configuration and neither does deleting "*akregator*"
files and directories in home folder (it still keeps its feeds).

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

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

Versions of packages akregator depends on:
ii  kinit5.54.0-1
ii  kio  5.54.1-1
ii  libc62.28-10
ii  libgcc1  1:8.3.0-6
ii  libkf5codecs55.54.0-1
ii  libkf5completion55.54.0-1
ii  libkf5configcore55.54.0-1+deb10u1
ii  libkf5configgui5 5.54.0-1+deb10u1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5grantleetheme-plugins  18.08.3-1
ii  libkf5grantleetheme5 18.08.3-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5iconthemes55.54.0-1
ii  libkf5jobwidgets55.54.0-1
ii  libkf5kcmutils5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiogui55.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5kontactinterface5  18.08.3-1
ii  libkf5libkdepim-plugins  4:18.08.3-2
ii  libkf5libkdepim5 4:18.08.3-2
ii  libkf5messageviewer5abi1 4:18.08.3-2
ii  libkf5mimetreeparser5abi14:18.08.3-2
ii  libkf5notifications5 5.54.0-1
ii  libkf5notifyconfig5  5.54.0-1
ii  libkf5parts5 5.54.0-1
ii  libkf5pimcommon5abi2 4:18.08.3-2
ii  libkf5pimtextedit5abi2   18.08.3-1
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5syndication5abi1   18.08.3-1
ii  libkf5textwidgets5   5.54.0-1
ii  libkf5webengineviewer5abi1   4:18.08.3-2
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libqt5core5a 5.11.3+dfsg1-1
ii  libqt5dbus5  5.11.3+dfsg1-1
ii  libqt5gui5   5.11.3+dfsg1-1
ii  libqt5network5   5.11.3+dfsg1-1
ii  libqt5printsupport5  5.11.3+dfsg1-1
ii  libqt5webenginecore5 5.11.3+dfsg-2+b1
ii  libqt5webenginewidgets5  5.11.3+dfsg-2+b1
ii  libqt5widgets5   5.11.3+dfsg1-1
ii  libqt5xml5   5.11.3+dfsg1-1
ii  libstdc++6   8.3.0-6

akregator recommends no packages.

akregator suggests no packages.

-- no debconf information

Bug#791362: perl: build timezone affects LOCALTIME_{MIN,MAX}

[Niko Tyni]

On Mon, Oct 28, 2019 at 12:28:32PM +0100, Guillem Jover wrote:
> On Wed, 2019-10-23 at 22:40:00 +0300, Niko Tyni wrote:

> > I'll re-instate TZ=UTC in 5.30.0-9 or so, but clearly the underlying
> > issue remains.
> 
> Just noticed this change from the changelog. :) UTC is not really a
> proper timezone specification, the format requires an offset, so here
> it would be UTC0 (see «man timezone»).

Oh! Thanks for the note. This is probably a very common misconception.
I think the reproducible builds docs have advised setting TZ=UTC in
the past, and I see https://reproducible-builds.org/docs/timezones/
mentions it currently.

Also, codesearch.debian.net reports 95 packages matching TZ=UTC
but only two match TZ=UTC[0-9]. Time for a mass bug filing? :)
-- 
Niko

Bug#943780: rc FTCBFS: fails running ./mksignal

[Helmut Grohne]

Source: rc
Version: 1.7.4+97.gceb59bb-2
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

rc fails to cross build from source, because it fails running
./mksignals. This tool seems to be intended towards creating a lookup
table from signal number to signal name. It's not going to work this way
for cross compilation at all. I'm not sure exactly whether we need rc to
be cross buildable given that most embedded users seem to prefer
systemd, but let me explain what it would take to fix this:

The signal numbers in mksignal.c should be looked up using
AC_COMPUTE_INT in configure.ac. Then given the discovered numbers, one
can create the source code without relying on host architecture
execution. One way would be to write a shell script creating sigmsgs.c
and sigmsgs.h. Alternatively, mksignal.c could be retained and instead
of relying on the signal macros, it would use the results from
AC_COMPUTE_INT and be compiled with CC_FOR_BUILD as discovered by
AX_CC_FOR_BUILD (from the autoconf-archive).

Do you think this is worth the effort? If not, please tag this bug
wontfix.

Helmut

Bug#943401: libreoffice C++ Unit tests failing when built with gcc >= 9.2.1-12 (Failure instantiating exceptionprotector) (was: Re: Bug#943401: libreoffice C++ Unit tests failing since gcc) 9.2.1-12 (

[Rene Engelhard]

reassign 943401 gcc-9
found 943401 9.2.1-12
retitle 943401 libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)
thanks

On Tue, Oct 29, 2019 at 03:09:50PM +0100, Vincent Lefevre wrote:
> 1. Build smoketest with the old g++-9 / libstdc++6.

In testing against 6.3.2 there:

== Starting smoketest with 1 job against 
path:/usr/lib/libreoffice/program/soffice ==
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  touch 
$W/Headers/CppunitTest/libtest_smoketest.so
[CXX] smoketest/smoketest_too.cxx
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  mkdir -p $W/CxxObject/smoketest/ 
$W/Dep/CxxObject/smoketest/ && cd 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 &&
x86_64-linux-gnu-g++ -DBOOST_ERROR_CODE_HEADER_ONLY 
-DBOOST_SYSTEM_NO_DEPRECATED -DCPPU_ENV=gcc3 -DLINUX -DNDEBUG 
-DOSL_DEBUG_LEVEL=0 -DUNIX -DUNX -DX86_64 -D_FORTIFY_SOURCE=2 -D_PTHREADS 
-D_REENTRANT -Wdate-time   -DCPPUNIT_PLUGIN_EXPORT='extern "C" 
SAL_DLLPUBLIC_EXPORT'   -fvisibility=hidden-Wall -Wno-missing-braces 
-Wnon-virtual-dtor -Wendif-labels -Wextra -Wundef -Wunreachable-code 
-Wunused-macros -finput-charset=UTF-8 -fmessage-length=0 -fno-common -pipe  
-Wno-maybe-uninitialized -Wduplicated-cond -Wlogical-op -Wshift-overflow=2 
-Wunused-const-variable=1 -Wno-cast-function-type -fvisibility-inlines-hidden 
-fPIC -Wshadow -Woverloaded-virtual -std=gnu++2a -pthread   -DEXCEPTIONS_ON 
-fexceptions -fno-enforce-eh-specs -g -O2 
-fdebug-prefix-map=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2=.
 -fstack-protector-strong -Wformat -Werror=format-security
-DLIBO_INTERNAL_ONLY  -c $S/smoketest/smoketest_too.cxx -o 
$W/CxxObject/smoketest/smoketest_too.o  -I$S/include  
-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux 
-I$S/config_host   -I/usr/include  -I$W/UnoApiHeadersTarget/udkapi/normal 
-I$W/UnoApiHeadersTarget/offapi/normal   
[LNK] CppunitTest/libtest_smoketest.so
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  x86_64-linux-gnu-g++ -pthread 
-shared -Wl,-z,noexecstack   -Wl,-z,origin '-Wl,-rpath,$ORIGIN/../Library' 
-Wl,-rpath-link,$I/program -Wl,-z,defs -Wl,-rpath-link,/lib:/usr/lib 
-Wl,-z,combreloc  -Wl,--hash-style=gnu  -Wl,-Bsymbolic-functions 
-L$W/LinkTarget/StaticLibrary -L$I/sdk/lib  -L$S/instdir/program  
-L$S/instdir/program  -L$W/LinkTarget/Library -Wl,-z,relro
$W/CxxObject/smoketest/smoketest_too.o  -Wl,--start-group-lcppunit   
-Wl,--end-group -Wl,--no-as-needed -luno_cppu -luno_cppuhelpergcc3 -luno_sal 
-lunotest  -o $W/LinkTarget/CppunitTest/libtest_smoketest.so 
TEMPFILE=/tmp/gbuild.ptBn7D &&  mv ${TEMPFILE} 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/LinkTarget/CppunitTest/libtest_smoketest.so.objectlist
rm -rf 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest
mkdir -p 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest/user
cp 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/qadevOOo/qa/registrymodifications.xcu
 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest/user
mkdir -p 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/
touch 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.prepare
[ZIP] smoketestdoc
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&   RESPONSEFILE=/tmp/gbuild.jGkR3E && 
cd $S/smoketest/data && cat ${RESPONSEFILE} | tr "[:space:]" "\n" | zip  -D 
-@rX --filesync --must-match $W/Zip/smoketestdoc.zip && rm -f ${RESPONSEFILE} 
&& touch $W/Zip/smoketestdoc.zip   
  adding: mimetype (stored 0%)
  adding: content.xml (deflated 77%)
  adding: meta.xml (deflated 55%)
  adding: settings.xml (deflated 80%)
  adding: styles.xml (deflated 77%)
  adding: META-INF/manifest.xml (deflated 73%)
  adding: Basic/script-lc.xml (deflated 47%)
  adding: Basic/Standard/script-lb.xml (deflated 52%)
  adding: Basic/Standard/Events.xml (deflated 54%)
  adding: Basic/Standard/Global.xml (deflated 78%)
  adding: Basic/Standard/Test_10er.xml (deflated 80%)
  adding: Basic/Standard/Test_DB.xml (deflated 68%)
  adding: Basic/Standard/Test_Ext.xml (deflated 47%)
  adding: Dialogs/dialog-lc.xml (deflated 47%)
  adding: Dialogs/Standard/dialog-lb.xml (deflated 47%)
  adding: Dialogs/Standard/OptionsDlg.xml (deflated 73%)
cp 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.zip
 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.sxw
[CUT] s

Bug#943779: Bluez GATT server (peripheral) secure characteristic read/write not working

[Rohit PAI]

Package: Bluez

Version: 5.50



I have implemented a GATT server in CPP which communicates to Bluez stack over 
DBUS APIs. I am able to advertise, expose characteristics and have clients 
connect with me. My reference is the doc and test folder in the bluez folder.

I would like to make my characteristic accessible only on secure (not legacy) 
pairing. So I have added 'secure-write' and 'secure-read' flags to my 
characteristic. When I try to read and write them using the nRF connect tool I 
see that bluez is not forcing for pairing requests and I am able to read/write 
the characteristic.

My app does not register any agent with the bluez since my peripheral has 
NoInputOutput capability.
static int GetHandlerGattChar(sd_bus* bus, const char* path, const char* 
interface, const char* prop, sd_bus_message* reply,
  void* userdata, sd_bus_error* error) {
.
if (property == "UUID") {
ret = sd_bus_message_append(reply, "s", 
"12345678-1234-5678-1234-56789abcdef1");
} else if (property == "Service") {
ret = sd_bus_message_append(reply, "o", 
DBUS_OBJECT_SERVICE0_NAME.c_str());
} else if (property == "Flags") {
ret = sd_bus_message_append(reply, "as", 3, "write-without-response", 
"secure-write", "secure-read");
} else {
ret = sd_bus_error_set(error, SD_BUS_ERROR_UNKNOWN_PROPERTY, "" /* 
message*/);
}
..
}




I don't understand what I am missing. Any help/support would be really 
appreciated.

Rohit PAI
Project Design Lead, Connected Systems
Global Technology Organization,
Energy Management Business
Schneider Electric
D  +91 (80) 45540171 x 40171
M  +91 9008728855
F  +91 (80) 45542000
E  rohit@se.com
Bearys Global Research Triangle (BGRT)
7th Floor, Tower-C, #63/3B, Gorvigere Village, Whitefield Ashram Road, 
Bangalore - 560067, India

[cid:image001.png@01D29BE2.09B31090]

Bug#943778: gnuradio: Cannot start gnuradio-companion without also installing gir1.2-gtk-3.0

[Karl Sickendick]

Source: gnuradio
Version: 3.8.0.0-5
Severity: important

Dear Maintainer,
I installed a fresh Debian unstable in a docker container, followed by
gnuradio.  Upon starting gnuradio-companion I got the errors below.  I
resolved
it by installing gir1.2-gtk-3.0.  Perhaps it should be a dependency.

~$ gnuradio-companion
Traceback (most recent call last):
  File "/usr/bin/gnuradio-companion", line 59, in check_gtk
gi.require_version('Gtk', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/gnuradio-companion", line 100, in 
 check_gtk()
  File "/usr/bin/gnuradio-companion", line 67, in check_gtk
die(err, "Failed to initialize GTK. If you are running over ssh, "
  File "/usr/bin/gnuradio-companion", line 41, in die
gi.require_version('Gtk', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
-Karl

Bug#943732: pandas: test failures on non-Intel

[Rebecca N. Palmer]

and 14 on riscv64, not investigated yet.

Bug#888991: please add multiarch support

[Witold Baryluk]

Package: libcunit1-dev
Version: 2.1-3-dfsg-2+b12
Followup-For: Bug #888991

Dear Maintainer,

any updates on this?

It is still not possible to install amd64 and i386 versions of dev and
lib packages:

$ sudo apt install libcunit1-dev:amd64 libcunit1-dev:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libcunit1-dev : Conflicts: libcunit1-dev:i386 but 2.1-3-dfsg-2+b12 is to be 
installed
 libcunit1-dev:i386 : Conflicts: libcunit1-dev but 2.1-3-dfsg-2+b12 is to be 
installed
E: Unable to correct problems, you have held broken packages.
$

I would like to have both installed for building (cross-compiling) libdrm
for 32-bit and 64-bit cases.


Did you have time to review proposed patches from the other reporter?

Cheers,
Witold



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages libcunit1-dev depends on:
pn  libcunit1  

libcunit1-dev recommends no packages.

Versions of packages libcunit1-dev suggests:
pn  libcunit1-doc  

Bug#941141: codeblocks: Should codeblocks be removed from Debian?

[David Prévot]

Hi,

On Thu, Oct 24, 2019 at 02:45:22PM +1300, Olly Betts wrote:
> On Wed, Sep 25, 2019 at 12:08:36PM -0400, Scott Talbert wrote:
> > I think it's time to remove the codeblocks package:
[…]
> > * codeblocks is a major release behind upstream
> > * There are multiple open bug reports about frequent crashes
[…]
> It's now been over 4 weeks with no objections.

Err, wait a little bit please ;).

> The wxwidgets3.0-gtk3 transition is almost complete
[…]

> This package seems to have an active upstream and a user base
> in Debian so I'd much rather see it return to a usable state than remove
> it.

I recently started to use this package, and am interrested to see it
working (hopefully with less crashes). I’ve just built the last upstream
release with wxwidgets3.0-gtk3 and I’m currently running and testing it.

I’ve pushed the repository to [Salsa], and I’m confident I’ll be able to
upload it soon (there are over 100,000 lines of code changed, so I need
some time to review it anyway).

Salsa: https://salsa.debian.org/debian/codeblocks

Regards

David


signature.asc
Description: PGP signature

Bug#943777: libdrm-amdgpu1: Please package libdrm 2.4.100

[Witold Baryluk]

Package: libdrm-amdgpu1
Severity: normal

Dear Maintainer,

building newest Mesa from git master as of 2019-10-28 requires libdrm
2.4.100 for building amdgpu related code, but only libdrm 2.4.99 is
available in Debian at the moment.

https://dri.freedesktop.org/libdrm/libdrm-2.4.100.tar.gz

It was release about two weeks ago, it contains minor bug fixes
and improved support for newest hardware.

https://lists.x.org/archives/xorg-announce/2019-October/003028.html

Packaging would be highly appreciated.

Thank you! :)



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Bug#943775: wiki.debian.org: 404 link in Packaging in Debian (https://wiki.debian.org/vim)

[krishna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

i have just discovered that Alioth has been switched off.

https://wiki.debian.org/Salsa

i am at loss...
-BEGIN PGP SIGNATURE-

iQGyBAEBCgAcFRwgPGtyaXNobmFAZ3JybHoubmV0PgUCXbh+5AAKCRCNtG2+rmTl
7S9+C/kB8bGFK5DkJMj3ds1cAbCxrcMBCLjaDVfdwN0NuZqkDMQ+DFEyFkytKBhc
zPdgaLn7BiUXG9JrtdBdMF1Hcm41vFJsS2yjpPOsWBJlF3A2VaHoEMG8Kd721Wxg
UyNknBCkgg3MxtRsVNVUMLqrS04dIZILSY1MKPVnNW1iwq4PeSKFAr6dQ+gQtrQ4
/s7qJS6J4bEYeG5xshvlumM+aGh1Ccu8Q3w1uZWvsjlX5nF6Hoj476MSCq1KpYLT
0ek3sO8rAJL9EdVwFBs+pzGBtnNUFtODmhHg5/1mD4Yw0EEUgYzLfLd9HawzMOkx
BJbud5ThjAeBxSIRYxs+IqxjY5gvAL0yzpiyRFUFkF+QvsSTKBZuKiMlolu6i+45
MUjJXHE8BX9JxwacTkJkkq8k+2W8Nu1y5K7g0LuLmYPrRYefDRzHmVyobrPeHDQ8
3UZA43gZgCBw8rxKp7rsRfbBiHWpTjQy09xEa0e2jHA0KJ71bxnifaihiBp95gQV
bfFBJ9c=
=2ZE2
-END PGP SIGNATURE-

Bug#943649: [pkg-apparmor] Bug#943649: apparmor ignores errors in debian/rules

[intrigeri]

Hi Matthias,

Matthias Klose:
> debian/rules has lots of

>   set -e && 

> starting the set in one shell and  in the next one. Please fix all 
> those.
> Seen while trying to build for multiple python3 versions.

>   set -e; 

> is the right thing to do.

I confess I was not able to reproduce the problem myself: I've tried
inserting "false" in various places where I would naively expect
"set -e" to fail the build, and I did not manage to find a case when
"set -e" did not fail the build.

Still, I'm not good Makefile and I'm very much inclined to trust your
expertise on this front, so I've applied your suggestion (locally for
now).

I would greatly appreciate a practical example in which "set -e &&
" does not behave as I thought it would :)

Thanks!

Cheers,
-- 
intrigeri

Bug#943216: Bug#943753: RFS: simple-scan/3.34.1-2 -- Simple Scanning Utility

[Jörg Frings-Fürst]

Hello,

after the answer to my RFS - bug went directly to non-participants, I
answer the same way. 

A note in advance: I am neither employed by Debian nor by Canonical. I
have to do a job because of that.
My employer supports my work for Debian, but at the moment I can only
work for Debian in my spare time. 

Therefore, I don't allow myself to answer mails that contain sayings
like "... It's frustrating that there has been no response to ...".

Now in detail to the requested changes:

c18055e3: I set "Rules-Requires-Root: binary-targets" to write the
logfiles for bug #860311 to /var/log/ and pack them via logrotate.

2060cea5: I will use the old calls as long as possible.

362fe5fa: I find comments important. They are also marked as comments
via '#'.

13c25e88: git:// is used to directly call the correct frontend when
clicked.

6b4a059a: python3-gi-cairo is already used with release 3.34.1-2.
gir1.2-rsvg-2.0 is required for scour, but is only suggested there. So
this is a bug in the scour package.

CU
Jörg



-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#943775: wiki.debian.org: 404 link in Packaging in Debian (https://wiki.debian.org/vim)

[Steve McIntyre]

On Tue, Oct 29, 2019 at 05:23:32PM +, krishna wrote:
>Package: wiki.debian.org
>Severity: normal
>
>on https://wiki.debian.org/vim, Packaging in Debian
>
>404 links :
>
>Vim packaging group on Alioth [ 
>https://pkg-vim.alioth.debian.org/vim-policy.html/ ]
>
>Packaging policy [ https://pkg-vim.alioth.debian.org/vim-policy.html/ ]

Hi Krishna,

Thanks for picking up on issues in the wiki. You can also easily fix
them as you find them - the wiki is editable directly by users with
accounts. :-)

-- 
Steve McIntyre93...@debian.org
Debian wiki admin - wiki.debian.orgw...@debian.org

Bug#943775: wiki.debian.org: 404 link in Packaging in Debian (https://wiki.debian.org/vim)

[krishna]

Package: wiki.debian.org
Severity: normal

on https://wiki.debian.org/vim, Packaging in Debian

404 links :

Vim packaging group on Alioth [ 
https://pkg-vim.alioth.debian.org/vim-policy.html/ ]

Packaging policy [ https://pkg-vim.alioth.debian.org/vim-policy.html/ ]

signature.asc
Description: PGP signature

Bug#943776: missing gir1.2-rsvg-2.0 Depends

[Jörg Frings-Fürst]

Package: scour
Version: 0.37-3
Severity: grave
Tags: newcomer

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

build simple-scan produces this errors:

[quote]
Scour processed file "icon.svg" in 32 ms: 7227/14298 bytes new/orig -> 50.5%
Traceback (most recent call last):
  File "/usr/share/scour/cmpsvg", line 13, in 
gi.require_version('Rsvg', '2.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Rsvg not available
dh_scour: scour was not able to process icon.svg
[/quote]


gir1.2-rsvg-2.0 is requested for a proper use of scour.

Please switch them from Suggests to Depends.


CU
Jörg



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages scour depends on:
ii  python33.7.5-1
ii  python3-scour  0.37-3

scour recommends no packages.

Versions of packages scour suggests:
ii  gir1.2-rsvg-2.0   2.44.14-1
ii  python3-gi-cairo  3.34.0-1

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl24dX8ACgkQCfifPIyh
0l0BERAArLqg1cnc0/g+XnViIMo4RJ+VfELYkjPOppAPGnGducIHzw/ePR0OARw4
5Zfqx5dmvw2KTpC7V9jEp5jSYBmfPdJyqmeilPbs7ED4//Gf4CmK65b+bGZZYJnf
vfebVMUexdrcntiSQzD8WhI7GixPqIum7HA2w8bpTT72t2XhWi9ScfCxpWjRRm1I
W8ByVrvL3Rbx7UmL3SLHrE45Jvw9jajyA+dy9q00ihnIPN9Rj+UTv2SwM9W+3HzF
a9Xt4lrZ1PBdbJLZSyYF/lwf8VWN5tP6A6ohg4LaMQtbQO58517Uf6Iywb9WMhNp
dV36RibB4fcq3is5RGKlCm2fMoZd2a9iMbNqBoW4pYnXR3K/+es4i4zMbjzRtPtb
z95hYH6wwU2dz6oaVE1PXHbaLh/OzXyK1mAav6W3aQaC/h5wqi2VDGUk2PzYWDNv
qO4TfwANqvyD1kwoxkdLYigKiHu3YSGX3dEQd+GPWZA5nQOk4VzSeQx3eWl7Tuvf
ViPf/vrM7WVt6VKv2qbdAIsxrllzpWbUo2C+nvOPz7TltolOPLlJ4w4FEPlZ2Cfh
2ifxMA/Ub8KSbinTpob5FVMx3DdsI3KVPJqel3NzTfcfhHmtoR7bYfd5RoBg8UuU
3ht/upVbBU5rHCjmVSXlvOkd+Xxe0AAJ2rLv1s244oiqueiWQwg=
=4RIn
-END PGP SIGNATURE-

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

[Jussi Pakkanen]

On Mon, Oct 28, 2019 at 11:15 PM Scott Talbert  wrote:

> The fpga test failure is also occurring with autopkgtest:
> https://ci.debian.net/data/packages/unstable/amd64/m/meson/latest-autopkgtest/log.gz
>
> Jussi also mentioned it.  Perhaps it's related to the recent upload of
> fpga-icestorm?

This is a bug in either yosys or arachne-pnr, I reported it here:

https://github.com/YosysHQ/yosys/issues/1467

Bug#943684: lintian: Refine ‘override_dh_auto_test’ check to trigger only when different command

[Chris Lamb]

Hi Ben,

> override_dh_auto_test:
> dh_auto_test --buildsystem=makefile
> 
[..]
> The above usage is a normal use of override target to change the
> command-line option with which ‘dh_auto_test’ is invoked.

Indeed, but this is actually not the reason you were seeing this tag.
Rather, lintian was counting the two lines following the dh_auto_test
line (that consisted of whitespace) as "meaningful" lines.

I have fixed this in:

  
https://salsa.debian.org/lintian/lintian/commit/c71707b15d27aa5c19ab3038538ac91efe299bf2

Thanks for reporting this regardless, of course. :)


Best wishes,

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

Bug#905963: unbound: FTBFS on hurd-i386

[Svante Signell]

On Tue, 2019-10-29 at 13:14 +0100, Samuel Thibault wrote:
> Hello,
> 
> Samuel Thibault, le dim. 27 oct. 2019 15:56:51 +0100, a ecrit:
> > Svante Signell, le dim. 12 août 2018 14:28:36 +0200, a ecrit:
> > > a missing function: compat/getentropy_gnu.c, derived from
> > > getentropy_solaris.c. Attached is hurd.diff defining that
> > > function by
> > > modifying configure.ac and Makefile.in too.
> > 
> > Thanks for this! Here is a fixed version which I have uploaded to
> > the
> > "unreleased" distribution.
> 
> Had you actually tested it? It was missing the SHA512_* functions.
> Here is a re-fixed version.

Thank you for looking into this bug. Maybe I missed these functions
when creating the patch, it was based on getentropy_solaris.c. I'm kind
of AFK for some more time and won't be able to build or test anything
requiring too much effort. I will submit your updated patch upstream
when time permits.

Thanks!

Bug#943774: wiki.debian.org: outdated and redirect link in Resources (https://wiki.debian.org/Xen)

[krishna]

Package: wiki.debian.org
Severity: normal

on https://wiki.debian.org/Xen, Resources

Xen Homepage [ http://www.xen.org ] changed to https://xenproject.org/

Best Practices for Xen [ http://wiki.xen.org/wiki/XenBestPractices ] redirects 
: http://wiki.xen.org/wiki/XenBestPractices

signature.asc
Description: PGP signature

Bug#943773: CVE-2019-13464

[Moritz Muehlenhoff]

Package: modsecurity-crs
Severity: important
Tags: security

This was assigned CVE-2019-13464: 
https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/1386

Patch:
https://github.com/SpiderLabs/owasp-modsecurity-crs/commit/6090d6b0a90417f1a60aa68a01eb777cef2e1184

Cheers,
Moritz

Bug#943772: wiki.debian.org: WordPress Manual Update Guide link moved (https://wiki.debian.org/WordPress)

[krishna]

Package: wiki.debian.org
Severity: normal

on https://wiki.debian.org/WordPress, external links

WordPress Manual Update Guide link: 
http://codex.wordpress.org/Updating_WordPress#Manual_Update/

when you visit above link, it shows message about moving the content to new 
location :  https://wordpress.org/support/article/updating-wordpress/

btw, links of Home Page, WordPress Online Documentation links are not https, 
but http


regards,
leela52452

signature.asc
Description: PGP signature

Bug#943765: libvtkgdcm3-dev: missing Breaks+Replaces: libvtkgdcm2-dev

[Mathieu Malaterre]

On Tue, Oct 29, 2019 at 3:39 PM Andreas Beckmann  wrote:
>
> Followup-For: Bug #943765
>
> and furthermore libgdcm3-dev is missing breaks+Replaces: libgdcm2-dev
>
>   Preparing to unpack .../libgdcm3-dev_3.0.3-1~exp1_amd64.deb ...
>   Unpacking libgdcm3-dev (3.0.3-1~exp1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/libgdcm3-dev_3.0.3-1~exp1_amd64.deb (--unpack):
>trying to overwrite '/usr/lib/x86_64-linux-gnu/libgdcmCommon.so', which is 
> also in package libgdcm2-dev 2.8.8-9+b1
>   Errors were encountered while processing:
>/var/cache/apt/archives/libgdcm3-dev_3.0.3-1~exp1_amd64.deb

I believe this is the right time to finally kill libgdcm2-dev. Just
like what was done for dcmtk, time is now to releave a libgdcm-dev
package and get rid of this issue forever.

As a side note libgdcm3-dev, should really be libgdcm3.0-dev, since
SOVERSION is 3.0. I belive this is mandated in the dev reference
handbook.

2cts

Bug#941557: Processed: Re: gri: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3364.

[Tobias Hansen]

Control: affects 941557 - src:maxima-sage

Thanks for providing the solution for the problem!

Best,
Tobias

On 10/29/19 2:24 PM, Norbert Preining wrote:
> reassign 941557 src:gri
> tags 941557 + patch
> retitle 941557 texi file need @documentencoding
> thanks
> 
> With texinfo 6.7 finally the default encoding is UTF-8, thus gri.texi
> fails to compile since it is in ISO-8859-1. If files in other encodings
> are to be translated @documentencoding needs to be used - this has been
> the case since ... version 6.0 or so (?).
> 
> Please add
>   @documentencoding ISO-8859-1
> after the 
>   \input texinfo
> so that it reads
>   \input texinfo
>   @documentencoding ISO-8859-1
> to fix it.
> 
> Thanks
> 
> Norbert
> 
> --
> PREINING Norbert   http://www.preining.info
> Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
> 

Bug#943771: linux-ftpd: Homepage URL fails name resolution

[Ricardo Mones]

Package: linux-ftpd
Severity: minor

Dear Maintainer,

Trying to open current homepage gives a DNS failure.

Seems this one works though:
http://ftp.linux.org.uk/pub/linux/Networking/netkit/

Thanks in advance and best regards,

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

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

Bug#811180: etckeeper: diff for NMU version 1.18.10-1.1

[Antoine Beaupré]

On 2019-10-29 11:25:06, Mattia Rizzolo wrote:
> On Mon, Oct 28, 2019 at 12:49:04PM -0400, Antoine Beaupré wrote:
>> This looks fine, go ahead and directly upload if you wish.
>
> ACK, rescheduled to 0-day!  Thank you! :)
>
>> I really need to open a repo on salsa for this... :/
>
> I would have done it, but I'm unsure what kind of format you prefer,
> basing on the upstream's git or an import of the debian uploads.
>
> Also, please forward those patches upstream :)

I have very little time for this package right now unfortunately, so I'd
say: do as you wish! :)

It has been based on upstream git for a while now, so maybe it's better
to keep that history...

a.

Bug#942060: closed by Peter Palfrader (reply to Debian Mirror Team ) (Re: Bug#942060: mirror submission for us.mirror.nsec.pt)

[Yev G]

Hello.

Looks like we had some issues with the cron, by ftpsync logs(and
trace) that should be fixed.

So I'm reopening the ticket for the same purpose.

Thanks.

On 10/14/19, Debian Bug Tracking System  wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the mirrors package:
>
> #942060: mirror submission for us.mirror.nsec.pt
>
> It has been closed by Peter Palfrader  (reply to Debian
> Mirror Team ).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Peter Palfrader
>  (reply to Debian Mirror Team ) by
> replying to this email.
>
>
> --
> 942060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942060
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
> --
> You received this message because you are subscribed to the Google Groups
> "Mirrors Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mirrors+unsubscr...@bitsighttech.com.
> To view this discussion on the web visit
> https://groups.google.com/a/bitsighttech.com/d/msgid/mirrors/handler.942060.D942060.157105510319288.notifdone%40bugs.debian.org.
>

Bug#943770: prometheus-pushgateway: Only depend on daemon if systemd-sysv is not installed

[Michal Politowski]

Package: prometheus-pushgateway
Version: 0.7.0+ds-1+b20

The same way as the prometheus package does, prometheus-pushgateway
should depend on daemon | systemd-sysv.

-- 
Michał Politowski

Bug#943769: falkon crash at start or when search

[Bardot Jerome]

Package: falkon
Version: 3.0.0-3
Severity: important

Dear Maintainer,
everything is in the title

i join end output from command line
LC_ALL=C strace falkon

ioctl(8, DRM_IOCTL_GEM_CLOSE, 0x7ffc3adccc50) = 0
munmap(0x7fab8a061000, 7979008) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3,
[{iov_base="\224\1\22\0\27\0\240\tC\0\240\t\320\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
iov_len=72}], 1) = 72
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 0) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\2\0\0\0\0\0\0\0", 16) = 8
sendto(294,
"\330\0\0\0\20\0\1\0\0\0\0\0\0\0\0\0\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 216,
MSG_NOSIGNAL, NULL, 0) = 216
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 0) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\2\0\0\0\0\0\0\0", 16) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 0) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\2\0\0\0\0\0\0\0", 16) = 8
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 8) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
sendto(294,
"\330\0\0\0\20\0\1\0\0\0\0\0\0\0\0\0\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 216,
MSG_NOSIGNAL, NULL, 0) = 216
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 0) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 16) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
sendto(294,
"\330\0\0\0\20\0\1\0\0\0\0\0\0\0\0\0\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 216,
MSG_NOSIGNAL, NULL, 0) = 216
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 0) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\2\0\0\0\0\0\0\0", 16) = 8
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 2) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=257, events=POLLIN},
{fd=262, events=POLLIN}], 4, 0) = 1 ([{fd=5, revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="&\0\2\0\267\5\0\0", iov_len=8}], 1) = 8
futex(0x7ffc3adcb628, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x55e58add8f38, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x55e58add8f38, FUTEX_WAKE_PRIVATE, 1) = 0
getpid()= 13119
ioctl(8, DRM_IOCTL_NOUVEAU_GEM_PUSHBUF, 0x7ffc3adcc7f0) = 0
ioctl(8, DRM_IOCTL_NOUVEAU_GEM_NEW, 0x7ffc3adcc800) = 0
mmap(NULL, 7979008, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x135faf000) =
0x7fab8a061000
ioctl(8, DRM_IOCTL_NOUVEAU_GEM_CPU_PREP, 0x7ffc3adcc880) = 0
futex(0x55e58af182a0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55e58af182a0, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x55e58af182a0, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
futex(0x55e58af182a0, FUTEX_WAKE_PRIVATE, 1) = 0
getpid()= 13119
getpid()= 13119
ioctl(8, DRM_IOCTL_NOUVEAU_GEM_PUSHBUF, 0x7ffc3adccbe0) = 0
ioctl(8, DRM_IOCTL_GEM_CLOSE, 0x7ffc3adccc30) = 0
munmap(0x7fac1c353000, 4096)= 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7fac1c353000} ---
nouveau: kernel rejected pushbuf: Invalid argument
nouveau: ch10: krec 0 pushes 0 bufs 0 relocs 0
openat(AT_FDCWD, "/proc/self/status", O_RDONLY) = 329
read(329, "Name:\tfalkon\nUmask:\t0027\nState:\t"..., 1024) = 1024
+++ killed by SIGSEGV +++
seg fault

Erreur de segmentation in french in the original output



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

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

Versions of packages falkon depends on:
ii  libc62.29-2
ii  libgcc1  1:9.2.1-8
ii  libkf5wallet-bin 5.62.0-1
ii  libkf5wallet55.62.0-1
ii  libqt5core5a  

Bug#943587: openafs: 1.8.5 available (security fixes, Linux 5.3 support)

[Salvatore Bonaccorso]

Hi,

On Sat, Oct 26, 2019 at 11:10:54PM -0400, Aaron M. Ucko wrote:
> Source: openafs
> Version: 1.8.4~pre1-1
> Severity: important
> Tags: security
> 
> Could you please upload OpenAFS 1.8.5 to Debian, for the sake of both
> the security fixes (OPENAFS-SA-2019-00{1,2,3}) and Linux 5.3 support,
> which Debian's 1.8.4 prerelease slightly predates?

There were CVE assignments btw for those three, resulting in

CVE-2019-18601: http://openafs.org/pages/security/OPENAFS-SA-2019-003.txt
CVE-2019-18602: http://openafs.org/pages/security/OPENAFS-SA-2019-002.txt
CVE-2019-18603: http://openafs.org/pages/security/OPENAFS-SA-2019-001.txt

Regards,
Salvatore

Bug#938611: swiftsc: diff for NMU version 0.5-1.1

[Ondřej Nový]

Control: tags 938611 + patch
Control: tags 938611 + pending


Dear maintainer,

I've prepared an NMU for swiftsc (versioned as 0.5-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru swiftsc-0.5/debian/control swiftsc-0.5/debian/control
--- swiftsc-0.5/debian/control  2013-08-15 15:21:14.0 +0200
+++ swiftsc-0.5/debian/control  2019-10-29 14:31:26.0 +0100
@@ -2,22 +2,13 @@
 Section: python
 Priority: optional
 Maintainer: Kouhei Maeda 
-Build-Depends: debhelper (>= 8.0.0), python-all (>= 2.6), python-setuptools, 
python-pytest, pep8, python-mock, python-requests, python-magic, python3-all, 
python3-setuptools, python3-requests, python3-magic, python3-pytest, 
python3-mock
+Build-Depends: debhelper (>= 8.0.0), pep8, python3-all, python3-setuptools, 
python3-requests, python3-magic, python3-pytest, python3-mock
 Standards-Version: 3.9.4
 X-Python-Version: >= 2.6, >= 3.2
 Homepage: https://github.com/mkouhei/swiftsc
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=openstack/swiftsc.git
 Vcs-Git: git://anonscm.debian.org/openstack/swiftsc.git
 
-Package: python-swiftsc
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${python:Depends}, ${misc:Depends}, python-requests, python-magic
-Description: simple client library of OpenStack Swift
- This tool is simple client library of OpenStack Swift.
- This tool is intended to be used in the module and Python script other.
- The main purpose of this tool is used as a core module for backup tool.
-
 Package: python3-swiftsc
 Architecture: all
 Depends: ${python3:Depends}, ${misc:Depends}, python3-requests, python3-magic
diff -Nru swiftsc-0.5/debian/changelog swiftsc-0.5/debian/changelog
--- swiftsc-0.5/debian/changelog2013-08-15 15:21:14.0 +0200
+++ swiftsc-0.5/debian/changelog2019-10-29 14:31:56.0 +0100
@@ -1,3 +1,11 @@
+swiftsc (0.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use pybuild to build package.
+  * Drop Python 2 support (Closes: #938611).
+
+ -- Ondřej Nový   Tue, 29 Oct 2019 14:31:56 +0100
+
 swiftsc (0.5-1) unstable; urgency=low
 
   * Initial release (Closes: #717926)
diff -Nru swiftsc-0.5/debian/py3dist-overrides 
swiftsc-0.5/debian/py3dist-overrides
--- swiftsc-0.5/debian/py3dist-overrides2013-08-15 15:21:14.0 
+0200
+++ swiftsc-0.5/debian/py3dist-overrides2019-10-29 14:31:56.0 
+0100
@@ -1,2 +1 @@
 setuptools python3-setuptools 
-
diff -Nru swiftsc-0.5/debian/rules swiftsc-0.5/debian/rules
--- swiftsc-0.5/debian/rules2013-08-15 15:21:11.0 +0200
+++ swiftsc-0.5/debian/rules2019-10-29 14:31:56.0 +0100
@@ -3,38 +3,10 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-%:
-   dh $@ --with python2,python3
-
-override_dh_auto_build:
-   for py in $(shell pyversions -vr); do \
-   python$$py setup.py build --build-base=_build$$py; \
-   done
-
-override_dh_auto_test:
-   set -e; \
-   for py in $(shell pyversions -vr); do \
-   if [ "$$py" < "3.0" ]; then \
-   py.test-$$py -v $(CURDIR)/_build/lib.$(shell python -c 
'import distutils.util as d; print d.get_platform()')-$$py; \
-   else \
-   py.test-3 -v $(CURDIR)/_build/lib ;\
-   fi ;\
-   done
+export PYBUILD_NAME=swiftsc
+export PYBUILD_BEFORE_TEST=mkdir -p {build_dir}/src/swiftsc_tests ; cp -r 
{dir}/src/swiftsc_tests/*.txt {build_dir}/src/swiftsc_tests
+export PYBUILD_AFTER_TEST=rm -rf {build_dir}/src/swiftsc_tests
+export PYBUILD_AFTER_INSTALL=rm -rf {destdir}/{install_dir}/swiftsc_tests
 
-override_dh_auto_install:
-   python setup.py install --no-compile -O0 --install-layout=deb \
-   --root $(CURDIR)/debian/python-swiftsc && \
-   python3 setup.py install --no-compile -O0 --install-layout=deb \
-   --root $(CURDIR)/debian/python3-swiftsc
-   rm -rf $(CURDIR)/debian/python-swiftsc/usr/share/pyshared/swiftsc_tests
-   rm -rf 
$(CURDIR)/debian/python-swiftsc/usr/lib/python2.6/dist-packages/swiftsc_tests
-   rm -rf 
$(CURDIR)/debian/python-swiftsc/usr/lib/python2.7/dist-packages/swiftsc_tests
-   rm -rf 
$(CURDIR)/debian/python3-swiftsc/usr/lib/python3/dist-packages/swiftsc_tests
-
-override_dh_auto_clean:
-   dh_clean
-   for py in $(shell pyversions -vr); do \
-   python$$py setup.py clean --build-temp=_build && \
-   python$$py setup.py clean --build-temp=_build$$py; \
-   done
-   rm -rf $(CURDIR)/_build
+%:
+   dh $@ --with python3 --buildsystem=pybuild