Bug#963987: buster-pu: package libtool/2.4.6-9

2020-06-29 Thread Mohammed Naser
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

The following bug was reported back in 2017:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864018

Because of that bug, it's not possible to build certain packages from
source such as 'qemu' because it fails with the following:

powerpc64-linux-gnu-ar: `u' modifier ignored since `D' is the default (see `U')

The bug explains the details of why/how this issue is happening.

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

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



Bug#950128: Experimental

2020-01-29 Thread Mohammed Naser
Hi there,

I agree that a fix should be done.  Personally, I'm not a contributor
but just someone who was affected by the same issue.

I'd be happy to help fix it if someone can point me in the right direction.

Thanks,
Mohammed



Bug#950128: Fix included in 440.31

2020-01-29 Thread Mohammed Naser
Hi everyone,

Based on some small research, I've discovered that there was a fix
included for this in 440.31 (which I'm not sure we can either backport
or bump version):

https://devtalk.nvidia.com/default/topic/1065987/announcements-and-news/linux-solaris-and-freebsd-driver-440-31-long-lived-branch-release-/

As a temporary fix, and I only suggest this for the brave, I would
enable experimental repositories:

deb http://deb.debian.org/debian experimental main non-free

...and install the 440.44 driver from there which includes that fix.

(please understand the consequences of doing the above before doing so)

Good luck

Mohammed



Bug#950128:

2020-01-28 Thread Mohammed Naser
I can confirm the same issue on my side. I have not attempted any
workarounds but reading online this seems to be related to changes
some Kernel symbol changes.

http://rglinuxtech.com/?p=2614

The reading also has a patch in there which might help.