UP - 01/07/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
grizzler
Posts: 2042
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

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

Postby grizzler » 03 Jul 2014 12:32

Downgrading with apt-get -o Dpkg::Options::="--force-overwrite" install $(cat $Downgrade). Overwrites are carried out:

Code: Select all

dpkg: warning: downgrading knode from 4:4.12.5+really4.4.11.1+l10n-0r0+b8 to 4:4.12.4-1
Preparing to unpack .../knode_4%3a4.12.4-1_amd64.deb ...
Unpacking knode (4:4.12.4-1) over (4:4.12.5+really4.4.11.1+l10n-0r0+b8) ...
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/kde4/apps/knode/pics/key.png', which is also in package libkpgp4 4:4.12.5+really4.4.11.1+l10n-0r0+b8
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/kde4/apps/knode/pics/key_bad.png', which is also in package libkpgp4 4:4.12.5+really4.4.11.1+l10n-0r0+b8
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/kde4/apps/knode/pics/key_ok.png', which is also in package libkpgp4 4:4.12.5+really4.4.11.1+l10n-0r0+b8
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/kde4/apps/knode/pics/key_unknown.png', which is also in package libkpgp4 4:4.12.5+really4.4.11.1+l10n-0r0+b8
The other package is downgraded as well:

Code: Select all

dpkg: warning: downgrading libkpgp4 from 4:4.12.5+really4.4.11.1+l10n-0r0+b8 to 4:4.12.4-1
Preparing to unpack .../libkpgp4_4%3a4.12.4-1_amd64.deb ...
Unpacking libkpgp4 (4:4.12.4-1) over (4:4.12.5+really4.4.11.1+l10n-0r0+b8) ...
After the downgrade run has finished (without interruptions), the conflicting files are still there:

Code: Select all

solydk64@vbox ~ $ ls -l /usr/share/kde4/apps/knode/pics
totaal 56
-rw-r--r-- 1 root root 429 mrt 31 22:36 article.png
-rw-r--r-- 1 root root 416 mrt 31 22:36 eyes.png
-rw-r--r-- 1 root root 382 mrt 31 22:36 greyballchk.png
-rw-r--r-- 1 root root 357 mrt 31 22:36 greyball.png
-rw-r--r-- 1 root root 429 mrt 31 22:36 group.png
-rw-r--r-- 1 root root 582 mrt 31 22:36 ignore.png
-rw-r--r-- 1 root root 250 mrt 31 22:36 key_bad.png
-rw-r--r-- 1 root root 256 mrt 31 22:36 key_ok.png
-rw-r--r-- 1 root root 239 mrt 31 22:36 key.png
-rw-r--r-- 1 root root 245 mrt 31 22:36 key_unknown.png
-rw-r--r-- 1 root root 889 mrt 31 22:36 mail.png
-rw-r--r-- 1 root root 315 mrt 31 22:36 newsubs.png
-rw-r--r-- 1 root root 589 mrt 31 22:36 posting.png
-rw-r--r-- 1 root root 300 mrt 31 22:36 snderr.png
So using --force-overwrite seems to do the job.
Attachments
un-kdenext.txt
Version 1.1.1 of the script.
(4.63 KiB) Downloaded 30 times
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby grizzler » 03 Jul 2014 12:42

zerozero wrote:
grizzler wrote:It will come up on any system that has the full KDE PIM Suite installed and there may be other packages that trigger it as well.
i faced 2 here >> http://forums.solydxk.nl/viewtopic.php? ... =20#p38778
One of those is the same as mentioned in my previous posting. I didn't install okular-extra-backends in this VM, so I didn't see the other one. However, I don't expect any problems with that one either.

Edit: on the other hand, that second one happens during the dist-upgrade (because the new one is a 4.13, it isn't downgraded first). I need to run this again to check...

Edit 2: that'll have to be (much) later today. Wetter's too nice and I'm being dragged outside again... ;)
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby Arjen Balfoort » 03 Jul 2014 12:51

un-kdenext has been adapted with your suggestion.
Testing it now on bare metal :)


SolydXK needs you!
Development | Testing | Translations

User avatar
Santa
Posts: 16
Joined: 09 Jun 2013 23:39

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

Postby Santa » 03 Jul 2014 13:27

grizzler, I think I already know the answer, but akisng anyway: do you have any experience packaging kde or something else for debian?
grizzler wrote:Anyone not reading the instructions will blow up his system. That'll teach 'em!
Well, this is just blaming users for packaging problems which developers weren't able to solve properly. Also note that SolydK was suposed to be user friendly.
Sometimes, standing for what you believe means standing alone.

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

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

Postby Arjen Balfoort » 03 Jul 2014 15:16

Okay, I ran UM with the adapted script.

I felt brave (just created a system image :) ), and also removed the multimedia repository!

In the confirmation box:

Code: Select all

