Bug#927329: [Pkg-electronics-devel] Bug#927329: Update Arduino from 1.8.2 to 1.8.9

[Brian Holaday]

Hi Rock,

I don't have a problem with waiting for a release in SID but I wanted to
try and get several electronic tools I use for hobby reported such that
someone with expertise can fix them. I have no problems with the work
around I have attached I just created my own script installer in the
meantime because the AVR ICE programmer which I use is supported on Arduino
IDE 1.8.4 or greater the best. The other package I am using is avrdude and
avrgcc which is used in conjunction with Arduino no other dependencies I
use.

I have filled a bug in the avrgcc package relating to using MPLab and
avrgcc but I have yet to hear anything back on that bug yet and is not a
huge issue as explained I have a work around for both issues so far so no
hurry here.

Thanks for all your hard work,

I hope soon I can try and help but at the moment don't have much experience
packaging.

On Sat, Apr 27, 2019 at 1:04 PM Kashif Shah  wrote:

> Hi Rock,
>
> I'd be happy to contribute if you have a suggestion of what best to
> contribute?  I'd made a first attempt at an updated package as my first
> package creation ever and got fairly far before I ran out of time.  I can
> continue that effort in parallel, perhaps this weekend, and provide updates
> to you, but I'd prefer to follow your direction of what sub-tasks I could
> do for you.
>
> Best regards,
>
> Kashif Shah
> GPG KeyID: 7B22E3E1
> GPG Fingerprint: AD33 88BB D5A4 653E 511E  A87C 2668 4569 7B22 E3E1
>
> On Sat, Apr 27, 2019 at 5:48 AM Rock Storm  wrote:
>
>> Control: affects -1 - arduino-builder
>>
>> On Wed, Apr 17, 2019 at 10:46:41PM -0600, Brian Holaday wrote:
>> > Hello Carsten and Team,
>> >
>> > Is there a way we can get an update into backports from 1.8.2 to 1.8.9
>> > and/or work with the author in trying to fix up one package for
>> Arduino. I
>> > am finding that for now I manually install the latest version using the
>> > command line.
>>
>> Hi Brian,
>>
>> Before even considering backporting we need to get a stable version of
>> Arduino into Sid. To get this, we still need to solve the dependency
>> nightmare Arduino has become. One of them being arduino-builder which
>> I'm removing from this bug because it is technically not affected by it.
>>
>> Getting Arduino into Debian is on my to-do list, and it will become my
>> next priority, please bear with me. Contributions are of course very
>> welcome.
>>
>> Regards,
>>
>> --
>> Rock Storm
>> GPG KeyID: 4096R/C96832FD
>> GPG Fingerprint:
>>  C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD
>>
>> ___
>> Pkg-electronics-devel mailing list
>> pkg-electronics-de...@alioth-lists.debian.net
>>
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-electronics-devel
>
>

Bug#927328: Update KiCad from 5.0.2 to 5.1.1

[Brian Holaday]

Hi Carsten,

