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.
woodsman
Posts: 115
Joined: 06 Jun 2014 01:59

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

Postby woodsman » 02 Jul 2014 01:36

Using SolydX fully updated with the testing repo. The solydx-meta-office package does not work, invoking a dialog about unresolvable dependencies. Marking the packages individually works as expected.

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

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

Postby Arjen Balfoort » 02 Jul 2014 02:04

woodsman wrote:Using SolydX fully updated with the testing repo. The solydx-meta-office package does not work, invoking a dialog about unresolvable dependencies. Marking the packages individually works as expected.
solydxk-meta-office dependencie issue solved.


SolydXK needs you!
Development | Testing | Translations

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

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

Postby Arjen Balfoort » 02 Jul 2014 02:46

Moved UM posts to its proper topic: http://forums.solydxk.nl/viewtopic.php? ... 9&start=40


SolydXK needs you!
Development | Testing | Translations

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

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

Postby ScottQuier » 02 Jul 2014 11:40

Schoelje wrote: 2. I probably can enforce a downgrade on a fixed set of packages with the UM, but how about those terminal users that simply run dist-upgrade?

As an alternative solution, we can also wait until all necessary files enter testing: postpone, or even cancel this UP.
For #2, if you can set up the UM to handle the UM users and you can provide a set of directions for the terminal users, then I think you are golden. The UM will handle it for those who use it.

The terminal users are on their own to either follow your directions or bork their system. And, if they bork their system, then they can fix it. Or, is that too harsh?

If a postponement of the UP is required to make it right, then postpone it. But, not doing the UP would not be my first choice ... at not least not without a fair bit of communication to the community. Without wanting to throw stones, anything else would look a bit too much like LMDE of old.
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

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

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

Postby grizzler » 02 Jul 2014 11:57

grizzler wrote:I'll try the same upgrade procedure again tomorrow, after first installing the Suite from kdenext.
Currently running the dist-upgrade. The preceding downgrade went almost as well as the one without the Suite. Unfortunately, between versions a file has been moved from one package to another and of course those packages happened to be downgraded in the wrong order, causing an overwrite conflict. Downgrading the package with the problem separately afterwards fixed it.

Also two removals during the downgrade: kdepim-groupware and kdepim-wizards. These two only exist in squeeze and wheezy, so that's not surprising.
schoelje wrote: I like downgrading, but I have some doubts about that.

Which packages do we need to downgrade?
Doesn't that all depend on what is installed by the user?
Yes, that's what my 'un-kdenext' script is for. It builds a list of packages to downgrade. It's supposed to do that on the system to be downgraded, so the list isn't built in advance.
I hadn't anticipated the overwrite issue though, and if that can occur on a system as 'clean' as this VM, with only the PIM Suite added to the basic install, I wonder where else it could show up.
I probably can enforce a downgrade on a fixed set of packages with the UM, but how about those terminal users that simply run dist-upgrade?
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...

I wanted to attach the script for people to look at, but I'm getting 'The extension is not allowed' (what extension? it doesn't frikking have one!), so I'll put it on my site somewhere later today.
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

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

Postby ScottQuier » 02 Jul 2014 12:12

grizzler wrote:
grizzler 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...

I wanted to attach the script for people to look at, but I'm getting 'The extension is not allowed' (what extension? it doesn't frikking have one!), so I'll put it on my site somewhere later today.
Let 'em ... it'll serve them right. BTW - I'm one of those that preferrs to use the terminal :)

As for the extension .... just add ".txt" and it should be attachable. Or, you can simple post it between code tags.
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

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

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

Postby Arjen Balfoort » 02 Jul 2014 12:53

As an experiment I ran this in the pre-script:

Code: Select all

if [ "$RELEASE" == "solydk32" ] || [ "$RELEASE" == "solydk64" ]; then
  apt-get install --yes --force-yes python-kde4=4:4.12.2-3 python3-pykde4=4:4.12.2-3
fi
UM told me that it would remove these:

Code: Select all

gdebi-kde kde-config-touchpad plasma-scriptengine-python plasma-widget-facebook python-kde4 python3-pykde4 software-properties-kde userconfig
, but it didn't take the result of the pre-script into account.