The following packages will be REMOVED:
amarok audacity browser-plugin-vlc dvgrab ffmpeg ffmpegthumbnailer gdebi-kde jitsi kaddressbook kde-config-touchpad kdenlive knotes libasound2-plugins:i386 libavdevice55 libavfilter3 libcogl-pango12 libcogl12 libffmpegthumbnailer4 libjitsi-jni libkdepim4 libkleo4 liblavfile-2.1-0 liblavplay-2.1-0 libmlt++3 libmlt6 libquicktime2 melt mjpegtools plasma-scriptengine-python plasma-widget-facebook python-kde4 python3-pykde4 skype:i386 software-properties-kde userconfig vlc vlc-plugin-notify vlc-plugin-pulse
I just hit OK.

Downgrade went fine, but when upgrading libgdbm3:i386:

Code: Select all

Preparing to unpack .../libgdbm3_1.8.3-12+b1_i386.deb ...
Unpacking libgdbm3:i386 (1.8.3-12+b1) over (1.8.3-12) ...
dpkg: error processing archive /var/cache/apt/archives/libgdbm3_1.8.3-12+b1_i386.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libgdbm3/changelog.Debian.gz', which is different from other instances of package libgdbm3:i386
I'm running SolydK64, and have libgdbm3:amd64 installed. So, I purged libgdbm3:i386:

Code: Select all

sudo apt-get purge libgdbm3:i386
This didn't affect other packages.

I hit Refresh, and the upgrade continued.

I had to downgrade the multimedia packages in the maintenance section of the UM, and reinstall those package that were removed.

Conclusion:
Grizzler's script functions great: no issues whatsover.
We need to purge libgdbm3:i386 on SolydK64 before upgrading.
Do not remove the multimedia repository during the update, but do that separately.


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 03 Jul 2014 15:26

Santa wrote:grizzler, I think I already know the answer, but akisng anyway: do you have any experience packaging kde or something else for debian?
Some (not KDE).
grizzler wrote:Anyone not reading the instructions will blow up his system. That'll teach 'em!
No, I didn't. I wrote:
Anyone not reading the instructions will blow up his system. That'll teach 'em! :twisted:

Seriously though. That is going to be a problem. People will have to do what they're told. There will be some who won't...
Santa wrote:Well, this is just blaming users for packaging problems which developers weren't able to solve properly.
No, it isn't. It's a joke, followed by a sentence expressing concern about that issue.
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby grizzler » 03 Jul 2014 15:38

Schoelje wrote:Conclusion:
Grizzler's script functions great: no issues whatsover.
That would have been nice. However...

I ran the dist-upgrade after adding okular-extra-backends (and some other bits) and ran into the problem zerozero described here (last problem mentioned there). Because okular's new version is in the 4.13 range, it isn't downgraded early. So the overwrite issue still comes up during the dist-upgrade. In order to handle that, a similar addition to that bit is required.

Version 1.1.2 of the script is attached.
Attachments
un-kdenext.txt
(4.66 KiB) Downloaded 27 times
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby Arjen Balfoort » 03 Jul 2014 15:43

I see, but that would be the case if the UM would use un-kdenext for the dist-upgrade as well, but UM runs un-kdenext with the "-d" parameter only. UM was not designed to let the upgrading be handled by an external script. I can, however, adapt UM to always run the dist-upgrade with Dpkg::Options::="--force-overwrite" but I don't know whether that's a good idea.


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 03 Jul 2014 15:58

I'm not sure that's a good idea in general. But this is a special situation which shouldn't occur more often (should it?). So maybe you could add a condition somewhere in the UM's code to have the force-overwrite bit added only with this upgrade? I admit I've never looked at the UM's code, so I have no idea if that's feasible...

Edit: alternative would be to force these packages to upgrade during the downgrade stage, but I'm not sure that wouldn't create other issues. I'll give it a try though.
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby Arjen Balfoort » 03 Jul 2014 16:11

I'll check UM this weekend then.

I also found a graphical change. Not an issue, but I thought I was going mad:
Before UP
msgbox-before-up.png
msgbox-before-up.png (13.21 KiB) Viewed 1689 times
After UP
msgbox-after-up.png
msgbox-after-up.png (5.04 KiB) Viewed 1689 times


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 03 Jul 2014 17:18

Schoelje wrote:I'll check UM this weekend then.
May not be necessary. Getting rid of everything from kdenext during downgrading appears to work. I'll run some more tests later today (possibly tomorrow) and let you know.

Edit: no errors during downgrade or dist-upgrade, but after rebooting I can't get past the login screen. No time to look into that right now. Later.

