Bug#906538: Possibly still not fixed

2018-08-25 Thread Matthias Klumpp
Am Sa., 25. Aug. 2018 um 22:39 Uhr schrieb Alan W. Irwin : > > For those (like me, it is a long story) who want to delay doing a full > system update of Buster, I confirm that > > apt-get install --reinstall libappstream4 > > fixed this severe problem in Debian Buster for me. > > I am surprised

Bug#906538: Possibly still not fixed

2018-08-25 Thread Alan W. Irwin
For those (like me, it is a long story) who want to delay doing a full system update of Buster, I confirm that apt-get install --reinstall libappstream4 fixed this severe problem in Debian Buster for me. I am surprised this issue migrated from Debian unstable to Buster at all. According to

Bug#906538: Possibly still not fixed

2018-08-24 Thread Matthias Klumpp
Source: appstream Source-Version: 0.12.2-2 > Am Fr., 24. Aug. 2018 um 16:02 Uhr schrieb Christoph Berg : > Re: Matthias Klumpp 2018-08-24 > > > Can you verify the issue is fixed when you upgrade the library? > > I'm not seeing any error messages anymore with a fully uptodate buster > system.

Bug#906538: Possibly still not fixed

2018-08-24 Thread Christoph Berg
Re: Matthias Klumpp 2018-08-24 > Can you verify the issue is fixed when you upgrade the library? I'm not seeing any error messages anymore with a fully uptodate buster system. Christoph

Bug#906538: Possibly still not fixed

2018-08-24 Thread Matthias Klumpp
Am Fr., 24. Aug. 2018 um 15:14 Uhr schrieb Christoph Berg : > > Re: Matthias Klumpp 2018-08-24 > > > Are you *sure* that you upgraded *completely*? The fix is in > > libappstream4, and so far all occurrences where people still had the > > bug came from incomplete upgrades. Please check that you

Bug#906538: Possibly still not fixed

2018-08-24 Thread Christoph Berg
Re: Matthias Klumpp 2018-08-24 > Are you *sure* that you upgraded *completely*? The fix is in > libappstream4, and so far all occurrences where people still had the > bug came from incomplete upgrades. Please check that you really also > have libappstream4 >= 0.12.2-2. I did only upgrade

Bug#906538: Possibly still not fixed

2018-08-24 Thread Matthias Klumpp
Am Fr., 24. Aug. 2018 um 10:24 Uhr schrieb Christoph Berg : > > Control: reopen -1 > Control: found -1 0.12.2-2 > Control: severity -1 important > > Re: Johannes Winter 2018-08-23 <20180823115724.64e93...@radell.fritz.box> > > After upgrading appstream to 0.12.2-2 the problem still persists on > >

Bug#906538: Possibly still not fixed

2018-08-24 Thread Christoph Berg
Control: reopen -1 Control: found -1 0.12.2-2 Control: severity -1 important Re: Johannes Winter 2018-08-23 <20180823115724.64e93...@radell.fritz.box> > After upgrading appstream to 0.12.2-2 the problem still persists on > debian sid. The problem is still there with 0.12.2-2: $ sudo apt-get

Bug#906538: Possibly still not fixed

2018-08-23 Thread Johannes Winter
After upgrading appstream to 0.12.2-2 the problem still persists on debian sid.

Bug#906538: Possibly still not fixed

2018-08-20 Thread antoszka
I'm running Kali Linux, but as far as this bug is concerned that shouldn't matter, I'm still hitting the issue after manually upgrading to 0.12.2. I've pasted code in the github issue [1]. [1] https://github.com/ximion/appstream/issues/198#issuecomment-414211767