All went fine, and nothing was removed.
The post-script removed hal, and there were no problems rebooting.

I think that's a step further in the right direction, but still this leaves me with unavailable packages (kdenext).
I'm running "Downgrading packages" in the UM maintenance section to see how that goes:

Code: Select all

The following NEW packages will be installed:
libakonadi-notes4 libcalendarsupport4 libgrantlee-core0 libgrantlee-gui0 libincidenceeditorsng4 libkalarmcal2 libkdepimdbusinterfaces4 libkdgantt2-0 libkgapi2-2 libkmbox4 libkolab0 libkolabxml0 libkpgp4 libktnef4 libmailcommon4 libmailimporter4 libmessagecomposer4 libmessagecore4 libmessageviewer4 libpimcommon4 libsendlater4 libtemplateparser4 libxerces-c3.1
 

The following packages are going to be downgraded:
dolphin gwenview kaddressbook kcharselect kde-base-artwork kde-baseapps-bin kde-baseapps-data kdenetwork-filesharing kdepasswd kdepim-runtime kdepimlibs-kio-plugins kdf kfind knotes konqueror-nsplugins krdc ksaneplugin ksnapshot ksystemlog ktorrent ktorrent-data libakonadi-calendar4 libakonadi-contact4 libakonadi-kabc4 libakonadi-kcal4 libakonadi-kde4 libakonadi-kmime4 libakonadi-xml4 libgpgme++2 libkabc4 libkcal4 libkcalcore4 libkcalutils4 libkcompactdisc4 libkdepim4 libkholidays4 libkimap4 libkldap4 libkleo4 libkmime4 libkonq-common libkonq5-templates libkonq5abi1 libkontactinterface4 libkpimidentities4 libkpimtextedit4 libkpimutils4 libkresources4 libksane-data libksane0 libkxmlrpcclient4 libmailtransport4 libmicroblog4 libnepomukcore4 libqgpgme1 libqmobipocket1 libqtruby4shared2 libqtwebkit4 libsyndication4 nepomuk-core-data nepomuk-core-runtime plasma-scriptengine-superkaramba plasma-widget-folderview ruby-qt4 ruby-qt4-webkit
I'll post back when done.


SolydXK needs you!
Development | Testing | Translations

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

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

Postby Arjen Balfoort » 02 Jul 2014 13:28

All downgraded, rebooted, and all seems to function as expected.


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 02 Jul 2014 13:36

ScottQuier wrote:As for the extension .... just add ".txt" and it should be attachable. Or, you can simple post it between code tags.
Thanks. I realised that later.
I started tweaking the script (always difficult for me not to...) and I'll post it when I'm done.
Schoelje wrote:I'm running "Downgrading packages" in the UM maintenance section to see how that goes:
That list looks a lot like the downgrade list 'un-kdenext' produced of course:

Code: Select all

