[opensuse-factory] 42.1 Beta: Trying to understand difference of dup between USB and online repos
I just downloaded 42.1 Beta1 earlier today and put it on Lexar USB The I ran zypper up on a 42.1 M2 system. Then I was thinking "let's test zypper dup". In preparation, I made the USB the only enabled repository. I get basically "all is up to date" Then I also enable the 42.1 Beta online repos. Then, zypper dup tries to do something completely different, most important, zypper dup is now trying to change vendor. Why is that? For example: change vendor: ConsoleKit obs://build.opensuse.org/openSUSE:42 -> openSUSE What is different about the online repos vs the repo on USB? Thanks, Milan ---------------------------------------------------------------- *partial* log with ** highlights below: home-server:~ # zypper lr # | Alias | Name | Enabled | GPG Check | Refresh --+--------------+-----------------------+---------+-----------+-------- 1 | lexar | lexar-Leap-42.1-beta | Yes | ( p) Yes | Yes 2 | repo-debug | openSUSE-Leap-Debug | No | ---- | No 3 | repo-non-oss | openSUSE-Leap-Non-Oss | No | ---- | No 4 | repo-oss | openSUSE-Leap-Oss | No | ---- | No 5 | repo-source | openSUSE-Leap-Source | No | ---- | No 6 | repo-update | openSUSE-Leap-Update | No | ---- | No home-server:~ # zypper dist-upgrade --dry-run --no-recommends Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Retrieving repository 'lexar-Leap-42.1-beta' metadata ........................................................[done] Building repository 'lexar-Leap-42.1-beta' cache .............................................................[done] Loading repository data... Reading installed packages... Computing distribution upgrade... **Nothing to do.** **Let us enable online repos ** home-server:~ # zypper modifyrepo -e -r repo-oss Repository 'repo-oss' has been successfully enabled. Autorefresh has been enabled for repository 'repo-oss'. home-server:~ # zypper modifyrepo -e -r repo-non-oss Repository 'repo-non-oss' has been successfully enabled. Autorefresh has been enabled for repository 'repo-non-oss'. home-server:~ # zypper modifyrepo -e -r repo-source Repository 'repo-source' has been successfully enabled. Autorefresh has been enabled for repository 'repo-source'. home-server:~ # zypper modifyrepo -e -r repo-debug Repository 'repo-debug' has been successfully enabled. Autorefresh has been enabled for repository 'repo-debug'. **These are the URLs *** home-server:~ # zypper ls -u # | Alias | Name | Enabled | GPG Check | Refresh | Type | URI --+--------------+-----------------------+---------+-----------+---------+----------+---------------------------------------------------------------------------------------------- 1 | lexar | lexar-Leap-42.1-beta | Yes | ( p) Yes | Yes | plaindir | hd:///?device=/dev/disk/by-id/scsi-SATA_Samsung_SSD_840_S1DHNSAFB69955B-part1&filesystem=auto 2 | repo-debug | openSUSE-Leap-Debug | Yes | (r ) Yes | Yes | yast2 | http://download.opensuse.org/debug/distribution/leap/42.1/repo/oss/ 3 | repo-non-oss | openSUSE-Leap-Non-Oss | Yes | (r ) Yes | Yes | yast2 | http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/ 4 | repo-oss | openSUSE-Leap-Oss | Yes | (r ) Yes | Yes | yast2 | http://download.opensuse.org/distribution/leap/42.1/repo/oss/ 5 | repo-source | openSUSE-Leap-Source | Yes | (r ) Yes | Yes | yast2 | http://download.opensuse.org/source/distribution/leap/42.1/repo/oss/ 6 | repo-update | openSUSE-Leap-Update | No | ---- | No | NONE | http://download.opensuse.org/update/42.1/ **Why is the dup so much different now? parial log only ** home-server:~ # zypper dist-upgrade --dry-run --no-recommends Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Retrieving repository 'lexar-Leap-42.1-beta' metadata ........................................................[done] Building repository 'lexar-Leap-42.1-beta' cache .............................................................[done] Loading repository data... Reading installed packages... Computing distribution upgrade... Problem: kdebase4-openSUSE-lang-13.2-9.11.noarch requires kdebase4-openSUSE = 13.2, but this requirement cannot be provided deleted providers: plasma5-workspace-branding-openSUSE-13.2-16.1.x86_64 uninstallable providers: kdebase4-openSUSE-13.2-9.11.x86_64[repo-oss] Solution 1: Following actions will be done: keep obsolete plasma5-workspace-branding-openSUSE-13.2-16.1.x86_64 keep obsolete plasma5-desktop-branding-openSUSE-13.2-16.1.x86_64 keep obsolete susegreeter-branding-openSUSE-13.2-1.4.noarch keep obsolete wallpaper-branding-openSUSE-13.2-1.11.noarch keep obsolete desktop-data-openSUSE-13.2-1.2.noarch keep obsolete plasma5-workspace-5.3.2-4.1.x86_64 keep obsolete plasma5-desktop-5.3.2-6.1.x86_64 keep obsolete plasma5-session-5.3.2-5.1.noarch keep obsolete plasma5-workspace-lang-5.3.2-4.1.noarch keep obsolete plasma5-desktop-lang-5.3.2-6.1.noarch keep obsolete plasma5-workspace-libs-5.3.2-4.1.x86_64 keep obsolete powerdevil5-5.3.2-4.1.x86_64 keep obsolete powerdevil5-lang-5.3.2-4.1.noarch Solution 2: deinstallation of kdebase4-openSUSE-lang-13.2-8.4.noarch Solution 3: break kdebase4-openSUSE-lang-13.2-9.11.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): 2 Resolving dependencies... Computing distribution upgrade... The following 35 NEW packages are going to be installed: accountsservice baloo5-tools graphite2-devel kaccounts-integration kde-user-manager kernel-pv-devel-4.1.6-10.5 kernel-source-4.1.6-10.2 kernel-syms-4.1.6-10.2 kwayland libGLEW1_13 libKF5Baloo5 libKF5BalooEngine5 libaccounts-glib0 libaccounts-qt5-1 libaudiofile1-32bit libebml4 libesd0-32bit liblmdb-0_9_14 libmatroska6 libpng15-15 libsignon-qt5-1 libwx_gtk2u_qa-2_8-0-stl libyui-ncurses-pkg7 libyui-ncurses7 libyui-qt-pkg7 libyui-qt7 libyui7 lsb5 lsb5-core lsb5-desktop lsb5-imaging lsb5-languages purpose python3-apparmor vlc-noX The following 7 applications are going to be REMOVED: Choqok "Déjà Dup Backup Tool" GIMP "GStreamer Multimedia Codecs" Konqueror Showfoto digiKam The following 41 packages are going to be REMOVED: baloo-tools kdebase4-openSUSE-lang kio-extras5-lang lib++dfb-1_7-5 libGLEW1_10 libGLEW1_12 libGraphicsMagick++-Q16-3 libKF5Baloo1 libKF5BalooXapian1 libKF5WaylandClient5 libKF5WaylandServer5 libcamel-1_2-49 libcollection4 libdirectfb-1_7-5 libexiv2-13 libfribidi0 libgd3 libgd3-32bit libgsl0 libhdf5-8 libicu53_1 libicu53_1-ledata libmarblewidget19 libmgl7_3_0 libmng2 libmng2-32bit libntfs-3g85 libplist2 libpolarssl7 libpoppler46 libxkbcommon-0_4_3 libxkbcommon-x11-0_4_3 libyui-ncurses-pkg6 libyui-ncurses6 libyui-qt-graph6 libyui-qt-pkg6 libyui-qt6 libyui6 lsb myspell-lightproof-en python-strict-tls-check The following 3311 packages are going to be upgraded: ConsoleKit ConsoleKit-32bit ConsoleKit-x11 GeoIP GeoIP-data ImageMagick ImageMagick-extra Mesa Mesa-32bit Mesa-libEGL-devel Mesa-libEGL1 Mesa-libEGL1-32bit Mesa-libGL-devel Mesa-libGL1 Mesa-libGL1-32bit ................... The following 3365 packages are going to change vendor: ConsoleKit obs://build.opensuse.org/openSUSE:42 -> openSUSE ConsoleKit-32bit obs://build.opensuse.org/openSUSE:42 -> openSUSE ConsoleKit-x11 obs://build.opensuse.org/openSUSE:42 -> openSUSE GeoIP obs://build.opensuse.org/openSUSE:42 -> openSUSE ........................... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, same here. On Fri, Sep 25, 2015 at 3:56 AM, Milan Zimmermann <milan.zimmermann@gmail.com> wrote:
The I ran zypper up on a 42.1 M2 system. Then I was thinking "let's test zypper dup". In preparation, I made the USB the only enabled repository. I get basically "all is up to date" Then I also enable the 42.1 Beta online repos. Then, zypper dup tries to do something completely different, most important, zypper dup is now trying to change vendor. Why is that? For example:
I also dont understand these things bout packages and differences inside the iso images and then the corresponding online repositories. Actually I wonder ever since the days of the still suse products for private use that you were able to buy on retail editions with cds. Later with them the yast online update module immediately reported that there were some packages to be exchanged from cd media edition to ftp edition or similar. Also went from Milestone-2 edition now to Beta-1 edition, and a zypper ref and then zypper up or was it dup, lists quite a few tens of packages that should be replaced or even added and some removed. Can anyone clarify the build and fabrication process of the iso images and the whole deal of the software packages, why sometimes also with 13.2 or earlier versions zypper up says everything is okay, but a zypper dup still wants to bring in new stuff or replace stuff even though the iso should match the online repositories and actually configured those online repositories and the two are intended to be and tied together. Why are the packages inside the iso not the very same packages that are in the ..../distribution/product/repo/oss/ directory, and only stuff from the updates folder would be applied? I am really confused. Thank you. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Sep 25, 2015 at 10:35 AM, cagsm <cumandgets0mem00f@gmail.com> wrote:
Also went from Milestone-2 edition now to Beta-1 edition, and a zypper ref and then zypper up or was it dup, lists quite a few tens of packages that should be replaced or even added and some removed.
Just verified: zypper up is empty, but zypper dup lists several tens of packages that result in a vendor change, something of obs build opensuse leap42 -> opensuse So the product is internally or then officially again simply named as opensuse? Anyways, I wonder why the just released Beta-1 doesnt have the same internal and technical informations that there is already a change in package vendor strings or way they are created. Why was Beta-1 iso still built in a different way from the packages on the online oss repository. Would welcome explanations about these kind of things. Thank you. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2015-09-24 at 20:56 -0500, Milan Zimmermann wrote:
I just downloaded 42.1 Beta1 earlier today and put it on Lexar USB
The I ran zypper up on a 42.1 M2 system.
Then I was thinking "let's test zypper dup". In preparation, I made the USB the only enabled repository. I get basically "all is up to date"
Then I also enable the 42.1 Beta online repos. Then, zypper dup tries to do something completely different, most important, zypper dup is now trying to change vendor. Why is that? For example:
change vendor: ConsoleKit obs://build.opensuse.org/openSUSE:42 -> openSUSE
That is very strange.. openSUSE:42 has not been used AT all in the production of the Beta images.. the project moved a while ago to openSUSE:Leap:42.1; The vendor change is correct, as :42 was never properly setup to override the vendor to openSUSE. So the question for me would actually be: - Did you install afresh from the USB Media, or was this an upgrade from earlier milestones, that was still built from openSUSE:42? Indeed, the packages on the media are the same as are to be found in the FTP tree... as well the DVD as also the FTP tree are produced by OBS by the image builder. And they are strictly kept in sync. The fact that 'zypper up' would not want to change is normal: it ignores vendor changes per definition. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks for the follow up Dominique. One comment answering your question is inline On Fri, Sep 25, 2015 at 11:01 AM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
On Thu, 2015-09-24 at 20:56 -0500, Milan Zimmermann wrote:
I just downloaded 42.1 Beta1 earlier today and put it on Lexar USB
The I ran zypper up on a 42.1 M2 system.
Then I was thinking "let's test zypper dup". In preparation, I made the USB the only enabled repository. I get basically "all is up to date"
Then I also enable the 42.1 Beta online repos. Then, zypper dup tries to do something completely different, most important, zypper dup is now trying to change vendor. Why is that? For example:
change vendor: ConsoleKit obs://build.opensuse.org/openSUSE:42 -> openSUSE
That is very strange.. openSUSE:42 has not been used AT all in the production of the Beta images.. the project moved a while ago to openSUSE:Leap:42.1; The vendor change is correct, as :42 was never properly setup to override the vendor to openSUSE.
So the question for me would actually be: - Did you install afresh from the USB Media, or was this an upgrade from earlier milestones, that was still built from openSUSE:42?
Just before the commands I sent and described in my post, the lineage of this system has been: .. long histrory of SUSE and Opensuse releases ... maybe since 1999 :) Opensuse 13.2 M1 - ran as update, not sure it was zypper or Yast, and not sure about the exact commands M2 - ran as update, not sure it was zypper or Yast, and not sure about the exact commands .. at this point I can definitely confirm I limited the repositories to the Leap repos, online and USB put Beta on USB, inserted USB, and added the USB as repo ran zypper up ... at this point, I started asking what zypper dup does - the log attached in previous email is in this situation I am hoping the only solution will not be "install fresh 42.1", as I (and think others) would like to upgrade. The discrepancy between how zypper dup behaves with only USB repo and both USB and online repos seem to make no sense, and should not depend on history of the system. Plese let me know if I should provide more info. Thanks
Indeed, the packages on the media are the same as are to be found in the FTP tree... as well the DVD as also the FTP tree are produced by OBS by the image builder. And they are strictly kept in sync.
The fact that 'zypper up' would not want to change is normal: it ignores vendor changes per definition.
Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Milan, On Fri, 2015-09-25 at 14:15 -0500, Milan Zimmermann wrote:
Thanks for the follow up Dominique. One comment answering your question is inline
On Fri, Sep 25, 2015 at 11:01 AM, Dominique Leuenberger / DimStar
So the question for me would actually be: - Did you install afresh from the USB Media, or was this an upgrade from earlier milestones, that was still built from openSUSE:42?
Just before the commands I sent and described in my post, the lineage of this system has been:
.. long histrory of SUSE and Opensuse releases ... maybe since 1999 :) Opensuse 13.2 M1 - ran as update, not sure it was zypper or Yast, and not sure about the exact commands M2 - ran as update, not sure it was zypper or Yast, and not sure about the exact commands .. at this point I can definitely confirm I limited the repositories to the Leap repos, online and USB put Beta on USB, inserted USB, and added the USB as repo ran zypper up ... at this point, I started asking what zypper dup does - the log attached in previous email is in this situation
I am hoping the only solution will not be "install fresh 42.1", as I (and think others) would like to upgrade.
The discrepancy between how zypper dup behaves with only USB repo and both USB and online repos seem to make no sense, and should not depend on history of the system.
Plese let me know if I should provide more info.
Ok, now it makes all sense and I understand the difference... the issue is rather simple: * your system has packages installed, that are still supported, but that are not really nescessary anymore (ConsoleKit.. we migrated to systemd-login for session management). Now, the explanation why those packages are not touched when you dup with the USB Media, compared to when you dup with the online repo: the DVD/USB Media is only a subset of all packages available in the online repository. It contains packages that are nescessary to get a working 42.1 setup running. As such, ConsoleKit is not part of the DVD: it is simply no longer required. When you enable the online repository, the package can be found and a subsequent zypper dup correctly recognizes that there is a newer version in the repository and suggests to update it as well. So, in short: everything seen is actually working as expected... there is nothing wrong.. except that the DVD has limited capacity :) You should be able to remove ConsoleKit (nothing should really depend on it anymore... but be sure to verify the process removing it). Hope this explains the situation for you. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Dominique, On Fri, Sep 25, 2015 at 2:30 PM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
Hi Milan,
On Fri, 2015-09-25 at 14:15 -0500, Milan Zimmermann wrote:
Thanks for the follow up Dominique. One comment answering your question is inline
On Fri, Sep 25, 2015 at 11:01 AM, Dominique Leuenberger / DimStar
So the question for me would actually be: - Did you install afresh from the USB Media, or was this an upgrade from earlier milestones, that was still built from openSUSE:42?
Just before the commands I sent and described in my post, the lineage of this system has been:
.. long histrory of SUSE and Opensuse releases ... maybe since 1999 :) Opensuse 13.2 M1 - ran as update, not sure it was zypper or Yast, and not sure about the exact commands M2 - ran as update, not sure it was zypper or Yast, and not sure about the exact commands .. at this point I can definitely confirm I limited the repositories to the Leap repos, online and USB put Beta on USB, inserted USB, and added the USB as repo ran zypper up ... at this point, I started asking what zypper dup does - the log attached in previous email is in this situation
I am hoping the only solution will not be "install fresh 42.1", as I (and think others) would like to upgrade.
The discrepancy between how zypper dup behaves with only USB repo and both USB and online repos seem to make no sense, and should not depend on history of the system.
Plese let me know if I should provide more info.
Ok, now it makes all sense and I understand the difference... the issue is rather simple:
* your system has packages installed, that are still supported, but that are not really nescessary anymore (ConsoleKit.. we migrated to systemd-login for session management).
Now, the explanation why those packages are not touched when you dup with the USB Media, compared to when you dup with the online repo:
the DVD/USB Media is only a subset of all packages available in the online repository. It contains packages that are nescessary to get a working 42.1 setup running. As such, ConsoleKit is not part of the DVD: it is simply no longer required.
When you enable the online repository, the package can be found and a subsequent zypper dup correctly recognizes that there is a newer version in the repository and suggests to update it as well.
And through dependencies it triggered to other packages to change vendor, is my understanding correct?
So, in short: everything seen is actually working as expected... there is nothing wrong.. except that the DVD has limited capacity :)
Yes.
You should be able to remove ConsoleKit (nothing should really depend on it anymore... but be sure to verify the process removing it).
Hope this explains the situation for you.
Yes, this is definitely helpful - understanding of the fact that the DVD ISO is actually not the same (is a strict a subset of) the online repos. I was very puzzled, now it makes sense at least on a high level. One thing that I would like to understand more about, if you do not mind to follow up, is about is the vendor - who is obs://build.opensuse.org/openSUSE:42 vs openSUSE and where does it come from - does the "obs://build.opensuse.org/openSUSE:42" correspond to only the superset that is in the online repos, and openSUSE to the DVD contents? As a side question, considering one would want access to as large amount of packages as possible, it seems to made sense to keep those online repos in the repo list, would you agree? (Cannot see a reason of why not) I have more than the ConsoleKit changing vendor, I will delete the ConsoleKit, and deal with the others,, and see what zypper dup wants to do after that, and will follow up with questions if I have any, but at this point I am happy, to understand. Thanks very much for your follow up! Milan
Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Milan On Fri, 2015-09-25 at 16:54 -0500, Milan Zimmermann wrote:
When you enable the online repository, the package can be found and
a subsequent zypper dup correctly recognizes that there is a newer version in the repository and suggests to update it as well.
And through dependencies it triggered to other packages to change vendor, is my understanding correct?
You have ConsoleKit already installed on your machine.. dependencies have nothing to do with it.. as it's there, zypper will see that a 'better' package is now avaialble in the repo.. so it suggest to update it.
One thing that I would like to understand more about, if you do not mind to follow up, is about is the vendor - who is obs://build.opensuse.org/openSUSE:42 vs openSUSE and where does it come from - does the "obs://build.opensuse.org/openSUSE:42" correspond to only the superset that is in the online repos, and openSUSE to the DVD contents?
the vendor obs://build.opensuse.org/openSUSE:42 was the default vendor used up to M2... this was in fact the project in the build service the distribution was built in. And as we missed to explicitly set the vendor to openSUSE, OBS applied the default rule of using the project name.
As a side question, considering one would want access to as large amount of packages as possible, it seems to made sense to keep those online repos in the repo list, would you agree? (Cannot see a reason of why not)
If you most of the time have access to the online repo, I'd say yes, keep the online repo active.. on my systems, I generally only have the online repos and never use the DVD post install..
I have more than the ConsoleKit changing vendor, I will delete the ConsoleKit, and deal with the others,, and see what zypper dup wants to do after that, and will follow up with questions if I have any, but at this point I am happy, to understand.
The situation will be the same for all those packages: they exist in the repo, but not on the DVD (DVD is max 4.7 GB, I don't have the info at hand how big the FTP Tree is... but it is clearly much much more. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Dominique: On Fri, Sep 25, 2015 at 5:11 PM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
Hi Milan
On Fri, 2015-09-25 at 16:54 -0500, Milan Zimmermann wrote:
When you enable the online repository, the package can be found and
a subsequent zypper dup correctly recognizes that there is a newer version in the repository and suggests to update it as well.
And through dependencies it triggered to other packages to change vendor, is my understanding correct?
You have ConsoleKit already installed on your machine.. dependencies have nothing to do with it.. as it's there, zypper will see that a 'better' package is now avaialble in the repo.. so it suggest to update it.
Ah Ok, understand. I thought previously the wording suggested the ConsoleKit itself triggered all the vendor changes, or rather I added that conclusion there :) The fact that the ConsoleKit install wants to change vendor, is because M2's vendor was obs://build.opensuse.org/openSUSE:42 (and marked as such on my system) and now the new version's vendor is and will remain openSUSE, right?
One thing that I would like to understand more about, if you do not mind to follow up, is about is the vendor - who is obs://build.opensuse.org/openSUSE:42 vs openSUSE and where does it come from - does the "obs://build.opensuse.org/openSUSE:42" correspond to only the superset that is in the online repos, and openSUSE to the DVD contents?
the vendor obs://build.opensuse.org/openSUSE:42 was the default vendor used up to M2...
Ok, that was a big missing piece in my understanding.
this was in fact the project in the build service the distribution was built in. And as we missed to explicitly set the vendor to openSUSE, OBS applied the default rule of using the project name.
So from now, going forward, "official" 42.1 repos, online or DVD , the vendor name will be openSUSE, is that right?
As a side question, considering one would want access to as large amount of packages as possible, it seems to made sense to keep those online repos in the repo list, would you agree? (Cannot see a reason of why not)
If you most of the time have access to the online repo, I'd say yes, keep the online repo active.. on my systems, I generally only have the online repos and never use the DVD post install..
Thanks, appreciate the comment.
I have more than the ConsoleKit changing vendor, I will delete the ConsoleKit, and deal with the others,, and see what zypper dup wants to do after that, and will follow up with questions if I have any, but at this point I am happy, to understand.
The situation will be the same for all those packages: they exist in the repo, but not on the DVD (DVD is max 4.7 GB, I don't have the info at hand how big the FTP Tree is... but it is clearly much much more.
Cool, I am clear - and thanks again for clear explanations. Milan
Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2015-09-25 at 20:08 -0500, Milan Zimmermann wrote:
The fact that the ConsoleKit install wants to change vendor, is because M2's vendor was obs://build.opensuse.org/openSUSE:42 (and marked as such on my system) and now the new version's vendor is and will remain openSUSE, right?
yes, the openSUSE releases have been using vendor openSUSE for a long time... and there is no reason to change that (and, as said before: it was an oversight in M1 and M2 that it WAS different)
So from now, going forward, "official" 42.1 repos, online or DVD , the vendor name will be openSUSE, is that right?
Until we screw it up somehow :) but I hope we won't Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Sep 26, 2015 at 5:17 AM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
On Fri, 2015-09-25 at 20:08 -0500, Milan Zimmermann wrote:
The fact that the ConsoleKit install wants to change vendor, is because M2's vendor was obs://build.opensuse.org/openSUSE:42 (and marked as such on my system) and now the new version's vendor is and will remain openSUSE, right?
yes, the openSUSE releases have been using vendor openSUSE for a long time... and there is no reason to change that (and, as said before: it was an oversight in M1 and M2 that it WAS different)
So from now, going forward, "official" 42.1 repos, online or DVD , the vendor name will be openSUSE, is that right?
Until we screw it up somehow :) but I hope we won't
The openSUSE team is providing us with a great distro - Thanks! (oh, and among others, the branding, the lizard light bulb, that is just briliant :) )
Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
cagsm -
Dominique Leuenberger / DimStar -
Milan Zimmermann