UP - 01/10/2014 [TESTING] [DONE]

SolydXK is too quiet for you? SolydXK Enthusiast Editions, based on Debian Testing is for you! Here you can find news about Debian Testing and Unstable too, and also tests on SolydXK programs.
The support for SolydXK EE is provided by the community.
User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 16:19

Hmmm... this second virtual machine frozen during the update too. Going to reboot and see what happens.

Well, not the machine, just the UP got frozen.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 16:54

Not freezings after rebooting. The process completed, but I was in a Razor-Qt sessions instead of KDE. When rebooting I got this error.

Image

Might be a clue of the reboot/logout issue some users have reported? I was not permitted to reboot so I logged out, then logged into KDE to see what happens and problems disappeared. Rebooted repeatedly and keeps going fine.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 17:01

Update: Now the UP manager shows a no network icon and it really doesn't connect to the web if I try to check it. But the network is fine. Firefox works fine. Only UP doesn't seem to connect. Connection timed out. Is it only me?
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 17:10

Aaah, it's in all the systems. My main desktop and all the VMs. Is the server down or flooded?
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
grizzler
Posts: 2217
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP - 01/10/2014 [TESTING]

Postby grizzler » 30 Sep 2014 17:25

Probably down. There appears to be a problem with one of the production servers (DMO).
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 17:28

Yep. I just saw the zz post in the VLC issues thread.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: UP - 01/10/2014 [TESTING]

Postby fleabus » 30 Sep 2014 17:31

Schoelje wrote:I've updated the pre-up script which now handles the libavformat55 package correctly (tested on SolydK64, SolydX32, and SolydX64)
I only read these posts after my test, and so paid no special attention to the libavformat thing. Having carried it all out with the terminal I'm left with this:

Code: Select all

fleabus@dv7-1270us ~ $ apt policy libavformat*
libavformat52:
  Installed: (none)
  Candidate: (none)
  Version table:
libavformat53:
  Installed: (none)
  Candidate: (none)
  Version table:
libavformat55:
  Installed: 6:10.3-1
  Candidate: 6:10.4-1
  Version table:
     6:10.4-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 6:10.3-1 0
        500 http://debian.solydxk.com/security/ testing/updates/main amd64 Packages
        100 /var/lib/dpkg/status
libavformat56:
  Installed: 6:11-1
  Candidate: 6:11-1
  Version table:
 *** 6:11-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
        500 http://debian.solydxk.com/security/ testing/updates/main amd64 Packages
        100 /var/lib/dpkg/status
libavformat-extra-52:
  Installed: (none)
  Candidate: (none)
  Version table:
libavformat-extra-53:
  Installed: (none)
  Candidate: (none)
  Version table:
libavformat-dev:
  Installed: (none)
  Candidate: 6:11-1
  Version table:
     6:11-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
        500 http://debian.solydxk.com/security/ testing/updates/main amd64 Packages

User avatar
Arjen Balfoort
Site Admin
Posts: 9502
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: UP - 01/10/2014 [TESTING]

Postby Arjen Balfoort » 30 Sep 2014 17:49

The server was unreachable and I had to reboot it.
That hasn't happened in a very long time.

Unfortunately something has gone wrong with the multimedia repository.
Both production and testing were updated and there is no way I can revert the production version back to its original state.

Does this accidental update pose problems with production systems that you know of?


SolydXK needs you!
Development | Testing | Translations

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 17:51

paid no special attention to the libavformat thing.
Same here. Should we remove libavformat55?
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: UP - 01/10/2014 [TESTING]

Postby zerozero » 30 Sep 2014 17:53

Schoelje wrote: Does this accidental update pose problems with production systems that you know of?
http://forums.solydxk.nl/viewtopic.php?f=7&t=4792
at least vlc and ffmpeg are broken from what i can see; possible others.
bliss of ignorance

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 17:55

Does this accidental update pose problems with production systems that you know of?
Not yet AFAIK. But UP went smooth so I guess there won't be a problem once the multimedia repo behaves again.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 17:57

zerozero wrote:
Schoelje wrote: Does this accidental update pose problems with production systems that you know of?
http://forums.solydxk.nl/viewtopic.php?f=7&t=4792
at least vlc and ffmpeg are broken from what i can see; possible others.
Oh, I see. I don't have any of those.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
grizzler
Posts: 2217
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP - 01/10/2014 [TESTING]

Postby grizzler » 30 Sep 2014 18:04

Schoelje wrote:Does this accidental update pose problems with production systems that you know of?
Provided the update is complete, I don't think it would cause too much problems. Unfortunately, it seems to be incomplete. On top of that, the mirrors - at least the Dutch one - appear to be in their original state.