akonadiconsole=4:4.12.4-1
akregator=4:4.12.4-1
blogilo=4:4.12.4-1
dolphin=4:4.12.4-1
gwenview=4:4.12.3-2
kaddressbook=4:4.12.4-1
kalarm=4:4.12.4-1
kcharselect=4:4.12.2-2
kde-base-artwork=4:4.11.5-1
kde-baseapps-bin=4:4.12.4-1
kde-baseapps-data=4:4.12.4-1
kdenetwork-filesharing=4:4.12.2-2
kdepasswd=4:4.12.4-1
kdepim=4:4.12.4-1
kdepim-kresources=4:4.12.4-1
kdepim-runtime=4:4.12.4-2
kdepimlibs-kio-plugins=4:4.12.4-1
kdf=4:4.12.2-2
kfind=4:4.12.4-1
kjots=4:4.12.4-1
kleopatra=4:4.12.4-1
kmail=4:4.12.4-1
knode=4:4.12.4-1
knotes=4:4.12.4-1
konqueror-nsplugins=4:4.12.4-1
konsolekalendar=4:4.12.4-1
kontact=4:4.12.4-1
korganizer=4:4.12.4-1
krdc=4:4.11.3-1+b1
ksaneplugin=4:4.11.3-2
ksnapshot=4:4.12.2-2
ksystemlog=4:4.12.2-2
ktimetracker=4:4.12.4-1
ktorrent=4.3.1-2
ktorrent-data=4.3.1-2
libakonadi-calendar4=4:4.12.4-1
libakonadi-contact4=4:4.12.4-1
libakonadi-kabc4=4:4.12.4-1
libakonadi-kcal4=4:4.12.4-1
libakonadi-kde4=4:4.12.4-1
libakonadi-kmime4=4:4.12.4-1
libakonadi-xml4=4:4.12.4-1
libgpgme++2=4:4.12.4-1
libkabc4=4:4.12.4-1
libkblog4=4:4.12.4-1
libkcal4=4:4.12.4-1
libkcalcore4=4:4.12.4-1
libkcalutils4=4:4.12.4-1
libkcompactdisc4=4:4.12.3-2
libkdepim4=4:4.12.4-1
libkholidays4=4:4.12.4-1
libkimap4=4:4.12.4-1
libkldap4=4:4.12.4-1
libkleo4=4:4.12.4-1
libkmime4=4:4.12.4-1
libkonq-common=4:4.12.4-1
libkonq5-templates=4:4.12.4-1
libkonq5abi1=4:4.12.4-1
libkontactinterface4=4:4.12.4-1
libkpgp4=4:4.12.4-1
libkpimidentities4=4:4.12.4-1
libkpimtextedit4=4:4.12.4-1
libkpimutils4=4:4.12.4-1
libkresources4=4:4.12.4-1
libksane-data=4:4.12.3-2
libksane0=4:4.12.3-2
libksieve4=4:4.12.4-1
libktnef4=4:4.12.4-1
libkxmlrpcclient4=4:4.12.4-1
libmailtransport4=4:4.12.4-1
libmessagecore4=4:4.12.4-1
libmessagelist4=4:4.12.4-1
libmicroblog4=4:4.12.4-1
libnepomukcore4=4:4.12.4-1+b1
libqgpgme1=4:4.12.4-1
libqmobipocket1=4:4.12.2-2
libqtruby4shared2=4:4.11.3-4
libqtwebkit4=2.2.1-7
libsyndication4=4:4.12.4-1
nepomuk-core-data=4:4.12.4-1
nepomuk-core-runtime=4:4.12.4-1+b1
plasma-scriptengine-superkaramba=4:4.12.2-2
plasma-widget-folderview=4:4.12.4-1
python-kde4=4:4.12.2-3
python3-pykde4=4:4.12.2-3
ruby-qt4=4:4.11.3-4
ruby-qt4-webkit=4:4.11.3-4
This was used in the command 'sudo apt-get install $(cat downgrade)' (downgrade being the list's filename).

libkpgp4 and knode were the packages that had the overwrite issue, by the way. They're not in your list, so I assume they're part of the PIM Suite.
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby Arjen Balfoort » 02 Jul 2014 13:47

So, If I'm not mistaken, there are two things left to do:
  1. Automate the downgrade script
  2. Decide whether to downgrade before, or after the dist-upgrade
I can, of course, fill kdenext in testing with the packages currently in production. Then we'd only need to downgrade python-kde4, and python3-pykde4. Hopefully we'll be then be able to upgrade fully next UP when the current experimental packages hit testing.

What, oh what, should we do? :?


SolydXK needs you!
Development | Testing | Translations

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

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

Postby Arjen Balfoort » 02 Jul 2014 14:09

I even removed deb-multimedia, and cleaned the system with UM maintenance.
Still functional after a reboot.
Now I'm going to create an image of my main system before I upgrade to testing...


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 02 Jul 2014 16:32

Right. Here's the script. If you want to do more than look at it, remove the extension and make sure it's executable.

I thought I could outsmart apt-get/dpkg w.r.t. the overwrite issue, but they bluntly ignored the changes I made, so I removed them again. If the downgrade step fails with an error because a file appears to belong to two different packages, just try the same step again and it should work (because by that time the package that owned the file before should have been downgraded to a state where it doesn't own it anymore).

That said, after working like a charm on three of my VMs, it will probably fail miserably elsewhere because I've overlooked something obvious...
Attachments
un-kdenext.txt
(4.56 KiB) Downloaded 39 times
Frank

SolydX EE 64 - tracking Debian Testing

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

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

Postby Arjen Balfoort » 02 Jul 2014 19:27

You have been busy!
Is there any way this can be safly run on any system (as a post-script)?


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 02 Jul 2014 20:07

The script is written so it can be run in parts/steps. If you run it from a terminal with all the necessary options set (i.e. -dru) it will run through the entire process in one go. Don't use any options and it will just create the lists, use only -d and it will create the lists and carry out the downgrade, etc.

It's really for someone who likes to run things in the terminal, knows what to look out for and doesn't mind running the downgrade step twice if it fails the first time round. Unfortunately, problems like the knode/libkpgp4 overwrite issue, which may or may not show up, depending on what people have installed, make it less suitable for a process that expects to run without human intervention.
Unless someone finds a reliable way to handle possible overwrite problems...

Edit: come to think of it, I remember seeing a solution for overwrite problems once, somehow passing the --force-overwrite switch to dpkg. However, I'm not sure how this would work out in this particular case. If my understanding of how --force-overwrite works is correct, it doesn't permanently change the 'ownership' of the file involved (if it does, that would be workable, so please correct me if I'm wrong...). This could mean that after using that switch the file would be overwritten, only to be removed later when the original owner was downgraded. That would bork things, I would think...
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 05:22

solydxk-meta-office dependencie issue solved.
Tested. Looks fine here. :)

I am unable to resolve the weird context menu problem in Firefox. I removed all Mate packages and the problem persists. I tried a new profile. I can only conclude a problem introduced through the testing repo. I will try to find time to start from scratch, install the latest SolydX ISO, and methodically test from there.

After removing the Mate packages I no longer experience an erratic mouse pointer. So that problem seems to be a conflict between Mate and Xfce.

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

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

Postby Arjen Balfoort » 03 Jul 2014 05:28

I also found a difference between downgrading, and upgrading KDE: in both cases the applications function as expected (as far as I could see), but it is impossible to shut down the system with the downgraded system. It does not even show the "Turn off computer" dialog, and simply hangs. A hard shut down is the only thing I can do.

Before I forget to mention it: both use systemd. So, it's out-of-scope for this UP.


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 » 03 Jul 2014 10:41

woodsman wrote:I am unable to resolve the weird context menu problem in Firefox
what's the output of

Code: Select all

dpkg -l | grep firefox
bliss of ignorance

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

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

Postby Arjen Balfoort » 03 Jul 2014 10:47

I changed the pre-script to use Grizzler's un-kdenext script.
This is why I had to make a minor change to the UM (version 2.3.0).

Now, before you upgrade your system, kdenext is going to get downgraded.
I've tested this several times, and it worked like a charm! 8-)
Of course, we need more testing, but it looks really promising. Thanks Grizzler, for that really nice script!

If I have some time, I'm going to test it on metal: a system that's been in use for a year now, had all the UPs, and really is a mess :D

The info page has been updated.
Check it out in the UM, or in the OP of this topic.


SolydXK needs you!
Development | Testing | Translations

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

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

Postby grizzler » 03 Jul 2014 11:20

Schoelje wrote:Of course, we need more testing, but it looks really promising. Thanks Grizzler, for that really nice script!
You're welcome. Just be aware of the overwrite issue I mentioned. 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'm currently trying to find a definitive answer to my --force-overwrite confusion, getting more confused in the process. There are indications it actually can be used here, even that dist-upgrade has it set by default. If that's true, running the downgrading apt-get install with -o Dpkg::Options::="--force-overwrite" should be enough to avoid any overwrite errors. Lots of contradicting views however, so I'm not sure yet.

I'll have another go at a downgrade with --force-overwrite set and see what that does to the conflicting file. Nothing like empirical evidence to prove something will work once and fail after that...
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/07/2014 [TESTING]

Postby zerozero » 03 Jul 2014 11:24

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
bliss of ignorance


Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 1 guest