No problem: I will add the new library packages I worked on in manually.
They are actually listed here: (
https://github.com/KiCad/kicad-footprints/tree/master/Symbol.pretty)

Thank you: Feel free to close and/or update this bug given time.

On Wed, Apr 17, 2019 at 11:58 PM Carsten Schoenert 
wrote:

> Hello Brian,
>
> Am 18.04.19 um 06:25 schrieb Brian Holaday:
> > Is there a way we can get an update into backports from 5.0.2 to 5.1.1
> > in Stretch?
>
> currently not.
> The rule for backports is simple, the same version needs to be available
> in testing. This can't be fulfilled now as testing is completely frozen
> and a request for updating the version in testing/buster was rejected.
> Buster will get released with 5.0.2.
>
> And before I've not finalized any work on the recent version 5.1.1 for
> unstable I won't spent time on a backports version. I need first to
> figure out if there is more work to do in stretch due the differences of
> wxpython and libwxgtk.
>
> --
> Regards
> Carsten Schoenert
>

Bug#917390: gcc-avr: Expand the version string with the atmel version

[Brian Holaday]

Hello Hakan,

Has there been any updates on this bug or is this still in the backlog for
awhile?

Bug#927329: Update Arduino from 1.8.2 to 1.8.9

[Brian Holaday]

Package: arduino arduino-builder

Version: 2:1.0.5+dfsg2-4.1


Hello Carsten and Team,

Is there a way we can get an update into backports from 1.8.2 to 1.8.9
and/or work with the author in trying to fix up one package for Arduino. I
am finding that for now I manually install the latest version using the
command line.

Here is a script (getting started):

# Arduino (Free)
# Path: /usr/local/bin/arduino
sudo apt-get install avrdude
mkdir "$HOME/Arduino"
sudo mkdir /usr/local/bin/arduino
cd /usr/local/bin/arduino || exit
sudo wget "https://downloads.arduino.cc/arduino-1.8.9-linux64.tar.xz;
sudo mv arduino-1.8.9-linux64.tar.xz arduino-amd64.tar.xz
sudo tar xfJ arduino-amd64.tar.xz
sudo mv arduino-1.8.9/* /usr/local/bin/arduino/
./install.sh
sudo rm -rf arduino-1.8.9
sudo rm -rf arduino-1.8.9/ arduino-amd64.tar.xz

# Check Last Sudo User (Worst case the user needs to add themselves to the
group)
name=$(logname)
sudo usermod -a -G dialout "$name"

Bug#927328: Update KiCad from 5.0.2 to 5.1.1

[Brian Holaday]

Package: KiCad

Version: 5.0.2+dfsg1-1~bpo9+1


Hello Carsten,

Is there a way we can get an update into backports from 5.0.2 to 5.1.1 in
Stretch? I was wanting to confirm some symbol/logo changes between versions
when I submitted them to to the KiCad Repo a few months ago. I still need
to fix a few but this might give me an idea. There is no hurry as I can
work with an older version if needed and clone the files separately.

Bug#925578: Update Package: Arduino : 1.8.9

[Brian Holaday]

Hi Geert,

No Problem: I reassigned the bug to the correct package I believe:
arduino-core would need updated assuming I am correct the package is 1.0.5.

Bug#846035: Eagle needs updated to a newer version

[Brian Holaday]

Eagle has been updated to 9.3.0:
https://www.autodesk.com/products/eagle/overview

Bug#925620: Update Package: Arduino : 1.8.9

[Brian Holaday]

Package: arduino
Version: 2:1.0.5+dfsg2-4.1
severity: important
affects: 925578

Hi Geert,

No Problem: I reassigned the bug to the correct package I believe:
arduino-core would need updated assuming I am correct the package is 1.0.5.

On Wed, Mar 27, 2019 at 11:36 AM Brian Holaday 
wrote:

> Hi Geert,
>
> No Problem: I reassigned the bug to the correct package I believe:
> arduino-core would need updated assuming I am correct the package is 1.0.5.
>
> On Wed, Mar 27, 2019 at 12:48 AM Geert Stappers 
> wrote:
>
>> Control: severity normal
>>
>> On Tue, Mar 26, 2019 at 09:15:36PM -0600, Brian Holaday wrote:
>>
>>
>> > I created a script for easier install.
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923220#42
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923220#52
>>
>>
>> Groeten
>> Geert Stappers
>> --
>> Leven en laten leven
>>
>

Bug#925578: Update Package: Arduino : 1.8.9

[Brian Holaday]

Package: arduino
Version: 2:1.0.5+dfsg2-4.1
severity: important

Issue:

Can the Arduino package be updated to 1.8.9 as per Arduino homepage? I
created a script for easier install.

# Install: 1.8.9 from Arduino Site

mkdir "$HOME/Arduino"
sudo mkdir /usr/local/bin/arduino
cd /usr/local/bin/arduino || exit
sudo wget "https://downloads.arduino.cc/arduino-1.8.9-linux64.tar.xz;
sudo mv arduino-1.8.9-linux64.tar.xz arduino-amd64.tar.xz
sudo tar xfJ arduino-amd64.tar.xz
sudo mv arduino-1.8.9/* /usr/local/bin/arduino/
./install.sh
sudo rm -rf arduino-1.8.9
sudo rm -rf arduino-1.8.9/ arduino-amd64.tar.xz

Bug#924324: libopenscap8: Push update to 1.3.0

[Brian Holaday]

Package: libopenscap8
Version: 1.2.16-2
Severity: important

Tagged Release Branch is 1.3.0:
https://github.com/OpenSCAP/openscap/releases

It does not bother me if stretch does not get updated but please can you
import over 1.3.0 into SID.

Thank you!

Bug#924323: libopenscap8 - Issue with Scanning

[Brian Holaday]

Package: libopenscap8
Version: 1.2.9-1
Severity: important

Issue:

Installing Open SCAP works just fine on Debian 9 just fine. In order to use
the tool however there are no XML Scap files installed by default to
"/usr/share/xml/scap/ssg/content/". However doing some digging I see a
package in buster for "ssg-debian" that includes this package rules. The
only issue here is that that package includes only details for Debian 8
which does not run with Debian 9 when trying to run the tool. Running this
on Fedora the tool seems to work fine even if for example a default profile
is set which means that for some reason some content under
"/usr/share/xml/scap/ssg/content/" is not being copied over correctly on
Debian.

Can we suggest a bug fix on including a standard profile for testing?

Bug#923734: closed by Matthias Klose (Re: Bug#923734: closed by Matthias Klose (Re: Bug#923734: Python needs updating: version push))

[Brian Holaday]

Hi Matthias,

I did not know if someone would get a reply if the ticket was closed: can
you confirm this for me. I am new: so I would ask that you review your
comments carefully even if it means just helping/self resolving with good
feedback: relevant information.

On Mon, Mar 4, 2019 at 4:09 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the python package:
>
> #923734: Python needs updating: version push
>
> It has been closed by Matthias Klose .
>
> 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 Matthias Klose <
> d...@debian.org> by
> replying to this email.
>
>
> --
> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: 923...@bugs.debian.org, 923734-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 5 Mar 2019 00:06:02 +0100
> Subject: Re: Bug#923734: closed by Matthias Klose  (Re:
> Bug#923734: Python needs updating: version push)
> On 04.03.19 23:29, Brian Holaday wrote:
> > I seem to be having issues then with installing: 3.5.3 on Stretch.
> >
> > # sudo apt-get install python3.5
> >> #python3.5 is already the newest version (3.5.3-1+deb9u1).
> >
> > Is Python 3.5 only for Buster or SID?
>
> no, for stretch. There is no 3.5 and 3.6. for buster.  Please stop
> re-opening
> this issue.
>
> > On Mon, Mar 4, 2019 at 12:48 PM Debian Bug Tracking System <
> > ow...@bugs.debian.org> wrote:
> >
> >> This is an automatic notification regarding your Bug report
> >> which was filed against the python package:
> >>
> >> #923734: Python needs updating: version push
> >>
> >> It has been closed by Matthias Klose .
> >>
> >> 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 Matthias Klose <
> >> d...@debian.org> by
> >> replying to this email.
> >>
> >>
> >> --
> >> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
> >> Debian Bug Tracking System
> >> Contact ow...@bugs.debian.org with problems
> >>
> >>
> >>
> >> -- Forwarded message --
> >> From: Matthias Klose 
> >> To: Brian Holaday , 923...@bugs.debian.org,
> >> 923734-d...@bugs.debian.org
> >> Cc:
> >> Bcc:
> >> Date: Mon, 4 Mar 2019 20:46:16 +0100
> >> Subject: Re: Bug#923734: Python needs updating: version push
> >> On 04.03.19 19:37, Brian Holaday wrote:
> >>> Package: python
> >>> Version: 2.7.13-2
> >>> severity: important
> >>>
> >>> Issue:
> >>>
> >>> Python 3.7.2 has been released out for some time now. Can we get an
> >> update
> >>> pushed out to stretch-backports
> >>
> >> no, not doing that.
> >>
> >>> or SID at some point?
> >>
> >> it's there "for some time now"
> >>
> >>
> >> -- Forwarded message --
> >> From: Brian Holaday 
> >> To: sub...@bugs.debian.org
> >> Cc:
> >> Bcc:
> >> Date: Mon, 4 Mar 2019 11:37:37 -0700
> >> Subject: Python needs updating: version push
> >> Package: python
> >> Version: 2.7.13-2
> >> severity: important
> >>
> >> Issue:
> >>
> >> Python 3.7.2 has been released out for some time now. Can we get an
> update
> >> pushed out to stretch-backports or SID at some point?
> >>
> >
>
>
> -- Forwarded message --
> From: Brian Holaday 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Mar 2019 11:37:37 -0700
> Subject: Python needs updating: version push
> Package: python
> Version: 2.7.13-2
> severity: important
>
> Issue:
>
> Python 3.7.2 has been released out for some time now. Can we get an update
> pushed out to stretch-backports or SID at some point?
>

Bug#923734: closed by Matthias Klose (Re: Bug#923734: Python needs updating: version push)

[Brian Holaday]

I seem to be having issues then with installing: 3.5.3 on Stretch.

# sudo apt-get install python3.5
> #python3.5 is already the newest version (3.5.3-1+deb9u1).

Is Python 3.5 only for Buster or SID?

On Mon, Mar 4, 2019 at 12:48 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the python package:
>
> #923734: Python needs updating: version push
>
> It has been closed by Matthias Klose .
>
> 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 Matthias Klose <
> d...@debian.org> by
> replying to this email.
>
>
> --
> 923734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923734
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: Brian Holaday , 923...@bugs.debian.org,
> 923734-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Mar 2019 20:46:16 +0100
> Subject: Re: Bug#923734: Python needs updating: version push
> On 04.03.19 19:37, Brian Holaday wrote:
> > Package: python
> > Version: 2.7.13-2
> > severity: important
> >
> > Issue:
> >
> > Python 3.7.2 has been released out for some time now. Can we get an
> update
> > pushed out to stretch-backports
>
> no, not doing that.
>
> > or SID at some point?
>
> it's there "for some time now"
>
>
> -- Forwarded message --
> From: Brian Holaday 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Mar 2019 11:37:37 -0700
> Subject: Python needs updating: version push
> Package: python
> Version: 2.7.13-2
> severity: important
>
> Issue:
>
> Python 3.7.2 has been released out for some time now. Can we get an update
> pushed out to stretch-backports or SID at some point?
>

Bug#923734: Python needs updating: version push

[Brian Holaday]

Package: python
Version: 2.7.13-2
severity: important

Issue:

Python 3.7.2 has been released out for some time now. Can we get an update
pushed out to stretch-backports or SID at some point?

Bug#923177: Firmware load failure - clean up

[Brian Holaday]

Package: firmware-atheros
Version: 20190114-1~bpo9+2
Severity: important

Firmware: Qualcomm Atheros QCA9377 802.11ac

Issue:
Installing the wireless driver works just fine : bluetooth seems to need a
restart each time I connect my headphones each time. The main issue I am
seeing is that I show several errors with missing firmware on
startup/shutdown. There are a few times where the key is never removed but
the system shuts down anyhow.

Log from gnome-logs:
ath10k_pci :02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
ath10k_pci :02:00.0: firmware: failed to load
ath10k/cal-pci-:02:00.0.bin (-2)
ath10k_pci :02:00.0: firmware: failed to load
ath10k/pre-cal-pci-:02:00.0.bin (-2)

Bug#922559: Firmware locks up on Vega 8

[Brian Holaday]

Package: firmware-amd-graphics
Version: 20180825+dfsg-1~bpo9+1

Laptop Information
- Inspiron 5775
- AMD Ryzen 5 - 2500U CPU
- Radeon Vega 8 GPU (Shared with CPU)

Kernel: 4.19.0-0.bpo.2-amd64, 4.19.16-1~bpo9+1

- Without Package Debian Stretch works fine with one config change:
/etc/default/grub/
* see notes

Steps to Reproduce:

* This assumes stretch-backports is installed *

#1. Install ATI Firmware:
#sudo apt-get install -t stretch-backports firmware-amd-graphics

#2. Reboot Install:
# After reboot - kernel loads just fine but then when it hits the
gnome-shell login screen the system locks up (cursor has no movement) and
only a grey background is shown.

Here is part of my log what I seem to show:
 gnome-session[857]: gnome-session-binary[857]: WARNING: App
'org.gnome.Shell.desktop' exited with code 1

Without the firmware-driver I can get gnome-shell to launch just fine
however for my laptop I have to set the following up for proper screen
booting: /etc/default/grub/ (see below). Even commenting these in/out still
produce a lock when the firmware is installed does not lock when firmware
is not installed.

* Yes: this is close *
> GFXMODE=1920x1080x32
> GFXPAYLOAD=keep


Last Note: Running Fedora live with vga=3d4 or vga=755 seems to boot up: I
have less lockup problems and HDMI is fully supported. Right now even with
the firmware there is no HDMI output using Debian Stretch. I don't know if
this has to do with a newer firmware of Fedora for AMD ATI and/or the
Kernel or if Mesa also is updated such that for the most part things are
working. I expect Buster to be working fully if what is pulled in is
updated.

Bug#921399: closed by Scott Kitterman (Re: ClamAV Needs (live-updates) on Post Install)

[Brian Holaday]

I will add this tad bit in my script. I just think that once the package is
installed:  freshclam needs to run for the first time before doing a scan
and gathers the latest definitions. I just would like to see output that it
happened then trust the daemon to run after just fine.

On Mon, Feb 4, 2019 at 9:57 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the clamav package:
>
> #921399: ClamAV Needs (live-updates) on Post Install
>
> It has been closed by Scott Kitterman .
>
> 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 Scott Kitterman <
> deb...@kitterman.com> by
> replying to this email.
>
>
> --
> 921399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921399
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Scott Kitterman 
> To: 921399-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 05 Feb 2019 04:54:01 +
> Subject: Re: ClamAV Needs (live-updates) on Post Install
> On Mon, 4 Feb 2019 18:56:38 -0700 Brian Holaday 
> wrote:
> > Package: clamav
> > Version: 0.100.2+dfsg-0+deb9u1
> > Severity: important
> >
> > Issue: Kickstart an Update on Install
> > Upon completing the install would an update be needed for scanning like
> > shown below before scanning a directory?
> >
> > # KickStart Service (Needs Ran before Scan using Cron)
> > sudo service clamav-freshclam stop
> > sudo freshclam
> > sudo service clamav-freshclam start
>
> No.  Don't do that.  The system will handle it for you.
>
> Scott K
>
>
> -- Forwarded message --
> From: Brian Holaday 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Feb 2019 18:56:38 -0700
> Subject: ClamAV Needs (live-updates) on Post Install
> Package: clamav
> Version: 0.100.2+dfsg-0+deb9u1
> Severity: important
>
> Issue: Kickstart an Update on Install
> Upon completing the install would an update be needed for scanning like
> shown below before scanning a directory?
>
> # KickStart Service (Needs Ran before Scan using Cron)
> sudo service clamav-freshclam stop
> sudo freshclam
> sudo service clamav-freshclam start
>

Bug#921400: closed by Scott Kitterman (Re: [Pkg-clamav-devel] Bug#921400: ClamAV tosses error on notifications)

[Brian Holaday]

Great Scott,

I will treat this as a error message (warning) that is suppressed. Are you
able to confirm exactly what clamav-daemon can be used for is this better
to set up or leave clamav running as a daemon by default: what benefit does
it have over using clamav.

On Mon, Feb 4, 2019 at 7:51 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the clamav package:
>
> #921400: ClamAV tosses error on notifications
>
> It has been closed by Scott Kitterman .
>
> 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 Scott Kitterman <
> deb...@kitterman.com> by
> replying to this email.
>
>
> --
> 921400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921400
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Scott Kitterman 
> To: 921400-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 04 Feb 2019 21:47:04 -0500
> Subject: Re: [Pkg-clamav-devel] Bug#921400: ClamAV tosses error on
> notifications
> On Monday, February 04, 2019 07:06:37 PM Brian Holaday wrote:
> > Package: clamav
> > Version: 0.100.2+dfsg-0+deb9u1
> > Severity: normal
> >
> > Step #1: Run Update
> > # sudo freshclam
> >
> > Step #2: Error is shown:
> > "Clamd was NOT notified: Can't connect to clamd through
> > /var/run/clamav/clamd.ctl: No such file or directory"
> >
> > Looking at a fix looks like it may be this:
> > # clamav is dependent of clamav-daemon
> >
> > I have yet to test this however to see if the issue resolves itself :
> seems
> > like on a fresh install this happens.
>
> None of this is a bug.
>
> In Debian, freshclam is configured to run as a daemon.  You do not need to
> run
> it manually.  In any case, all the 'error' means is that clamd isn't
> running.
> If you haven't either installed clamav-daemon or you've stopped it, then
> that's normal.
>
> Scott K
>
>
> -- Forwarded message --
> From: Brian Holaday 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 4 Feb 2019 19:06:37 -0700
> Subject: ClamAV tosses error on notifications
> Package: clamav
> Version: 0.100.2+dfsg-0+deb9u1
> Severity: normal
>
> Step #1: Run Update
> # sudo freshclam
>
> Step #2: Error is shown:
> "Clamd was NOT notified: Can't connect to clamd through
> /var/run/clamav/clamd.ctl: No such file or directory"
>
> Looking at a fix looks like it may be this:
> # clamav is dependent of clamav-daemon
>
> I have yet to test this however to see if the issue resolves itself :
> seems like on a fresh install this happens.
>
>

Bug#921400: ClamAV tosses error on notifications

[Brian Holaday]

Package: clamav
Version: 0.100.2+dfsg-0+deb9u1
Severity: normal

Step #1: Run Update
# sudo freshclam

Step #2: Error is shown:
"Clamd was NOT notified: Can't connect to clamd through
/var/run/clamav/clamd.ctl: No such file or directory"

Looking at a fix looks like it may be this:
# clamav is dependent of clamav-daemon

I have yet to test this however to see if the issue resolves itself : seems
like on a fresh install this happens.

Bug#921399: ClamAV Needs (live-updates) on Post Install

[Brian Holaday]

Package: clamav
Version: 0.100.2+dfsg-0+deb9u1
Severity: important

Issue: Kickstart an Update on Install
Upon completing the install would an update be needed for scanning like
shown below before scanning a directory?

# KickStart Service (Needs Ran before Scan using Cron)
sudo service clamav-freshclam stop
sudo freshclam
sudo service clamav-freshclam start

Bug#921398: ClamAV Needs Updated

[Brian Holaday]

Package: clamav
Version: 0.100.2+dfsg-0+deb9u1

Issue #1: Update to 0.101.1
Upon installation of clamav - running freshclam shows that the local
version is: 0.100.2 and updated version is 0.101.1.

Issue #2: Kickstart an Update on Install
Upon completing the install would an update be needed for scanning files
like shown below?

# KickStart Service (Needs Ran before Scan using Cron)
sudo service clamav-freshclam stop
sudo freshclam
sudo service clamav-freshclam start

Thanks!

Bug#917390: avr-gcc version mismatch

[Brian Holaday]

Adding Microchips Support Responses.

Case Comments
Comment
*Created By: Brian Holaday
<https://microchipsupport.force.com/0051N05UerV> (12/28/2018 12:12 PM)*
Created Attachment: Shot2.png
*Created By: Brian Holaday
<https://microchipsupport.force.com/0051N05UerV> (12/28/2018 12:11 PM)*
Hi Amit,

Looking at your screenshots I see that the GCC-AVR compiler is installed on
Windows automatically. On Linux this is packaged as (gcc-avr) or
downloading the toolkit manually for each project.

I have created a debian bug request:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917390 and reached the
developer to see if we can get the versioning fixed in gcc-avr on build. If
you look at the screenshot I attached their is a version mismatch between
the downloaded version and packaged version in debian.

The project is also here: https://salsa.debian.org/debian/gcc-avr/branches

** Again if we can wait for Hakan (developer) for packing gcc-avr to fix
this then it would be much easier using one tool for install than providing
a backup install to /opt/ like I suggested. It almost might be easier also
to reach out to the debian packaging team to see if MP LAB X and the other
toolkits could be complied into a package. **

Link #1: https://wiki.debian.org/HowToPackageForDebian (Packaging)
Link #2: https://www.debian.org/doc/manuals/maint-guide/ (Guidance)
Link #3: You could email ha...@debian.org if you have questions : at least
I came to him for reporting.

I just would hate to see MP LAB X be complied from their own tool base but
rather use what has been set up.
*Created By: Amit Shali
<https://microchipsupport.force.com/005o002d1LV> (12/28/2018 5:34 AM)*
Hi Brian,

Thanks for reporting this.

I was able to replicate the AVR and AVRASM 2 toolchain selection issue
under Ubuntu 16.04.

Steps to replicate:
a. Create a new standalone project under MPLAB X IDE
b. Select ATMEGA328P and Atmel-ICE
c. AVR or AVRASM 2 isn’t selectable

However, this issue didn't occur on my Windows machine.
I have attached screenshots from my Windows machine.

We will investigate this in depth.
I will keep you posted on the updates on this.

Regards,
Amit
*Created By: Brian Holaday
<https://microchipsupport.force.com/0051N05UerV> (12/27/2018 1:12 AM)*
I figured out the issue with my Debian install and MPLab X. I will share
the results below after looking at patching:

Please correct: http://microchipdeveloper.com/install:mplabx-lin64

Debian: Ubuntu and Mint: (dpkg)
#sudo dpkg --add-architecture i386
#sudo apt-get install libc6:i386 libx11-6:i386 libxext6:i386
libstdc++6:i386 libexpat1:i386
#sudo apt-get install gcc-avr avr-libc

Attempt #1: Fail on GCC-AVR
MPLAB X requires gcc-avr to be installed if using an ATMEGA* however I
found out that for now this package on Debian needs re-worked with
versioning for this to work on MPLAB X. I did install this package and a
toolchain became available however the packaging was off with versioning on
Debian and the developer pushing this package.

(https://packages.debian.org/stretch/gcc-avr)

Manual Package: GCC-AVR Official
I then tried to download the AVR Toolchain Proper Link: (
http://ww1.microchip.com/downloads/en/DeviceDoc/avr8-gnu-toolchain-3.6.2.1759-linux.any.x86_64.tar.gz
)

Command:
#wget
http://ww1.microchip.com/downloads/en/DeviceDoc/avr8-gnu-toolchain-3.6.2.1759-linux.any.x86_64.tar.gz

#gunzip -k avr8-gnu-toolchain-3.6.2.1759-linux.any.x86_64.tar.gz
#mkdir /opt/avr-gcc
#mv avr8-gnu-toolchain-3.6.2.1759-linux.any.x86_64.tar.gz /opt/avr-gcc

I then added the New Toolchain to MPLAB X : Project Selection works: All is
good.


Final:
What was wrong was I had thought the package avr-gcc used by Debian was
current. It appears that on build it is missing several items and I have
filed a bug with the developer to see if we can get this fixed and/or move
the toolchain to /opt/ or you could even include this on install as you did
another toolchain. Ideally I would use /opt to export your toolchains and
configure MPLAB to pick them up rather than depend on a second package.

I personally use avrdude for programming and am building a tool for the AVR
ICE on a breadboard - I would almost like to see MP LAB X use GCC rather
than use Java as more open source projects come to live.
*Created By: Brian Holaday
<https://microchipsupport.force.com/0051N05UerV> (12/26/2018 12:05 AM)*
Created Attachment: A1.png

On Fri, Dec 28, 2018 at 2:40 PM Brian Holaday 
wrote:

> FYI:
>
> On Fri, Dec 28, 2018 at 12:16 PM Brian Holaday 
> wrote:
>
>>
>> FYI:
>>
>> -- Forwarded message -
>> From: Brian Holaday 
>> Date: Fri, Dec 28, 2018 at 11:47 AM
>> Subject: Re: avr-gcc version mismatch
>> To: Hakan Ardo 
>>
>>
>> Hi Hakan,
>>
>> #1. I have attached a screenshot below just in case you need to see where
>> I am seeing the error after installing MP Lab X. I also 

Bug#917390: avr-gcc version mismatch

[Brian Holaday]

FYI:

On Fri, Dec 28, 2018 at 12:16 PM Brian Holaday 
wrote:

>
> FYI:
>
> -- Forwarded message -----
> From: Brian Holaday 
> Date: Fri, Dec 28, 2018 at 11:47 AM
> Subject: Re: avr-gcc version mismatch
> To: Hakan Ardo 
>
>
> Hi Hakan,
>
> #1. I have attached a screenshot below just in case you need to see where
> I am seeing the error after installing MP Lab X. I also included some
> directions I followed for the install if you wanted to test MP LAB X.
>
> #2. I will check out the git package to see if I can provide any help: I
> very new to packaging but thought I would at least explore the project. I
> do write some C but aim to try and help with troubleshooting.
>
> #3. I have filled a bug with Microchip for MP LAB X (00367883) and am
> working with them to see what they want to do and am providing updates from
> here. I just want to make sure their document is corrected. I much rather
> try and have them use what is working than go explore to fix this using my
> 2nd backup fix. I am not sure either but I almost would think MP LAB X at
> some point could be packaged in the same way.
>
> Thanks!
>
> 
>
> Directions:
>
> Please correct: http://microchipdeveloper.com/install:mplabx-lin64
>
> Debian: Ubuntu and Mint: (dpkg)
> #sudo dpkg --add-architecture i386
> #sudo apt-get install libc6:i386 libx11-6:i386 libxext6:i386
> libstdc++6:i386 libexpat1:i386
> #sudo apt-get install gcc-avr avr-libc
>
> Attempt #1: Fail on GCC-AVR
> MPLAB X requires gcc-avr to be installed if using an ATMEGA* however I
> found out that for now this package on Debian needs re-worked with
> versioning for this to work on MPLAB X. I did install this package and a
> toolchain became available however the packaging was off with versioning on
> Debian and the developer pushing this package.
>
> (https://packages.debian.org/stretch/gcc-avr)
>
> Manual Package: GCC-AVR Official
> I then tried to download the AVR Toolchain Proper Link: (
> http://ww1.microchip.com/downloads/en/DeviceDoc/avr8-gnu-toolchain-3.6.2.1759-linux.any.x86_64.tar.gz
> )
>
> Command:
> #wget
> http://ww1.microchip.com/downloads/en/DeviceDoc/avr8-gnu-toolchain-3.6.2.1759-linux.any.x86_64.tar.gz
>
> #gunzip -k avr8-gnu-toolchain-3.6.2.1759-linux.any.x86_64.tar.gz
> #mkdir /opt/avr-gcc
> #mv avr8-gnu-toolchain-3.6.2.1759-linux.any.x86_64.tar.gz /opt/avr-gcc
>
> I then added the New Toolchain to MPLAB X : Project Selection works: All
> is good.
>
> Picture of Compiler UI
>
> [image: Shot2.png]
>
> On Thu, Dec 27, 2018 at 1:04 PM Hakan Ardo  wrote:
>
>> Hi,
>> for details, please check out the package repo:
>>
>> https://salsa.debian.org/debian/gcc-avr.git
>>
>> There is an upstream branch and an debian branch, so it should be easy to
>> compare. There are also a few patches, listed in debian/patchlist, applied
>> during the build.
>>
>> The main difference is that the build script
>> build-avr8-gnu-toolchain-git.sh is replaced with debian/rules. They should
>> do more or less the same thing. Or atleast they did once, but we have not
>> tracked changes to this script, so they migh have diverged resulting in
>> differences in the build environment and configuration parameters where for
>> example the version string can be defined.
>>
>> We also remove the docs due to license issues and we've applied some
>> patches to allow avr-gcc to be compiled with a modern host gcc and for
>> non-x86 hosts.
>>
>> On Thu, Dec 27, 2018 at 7:20 PM Brian Holaday 
>> wrote:
>>
>>>  Are you able to summarize the changes or am I best to look at the
>>> debian build. I am just determining what changes are made.
>>>
>>> On Thu, Dec 27, 2018, 9:14 AM Hakan Ardo >>
>>>> Yes, latest version is built from 3.6.1 of that tree:
>>>>
>>>>
>>>> http://distribute.atmel.no/tools/opensource/Atmel-AVR-GNU-Toolchain/3.6.1
>>>>
>>>> On Thu, Dec 27, 2018 at 4:33 PM Brian Holaday <
>>>> br...@codemonkeyrawks.net> wrote:
>>>>
>>>>> No problem,
>>>>>
>>>>> I just know using MP LAB X this is reported as 1.0 instead of 5.4. If
>>>>> you get this fixed I may use it depending on the change.
>>>>>
>>>>> Are you building the package from:
>>>>> http://distribute.atmel.no/tools/opensource/Atmel-AVR-GNU-Toolchain/3.5.4/SOURCES.README
>>>>>
>>>>> I am just curious what changes are different. I have noted:
>>>>> https://github.com/strongly-typed/build-atmel-avr

Bug#848893: closed by Andreas Beckmann <a...@debian.org> (Bug#848893: fixed in nvidia-settings 375.26-2)

[Brian Holaday]

Patch finally arrived via jessie-backports. nvidia-settings is working
correctly.

On Tue, Jan 17, 2017 at 8:05 PM, Brian Holaday <br...@codemonkeyrawks.net>
wrote:

> Hi Andreas,
>
> I will wait for the patch on jessie-backports (currently the branch is
> still on 367.57.2) and will test it once I see the update.
>
> Thanks, Arcade.
>
> On Tue, Jan 10, 2017 at 3:54 PM, Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> This is an automatic notification regarding your Bug report
>> which was filed against the nvidia-settings package:
>>
>> #848893: nvidia-settings: When launching "nvidia-settings" -- "undefined
>> symbol error"
>>
>> It has been closed by Andreas Beckmann <a...@debian.org>.
>>
>> 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 Andreas Beckmann <
>> a...@debian.org> by
>> replying to this email.
>>
>>
>> --
>> 848893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848893
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>>
>> -- Forwarded message --
>> From: Andreas Beckmann <a...@debian.org>
>> To: 848893-cl...@bugs.debian.org
>> Cc:
>> Date: Tue, 10 Jan 2017 22:51:15 +
>> Subject: Bug#848893: fixed in nvidia-settings 375.26-2
>> Source: nvidia-settings
>> Source-Version: 375.26-2
>>
>> We believe that the bug you reported is fixed in the latest version of
>> nvidia-settings, which is due to be installed in the Debian FTP archive.
>>
>> A summary of the changes between this version and the previous one is
>> attached.
>>
>> Thank you for reporting the bug, which will now be closed.  If you
>> have further comments please address them to 848...@bugs.debian.org,
>> and the maintainer will reopen the bug report if appropriate.
>>
>> Debian distribution maintenance software
>> pp.
>> Andreas Beckmann <a...@debian.org> (supplier of updated nvidia-settings
>> package)
>>
>> (This message was generated automatically at their request; if you
>> believe that there is a problem with it please contact the archive
>> administrators by mailing ftpmas...@ftp-master.debian.org)
>>
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Format: 1.8
>> Date: Tue, 10 Jan 2017 23:19:38 +0100
>> Source: nvidia-settings
>> Binary: nvidia-settings libxnvctrl0 libxnvctrl-dev
>> Architecture: source
>> Version: 375.26-2
>> Distribution: unstable
>> Urgency: medium
>> Maintainer: Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth
>> .debian.org>
>> Changed-By: Andreas Beckmann <a...@debian.org>
>> Description:
>>  libxnvctrl-dev - NV-CONTROL X extension (development files)
>>  libxnvctrl0 - NV-CONTROL X extension (runtime library)
>>  nvidia-settings - tool for configuring the NVIDIA graphics
>> driver${nvidia:LegacyDes
>> Closes: 848893
>> Changes:
>>  nvidia-settings (375.26-2) unstable; urgency=medium
>>  .
>>* pie.patch: New, filter out -pie when linking shared libraries.
>>  (Closes: #848893)
>> Checksums-Sha1:
>>  7051fd4c4fedd12e8a3382eedad1cf83b4b2c24c 2532
>> nvidia-settings_375.26-2.dsc
>>  14b121ecdf206ae47ef892fbde28ad665472bb09 20696
>> nvidia-settings_375.26-2.debian.tar.xz
>> Checksums-Sha256:
>>  133733b851fa797f08e6e808b4dc3c3cc24583b44e046d538048d639de096dc2 2532
>> nvidia-settings_375.26-2.dsc
>>  4f72a9bf92d39a275081b129aae2d8e0651fea7b4bf2a770d6e91f6eab19fe8b 20696
>> nvidia-settings_375.26-2.debian.tar.xz
>> Files:
>>  d61e60d0200c7d7309a742df37d0bb1f 2532 x11 optional
>> nvidia-settings_375.26-2.dsc
>>  386447836f0643c7670433b1c84fabde 20696 x11 optional
>> nvidia-settings_375.26-2.debian.tar.xz
>>
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1
>>
>> iQIcBAEBCAAGBQJYdWCuAAoJEF+zP5NZ6e0I+9kP/iy006ePiDXh8U/tPclStJLP
>> Y2j/ckW06qNE1RFYUHZIELQLoodbQrSywEEvBtMY50GC5BnZVMZUvM3SuMFQzsJO
>> bcXwLgZuzW2fTqc1fec83c3HFS9+J8kZS0juaBjgUga1HMWpDqjzuh1q0kw06TO6
>> CEiDd283x6x1HQwnkD4W1oEk+lhjM5oxNvkaEZTZ1b1J4HRN7R0Q6SDQ7l21wSr5
>> 0qiFwIi/gOradIjHtg5RM6CxmeG+Bzr5+ZW406CVOzAMmIeKd+jsxkGBeFtLs7m0
>> rKWKNTpeRUfL6rQo2zgXcND42CIaMCAHGKJHy2IZ+MQaDsYWgDu1Y3lZY+OrDM19
>> MRItmT1WUmEE3KJqHlIlx4Uyw/DI1feiOeIwTD+KZlwRc/VIdilkc7/A01ICmkY6
>> DvVHi6xk+z41wBFg30LvZsEhFa6nWZ/VPHMhzF

Bug#848893: closed by Andreas Beckmann <a...@debian.org> (Bug#848893: fixed in nvidia-settings 375.26-2)

[Brian Holaday]

Hi Andreas,

I will wait for the patch on jessie-backports (currently the branch is
still on 367.57.2) and will test it once I see the update.

Thanks, Arcade.

On Tue, Jan 10, 2017 at 3:54 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the nvidia-settings package:
>
> #848893: nvidia-settings: When launching "nvidia-settings" -- "undefined
> symbol error"
>
> It has been closed by Andreas Beckmann .
>
> 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 Andreas Beckmann <
> a...@debian.org> by
> replying to this email.
>
>
> --
> 848893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848893
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Andreas Beckmann 
> To: 848893-cl...@bugs.debian.org
> Cc:
> Date: Tue, 10 Jan 2017 22:51:15 +
> Subject: Bug#848893: fixed in nvidia-settings 375.26-2
> Source: nvidia-settings
> Source-Version: 375.26-2
>
> We believe that the bug you reported is fixed in the latest version of
> nvidia-settings, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 848...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Andreas Beckmann  (supplier of updated nvidia-settings
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Tue, 10 Jan 2017 23:19:38 +0100
> Source: nvidia-settings
> Binary: nvidia-settings libxnvctrl0 libxnvctrl-dev
> Architecture: source
> Version: 375.26-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian NVIDIA Maintainers  alioth.debian.org>
> Changed-By: Andreas Beckmann 
> Description:
>  libxnvctrl-dev - NV-CONTROL X extension (development files)
>  libxnvctrl0 - NV-CONTROL X extension (runtime library)
>  nvidia-settings - tool for configuring the NVIDIA graphics
> driver${nvidia:LegacyDes
> Closes: 848893
> Changes:
>  nvidia-settings (375.26-2) unstable; urgency=medium
>  .
>* pie.patch: New, filter out -pie when linking shared libraries.
>  (Closes: #848893)
> Checksums-Sha1:
>  7051fd4c4fedd12e8a3382eedad1cf83b4b2c24c 2532
> nvidia-settings_375.26-2.dsc
>  14b121ecdf206ae47ef892fbde28ad665472bb09 20696 nvidia-settings_375.26-2.
> debian.tar.xz
> Checksums-Sha256:
>  133733b851fa797f08e6e808b4dc3c3cc24583b44e046d538048d639de096dc2 2532
> nvidia-settings_375.26-2.dsc
>  4f72a9bf92d39a275081b129aae2d8e0651fea7b4bf2a770d6e91f6eab19fe8b 20696
> nvidia-settings_375.26-2.debian.tar.xz
> Files:
>  d61e60d0200c7d7309a742df37d0bb1f 2532 x11 optional
> nvidia-settings_375.26-2.dsc
>  386447836f0643c7670433b1c84fabde 20696 x11 optional
> nvidia-settings_375.26-2.debian.tar.xz
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
>
> iQIcBAEBCAAGBQJYdWCuAAoJEF+zP5NZ6e0I+9kP/iy006ePiDXh8U/tPclStJLP
> Y2j/ckW06qNE1RFYUHZIELQLoodbQrSywEEvBtMY50GC5BnZVMZUvM3SuMFQzsJO
> bcXwLgZuzW2fTqc1fec83c3HFS9+J8kZS0juaBjgUga1HMWpDqjzuh1q0kw06TO6
> CEiDd283x6x1HQwnkD4W1oEk+lhjM5oxNvkaEZTZ1b1J4HRN7R0Q6SDQ7l21wSr5
> 0qiFwIi/gOradIjHtg5RM6CxmeG+Bzr5+ZW406CVOzAMmIeKd+jsxkGBeFtLs7m0
> rKWKNTpeRUfL6rQo2zgXcND42CIaMCAHGKJHy2IZ+MQaDsYWgDu1Y3lZY+OrDM19
> MRItmT1WUmEE3KJqHlIlx4Uyw/DI1feiOeIwTD+KZlwRc/VIdilkc7/A01ICmkY6
> DvVHi6xk+z41wBFg30LvZsEhFa6nWZ/VPHMhzFWE2dvYMi+d8QCIFV3oEF4jdV2h
> Av/WDkCiZVrlOhTpabpI/ISy8Q6OR8Ua07/XC7NtcwCkwfE+dZWCKdH80jAOEqpb
> LRhk31mXBP6duhlixxHLc5d5YLDBmvfAf0dRW3H254rLukD2UyV4RX9NXA8TYkek
> W5vinggmgJs0TKC2khU/f9795EiVAn3PEjtVc5BVZdx40JaWsPYFPQV0ZcOV2EAE
> rzojF9647KG+OWKMIZcx
> =yILY
> -END PGP SIGNATURE-
>
> -- Forwarded message --
> From: Arcademan 
> To: Debian Bug Tracking System 
> Cc:
> Date: Tue, 20 Dec 2016 08:41:15 -0700
> Subject: nvidia-settings: When launching "nvidia-settings" -- "undefined
> symbol error"
> Package: nvidia-settings
> Version: 367.57-1~bpo8+1
> Severity: important
>
> Dear Maintainer,
>
> When launching "nvidia-settings" via the terminal window I see the
> following error:
>
> ERROR: /usr/lib/libnvidia-gtk3.so.367.57: undefined symbol: ctk_init_check
>/usr/lib/libnvidia-gtk3.so.367.57: undefined symbol:
> ctk_get_display
>/usr/lib/libnvidia-gtk3.so.367.57: undefined symbol: ctk_main
> 

Bug#848893: nvidia-settings: When launching "nvidia-settings" -- "undefined symbol error"

[Brian Holaday]

Hi Andreas,

I did some general looking/testing (I am a python/web coder but really
don't know gtk directly but am able to test a few things):

I did a file check:
A. It looks like .nvidia-settings-rc does not get created when running 367.57
yet 375.26.1 does after launch.

I did a library check: (seems to have an issue loading)
B. Testing nvidia-settings using the library directly #nvidia-settings -I
/usr/lib/libnvidia-gtk3.so.367.57 , results in the same error.

I did a command line check: see if the nvidia-driver is working:
C. Testing nvidia-smi, #nvidia-smi, the nvidia modules appear to load just
fine so *it must be a gtk or library related issue under **/usr/lib/
possibly*.

Looking at the sid branch:
https://anonscm.debian.org/cgit/pkg-nvidia/nvidia-settings.git/diff/?h=upstream,
it seems like there was quite a few changes to go though, That is something
a little beyond my build experience.


One Solution:
As far as installing the driver 375.26.1 on Jessie like you suggested it
all works fine (nvidia-settings) works fine.

Bug#844392: vlc refuses to install with debian backports enabled

[Brian Holaday]

Hi Sebastion,

Interesting that the deb package manager will install using the -t flag
even though the repo does not exist online as we both looked at and saw.
Hopefully the apt team can figure a solution out in checking the repo
before installing the package. It also might be bad then I can't install
vlc so a catch 22.

Installing libcss using the debian package seemed to work. I may look at
adding the repo depending as it looks like it requires less install of
packages.

Bug#844392: vlc refuses to install with debian backports enabled

[Brian Holaday]

Hi Sebastian,

Using jessie-backports seemed to fix the issue (should of tried it to begin
with):
apt-get install -t jessie-backports vlc
apt-get install -t jessie-backports browser-plugin-vlc

I was confused on the fact that looking at
https://packages.debian.org/jessie/vlc it shows jessie but does not list
packages for jessie-backports so I assumed there was none even though there
is a package.

I did have one more question: as far as installing libdvdcss: I see that
you guys don't package it, is it best to install via VideoLan directly or
is there a repo set up already under debian packaging?

Thanks, Brian.

Bug#844392: vlc refuses to install with debian backports enabled

[Brian Holaday]

Hi Sebastian,

Yes it is version 2.2.4-1~deb8u1. First time filing a bug.

It happens when trying to install vlc (#apt-get install vlc). From what I
can figure libgles-1-mesa version 12.0.3-1~bpo8+1 and libgles2-mesa
version  12.0.3-1~bpo8+1 gets installed via backports (I think the nvidia
driver changes versions) and causes the issue.

vlc seems to want to expect version 10.3.2-1+deb8u1. I have yet to test
installing vlc without backports.

On Tue, 15 Nov 2016 09:31:34 +0100 Sebastian Ramacher 
wrote:
> Control: tags -1 + moreinfo
>
> On 2016-11-15 00:29:16, Arcademan wrote:
> > Source: vlc
> > Version: 2.2.4-1
>
> Do you mean 2.2.4-1~deb8u1?
>
> > Severity: important
> >
> > Dear Maintainer,
> >
> > *** Reporter, please consider answering these questions, where
appropriate ***
> >
> >* What led up to the situation?
> >  Trying to install vlc with debian jessie backports installed  led
to unmet dependencies
> >
> >  OS: Debian 8.6 (Jessie) with Backports Enabled
> >
> > Error:
> >
> >  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:
> >  vlc : Depends: libgles1-mesa (>= 7.8.1) but it is not going to be
installed or
> > libgles1
> >Depends: libgles2-mesa (>= 7.8.1) but it is not going to be
installed or
> > libgles2
> > E: Unable to correct problems, you have held broken packages.
>
> This looks like you already have some other mesa packages from backports
> installed. Is that correct?
>
> Cheers
> --
> Sebastian Ramacher