Ah, right. It's startkde 4.8.2 from solydk-system-adjustments 1.2.9 again. Because the upgrading of kde-workspace-bin has moved from the dist-upgrade to the downgrade stage, overwriting the old version of startkde with the 4.11.9 one is cancelled out by some action of solydk-system-adjustments 1.2.9, before this is overwritten (during dist-upgrade) by 1.3.0, which doesn't have a startkde to replace the default one (which is a good thing in itself). I think.
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby grizzler » 03 Jul 2014 17:20

Santa wrote:Yes, it is. Or, alternatively you don't have much experience packaging and you have no idea how to solve this in packaging, because this is a packaging isssue, you know? Do you remember any single upgrade pack where I had to write such an upgrade script?
I don't even remember you, so why would I remember anything you had or didn't have to write?

If you have a better idea to handle this, come up with something constructive or take it up with Arjen instead of insulting people who are just trying to help. I'm not going to respond to you any further.
Frank

SolydX EE 64 - tracking Debian Testing

woodsman
Posts: 115
Joined: 06 Jun 2014 01:59

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

Postby woodsman » 03 Jul 2014 18:38

what's the output of
dpkg -l | grep firefox
As expected: firefox 30.0 i386 The Firefox web browser

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

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

Postby Arjen Balfoort » 03 Jul 2014 21:09

The last two posts of Santa were removed.
They didn't seem to serve any other purpose then to vent his/her displeasure with the current situation.


SolydXK needs you!
Development | Testing | Translations

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

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

Postby zerozero » 04 Jul 2014 00:16

woodsman wrote:
what's the output of
dpkg -l | grep firefox
As expected: firefox 30.0 i386 The Firefox web browser
usually we are used to share the real output of the requested commands ;)
but anyway i will guess that something went amiss during the update;
try this

Code: Select all

sudo apt-get install --reinstall firefox firefox-solydxk-adjustments
you probably need to logout/login
bliss of ignorance

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

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

Postby grizzler » 04 Jul 2014 10:33

Yesterday, I wrote:Ah, right. It's startkde 4.8.2 from solydk-system-adjustments 1.2.9 again...
I've modified the script so it will process any update for solydk-system-adjustments first, before downgrading all the kdenext packages. That way the real startkde file is restored when the upgrade of kde-workspace-bin is processed, which happens during the downgrade stage. So far, that seems to have worked as expected. Now for the dist-upgrade test.

I'll provide version 1.2.0 of the script later today.
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby Arjen Balfoort » 04 Jul 2014 10:59

Cool!

I even upgraded my main system.

downgrade, dist-upgrade, removal of multimedia, another downgrade, replace kdm with ligthdm, install systemd, and just one issue: I couldn't normally shutdown, or restart. KDE hung, and I had to forcefully shutdown the system.

The solution was rather simple: boot into recovery mode as root, and run these commands:

Code: Select all

rm /tmp; mkdir /tmp; chmod 777 /tmp; chmod +t /tmp
rm -r /var/tmp/*


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 04 Jul 2014 11:31

So /tmp is no longer a symlink to /var/tmp? Is that an 'official' change?

Are you sure about the 777? I thought /tmp was supposed to be 2777 or 1777 (always forget which - the t-bit in drwxrwxrwt).

My tests haven't produced anything unexpected, by the way, but I still think we need a lot more people testing this. I'm also going to set up a couple of old-ish machines (even got my old laptop working again...) to try it on.

The new version of the script is attached. It's also available here: http://duinsoft.nl/pkg/pool/all/un-kdenext (be careful with that link - in my firefox it opens as a text file on the same tab...).

Edit: forgot to mention, this version also tries to remove the old hal packages. If you don't want that, I can add a switch to make it optional.
Attachments
un-kdenext.txt
md5: 76c668e49e857b9cb30cb801f24a7c69
(5.59 KiB) Downloaded 27 times
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby Arjen Balfoort » 04 Jul 2014 12:01

grizzler wrote:So /tmp is no longer a symlink to /var/tmp? Is that an 'official' change?
Yep, for the next ISOs.
grizzler wrote:Are you sure about the 777? I thought /tmp was supposed to be 2777 or 1777 (always forget which - the t-bit in drwxrwxrwt).
Totally forgot about that! updated my previous post.
grizzler wrote:Edit: forgot to mention, this version also tries to remove the old hal packages. If you don't want that, I can add a switch to make it optional.
Fine, just leave it there. I had it in the post-script, but you're probably right doing it before the upgrade.

I just uploaded the script to the server.


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 04 Jul 2014 15:41

Couple of duh moments:
  • we don't want to add code to external programs (i.e. the UM) to make sure we're not trying to install solydk-system-adjustments on SolydX, so the pre-downgrade apt-get install should only run if the package is installed in the first place
  • purging something that isn't there may not really be a problem, but it looks off, so we want to check if a package is installed before we try to remove it
Working on version 1.3.0 of the script...
Frank

SolydX EE 64 - tracking Debian Testing


Return to “Testing zone”

Who is online

Users browsing this forum: No registered users and 1 guest