Edit: would it be possible to 'restore' the main dmo repository using one of the mirrors?
Never mind. I see the Dutch mirror has now started to update. [Scratch that - only the date stamps on the directories appear to have changed...]
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
grizzler
Posts: 2217
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP - 01/10/2014 [TESTING]

Postby grizzler » 30 Sep 2014 18:25

I replaced multimedia with multimedia.new in one of my VMs and ran a dist-upgrade. No real conflicts, just the new versions of vlc and vlc-plugin-notify held back. So as I expected, a fully updated multimedia repo doesn't seem to cause real problems.

Edit: of course, this VM is very basic...
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
Arjen Balfoort
Site Admin
Posts: 9502
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: UP - 01/10/2014 [TESTING]

Postby Arjen Balfoort » 30 Sep 2014 18:33

I've taken the multimedia repository from the Dutch mirror.
Is this solving this issue?


SolydXK needs you!
Development | Testing | Translations

User avatar
grizzler
Posts: 2217
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP - 01/10/2014 [TESTING]

Postby grizzler » 30 Sep 2014 18:43

Getting 0 upgrades available (in another VM) if I do dist-upgrade with the main dmo repo, so it looks like it's fixed.
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 30 Sep 2014 18:48

Thumbsup! Great job, folks.
This likely means that your installation is broken. -Mr Pixbuf.

Image

User avatar
grizzler
Posts: 2217
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP - 01/10/2014 [TESTING]

Postby grizzler » 30 Sep 2014 19:02

Right. Back to testing the 01-10-2014 UP. ;)

Earlier this evening I upgraded yet another VM (SolydK, 64-bit, with dmo) without issues. I did notice the libavformat55 fix from the pre-up file was only partially useful there, though (libavcodec-extra-56 is incompatible with dmo, so it's removed again during the dist-upgrade).
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: UP - 01/10/2014 [TESTING]

Postby zerozero » 30 Sep 2014 21:49

Code: Select all

Attempt to unlock mutex that was not locked
with this output, mirage crashes and burns

Code: Select all

zerozero@home ~ $ mirage
/usr/lib/python2.7/dist-packages/mirage.py:608: Warning: The property GtkWindow:allow-shrink is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.window.set_property('allow-shrink', False)
Attempt to unlock mutex that was not locked
Aborted
the only debian bug report close to this is submitted to reportbug [https://bugs.debian.org/cgi-bin/bugrepo ... bug=758619 ];
there's one at ubuntu [https://bugs.launchpad.net/ubuntu/+sour ... ug/1346299 ] against psensor.

in all situations the problem seems the same: deprecation of gtk2 code [1 and 2]
bliss of ignorance

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: UP - 01/10/2014 [TESTING]

Postby zerozero » 30 Sep 2014 21:50

had to re-install virtualbox-guest-dkms in K-64 to have proper screen resolution, full-screen and correct mouse integration

Code: Select all

-------- Uninstall Beginning --------
Module:  virtualbox-guest
Version: 4.3.14
Kernel:  3.16-2-amd64 (x86_64)
-------------------------------------

Status: This module version was INACTIVE for this kernel.
depmod............

DKMS: uninstall completed.

------------------------------
Deleting module version: 4.3.14
completely from the DKMS tree.
------------------------------
Done.
Unpacking virtualbox-guest-dkms (4.3.14-dfsg-1) over (4.3.14-dfsg-1) ...
Preparing to unpack .../virtualbox-guest-utils_4.3.14-dfsg-1_amd64.deb ...
Unpacking virtualbox-guest-utils (4.3.14-dfsg-1) over (4.3.14-dfsg-1) ...
Preparing to unpack .../virtualbox-guest-x11_4.3.14-dfsg-1_amd64.deb ...
Unpacking virtualbox-guest-x11 (4.3.14-dfsg-1) over (4.3.14-dfsg-1) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up virtualbox-guest-utils (4.3.14-dfsg-1) ...
Setting up virtualbox-guest-dkms (4.3.14-dfsg-1) ...
Loading new virtualbox-guest-4.3.14 DKMS files...
Building only for 3.16-2-amd64
Building initial module for 3.16-2-amd64
Done.

vboxguest:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.16-2-amd64/updates/

vboxsf.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.16-2-amd64/updates/

vboxvideo.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.16-2-amd64/updates/

sed: -e expression #1, char 6: unknown command: `m'
depmod....

DKMS: install completed.
Setting up virtualbox-guest-x11 (4.3.14-dfsg-1) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
bliss of ignorance


Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 16 guests