[opensuse-factory] Who is right, who is wrong?
Last night I downlaoded Factory Snapshot 201406626, burnt it to a DVD and a short time ago tried to follow, word for word, what is stated in- http://en.opensuse.org/openSUSE:Factory_installation Specifically this bit quote: Then add the new repos zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug Oh, yea, pigs will fly, senor! :-( No such repos were added - but invoking each of the above commands produced the "help" screen for zypper. Then I decided to use YaST to install the above repos - and guess what? The piggies did not even begin to show signs of growing wings! :-( The YaST repository screen was empty and remained empty. So, is the blurb in http://en.opensuse.org/openSUSE:Factory_installation rubbish or is there something missing in the Factory Snapshot I downloaded last night? Does anyone have an answer re this, please? BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2014-07-01 at 20:06 +1000, Basil Chupin wrote:
Last night I downlaoded Factory Snapshot 201406626, burnt it to a DVD and a short time ago tried to follow, word for word, what is stated in-
You downloaded a factory snapshot..therefore the only part of that URL you need to follow is the 'Front Scratch' section..it's one line quote: "Download an image, burn it on a DVD or write it to a USB stick and launch the installation from there after a reboot." All the other stuff you followed, is in the 'UPGRADE' section of the wiki page, as you can see by the fact it's under the Upgrade sub header.. So, it looks to me that you installed Factory, and then tried to upgrade Factory to Factory Which is so wrong, I'm not sure if the misbehaviour you report with "zypper ar .." is actually a legitimate problem with zypper in Factory, or just a result of totally unexpected side effects of attempting to upgrade something to itself ;-) Maybe you can just reinstall from the media?
Specifically this bit
quote:
Then add the new repos
zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug
Oh, yea, pigs will fly, senor! :-(
No such repos were added - but invoking each of the above commands produced the "help" screen for zypper.
Then I decided to use YaST to install the above repos - and guess what? The piggies did not even begin to show signs of growing wings! :-( The YaST repository screen was empty and remained empty.
So, is the blurb in http://en.opensuse.org/openSUSE:Factory_installation rubbish or is there something missing in the Factory Snapshot I downloaded last night?
Does anyone have an answer re this, please?
BC
-- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/07/14 20:39, Richard Brown wrote:
On Tue, 2014-07-01 at 20:06 +1000, Basil Chupin wrote:
Last night I downlaoded Factory Snapshot 201406626, burnt it to a DVD and a short time ago tried to follow, word for word, what is stated in-
http://en.opensuse.org/openSUSE:Factory_installation You downloaded a factory snapshot..therefore the only part of that URL you need to follow is the 'Front Scratch' section..it's one line
quote: "Download an image, burn it on a DVD or write it to a USB stick and launch the installation from there after a reboot."
All the other stuff you followed, is in the 'UPGRADE' section of the wiki page, as you can see by the fact it's under the Upgrade sub header..
So, it looks to me that you installed Factory, and then tried to upgrade Factory to Factory
Which is so wrong, I'm not sure if the misbehaviour you report with "zypper ar .." is actually a legitimate problem with zypper in Factory, or just a result of totally unexpected side effects of attempting to upgrade something to itself ;-)
Maybe you can just reinstall from the media?
Thank you for you reply. As I stated, I followed the blurb word for word, namely: quote Introduction Just like other distributions openSUSE Factory can be installed either by downloading and launching an installation image to start from scratch or by upgrading from a stable release. From Scratch Download an image, burn it on a DVD or write it to a USB stick and launch the installation from there after a reboot. Upgrade There are two tasks needed in order to upgrade from any release to factory: Changing repositories to point to Factory Running zypper dup to upgrade all packages Repositories Start by removing the existing repos: mkdir /etc/zypp/repos.d/old mv /etc/zypp/repos.d/*.repo /etc/zypp/repos.d/old Then add the new repos zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug unquote Where in my OP did I say I tried to upgrade factory to factory? How could I possibly do such an upgrade if the bloody repos have not been created?! - as I stated, the list of repos is a BLANK, no, zilch, zero, nil repos shown. And now that I think about it after having tried to start YaST from the Desktop Settings in "Gecko", YaST goes "poof" when one left-clicks on it to start it. BC Specifically this bit quote: Then add the new repos zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug Oh, yea, pigs will fly, senor! :-( No such repos were added - but invoking each of the above commands produced the "help" screen for zypper. Then I decided to use YaST to install the above repos - and guess what? The piggies did not even begin to show signs of growing wings! :-( The YaST repository screen was empty and remained empty. So, is the blurb in http://en.opensuse.org/openSUSE:Factory_installation rubbish or is there something missing in the Factory Snapshot I downloaded last night? Does anyone have an answer re this, please? BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU
-- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 1 July 2014 13:46, Basil Chupin
Thank you for you reply.
As I stated, I followed the blurb word for word, namely:
You followed to many words, as I'll explain in line below
quote
Introduction
Just like other distributions openSUSE Factory can be installed either by downloading and launching an installation image to start from scratch or by upgrading from a stable release. From Scratch
Download an image, burn it on a DVD or write it to a USB stick and launch the installation from there after a reboot.
*STOP HERE* You're done, you just installed Factory, congratulations
Upgrade
Are you upgrading from an openSUSE Release (eg. 13.1) to Factory? No? Then *Stop Reading*
There are two tasks needed in order to upgrade from any release to factory:
If you're still reading this, you really should know these instructions are only if you're upgrading from an openSUSE release (eg. 13.1) to Factory
Changing repositories to point to Factory Running zypper dup to upgrade all packages
Repositories
Start by removing the existing repos:
mkdir /etc/zypp/repos.d/old mv /etc/zypp/repos.d/*.repo /etc/zypp/repos.d/old
I have no clue what would happen if you do this on Factory, but it doesn't matter, because you shouldn't be doing this on factory, you should only be doing it if you're doing an upgrade, if you're installing Factory, you were done ages ago... etc.. etc do you get my point now?
SNIP<
Where in my OP did I say I tried to upgrade factory to factory? How could I possibly do such an upgrade if the bloody repos have not been created?! - as I stated, the list of repos is a BLANK, no, zilch, zero, nil repos shown.
What does "zypper lr -u" show? but seriously, you really really shouldn't have followed the *UPGRADE* Instructions when you started out this topic by saying you were *INSTALLING* a Factory snapshot! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/07/14 21:52, Richard Brown wrote:
On 1 July 2014 13:46, Basil Chupin
wrote: Thank you for you reply.
As I stated, I followed the blurb word for word, namely: You followed to many words, as I'll explain in line below
Yep, sure did :-) . I re-installed earlier today and without any problems. But tell me: on booting the screen shows "openSUSE 12.3" and the login menu is from oS 12.3. Is this correct or something which I didn't do? [pruned] BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-07-02 08:38, Basil Chupin wrote:
On 01/07/14 21:52, Richard Brown wrote:
I re-installed earlier today and without any problems.
Good. :-)
But tell me: on booting the screen shows "openSUSE 12.3" and the login menu is from oS 12.3. Is this correct or something which I didn't do?
No, not correct. You should be getting 13.2, or 13.1 if they didn't change it. You are probably reusing some older grub setup. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 02/07/14 18:57, Carlos E. R. wrote:
On 2014-07-02 08:38, Basil Chupin wrote:
On 01/07/14 21:52, Richard Brown wrote: I re-installed earlier today and without any problems. Good. :-)
But tell me: on booting the screen shows "openSUSE 12.3" and the login menu is from oS 12.3. Is this correct or something which I didn't do? No, not correct. You should be getting 13.2, or 13.1 if they didn't change it. You are probably reusing some older grub setup.
This is a clean install on a laptop which has nothing else on it. And it has never had 12.3 installed on it because it came with Windows 8 pre-installed (which I removed) and installed 13.1 on it (which now has been 'zapped' and replaced by aforementioned Factory Snapshot). BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-07-02 11:19, Basil Chupin wrote:
On 02/07/14 18:57, Carlos E. R. wrote:
You are probably reusing some older grub setup.
This is a clean install on a laptop which has nothing else on it.
And it has never had 12.3 installed on it because it came with Windows 8 pre-installed (which I removed) and installed 13.1 on it (which now has been 'zapped' and replaced by aforementioned Factory Snapshot).
Then, you investigate and find out why, and report :-) Remember, this is factory! Welcome to the fun. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOz3lgACgkQtTMYHG2NR9VnjQCfZIjyibJiTQK4NHvr97B+A7qF mPIAnRrrmW3joGuiHCWKp1ZrCC5XMP+x =Ajh7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-07-01 13:46, Basil Chupin wrote:
On 01/07/14 20:39, Richard Brown wrote:
Thank you for you reply.
As I stated, I followed the blurb word for word, namely:
quote
Introduction
Just like other distributions openSUSE Factory can be installed either by downloading and launching an installation image to start from scratch or by upgrading from a stable release. From Scratch
Download an image, burn it on a DVD or write it to a USB stick and launch the installation from there after a reboot.
Upgrade
There are two tasks needed in order to upgrade from any release to factory:
But you are NOT upgrading. You are *installing*. You are installing "from scratch". From that word "Upgrade" onwards, stop reading, till the next paragraph with the same font face as "Upgrade", which is "Boring?". :-)
Where in my OP did I say I tried to upgrade factory to factory?
Because you are trying to follow the instructions from the "upgrade" paragraph, which does not apply to you. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-07-01 12:39, Richard Brown wrote:
On Tue, 2014-07-01 at 20:06 +1000, Basil Chupin wrote:
So, it looks to me that you installed Factory, and then tried to upgrade Factory to Factory
Which is so wrong, I'm not sure if the misbehaviour you report with "zypper ar .." is actually a legitimate problem with zypper in Factory, or just a result of totally unexpected side effects of attempting to upgrade something to itself ;-)
Even so, doing: zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss would simply try to add a repository that should already be listed, and zypper should say that, that the repo was already added. If the command generates the zypper help page, it means that zypper says the entered syntax is wrong. In 13.1, this is what happens: Telcontar:~ # zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-ossf Adding repository 'repo-ossf' ........................................................................................................................................................................................................................[done] Repository 'repo-ossf' successfully added Enabled: Yes Autorefresh: Yes GPG check: Yes URI: http://download.opensuse.org/factory/repo/oss Telcontar:~ # zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-ossf Adding repository 'repo-ossf' ........................................................................................................................................................................................................................[done] Repository named 'repo-ossf' already exists. Please use another alias. Telcontar:~ # and that is the correct result. Of course, following that procedure on a freshly installed snapshot makes no sense. It should not produce an error, but it makes no sense. ;-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOyoDgACgkQtTMYHG2NR9Xl3wCaAxUYcgfQRd0THs2auNM9pNfi hQgAn2NrGsd8b1NQ11shNjOeIVMONE3m =uM87 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/07/14 21:49, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-07-01 12:39, Richard Brown wrote:
On Tue, 2014-07-01 at 20:06 +1000, Basil Chupin wrote:
So, it looks to me that you installed Factory, and then tried to upgrade Factory to Factory
Which is so wrong, I'm not sure if the misbehaviour you report with "zypper ar .." is actually a legitimate problem with zypper in Factory, or just a result of totally unexpected side effects of attempting to upgrade something to itself ;-) Even so, doing:
zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss
would simply try to add a repository that should already be listed, and zypper should say that, that the repo was already added. If the command generates the zypper help page, it means that zypper says the entered syntax is wrong.
Then what is on that (?)wiki page is wrong because I followed what's there character for character :-) . [pruned] BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01.07.2014 12:06, Basil Chupin wrote:
Last night I downlaoded Factory Snapshot 201406626, burnt it to a DVD and a short time ago tried to follow, word for word, what is stated in-
http://en.opensuse.org/openSUSE:Factory_installation
Specifically this bit
quote:
Then add the new repos
zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug
Oh, yea, pigs will fly, senor! :-(
No such repos were added - but invoking each of the above commands produced the "help" screen for zypper.
Then I decided to use YaST to install the above repos - and guess what? The piggies did not even begin to show signs of growing wings! :-( The YaST repository screen was empty and remained empty.
The repository screen is using a XML list that does not yet exist for Factory, but only for 13.1 - we will need to fix this. Please file a bug. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/07/14 21:52, Stephan Kulow wrote:
On 01.07.2014 12:06, Basil Chupin wrote:
Last night I downlaoded Factory Snapshot 201406626, burnt it to a DVD and a short time ago tried to follow, word for word, what is stated in-
http://en.opensuse.org/openSUSE:Factory_installation
Specifically this bit
quote:
Then add the new repos
zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug
Oh, yea, pigs will fly, senor! :-(
No such repos were added - but invoking each of the above commands produced the "help" screen for zypper.
Then I decided to use YaST to install the above repos - and guess what? The piggies did not even begin to show signs of growing wings! :-( The YaST repository screen was empty and remained empty.
The repository screen is using a XML list that does not yet exist for Factory, but only for 13.1 - we will need to fix this. Please file a bug.
Surely I am not the only bunny who has taken his life into his own hands and installed a Factory Snapshot? :-) I simply cannot claim to be the first one to shout, "EUREKA! I found this bug in Factory Snapshot!"? :-) In any case, from what you wrote above you already know about this so I guess that there is already a bug report about it in the works? BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-07-02 09:40, Basil Chupin wrote:
In any case, from what you wrote above you already know about this so I guess that there is already a bug report about it in the works?
Typically, no. The solution will probably done at some time, sooner or later, but unless they get a written report that justifies working on it, it will be later. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOzyWsACgkQtTMYHG2NR9WzOQCeOJdGkkm4B0PjMWWsFskwKiCx vdAAoIhNcdGRTCSAzQDfvVGe9VyJLevt =Uiwa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/07/14 18:57, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-07-02 09:40, Basil Chupin wrote:
In any case, from what you wrote above you already know about this so I guess that there is already a bug report about it in the works? Typically, no.
The solution will probably done at some time, sooner or later, but unless they get a written report that justifies working on it, it will be later.
Ah, I didn't know that Stephan was exempt from making bug reports. Mea culpa. I now know better. BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-07-02 11:04, Basil Chupin wrote:
On 02/07/14 18:57, Carlos E. R. wrote:
The solution will probably done at some time, sooner or later, but unless they get a written report that justifies working on it, it will be later.
Ah, I didn't know that Stephan was exempt from making bug reports.
What do you prefer, that he spends time writing a report, or that YOU write it, so that he can concentrate on his job, which you (nor me, nor many people) can not do? :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOz3x0ACgkQtTMYHG2NR9VrdACfaV2OQtiwvd9UMBz+biHCkbVP k3YAnAx9j+TuRaCPT1rTvoxXM6GNqMaL =JRt/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/07/14 20:29, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-07-02 11:04, Basil Chupin wrote:
On 02/07/14 18:57, Carlos E. R. wrote:
The solution will probably done at some time, sooner or later, but unless they get a written report that justifies working on it, it will be later. Ah, I didn't know that Stephan was exempt from making bug reports. What do you prefer, that he spends time writing a report, or that YOU write it, so that he can concentrate on his job, which you (nor me, nor many people) can not do? :-)
Well, when I was in the "business", I would pick up the telephone sitting on my desk, press 4 keys to call up the chief programmer and tell him in a sentence of the problem. Problem reported - and fixed. BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-07-01 20:06 (GMT+1000) Basil Chupin composed:
Last night I downlaoded Factory Snapshot 201406626, burnt it to a DVD and a short time ago tried to follow, word for word, what is stated in-
Specifically this bit
quote:
Then add the new repos
zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug
Oh, yea, pigs will fly, senor! :-(
Notwithstanding the difficulty of following a very simple web page instruction, and the explanations from others that followed, there is an alternative approach one can take to repository management. IOW, the ar and rr commands are zypper commands I find no use for. Instead, I use a file manager that works whether I have X running or not, one with built-in FTP, so that I can fetch directly from a mirror whenever I need one the LAN server doesn't already have; one with a built-in editor, so that I can use an old file as a template for editing. The mirrors have definitions for all the optional repos they contain in the form of .repo files in a form usable by YaST and Zypper simply by their presence in /etc/zypp/repos.d/. The non-optional repos, oss & non-oss & debug have the same names as always, just with minor internal differences on account of the differences in release names. So, rather than take a chance on typing errors, I use those files taken directly from the mirrors, or from any previously installed release, sort of. What I do is grab those optionals I ever use from the mirrors and put them on my LAN server, along with the basics debug, source, oss & non-oss, in subdirectories of a Suse directory with such unclever names as 123, 131 and Factory. In the process of putting them on the LAN server, I tailor their names to the way I think, which is to say I strip their names of whitespace, punctuation, redundance and superfluocity - their descriptions, the aliases, and their filenames save for the extension, are all one and the same string for each. Then I give them a distro release timestamp as a safety check. These are then available on the LAN for placement wherever they are wanted. e.g.: Suse: ... drwxrwxrwx 4 9216 Jun 27 15:21 114 drwxrwxrwx 2 3072 Feb 26 13:55 121 drwxrwxrwx 2 8192 Mar 4 17:21 122 drwxrwxrwx 2 6144 Jun 9 00:20 123 drwxrwxrwx 2 8192 Jun 28 22:31 131 drwxrwxrwx 2 1024 Aug 6 2013 Evergreen drwxrwxrwx 3 9216 Jun 28 19:53 Factory drwxrwxrwx 2 1024 Oct 12 2012 Kernel drwxrwxrwx 2 1024 Aug 6 2013 Tumbleweed ... 131: ... -rw-r--r-- 1 240 Nov 19 2013 131/BaseSystem.repoD -rw-r--r-- 1 302 Nov 19 2013 131/homeJiriSlaby131Kernel.repoD -rw-r--r-- 1 266 Nov 19 2013 131/homeJiriSlaby.repoD -rw-r--r-- 1 348 Nov 19 2013 131/homeSumskiBranchesOpenSUSE131Update.repoD -rw-r--r-- 1 260 Nov 19 2013 131/homeSumskiTest.repoD -rw-r--r-- 1 278 Nov 19 2013 131/homeTobijk-X11XOrg.repoD -rw-r--r-- 1 268 Nov 19 2013 131/KDE3NonFree.repoD -rw-r--r-- 1 236 Nov 19 2013 131/KDE3.repoD -rw-r--r-- 1 244 Nov 19 2013 131/KernelStableStd.repoD -rw-r--r-- 1 244 Nov 19 2013 131/MozillaBeta.repoD -rw-r--r-- 1 264 Nov 19 2013 131/MozillaExp.repoD -rw-r--r-- 1 293 Nov 19 2013 131/MozillaLegacy.repoD -rw-r--r-- 1 265 Nov 19 2013 131/Mozilla.repoD -rw-r--r-- 1 148 Nov 19 2013 131/Non-OSS.repoD -rw-r--r-- 1 152 Nov 19 2013 131/Non-OSS.repo-gwdg -rw-r--r-- 1 136 Nov 19 2013 131/OSS.repoD -rw-r--r-- 1 140 Nov 19 2013 131/OSS.repo-gwdg -rw-r--r-- 1 210 Nov 19 2013 131/Packman.repo-inodeat -rw-r--r-- 1 170 Nov 19 2013 131/Tools.repoD -rw-r--r-- 1 149 Nov 19 2013 131/UpdateNonOSS.repoD -rw-r--r-- 1 129 Nov 19 2013 131/Update.repoD -rw-r--r-- 1 133 Nov 19 2013 131/Update.repo-gwdg -rw-r--r-- 1 114 Nov 19 2013 131/VideoLAN.repoD -rw-r--r-- 1 242 Nov 19 2013 131/X11XOrg.repoD ... To make use of any I desire, I copy with a file manager from the LAN server into /etc/zypp/repos.d/ of the system needing them, then recopy whichever I actually want used, without the ID suffix, D meaning default (or d.o.o), others indicating the mirror name. Once I have them on the target the way I want them available, I do a zypper clean; zypper ref, and they are ready to use, with all possible typing, and hopefully all possible logic, mistakes filtered away in advance. Any time I wish a different mirror used for any particular repo, I do a Shift-F3 recopy of the alternate over the existing: e.g. Update.repo-gwdg -> Update.repo. To disable a repo, I delete its .repo file, leaving the template(s) in place ready for a Shift-F3 to conveniently reenable at any time. The templates ever only get rewritten/edited on the LAN server, and their timestamps restored to the release date, except for Factory files, in order to maintain the safety check that is seeing all with same date in the directory list the file manager shows me. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 01 Jul 2014 20:06:41 +1000
Basil Chupin
Then add the new repos
zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug
There seems to be a lot of misinformation in this discussion. Basil is basically correct. You do need to add those repos and delete the old ones. I installed that snapshot yesterday. As installed, the configured repos are those of 13.2M0, which are out-of-date by now. So you need to switch them to the factory repos. I uses Yast Software Repositories to do that. It's a bit slower than with the zypper command line. But I did not run into any problems doing it that way. I didn't delete the old ones, I just disabled them. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/07/14 12:43, Neil Rickert wrote:
On Tue, 01 Jul 2014 20:06:41 +1000 Basil Chupin
wrote: Then add the new repos
zypper ar -f -c http://download.opensuse.org/factory/repo/oss repo-oss zypper ar -f -c http://download.opensuse.org/factory/repo/non-oss repo-non-oss zypper ar -f -c http://download.opensuse.org/factory/repo/debug repo-debug There seems to be a lot of misinformation in this discussion.
Basil is basically correct. You do need to add those repos and delete the old ones.
I installed that snapshot yesterday. As installed, the configured repos are those of 13.2M0, which are out-of-date by now. So you need to switch them to the factory repos.
I uses Yast Software Repositories to do that.
Hold on..... you did say that you used YaST to do this? I tried to install the packman and the libdvdcss repos using YaST and nothing happened - YaST just blinked and showed me the 2-fingered salute :-) .
It's a bit slower than with the zypper command line. But I did not run into any problems doing it that way. I didn't delete the old ones, I just disabled them.
BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 02 Jul 2014 16:41:35 +1000
Basil Chupin
Hold on..... you did say that you used YaST to do this?
I tried to install the packman and the libdvdcss repos using YaST and nothing happened - YaST just blinked and showed me the 2-fingered salute :-) .
Yast works fine for this. But here's the guide: Step 1: yast --ncurses and remove the package "libproxy1-config-kde4" Thereafter, the GUI version should work. Step2: Yast --> Software Management Search for "libproxy1-config-kde4", and blacklist it. Otherwise it will be reinstalled. Once those steps are done, you should be able to use Yast normally. If you have Gnome installed, then "yast2 --gtk" should also work normally. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/07/14 23:52, Neil Rickert wrote:
On Wed, 02 Jul 2014 16:41:35 +1000 Basil Chupin
wrote: Hold on..... you did say that you used YaST to do this?
I tried to install the packman and the libdvdcss repos using YaST and nothing happened - YaST just blinked and showed me the 2-fingered salute :-) .
Yast works fine for this.
But here's the guide:
AH! I just KNEW that there was a "BUT" in there somewhere (always is)! :-D
Step 1: yast --ncurses and remove the package "libproxy1-config-kde4"
Thereafter, the GUI version should work.
Step2: Yast --> Software Management Search for "libproxy1-config-kde4", and blacklist it. Otherwise it will be reinstalled.
Once those steps are done, you should be able to use Yast normally.
If you have Gnome installed, then "yast2 --gtk" should also work normally.
Thank you Neil! I haven't tried the above yet but will do so after I have had my dinner. BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-07-02 04:43, Neil Rickert wrote:
On Tue, 01 Jul 2014 20:06:41 +1000 Basil Chupin <> wrote:
There seems to be a lot of misinformation in this discussion.
Basil is basically correct. You do need to add those repos and delete the old ones.
I installed that snapshot yesterday. As installed, the configured repos are those of 13.2M0, which are out-of-date by now. So you need to switch them to the factory repos.
Ah, but then it is because this particular snapshot has the wrong repos pre-configured. It is not the generic installation procedure. :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 02/07/14 19:00, Carlos E. R. wrote:
On 2014-07-02 04:43, Neil Rickert wrote:
On Tue, 01 Jul 2014 20:06:41 +1000 Basil Chupin <> wrote:
There seems to be a lot of misinformation in this discussion.
Basil is basically correct. You do need to add those repos and delete the old ones.
I installed that snapshot yesterday. As installed, the configured repos are those of 13.2M0, which are out-of-date by now. So you need to switch them to the factory repos. Ah, but then it is because this particular snapshot has the wrong repos pre-configured. It is not the generic installation procedure. :-)
Aaaw, come on Carlos :-( . People have been encouraged to switch to Factory. One goes to the wiki page I already mentioned and there is the URL which takes you to the directory which gives you the Snapshot to download - which is what I did. And you now come out with "this particular snapshot has the wrong repos pre-configured." and then "It is not the generic installation procedure." A lot of goobly-dook. What the heck is "the generic installation procedure"? And, who is responsible for writing the wiki page which gives you the wrong Snapshot-with-the-wrong-repos to download? BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-07-02 11:13, Basil Chupin wrote:
On 02/07/14 19:00, Carlos E. R. wrote:
Aaaw, come on Carlos :-( .
People have been encouraged to switch to Factory. One goes to the wiki page I already mentioned and there is the URL which takes you to the directory which gives you the Snapshot to download - which is what I did.
And you now come out with "this particular snapshot has the wrong repos pre-configured." and then "It is not the generic installation procedure."
A lot of goobly-dook.
What the heck is "the generic installation procedure"?
Put DVD on drive, boot, follow your nose. Literally :-)
And, who is responsible for writing the wiki page which gives you the wrong Snapshot-with-the-wrong-repos to download?
The page is absolutely correct. It told you to just download and boot the dvd, nothing more. The rest of the instructions are for upgrade, not install. It just happens that the procedure to correct the wrong repo entries are similar. And please remember: IT IS FACTORY. Meaning, that things are expected to break, you are expected to solve the issues that you find, yourself, on your own, and when stuck, ask here, in case somebody else has found the solution before than you, or knows that it is a bug, or something. And you are expected to contribute and report bugs in Bugzilla, and follow up on them. It is also expected to have new features and behaviours, which will surprise people, which will some times not know what to do. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOz3e4ACgkQtTMYHG2NR9V4OQCfRFAgl89ySj1BnQUuRFKfqQQo nj8An26nUn8Emvr0Tcilv/wPApspP8bC =dfpc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/07/14 20:24, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-07-02 11:13, Basil Chupin wrote:
On 02/07/14 19:00, Carlos E. R. wrote:
Aaaw, come on Carlos :-( .
People have been encouraged to switch to Factory. One goes to the wiki page I already mentioned and there is the URL which takes you to the directory which gives you the Snapshot to download - which is what I did.
And you now come out with "this particular snapshot has the wrong repos pre-configured." and then "It is not the generic installation procedure."
A lot of goobly-dook.
What the heck is "the generic installation procedure"? Put DVD on drive, boot, follow your nose. Literally :-)
And, who is responsible for writing the wiki page which gives you the wrong Snapshot-with-the-wrong-repos to download? The page is absolutely correct. It told you to just download and boot the dvd, nothing more.
The rest of the instructions are for upgrade, not install. It just happens that the procedure to correct the wrong repo entries are similar.
What is this, "It just happens that the procedure to correct the wrong repo entries are similar."? I install as per the instructions (as I did during the re-install) and see that the repos are for 13.1 - with no "factory" name in sight! :-) So I try to YaST to amend the repos and all I get is the "bird" from YaST.
And please remember: IT IS FACTORY.
Yes I KNOW that it is FACTORY. But we are assured that FACTORY now contains almost perfect files which have been tested before being placed into FACTORY - and all this is with the intention of providing a "rolling" version of openSUSE. Now come on :-) . Who is misunderstanding things? (Naturally moi, of course :-( .)
Meaning, that things are expected to break, you are expected to solve the issues that you find, yourself, on your own, and when stuck, ask here, in case somebody else has found the solution before than you, or knows that it is a bug, or something. And you are expected to contribute and report bugs in Bugzilla, and follow up on them.
I understand all of that. But how can one test anything and report on anything when the bloody thing does not work as expected to begin with?! The boot menu shows openSUSE 12.3. The repos shown in YaST are for 13.1 and not for "factory". If one wants to change the repos - according to what the wiki page states or as Neil tried - neither zypper nor YaST will let you. And I am asked to write a bug report..... based on WHAT? There is no "level playing field" here to even consider thinking about a bug report.
It is also expected to have new features and behaviours, which will surprise people,
Oooow, I like surprises - as long as they frighten the crap out of me and make me soil my panties :-) .
which will some times not know what to do.
Oh, I know what to do when I am 'surprised' :-) BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.2-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Basil Chupin
-
Carlos E. R.
-
Carlos E. R.
-
Felix Miata
-
Neil Rickert
-
Richard Brown
-
Stephan Kulow