openSUSE Factory search results for query "reproducible-builds"
factory@lists.opensuse.org- 21312 messages
Re: [opensuse-factory] New Tumbleweed snapshot 20181204 released!
by Christian Mahr
Issue seems to be fixed by today. Thanks! Christian
Am 05.01.19 um 18:25 schrieb Christian Mahr:
> PS:I forgot to mention that I fetch the vdr from
> obs://build.opensuse.org/vdr. The main tumbleweed repo is still obn
> vdr 2.2.0
>
>
> Am 05.01.19 um 17:50 schrieb Christian Mahr:
>> Hi!
>>
>> I think I have four a packaging problem for "vdr-plugin-vnsiserver" :
>>
>> ------------------------
>>
>> Problem: vdr-plugin-vnsiserver-1.8.0-1.1.x86_64 requires vdr(abi) =
>> 2.2.0, but this requirement cannot be provided
>> deleted providers: vdr-2.2.0-151.1.x86_64
>> not installable providers: vdr-2.2.0-6.1.i586[openSUSE-20180410-0]
>> vdr-2.2.0-6.1.x86_64[openSUSE-20180410-0]
>> Solution 1: install vdr-2.2.0-6.1.x86_64 (with vendor change)
>> obs://build.opensuse.org/vdr --> openSUSE
>> Solution 2: deinstallation of vdr-plugin-vnsiserver-1.5.2-1.23.x86_64
>> Solution 3: keep obsolete vdr-2.2.0-151.1.x86_64
>> Solution 4: break vdr-plugin-vnsiserver-1.8.0-1.1.x86_64 by ignoring
>> some of its dependencies
>> --------------------------------------
>>
>> The package avdr-plugin-vnsiserver-1.8.0-1.1.x86_64 aks for vdr
>> 2.2.0 (=a downgrade, since 2.4.0 is available), although the
>> maintainer of the "vdr-plugin-vnsiserver" source confirms the
>> adaptation for vdr 2.4.0 to be finished already some time ago.
>>
>> Who can help? re-trigger some build?
>>
>> Thanks Christian
>>
>>
>>
>>
>> Am 05.12.18 um 17:00 schrieb Dominique Leuenberger:
>>> Please note that this mail was generated by a script.
>>> The described changes are computed based on the x86_64 DVD.
>>> The full online repo contains too many changes to be listed here.
>>>
>>> Please check the known defects of this snapshot before upgrading:
>>> https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio…
>>>
>>>
>>> Please do not reply to this email to report issues, rather file a bug
>>> on bugzilla.opensuse.org. For more information on filing bugs please
>>> see https://en.opensuse.org/openSUSE:Submitting_bug_reports
>>>
>>> Packages changed:
>>> cyrus-imapd
>>> frogr (1.4 -> 1.5)
>>> goffice (0.10.43 -> 0.10.44)
>>> ibus-libpinyin
>>> mlocate
>>> nodejs10
>>> obs-service-set_version (0.5.10 -> 0.5.11)
>>> python-boto
>>> python-boto3 (1.9.38 -> 1.9.57)
>>> python-botocore (1.12.38 -> 1.12.57)
>>> rubygem-pathutil (0.16.1 -> 0.16.2)
>>> rubygem-pry (0.11.3 -> 0.12.2)
>>> rubygem-pry-doc (0.13.4 -> 0.13.5)
>>> rubygem-rack-1_6 (1.6.10 -> 1.6.11)
>>> rubygem-rack-oauth2 (1.9.2 -> 1.9.3)
>>> rubygem-rack-protection (2.0.3 -> 2.0.4)
>>> rubygem-rouge (3.2.1 -> 3.3.0)
>>> rubygem-sass (3.6.0 -> 3.7.2)
>>> rubygem-serverengine (2.0.7 -> 2.1.0)
>>> squid
>>> vdr
>>> virt-manager
>>> xfce4-branding-openSUSE
>>> xfce4-dict (0.8.1 -> 0.8.2)
>>>
>>> === Details ===
>>>
>>> ==== cyrus-imapd ====
>>> Subpackages: cyradm perl-Cyrus-IMAP perl-Cyrus-SIEVE-managesieve
>>>
>>> - Fixed startup of cyrus-imapd when using native systemd service
>>> by setting RuntimeDirectory=cyrus-imapd in the service file
>>> - cyrus-imapd: migrate from cron to systemd timers
>>> (bsc#1115438)
>>> Created script service and timer replacing cron daily script
>>> - Please convert SysV init scripts by cyrus-imapd into native
>>> systemd services
>>> (bsc#1115999)
>>> Fixed using the with_systemd macro
>>>
>>> ==== frogr ====
>>> Version update (1.4 -> 1.5)
>>> Subpackages: frogr-lang
>>>
>>> - Update to version 1.5:
>>> + Introduced "empty" initial state for when no pictures have been
>>> loaded yet.
>>> + Fixed issues with the content and installation of the AppData
>>> file.
>>> + Stopped installing frogr as a MIME handler for text/plain and
>>> text/html.
>>> + Stopped using gtk_widget_show_all(), use gtk_widget_show only
>>> instead.
>>> + Removed the application menu, moved functionality to hamburger
>>> menu.
>>> + Updated translations.
>>> - Drop obsolete conditional handling of desktop_database_post(un)
>>> and icon_theme_cache_post(un) in post(un).
>>>
>>> ==== goffice ====
>>> Version update (0.10.43 -> 0.10.44)
>>> Subpackages: goffice-lang libgoffice-0_10-10
>>>
>>> - Update to version 0.10.44:
>>> + No changes, version bump only.
>>>
>>> ==== ibus-libpinyin ====
>>>
>>> - Update ibus-libpinyin.spec: To adapt to tumbleweed's update to
>>> python3.
>>>
>>> ==== mlocate ====
>>> Subpackages: mlocate-lang
>>>
>>> - Reduce amount of emitted %service_* boilerplate.
>>>
>>> ==== nodejs10 ====
>>> Subpackages: nodejs10-devel npm10
>>>
>>> - flaky_test_rerun.patch: Rerun failing tests in case of flakiness
>>>
>>> ==== obs-service-set_version ====
>>> Version update (0.5.10 -> 0.5.11)
>>>
>>> - for now obs_scm_testsuite only for > 1315, needed python stuff
>>> not available otherwise
>>> - Update to version 0.5.11:
>>> * fix code to pass flake8 tests for python3
>>> * fix zipfile crash also for python2.7
>>> * avoid error with latest flake8 about unused variable
>>> * allow running tests with python3
>>> * second place where zip file handling can crash
>>> * avoid crashes due to false is_zipfile() response
>>> * Add python-flake8 to test suite package list
>>> * Fix indentation of condition
>>> * Fix basename to match documentation (#54)
>>>
>>> ==== python-boto ====
>>>
>>> - Undo previous change, name confustion between boto and boto3
>>> - Fix build for openSUSE Leap 42.3
>>> + urllib3 needs the ssl module, which in Leap 42.3 is delivered
>>> by python
>>> and not python-base. Set explicit build dependency on python
>>>
>>> ==== python-boto3 ====
>>> Version update (1.9.38 -> 1.9.57)
>>>
>>> - Version update to 1.9.57 (bsc#1118021, bsc#1118027)
>>> * bugfix:s3: [``botocore``] Add md5 header injection to new
>>> operations that require it
>>> * api-change:``s3``: [``botocore``] Update s3 client to latest
>>> version
>>> - from version 1.9.56
>>> * api-change:``elbv2``: [``botocore``] Update elbv2 client to
>>> latest version
>>> * api-change:``stepfunctions``: [``botocore``] Update
>>> stepfunctions client to latest version
>>> * api-change:``xray``: [``botocore``] Update xray client to
>>> latest version
>>> * api-change:``lambda``: [``botocore``] Update lambda client to
>>> latest version
>>> * api-change:``events``: [``botocore``] Update events client to
>>> latest version
>>> * api-change:``serverlessrepo``: [``botocore``] Update
>>> serverlessrepo client to latest version
>>> * api-change:``kafka``: [``botocore``] Update kafka client to
>>> latest version
>>> * api-change:``s3``: [``botocore``] Update s3 client to latest
>>> version
>>> - Update Requires in spec file from setup.py
>>> - Version update to 1.9.55
>>> * api-change:``ec2``: [``botocore``] Update ec2 client to latest
>>> version
>>> * api-change:``appmesh``: [``botocore``] Update appmesh client to
>>> latest version
>>> * api-change:``license-manager``: [``botocore``] Update
>>> license-manager client to latest version
>>> * api-change:``servicediscovery``: [``botocore``] Update
>>> servicediscovery client to latest version
>>> * api-change:``sagemaker``: [``botocore``] Update sagemaker
>>> client to latest version
>>> * api-change:``lightsail``: [``botocore``] Update lightsail
>>> client to latest version
>>> - from version 1.9.54
>>> * api-change:``securityhub``: [``botocore``] Update securityhub
>>> client to latest version
>>> * api-change:``rds``: [``botocore``] Update rds client to latest
>>> version
>>> * api-change:``fsx``: [``botocore``] Update fsx client to latest
>>> version
>>> * api-change:``dynamodb``: [``botocore``] Update dynamodb client
>>> to latest version
>>> - from version 1.9.53
>>> * api-change:``meteringmarketplace``: [``botocore``] Update
>>> meteringmarketplace client to latest version
>>> * api-change:``ec2``: [``botocore``] Update ec2 client to latest
>>> version
>>> * api-change:``codedeploy``: [``botocore``] Update codedeploy
>>> client to latest version
>>> * api-change:``translate``: [``botocore``] Update translate
>>> client to latest version
>>> * api-change:``logs``: [``botocore``] Update logs client to
>>> latest version
>>> * api-change:``kinesisanalytics``: [``botocore``] Update
>>> kinesisanalytics client to latest version
>>> * api-change:``comprehendmedical``: [``botocore``] Update
>>> comprehendmedical client to latest version
>>> * api-change:``mediaconnect``: [``botocore``] Update mediaconnect
>>> client to latest version
>>> * api-change:``kinesisanalyticsv2``: [``botocore``] Update
>>> kinesisanalyticsv2 client to latest version
>>> * api-change:``ecs``: [``botocore``] Update ecs client to latest
>>> version
>>> - from version 1.9.52
>>> * api-change:``iot``: [``botocore``] Update iot client to latest
>>> version
>>> * api-change:``sms``: [``botocore``] Update sms client to latest
>>> version
>>> * api-change:``s3``: [``botocore``] Update s3 client to latest
>>> version
>>> * api-change:``iotanalytics``: [``botocore``] Update iotanalytics
>>> client to latest version
>>> * api-change:``greengrass``: [``botocore``] Update greengrass
>>> client to latest version
>>> * api-change:``kms``: [``botocore``] Update kms client to latest
>>> version
>>> * api-change:``ec2``: [``botocore``] Update ec2 client to latest
>>> version
>>> * api-change:``globalaccelerator``: [``botocore``] Update
>>> globalaccelerator client to latest version
>>> - from version 1.9.51
>>> * api-change:``amplify``: [``botocore``] Update amplify client to
>>> latest version
>>> * api-change:``transfer``: [``botocore``] Update transfer client
>>> to latest version
>>> * api-change:``snowball``: [``botocore``] Update snowball client
>>> to latest version
>>> * api-change:``robomaker``: [``botocore``] Update robomaker
>>> client to latest version
>>> * api-change:``s3``: [``botocore``] Update s3 client to latest
>>> version
>>> * api-change:``datasync``: [``botocore``] Update datasync client
>>> to latest version
>>> - from version 1.9.50
>>> * api-change:``rekognition``: [``botocore``] Update rekognition
>>> client to latest version
>>> - from version 1.9.49
>>> * api-change:``autoscaling-plans``: [``botocore``] Update
>>> autoscaling-plans client to latest version
>>> * api-change:``xray``: [``botocore``] Update xray client to
>>> latest version
>>> * api-change:``devicefarm``: [``botocore``] Update devicefarm
>>> client to latest version
>>> * api-change:``ssm``: [``botocore``] Update ssm client to latest
>>> version
>>> * api-change:``medialive``: [``botocore``] Update medialive
>>> client to latest version
>>> * api-change:``redshift``: [``botocore``] Update redshift client
>>> to latest version
>>> * api-change:``rds-data``: [``botocore``] Update rds-data client
>>> to latest version
>>> * api-change:``appsync``: [``botocore``] Update appsync client to
>>> latest version
>>> * api-change:``cloudwatch``: [``botocore``] Update cloudwatch
>>> client to latest version
>>> * api-change:``quicksight``: [``botocore``] Update quicksight
>>> client to latest version
>>> * api-change:``cloudfront``: [``botocore``] Update cloudfront
>>> client to latest version
>>> - from version 1.9.48
>>> * api-change:``lightsail``: [``botocore``] Update lightsail
>>> client to latest version
>>> * api-change:``workspaces``: [``botocore``] Update workspaces
>>> client to latest version
>>> * api-change:``workdocs``: [``botocore``] Update workdocs client
>>> to latest version
>>> * api-change:``batch``: [``botocore``] Update batch client to
>>> latest version
>>> * api-change:``ec2``: [``botocore``] Update ec2 client to latest
>>> version
>>> * api-change:``devicefarm``: [``botocore``] Update devicefarm
>>> client to latest version
>>> * api-change:``rds``: [``botocore``] Update rds client to latest
>>> version
>>> * api-change:``cloudformation``: [``botocore``] Update
>>> cloudformation client to latest version
>>> * api-change:``lambda``: [``botocore``] Update lambda client to
>>> latest version
>>> * api-change:``config``: [``botocore``] Update config client to
>>> latest version
>>> * api-change:``cloudtrail``: [``botocore``] Update cloudtrail
>>> client to latest version
>>> * api-change:``mediaconvert``: [``botocore``] Update mediaconvert
>>> client to latest version
>>> * api-change:``iot``: [``botocore``] Update iot client to latest
>>> version
>>> - from version 1.9.47
>>> * api-change:``ssm``: [``botocore``] Update ssm client to latest
>>> version
>>> * api-change:``comprehend``: [``botocore``] Update comprehend
>>> client to latest version
>>> * api-change:``workspaces``: [``botocore``] Update workspaces
>>> client to latest version
>>> * api-change:``ce``: [``botocore``] Update ce client to latest
>>> version
>>> * api-change:``ecs``: [``botocore``] Update ecs client to latest
>>> version
>>> - from version 1.9.46
>>> * api-change:``s3``: [``botocore``] Update s3 client to latest
>>> version
>>> * api-change:``sms-voice``: [``botocore``] Update sms-voice
>>> client to latest version
>>> * api-change:``redshift``: [``botocore``] Update redshift client
>>> to latest version
>>> * api-change:``rds``: [``botocore``] Update rds client to latest
>>> version
>>> * api-change:``dms``: [``botocore``] Update dms client to latest
>>> version
>>> * api-change:``codebuild``: [``botocore``] Update codebuild
>>> client to latest version
>>> * api-change:``s3control``: [``botocore``] Update s3control
>>> client to latest version
>>> * api-change:``directconnect``: [``botocore``] Update
>>> directconnect client to latest version
>>> * api-change:``ram``: [``botocore``] Update ram client to latest
>>> version
>>> * api-change:``pinpoint``: [``botocore``] Update pinpoint client
>>> to latest version
>>> * api-change:``route53resolver``: [``botocore``] Update
>>> route53resolver client to latest version
>>> * api-change:``comprehend``: [``botocore``] Update comprehend
>>> client to latest version
>>> * api-change:``transcribe``: [``botocore``] Update transcribe
>>> client to latest version
>>> * api-change:``ecs``: [``botocore``] Update ecs client to latest
>>> version
>>> * api-change:``iam``: [``botocore``] Update iam client to latest
>>> version
>>> - from version 1.9.45
>>> * api-change:``resource-groups``: [``botocore``] Update
>>> resource-groups client to latest version
>>> * api-change:``autoscaling``: [``botocore``] Update autoscaling
>>> client to latest version
>>> * api-change:``mediatailor``: [``botocore``] Update mediatailor
>>> client to latest version
>>> * api-change:``sns``: [``botocore``] Update sns client to latest
>>> version
>>> * api-change:``sagemaker``: [``botocore``] Update sagemaker
>>> client to latest version
>>> * api-change:``servicecatalog``: [``botocore``] Update
>>> servicecatalog client to latest version
>>> * api-change:``ec2``: [``botocore``] Update ec2 client to latest
>>> version
>>> - from version 1.9.44
>>> * api-change:``chime``: [``botocore``] Update chime client to
>>> latest version
>>> * api-change:``budgets``: [``botocore``] Update budgets client to
>>> latest version
>>> * api-change:``redshift``: [``botocore``] Update redshift client
>>> to latest version
>>> - from version 1.9.43
>>> * api-change:``polly``: [``botocore``] Update polly client to
>>> latest version
>>> * api-change:``batch``: [``botocore``] Update batch client to
>>> latest version
>>> * api-change:``firehose``: [``botocore``] Update firehose client
>>> to latest version
>>> * api-change:``cloudformation``: [``botocore``] Update
>>> cloudformation client to latest version
>>> * api-change:``budgets``: [``botocore``] Update budgets client to
>>> latest version
>>> * api-change:``codepipeline``: [``botocore``] Update codepipeline
>>> client to latest version
>>> * api-change:``rds``: [``botocore``] Update rds client to latest
>>> version
>>> - from version 1.9.42
>>> * api-change:``mediapackage``: [``botocore``] Update mediapackage
>>> client to latest version
>>> - from version 1.9.41
>>> * api-change:``medialive``: [``botocore``] Update medialive
>>> client to latest version
>>> * api-change:``dlm``: [``botocore``] Update dlm client to latest
>>> version
>>> * api-change:``events``: [``botocore``] Update events client to
>>> latest version
>>> - from version 1.9.40
>>> * api-change:``dms``: [``botocore``] Update dms client to latest
>>> version
>>> * api-change:``ce``: [``botocore``] Update ce client to latest
>>> version
>>> * api-change:``ec2``: [``botocore``] Update ec2 client to latest
>>> version
>>> - from version 1.9.39
>>> * api-change:``codebuild``: [``botocore``] Update codebuild
>>> client to latest version
>>> * api-change:``pinpoint``: [``botocore``] Update pinpoint client
>>> to latest version
>>> * api-change:``ec2``: [``botocore``] Update ec2 client to latest
>>> version
>>> * api-change:``pinpoint-email``: [``botocore``] Update
>>> pinpoint-email client to latest version
>>> * api-change:``apigateway``: [``botocore``] Update apigateway
>>> client to latest version
>>> * api-change:``waf-regional``: [``botocore``] Update waf-regional
>>> client to latest version
>>> * bugfix:session config: [``botocore``] Added the default session
>>> configuration
>>> tuples back to session.session_vars_map.
>>> - Update Requires in spec file from setup.py
>>>
>>> ==== python-botocore ====
>>> Version update (1.12.38 -> 1.12.57)
>>>
>>> - Version update to 1.12.57 (bsc#1118021, bsc#1118027)
>>> * bugfix:s3: Add md5 header injection to new operations that
>>> require it
>>> * api-change:``s3``: Update s3 client to latest version
>>> - from version 1.12.56
>>> * api-change:``elbv2``: Update elbv2 client to latest version
>>> * api-change:``stepfunctions``: Update stepfunctions client to
>>> latest version
>>> * api-change:``xray``: Update xray client to latest version
>>> * api-change:``lambda``: Update lambda client to latest version
>>> * api-change:``events``: Update events client to latest version
>>> * api-change:``serverlessrepo``: Update serverlessrepo client to
>>> latest version
>>> * api-change:``kafka``: Update kafka client to latest version
>>> * api-change:``s3``: Update s3 client to latest version
>>> - from version 1.12.55
>>> * api-change:``ec2``: Update ec2 client to latest version
>>> * api-change:``appmesh``: Update appmesh client to latest version
>>> * api-change:``license-manager``: Update license-manager client
>>> to latest version
>>> * api-change:``servicediscovery``: Update servicediscovery client
>>> to latest version
>>> * api-change:``sagemaker``: Update sagemaker client to latest
>>> version
>>> * api-change:``lightsail``: Update lightsail client to latest
>>> version
>>> - from version 1.12.54
>>> * api-change:``securityhub``: Update securityhub client to latest
>>> version
>>> * api-change:``rds``: Update rds client to latest version
>>> * api-change:``fsx``: Update fsx client to latest version
>>> * api-change:``dynamodb``: Update dynamodb client to latest version
>>> - from version 1.12.53
>>> * api-change:``meteringmarketplace``: Update meteringmarketplace
>>> client to latest version
>>> * api-change:``ec2``: Update ec2 client to latest version
>>> * api-change:``codedeploy``: Update codedeploy client to latest
>>> version
>>> * api-change:``translate``: Update translate client to latest
>>> version
>>> * api-change:``logs``: Update logs client to latest version
>>> * api-change:``kinesisanalytics``: Update kinesisanalytics client
>>> to latest version
>>> * api-change:``comprehendmedical``: Update comprehendmedical
>>> client to latest version
>>> * api-change:``mediaconnect``: Update mediaconnect client to
>>> latest version
>>> * api-change:``kinesisanalyticsv2``: Update kinesisanalyticsv2
>>> client to latest version
>>> * api-change:``ecs``: Update ecs client to latest version
>>> - from version 1.12.52
>>> * api-change:``iot``: Update iot client to latest version
>>> * api-change:``sms``: Update sms client to latest version
>>> * api-change:``s3``: Update s3 client to latest version
>>> * api-change:``iotanalytics``: Update iotanalytics client to
>>> latest version
>>> * api-change:``greengrass``: Update greengrass client to latest
>>> version
>>> * api-change:``kms``: Update kms client to latest version
>>> * api-change:``ec2``: Update ec2 client to latest version
>>> * api-change:``globalaccelerator``: Update globalaccelerator
>>> client to latest version
>>> - from version 1.12.51
>>> * api-change:``amplify``: Update amplify client to latest version
>>> * api-change:``transfer``: Update transfer client to latest version
>>> * api-change:``snowball``: Update snowball client to latest version
>>> * api-change:``robomaker``: Update robomaker client to latest
>>> version
>>> * api-change:``s3``: Update s3 client to latest version
>>> * api-change:``datasync``: Update datasync client to latest version
>>> - from version 1.12.50
>>> * api-change:``rekognition``: Update rekognition client to latest
>>> version
>>> - from version 1.12.49
>>> * api-change:``autoscaling-plans``: Update autoscaling-plans
>>> client to latest version
>>> * api-change:``xray``: Update xray client to latest version
>>> * api-change:``devicefarm``: Update devicefarm clienProblem:
>>> vdr-plugin-vnsiserver-1.8.0-1.1.x86_64 requires vdr(abi) = 2.2.0,
>>> but this requirement cannot be provided
>>> deleted providers: vdr-2.2.0-151.1.x86_64
>>> not installable providers: vdr-2.2.0-6.1.i586[openSUSE-20180410-0]
>>> vdr-2.2.0-6.1.x86_64[openSUSE-20180410-0]
>>> Solution 1: install vdr-2.2.0-6.1.x86_64 (with vendor change)
>>> obs://build.opensuse.org/vdr --> openSUSE
>>> Solution 2: deinstallation of vdr-plugin-vnsiserver-1.5.2-1.23.x86_64
>>> Solution 3: keep obsolete vdr-2.2.0-151.1.x86_64
>>> Solution 4: break vdr-plugin-vnsiserver-1.8.0-1.1.x86_64 by
>>> ignoring some of its dependencies
>>>
>>> t to latest version
>>> * api-change:``ssm``: Update ssm client to latest version
>>> * api-change:``medialive``: Update medialive client to latest
>>> version
>>> * api-change:``redshift``: Update redshift client to latest version
>>> * api-change:``rds-data``: Update rds-data client to latest version
>>> * api-change:``appsync``: Update appsync client to latest version
>>> * api-change:``cloudwatch``: Update cloudwatch client to latest
>>> version
>>> * api-change:``quicksight``: Update quicksight client to latest
>>> version
>>> * api-change:``cloudfront``: Update cloudfront client to latest
>>> version
>>> - from version 1.12.48
>>> * api-change:``lightsail``: Update lightsail client to latest
>>> version
>>> * api-change:``workspaces``: Update workspaces client to latest
>>> version
>>> * api-change:``workdocs``: Update workdocs client to latest version
>>> * api-change:``batch``: Update batch client to latest version
>>> * api-change:``ec2``: Update ec2 client to latest version
>>> * api-change:``devicefarm``: Update devicefarm client to latest
>>> version
>>> * api-change:``rds``: Update rds client to latest version
>>> * api-change:``cloudformation``: Update cloudformation client to
>>> latest version
>>> * api-change:``lambda``: Update lambda client to latest version
>>> * api-change:``config``: Update config client to latest version
>>> * api-change:``cloudtrail``: Update cloudtrail client to latest
>>> version
>>> * api-change:``mediaconvert``: Update mediaconvert client to
>>> latest version
>>> * api-change:``iot``: Update iot client to latest version
>>> - from version 1.12.47
>>> * api-change:``ssm``: Update ssm client to latest version
>>> * api-change:``comprehend``: Update comprehend client to latest
>>> version
>>> * api-change:``workspaces``: Update workspaces client to latest
>>> version
>>> * api-change:``ce``: Update ce client to latest version
>>> * api-change:``ecs``: Update ecs client to latest version
>>> - from version 1.12.46
>>> * api-change:``s3``: Update s3 client to latest version
>>> * api-change:``sms-voice``: Update sms-voice client to latest
>>> version
>>> * api-change:``redshift``: Update redshift client to latest version
>>> * api-change:``rds``: Update rds client to latest version
>>> * api-change:``dms``: Update dms client to latest version
>>> * api-change:``codebuild``: Update codebuild client to latest
>>> version
>>> * api-change:``s3control``: Update s3control client to latest
>>> version
>>> * api-change:``directconnect``: Update directconnect client to
>>> latest version
>>> * api-change:``ram``: Update ram client to latest version
>>> * api-change:``pinpoint``: Update pinpoint client to latest version
>>> * api-change:``route53resolver``: Update route53resolver client
>>> to latest version
>>> * api-change:``comprehend``: Update comprehend client to latest
>>> version
>>> * api-change:``transcribe``: Update transcribe client to latest
>>> version
>>> * api-change:``ecs``: Update ecs client to latest version
>>> * api-change:``iam``: Update iam client to latest version
>>> - from version 1.12.45
>>> * api-change:``resource-groups``: Update resource-groups client
>>> to latest version
>>> * api-change:``autoscaling``: Update autoscaling client to latest
>>> version
>>> * api-change:``mediatailor``: Update mediatailor client to latest
>>> version
>>> * api-change:``sns``: Update sns client to latest version
>>> * api-change:``sagemaker``: Update sagemaker client to latest
>>> version
>>> * api-change:``servicecatalog``: Update servicecatalog client to
>>> latest version
>>> * api-change:``ec2``: Update ec2 client to latest version
>>> - from version 1.12.44
>>> * api-change:``chime``: Update chime client to latest version
>>> * api-change:``budgets``: Update budgets client to latest version
>>> * api-change:``redshift``: Update redshift client to latest version
>>> - from version 1.12.43
>>> * api-change:``polly``: Update polly client to latest version
>>> * api-change:``batch``: Update batch client to latest version
>>> * api-change:``firehose``: Update firehose client to latest version
>>> * api-change:``cloudformation``: Update cloudformation client to
>>> latest version
>>> * api-change:``budgets``: Update budgets client to latest version
>>> * api-change:``codepipeline``: Update codepipeline client to
>>> latest version
>>> * api-change:``rds``: Update rds client to latest version
>>> - from version 1.12.42
>>> * api-change:``mediapackage``: Update mediapackage client to
>>> latest version
>>> - from version 1.12.41
>>> * api-change:``medialive``: Update medialive client to latest
>>> version
>>> * api-change:``dlm``: Update dlm client to latest version
>>> * api-change:``events``: Update events client to latest version
>>> - from version 1.12.40
>>> * api-change:``dms``: Update dms client to latest version
>>> * api-change:``ce``: Update ce client to latest version
>>> * api-change:``ec2``: Update ec2 client to latest version
>>> - from version 1.12.39
>>> * api-change:``codebuild``: Update codebuild client to latest
>>> version
>>> * api-change:``pinpoint``: Update pinpoint client to latest version
>>> * api-change:``ec2``: Update ec2 client to latest version
>>> * api-change:``pinpoint-email``: Update pinpoint-email client to
>>> latest version
>>> * api-change:``apigateway``: Update apigateway client to latest
>>> version
>>> * api-change:``waf-regional``: Update waf-regional client to
>>> latest version
>>> * bugfix:session config: Added the default session configuration
>>> tuples back to session.session_vars_map.
>>>
>>> ==== rubygem-pathutil ====
>>> Version update (0.16.1 -> 0.16.2)
>>>
>>> - updated to version 0.16.2
>>> no changelog found
>>>
>>> ==== rubygem-pry ====
>>> Version update (0.11.3 -> 0.12.2)
>>>
>>> - updated to version 0.12.2
>>> see installed CHANGELOG.md
>>> [#]## [v0.12.2][v0.12.2] (November 12, 2018)
>>> [#]### Bug fixes
>>> * Restore removed deprecations, which were removed by accident
>>> due to a bad
>>> rebase.
>>> [#]## [v0.12.1][v0.12.1] (November 12, 2018)
>>> [#]### Bug fixes
>>> * Stopped creating a new hash each time `Pry::Prompt#[]` is invoked
>>> ([#1855](https://github.com/pry/pry/pull/1855))
>>> * Fixed `less` pager not working when it's available
>>> ([#1861](https://github.com/pry/pry/pull/1861))
>>> [#]## [v0.12.0][v0.12.0] (November 5, 2018)
>>> [#]### Major changes
>>> * Dropped support for Rubinius
>>> ([#1785](https://github.com/pry/pry/pull/1785))
>>>
>>> ==== rubygem-pry-doc ====
>>> Version update (0.13.4 -> 0.13.5)
>>>
>>> - updated to version 0.13.5
>>> see installed CHANGELOG.md
>>> [#]## [v0.13.5][v0.13.5] (November 8, 2018)
>>> * Fixed deprecation warnings emitted by Pry v0.12.0
>>> ([#87](https://github.com/pry/pry-doc/pull/87))
>>> * Fixed MRI 2.0 regression
>>> ([#88](https://github.com/pry/pry-doc/pull/88))
>>>
>>> ==== rubygem-rack-1_6 ====
>>> Version update (1.6.10 -> 1.6.11)
>>>
>>> - updated to version 1.6.11
>>> see installed HISTORY.md
>>>
>>> ==== rubygem-rack-oauth2 ====
>>> Version update (1.9.2 -> 1.9.3)
>>>
>>> - updated to version 1.9.3
>>> no changelog found
>>>
>>> ==== rubygem-rack-protection ====
>>> Version update (2.0.3 -> 2.0.4)
>>>
>>> - updated to version 2.0.4
>>> no changelog found
>>>
>>> ==== rubygem-rouge ====
>>> Version update (3.2.1 -> 3.3.0)
>>>
>>> - updated to version 3.3.0
>>> no changelog found
>>>
>>> ==== rubygem-sass ====
>>> Version update (3.6.0 -> 3.7.2)
>>>
>>> - updated to version 3.7.2
>>> no changelog found
>>>
>>> ==== rubygem-serverengine ====
>>> Version update (2.0.7 -> 2.1.0)
>>>
>>> - updated to version 2.1.0
>>> see installed Changelog
>>> 2018-11-14 version 2.1.0:
>>> * Improve socket manager security
>>>
>>> ==== squid ====
>>>
>>> - Fix permissions of installed file to tmpfilesdir
>>>
>>> ==== vdr ====
>>> Subpackages: vdr-lang
>>>
>>> - remove dvbhddevice plugin for Factory (kernel 4.19+), the needed
>>> drivers/APIs are no longer available
>>> - add "-pie -fPIE" compiler options to make rpmlint happier
>>> - use %license for COPYING file
>>>
>>> ==== virt-manager ====
>>> Subpackages: virt-install virt-manager-common
>>>
>>> - Change icons to those provided by package
>>> (yast2-theme doesn't provide some icons anymore)
>>>
>>> ==== xfce4-branding-openSUSE ====
>>> Subpackages: exo-branding-openSUSE libgarcon-branding-openSUSE
>>> libxfce4ui-branding-openSUSE openSUSE-xfce-icon-theme
>>> thunar-volman-branding-openSUSE xfce4-notifyd-branding-openSUSE
>>> xfce4-panel-branding-openSUSE xfce4-power-manager-branding-openSUSE
>>> xfce4-session-branding-openSUSE xfce4-settings-branding-openSUSE
>>> xfdesktop-branding-openSUSE xfwm4-branding-openSUSE
>>>
>>> - removed midori branding
>>>
>>> ==== xfce4-dict ====
>>> Version update (0.8.1 -> 0.8.2)
>>> Subpackages: xfce4-dict-lang xfce4-panel-plugin-dict
>>>
>>> - update to version 0.8.2
>>> - Avoid segfaults (bxo#14786)
>>> - Only show web search link if we have a valid URL/dict mode
>>> - Escape link tooltip
>>> - Minor visual improvements
>>> - Translation updates
>>>
>>>
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
5 years, 10 months
[opensuse-factory] Experience of switching to Factory from Ubuntu
by Alberto Passalacqua
I read this interesting wiki
http://en.opensuse.org/GNOME/Projects/Lived_in_Project/Ubuntu#Experience_of…
There are some interesting points I share, and some points that imho are
what characterize SUSE since the beginning, so I think it would be
interesting to discuss them a bit to hear what users think.
Vincent, the author of the page, asked me to clarify that what he wrote
are his opinions. Of course it's the same for what I write. :-)
I will comment point-to-point, hoping not to forget any. Quoted text is
from the page.
Let's start:
>Note that some of the items here are simply caused by the fact that
>openSUSE tries to be everything at the same time (distro for server,
>desktop, etc.). It might make sense to have an install CD for server,
>and another one for desktop.
I like the full-featured DVD, which can do everything. And I think that
having everything in one place just adds value and simplifies things
both for the final users and for the maintainers. I mean: 1 medium
allows you to do what you need to, and it's easier to keep under control
its quality, at least in the general aspects (more people use it).
>Also, there's something wrong with factory if we want people to use it
>(especially developers). Ubuntu is doing a much better job here.
>the installer is way too complex, with too many things to do, even with
>the current simplification work going on in Factory.
Yes, it does a lot of things and it takes longer than ubuntu, that's
sure. But on the contrary it leaves you with a fully configured system,
with the software selection you want, with network properly configured
even if you have various interfaces, with a firewall properly set-up and
with running printing services. So I vote for keeping it long.
>sudo should be used by default for a desktop install. It doesn't make
>any sense to have the root account. There's an option "Use the same
>password for root as the one used for the user" in the installer, but
>it's not about sudo, I believe.
Thanks for pointing this out. I was myself a sudo supporter, but someone
with more technical experience than me explained to me that sudo is not
the right way to follow for various security/conceptual reasons, and I
agree. In the end, UNIX has root, and the users should learn to manage
it. It doesn't add complexity if properly explained.
About the "Use the same password for root", I think it's plain wrong.
Using the same password for root and the user reduces security.
>in openSUSE, there are two radeon drivers: the old one and the
>randr1.2-enabled one (new one), probably because the new one is still
>in beta. Still, it doesn't make much sense to have both and the new one
>works fine. Only this one should be used.
I agree. If the one selected is really working in all the cases. If not,
better two than a complaining user.
>on startup, there's a 10 seconds delay in grub. Ubuntu only uses 1 or 2
>seconds. It helps with the feeling of booting faster.
>Ubuntu seems to boot faster. There might be less services, some
>services are started after GDM is shown, etc. upstart might help too.
Ten seconds in grub are a reasonable time to allow the user to select
the operating system. And I think it's a basic requirement also for
accessibility. Not all users are young, fast and without issues.
>Ubuntu uses brown as the color for the root window when starting GDM
>(it's a gdm config option, I believe). It helps with the transition
>from the brown gdm theme to the brown default background on the user
>desktop. In openSUSE, we still use the greyish blue. It should be some
>green.
Hehe I love green, so I agree. But green is not much appreciated by
various users, who switched back to blue or personalised backgrounds.
>the menu bar is completely unusable in openSUSE: icons are too big
>(distro patch), and there are tons of submenus (because we use the same
>menu config as KDE?)
I think it's related to the idea of offering a comparable choice of
applications to the users on both DE.
The real, not addressed, point is that the menu (main-menu) is not well
implemented and it's probably one of the most buggy piece of software we
have (read never solved leaks). I would love to see a kickoff-like
implementation in place of the app-browser.
>with only a very short look, I saw many
>not-updated-to-the-latest-versions packages: yelp, totem, epiphany,
>rhythmbox for example.
This is SUSE policy. The released version is not upgraded until the next
release. I usually agree with it, because it's thought to grant
stability, but I think it was used in the wrong way sometime, not
providing updates when features were lacking (for 10.3, read: anjuta,
gedit with python support, ...).
>Ubuntu is quite good at uploading new packages as soon as upstream
>releases (at least, for GNOME). This is really great for a developer
>like me.
I agree. But I don't want to think to continuous updates to the released
version ;-)
>when I update openSUSE with "zypper dup", I have to download nearly 1GB
>of packages. I seriously doubt that all of them were updated. It takes
>me hours to get all updates... (slow DSL line)
This is because dependency issues in the gnome side at opensuse are
historical. One package usually brings half of gnome with itself. I
don't know if it's necessary, but it's a common complaining we get.
>the Ubuntu development version is nearly never broken. Factory is
>always broken in some way (still usable, but either no network, or
>uninstallable updates, or impossible to mount a usb key, etc.).
Another historical issue. I always read/experienced these issues.
>I had to manually install the firmwares for my intel wireless card
>when I don't have a gstreamer plugin, totem shows a dialog proposing me
>to install it. It just opens a webpage. Ubuntu actually installs the
>right package (and adds the repository if needed)
Well, ubuntu violates a bunch of laws doing that :-)
The intel firmware is provided on a non-OSS support and on the DVD, and
should be installed by default. Online there's the non-OSS repository,
which can be added at installation time. Keeping OSS and non-OSS
separated is one of the long discussed key decision openSUSE made.
>I couldn't find all gstreamer plugins for factory... So no multimedia
>experience for me.
This depends on the fact that those plugins can't be hosted in -factory
for the same legal reasons they're not provided with the distribution.
Moreover they're packaged by non-Novell related guys.
>it's actually confusing to have so many repositories on
>software.opensuse.org. If possible, everything should go to the main
>factory repository.
I agree. But for codecs, drivers and others things, there are legal
issues.
>there are tons of installed packages by default that don't make any
>sense. Some graphical ones (gftp? skencil?), some non-graphical (tcsh,
>ksh, zsh: do we really need all shells by default?)
Well, except gftp (the only decent FTP client for GNOME), the rest
should be removed. It's ages we get the complaint of suse having this
issue.
>Ubuntu doesn't use a firewall by default because the default services
>are secure and trusted (ssh, avahi, eg). With openSUSE, I have to
>choose what I want to do with the firewall.
Ubuntu does wrong on this side. Services are secure until you don't
prove the contrary, and this happens often, considering that SSH is
regularly patched, for example.
A firewall is necessary imho, but its configuration should be easier.
For example, while it's easy to open SSH port, it's a mess to have a
properly working samba because of closed highports (hehe I know I said
this too many times).
>too many unneeded yast stuff. Users don't need to know about apparmor.
Why not? A user can happily ignore that. Who does decide that the user
doesn't need to know? That's not the UNIX philosophy. The user should
LEARN to use his system, and the system should provide sensible
defaults, of course (as a proper AppArmor configuration).
>A tool to config the mouse model in X shouldn't be needed.
The model of the mouse is selected in SaX, where the whole X is
configured, and I think it's there because it might be necessary to set
things in a fine way in certain cases.
>There are 8 >launchers in the Software category and I don't understand
>what they >are... etc.
Perfectly agree on this!
>seahorse/gnome-keyring integration: in Ubuntu, when I ssh somewhere, a
>dialog pops up. In openSUSE, I need to use the standard ssh-agent, it
>seems.
I agree on this one too :)
>in the middle of the afternoon, I see beagle-build-index and the man db
>rebuild happening. Lots of hard disk use. Middle of the afternoon is
>when I use my computer. It should be done during the night if possible.
Hmm. This looks like a cron-job issue. It's usually done around late
evening here.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
16 years, 8 months
[opensuse-factory] cyrus-sasl, the package that rules them all?
by Gerald Pfeifer
So, one of these days I figured I'd make the installation on one
of my systems a bit slimmer, and I really don't need an IMAP server
on that machine.
tomonaga# rpm -qa | grep cyrus-sasl
cyrus-sasl-gssapi-2.1.25-17.2.x86_64
cyrus-sasl-plain-2.1.25-17.2.x86_64
cyrus-sasl-saslauthd-2.1.25-17.2.x86_64
cyrus-sasl-crammd5-2.1.25-17.2.x86_64
cyrus-sasl-2.1.25-17.2.x86_64
cyrus-sasl-32bit-2.1.25-17.2.x86_64
cyrus-sasl-digestmd5-2.1.25-17.2.x86_64
Alas, when removing cyrus-sasl, zypper is inclined to remove quite
a bit more including the kernel, Firefox, and a load of others?
Something is overly aggressive in terms of dependencies it seems?
Or am I missing something?
tomonaga# rpm -qa | grep cyrus-sasl | xargs zypper rm
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following packages are going to be REMOVED:
ConsoleKit ConsoleKit-x11 DirectFB-Mesa Mesa ModemManager
MozillaFirefox MozillaFirefox-branding-openSUSE NetworkManager
NetworkManager-gnome NetworkManager-openvpn
NetworkManager-openvpn-gnome OpenPrintingPPDs-ghostscript
OpenPrintingPPDs-hpijs OpenPrintingPPDs-postscript PackageKit
PackageKit-branding-openSUSE PackageKit-browser-plugin
PackageKit-gstreamer-plugin PolicyKit SuSEfirewall2 a2ps aaa_base
aaa_base-extras accountsservice acpid alpine alsa-plugins-pulse
amarok at at-spi2-core audit autofs autoyast2-installation
biosdevname bluez bootsplash bootsplash-branding-openSUSE
brltty-driver-at-spi2 brltty-driver-espeak bug-buddy cantarell-fonts
cdrdao cdrkit-cdrtools-compat cifs-utils cmake colord cron cronie
cryptsetup cups cups-backends cups-pk-helper curl cyrus-sasl
cyrus-sasl-32bit cyrus-sasl-crammd5 cyrus-sasl-digestmd5
cyrus-sasl-gssapi cyrus-sasl-plain cyrus-sasl-saslauthd dbus-1
dbus-1-glib dbus-1-python dconf dejavu desktop-file-utils
device-mapper dhcp dhcp-client dhcpcd digikam dirmngr dmraid dnsmasq
dosbox droid-fonts efont-unicode emacs-x11 enblend-enfuse enscript
espeak evince evolution-data-server fam fetchmail fifth-leg-font
finger flash-player foomatic-filters freeglut gconf-editor
gconf-polkit gconf-sanity-check gconf2 gdm gdm-branding-openSUSE
ghostscript-fonts-std ghostscript-library ghostscript-x11 gimp
gimp-branding-openSUSE gimp-help gjs gnokii gnome-bluetooth
gnome-contacts gnome-keyring gnome-packagekit gnome-panel
gnome-panel-branding-openSUSE gnome-power-manager gnome-screensaver
gnome-session-core gnome-settings-daemon
gnome-settings-daemon-polkit-datetime gnome-terminal gnome-vfs2 gpg2
gpsd gsettings-backend-dconf gstreamer-0_10-libnice
gstreamer-0_10-plugin-esd gstreamer-0_10-plugins-bad
gstreamer-0_10-plugins-good gucharmap gutenprint gvfs
gvfs-backend-afc gvfs-backends gvfs-fuse haveged hplip-hpijs
hplip-sane icedax ifnteuro intlfnts irqbalance k3b kaffeine
kdebase4-runtime kdelibs4 kdelibs4-core kdepimlibs4 kdialog
kernel-default kernel-default-base kerneloops kipi-plugins
kipi-plugins-acquireimage kipi-plugins-geolocation kpartx kscd ksh
libGLEW1_6 libGLEW1_7 libQtWebKit4 libaccountsservice0 libakonadi4
libakonadiprotocolinternals1 libao-plugins4 libao4 libapr-util1
libatasmart0 libatasmart4 libatspi0 libattica0 libavahi-client3
libavahi-gobject0 libbrasero-burn3-1 libbrasero-utils3-1
libcamel-1_2-28 libcamel-1_2-29 libcanberra-gtk0 libcanberra-gtk3-0
libcanberra0 libcheese-gtk20 libcheese1 libclutter-glx-1_0-0
libclutter-gst-1_0-0 libclutter-gtk-1_0-0 libcogl-pango0 libcogl1
libcogl2 libcogl5 libcompizconfig libcryptsetup1 libcryptui0
libcurl4 libdbusmenu-qt2 libdconf0 libdns_sd libebackend-1_2-1
libebook-1_2-11 libebook-1_2-12 libecal-1_2-10 libecal-1_2-9
libedata-book-1_2-10 libedata-book-1_2-11 libedata-cal-1_2-12
libedata-cal-1_2-13 libedataserver-1_2-14 libedataserver-1_2-15
libedataserverui-3_0-1 libepc-1_0-2 liberation-fonts libfolks-eds25
libfolks-libsocialweb25 libfolks-telepathy25 libfolks25 libftgl2
libgconfmm-2_6-1 libgdata13 libgdmgreeter1 libgdu0 libgeoclue0
libgjs0 libgnome-bluetooth8 libgnome-keyring0 libgoa-backend-1_0-0
libgpgme11 libgphoto2 libgpod-tools libgpod4 libgrlnet-0_1-0
libgssdp-1_0-3 libgudev-1_0-0 libgupnp-1_0-4 libgupnp-av-1_0-2
libgupnp-igd-1_0-3 libgvfscommon0 libgvnc-1_0-0 libgweather-3-0
libgweather-data libimobiledevice2 libkcddb4 libkcompactdisc4
libkdcraw20 libkde4 libkdecore4 libkdeedu4-data libkdepimlibs4
libkeduvocdocument4 libkexiv2-10 libkface1 libkgeomap1 libkipi8
libksane0 libksuseinstall1 liblastfm0 liblazy1 libldap-2_4-2
libldap-2_4-2-32bit libldapcpp1 libldb1 liblockdev1
libmarblewidget12 libmission-control-plugins0 libmx-1_0-2
libmygpo-qt1 libnice10 libnm-glib-vpn1 libnm-glib4 libnm-gtk0
libnm-util2 liboauth0 libofx libofx4 libopal3_6_8 libopencv2_3
libpackagekit-glib2-14 libpanel-applet-4-0 libparted0 libphonon4
libpolkit-qt-1-1 libpolkit0 libpq5 libprison0
libproxy1-networkmanager libpt2_6_7 libpulse-mainloop-glib0
libpulse0 libqca2 libqdialogsolver1 libqjson0 libqt4
libqt4-qt3support libqt4-sql libqt4-sql-mysql libqt4-sql-postgresql
libqt4-sql-sqlite libqt4-x11 libquvi0 libquvi6 libqzeitgeist0
libraptor2-0 librasqal3 libredland0 libreoffice libreoffice-base
libreoffice-base-extensions libreoffice-calc
libreoffice-calc-extensions libreoffice-converter libreoffice-draw
libreoffice-draw-extensions libreoffice-filters-optional
libreoffice-help-en-US libreoffice-impress
libreoffice-impress-extensions libreoffice-mailmerge
libreoffice-math libreoffice-pyuno libreoffice-writer
libreoffice-writer-extensions librest0 libsmbclient0 libsocialweb
libsocialweb-branding-openSUSE libsocialweb-client2 libsocialweb0
libsoprano4 libsoup-2_4-1 libspectre1 libstorage3 libstrigi0
libtelepathy-glib0 libtelepathy-logger2 libtotem-plparser-mini17
libtotem-plparser17 libtunepimp libtunepimp5 libudev0
libupower-glib1 libusbmuxd1 libwebkitgtk-3_0-0 libxine1
libxine1-pulse libyelp0 libzypp lirc lockdev logrotate lvm2 marble
marble-data mariadb mcelog metacity microcode_ctl mkinitrd moodbar
multipath-tools mutter nautilus-evince nautilus-extension-seahorse
nautilus-open-terminal nautilus-totem netcfg nfs-client nfsidmap
notification-daemon ntp obex-data-server obexd obexd-client
openSUSE-build-key openldap2-client openssh openssh-askpass
parallel-printer-support parted patterns-openSUSE-base
patterns-openSUSE-enhanced_base patterns-openSUSE-games
patterns-openSUSE-imaging patterns-openSUSE-imaging_opt
patterns-openSUSE-non_oss patterns-openSUSE-non_oss_opt
patterns-openSUSE-sw_management patterns-openSUSE-x11
patterns-openSUSE-x11_opt patterns-openSUSE-yast2_basis
patterns-openSUSE-yast2_install_wf perl-WWW-Curl
phonon-backend-gstreamer-0_10 plotutils pm-utils polkit polkit-gnome
postfix pstoedit pulseaudio pulseaudio-esound-compat
pulseaudio-module-bluetooth pulseaudio-module-gconf
pulseaudio-module-jack pulseaudio-module-lirc pulseaudio-module-x11
pulseaudio-module-zeroconf pulseaudio-utils pwdutils
python-gnomekeyring python-smbc qt4-qtscript redland rpcbind rsyslog
rtkit samba samba-client seahorse seahorse-daemon smartmontools
snapper-zypp-plugin soprano soprano-backend-redland
soprano-backend-virtuoso sox speech-dispatcher
speech-dispatcher-module-espeak splashy splashy-branding-openSUSE
strigi subversion subversion-perl sudo suseRegister suspend
sysconfig syslog-ng syslog-service system-config-printer
system-config-printer-applet system-config-printer-common
system-config-printer-dbus-service systemd
systemd-presets-branding-openSUSE systemd-sysvinit telepathy-gabble
telepathy-idle telepathy-mission-control telepathy-salut
telepathy-sofiasip telnet tightvnc tmpwatch totem
totem-browser-plugin totem-browser-plugin-gmp totem-plugins transfig
transmission transmission-common udev udev-configure-printer udisks
update-desktop-files upower usbmuxd vim vim-base vim-data vino
virtuoso-server vorbis-tools wine wine-32bit wine-gecko
wpa_supplicant xchat xchat-perl xchat-tcl xinetd xkeyboard-config
xlockmore xorg-x11 xorg-x11-Xvnc xorg-x11-driver-input
xorg-x11-driver-video xorg-x11-driver-video-intel-legacy
xorg-x11-driver-video-nouveau xorg-x11-server xorg-x11-server-extra
xscreensaver-data xscreensaver-data-extra yast2 yast2-add-on
yast2-apparmor yast2-backup yast2-bootloader yast2-control-center
yast2-control-center-gnome yast2-control-center-qt yast2-country
yast2-dbus-client yast2-drbd yast2-fingerprint-reader yast2-firewall
yast2-gtk yast2-inetd yast2-inetd-doc yast2-installation yast2-irda
yast2-iscsi-client yast2-iscsi-server yast2-kerberos-client
yast2-ldap yast2-ldap-client yast2-mail yast2-metapackage-handler
yast2-mouse yast2-ncurses-pkg yast2-network yast2-nfs-client
yast2-nis-client yast2-ntp-client yast2-online-update
yast2-online-update-frontend yast2-packager yast2-pam
yast2-pkg-bindings yast2-printer yast2-qt yast2-qt-pkg yast2-restore
yast2-runlevel yast2-samba-client yast2-samba-server yast2-scanner
yast2-security yast2-slp yast2-snapper yast2-sound yast2-sshd
yast2-storage yast2-sudo yast2-support yast2-sysconfig
yast2-transfer yast2-tune yast2-tv yast2-update yast2-users yast2-vm
yelp ypbind yudit zypper
548 packages to remove.
After the operation, 2.0 GiB will be freed.
Continue? [y/n/?] (y):
Gerald
--
Dr. Gerald Pfeifer <gp(a)suse.com> || SUSE || Director Product Management
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
12 years, 11 months
Re: [opensuse-factory] openSUSE Leap's Next Major Version Number
by ianseeks
On Saturday, 22 April 2017 14:00:27 BST Richard Brown wrote:
> I don't think you thoroughly read the whole email given the last line asked
> responses to opensuse-project(a)opensuse.org, not factory ;)
I'm not on the opensuse-project list so i responded to the one posted to
tumbleweed. I'll have a read of the list and see if i have anything to
contribute.
> On 22 April 2017 at 14:53, ianseeks <bingmybong(a)btinternet.com> wrote:
> > On Saturday, 22 April 2017 12:37:48 BST Richard Brown wrote:
> >> Hi all,
> >>
> >> On behalf of the openSUSE Board and Leap Release Management I am
> >> pleased to announce the next version of openSUSE Leap after 42.3 will
> >> be:
> >>
> >> openSUSE Leap 15
> >
> > Oh dear.... This continual rebranding, renumbering and renaming only
> > causes
> > confusion, it looks like no-one knows what they are doing especially after
> > the big-sell of Leap and 42.
> > The same happened with the rebranding of KDE5 to Plasma when everyone
> > expects common sense to continue with KDE5 as its got so much history and
> > its logical to go from KDE4 to KDE5.
> >
> > I guess it keeps someone busy.
> >
> >> As with Leap 42.x, minor releases are expected annually for at least 3
> >> years, so you can expect a Leap 15.1 to follow, then 15.2 and onwards.
> >>
> >> Obviously this is quite a dramatic change from the current version
> >> number of 42.x, so I will explain what justifies this change in some
> >> detail below.
> >>
> >> First, some history. When we started openSUSE Leap, the version number
> >> was an issue that needed addressing. openSUSE at that time was at
> >> 13.2, but SUSE Linux Enterprise (SLE) was at 12 and heading towards 12
> >> SP1.
> >>
> >> As the main unique selling point of Leap compared to every other
> >> distribution is the fact it is based on SLE sources. We wanted to
> >> reflect that in the version number.
> >> This was particularly important when you consider that a major version
> >> in SLE really means something ("major architectural changes from the
> >> last version are introduced here") whereas minor versions/service
> >> packs have a very different message ("easy to upgrade to, no major
> >> workflow breaking changes"). Leap follows a similar philosophy, so we
> >> wanted a versioning scheme to reflect SLEs.
> >>
> >> But openSUSE had already had versions starting with 12, so we couldn't
> >> sync up with SLE. This is where 42.x came from. It gave us the
> >> opportunity to establish a relationship with SLE versions (SLE Version
> >> + 30 = Leap Version), reflect the major/minor nature of Leap releases,
> >> and avoid clashes with version numbers we'd already used.
> >> The choice of 42 doubled as a humorous nod to hitchhikers guide to the
> >> galaxy and the first version numbers of SuSE Linux and YaST (4.2 and
> >> 0.42 respectively).
> >>
> >> The plan was therefore for the next version of Leap to be 43 with it's
> >> release aligned with SLE 13, followed by Leap 43.1 (with SLE 13 SP1),
> >> Leap 43.2 (w. SP2), etc
> >>
> >> However, like all good plans, things change.
> >>
> >> SUSE have decided that their next version of SLE will be 15, not 13.
> >>
> >> Upon learning of SUSE's plans the Board and Leap release team have
> >> been considering our options.
> >> This included ignoring the changes to SLE and releasing Leap 43 as
> >> planned, at the cost of the link between SLE versions and Leap
> >> versions.
> >> 45 was also considered, as were some frankly hilarious ideas that made
> >> me worry about my own sanity and that of my fellow contributors.
> >>
> >> After considering the pros and cons of all the options however, the
> >> decision has been that Leap 15 will be our next version.
> >>
> >> SUSE's decision to skip SLE 13 and 14 gave us a perfect opportunity to
> >> sync up with SLE versions like we always wanted to originally with
> >> Leap. It's an opportunity we will not be able to take so easily a few
> >> years from now if we continued with Leaps current versioning.
> >>
> >> There are only a few packages in our distribution that reference the
> >> 42.x versioning, and they should be easily handled as part of a zypper
> >> dup, so we are not concerned about this decision impacting users
> >> upgrading.
> >>
> >> We are aware that this decision could be a minor annoyance for users
> >> of Leap with configuration management tools like saltstack and puppet,
> >> but the long term opportunity to simplify such configuration (by being
> >> able to treat SLE and Leap similarly) outweighed our desire to avoid a
> >> 'one-time' effort for people currently handling the overly complicated
> >> situation caused by Leap being at 42.x and SLE being at 12 SPx.
> >>
> >> Packagers should be able to look forward to an easier time of things
> >> as a result of this change. We intend to deprecate the
> >> 0%{leap_version} macro and simplify the current complex nest of
> >> suse_version and sle_versions that can make it very frustrating to
> >> build packages appropriately for Tumbleweed, Leap and SLE.
> >>
> >> 0%{suse_version} should continue to be available as a simple indicator
> >> of the major version of Leap & SLE for packagers (eg, 0%{suse_version}
> >> == 1500 is the expected value for SLE 15 and Leap 15 and all of their
> >> minor versions/service packs).
> >>
> >> 0%{sle_version} should remain as a more precise indicator when
> >> packagers need to handle specific versions of Leap and SLE (eg.
> >> 0%{sle_version} == 150000 is the expected value for SLE 15 & Leap 15,
> >> with 150100 being the expected value for SLE 15 SP1 & Leap 15.1)
> >>
> >> 0%{is_opensuse} will continue for those times when packagers need to
> >> distinguish between Leap and SLE even though they will now more
> >> closely share their versions.
> >>
> >> The above examples and what the future suse_version number will be for
> >> Tumbleweed is not yet final, so expect to see emails from ludwig in
> >> opensuse-factory(a)opensuse.org when they are set.
> >>
> >> Thanks to everyone involved in this so far, I'm looking forward to
> >> seeing what we make out of Leap 15, and even though I cross-posted
> >> this I would like to ask that any followup conversation is kept to the
> >> opensuse-project(a)opensuse.org thread.
> >>
> >> Regards,
> >>
> >> Richard Brown
> >> on behalf of the openSUSE Board
> >
> > --
> > opensuse:tumbleweed:20170419
> > Qt: 5.7.1
> > KDE Frameworks: 5.32.0
> > KDE Plasma: 5.9.4
> > kwin 5.9.4
> > kmail2 5.4.3
> > akonadiserver 5.4.3
> > Kernel: 4.10.9-1-default
> > Nouveau: 1.0.14_2.1
> >
> > --
> > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
> > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
--
opensuse:tumbleweed:20170419
Qt: 5.7.1
KDE Frameworks: 5.32.0
KDE Plasma: 5.9.4
kwin 5.9.4
kmail2 5.4.3
akonadiserver 5.4.3
Kernel: 4.10.9-1-default
Nouveau: 1.0.14_2.1
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
7 years, 7 months
Re: [opensuse-factory] Leap 15.1 Build 450.2 - user report
by Carlos E. R.
On 4/16/19 5:46 PM, Ancor Gonzalez Sosa wrote:
> On 4/16/19 3:25 PM, Neil Rickert wrote:
>> On 4/15/19 1:59 PM, Carlos E. R. wrote:
>>
>>> [...]>
>
> As I read it, Carlos' original mail points several things in the
> installation process that has changed for the worse. So I triggered an
> installation of 42.3 and 15.1 to compare some of those points, to see
> what can be fixed or worked-around.
Thanks.
The thing that worries me most is that the loading of the kernel took
seven minutes - I timed it. I don't remember in which version this
started to deteriorate, perhaps the kernel was simply smaller back then.
Yes, it is the BIOS that is used by Grub, I know.
>>> Activation of crypto mounts was impossible> > I wouldn't say "impossible" but it is a weak spot.> > For my recent
> installs, I have been writing down the UUID of the> encrypted partitions
> before starting, so that I could recognize them.> The use of UUID for
> identifying the partition is just a bad idea. UUIDs> are for machines;
> they are not for people.
> That can be fixed for 15.2, please report the bug in bugzilla so it can
> be tracked and prioritized.
Crypto partitions have no labels, unfortunately. They may have
partition-label in GPT disks, though, but I'm unsure if LUKS support them.
The thing to improve is to try the given password on all LUKS
filesystems found.
Ok, I'll write a bugzilla.
>
>>> IMO, some of the screens are not nice, they do not look professional,
>>> they look antique. The system role display, for instance. In the past
>>> these things were nicer.
>>
>> This did not bother me. Yes, it is less compact than for the 42.3 or
>> earlier installs, because there are more choices. But they were easy
>> enough to read and select.
>
> This is how it looked in 42.3
> http://paste.opensuse.org/view//44062587
>
> And this is how it looks in one of the early 15.1 beta
> http://paste.opensuse.org/view//24875858
>
> We can discuss which one looks "nicer" (I guess it's a matter of taste).
> But I believe there is no question about which one is more informative.
I should have taken a photo. This looks nice, but what I got was not so
nice; perhaps the proportions in my display were wrong.
>
>>> The expert partitioner has changed, and IMO it is not better. Huge display.
>
> What does "huge display" mean?
>
> Again, this is how it looked in 42.3
> http://paste.opensuse.org/view//99085952
>
> And this is how it looks in 15.1
> http://paste.opensuse.org/view//10725727
>
> What is so different or so huge in the general display? It looks very
> similar to me.
Except when one has perhaps fifty partitions and several disks, and the
default expands them all...
>
> And about "being not better", I can tell you the partitioner in 15.1
> contain less bugs than the version in 43.2 (that one was full of
> pitfalls). In addition, it can now directly format full disks, create
> software MD RAIDs on top of disks without partitions, create partitions
> within a software-defined MD RAID and many others combinations that were
> impossible in the past. It also makes possible to setup bcache devices.
> So from both reliability and functionality point of views, I would dare
> to say it IS better. ;-)
I have not tested all that, but I'm sure it is true :-)
It is the visual aspect, and that "settings" has fewer things that
perhaps 13.1 had. I miss choosing the default type of partition.
One question. Is it possible to set all system encrypted, without using
LVM? This is possible to do manually, but there was talk of including it
in YaST.
>
>> It took me a while to get used to this. But by now it seems to work
>> pretty well.
>
> Since the new one have many more options per each device, the buttons
> had to be rearranged a bit (remember the interface has to fit in small
> text-mode displays). Some operations take one more click now... that was
> the price of having more options to choose from. But in general we have
> tried to preserve the overall experience.
>
> And we are VERY open to constructive feedback about how to make it better.
>
>>> I could select "mount by Label" as default, but not say that I prefer
>>> ext4. This was possible in the past.
>>
>> I think you can do that if you click the "Guided" instead of "Expert
>> Partitioner".
>
> I don't think Carlos is talking about selecting Ext4 per EACH
> filesystem. Of course that can be done one by one in both the
> Partitioner and the Guided Setup.
>
> He is talking about going to "Settings" as a first step in the
> Partitioner. Then, all partitions created at a later point already has
> "ext4" preselected.
Right.
> Again, if you miss that, open a bug report. We can bring it back at some
> point (likely for SP2).
Ok, I will.
>>> Import mount points worked, once I found where it was and how it
>>> worked. And unclick "format system volumes". This is very dangerous!
>
> It's EXACTLY in the same place it was in 42.3. That can be checked in
> the previous comparison screenshots.
>
> And it works EXACTLY in the same way it used to work in 42.3. With
> "format system volumes" being preselected by default... exactly as it
> was in 42.3.
Maybe, but the way I remember was from 13.1 ;-)
In this design, I find it difficult to find it, because when going to
"disks" it disappears.
>
> Again, let's compare screenshots of 42.3...
> http://paste.opensuse.org/view//60097489
>
> and 15.1
> http://paste.opensuse.org/view//90586477
>
> One of the points that people disliked in 15.0 was that we had
> simplified that option too much. Now it works exactly as it always did.
> How it comes that classic behavior we have cloned 1:1 on popular demand
> is suddenly hard to find, hard to understand and dangerous?
I only said that I found it hard to find. I didn't say any of the
others, it worked well. I found the meaning of the "next" and
"previous" button not trivial.
>>> Import previous users did not default to import from the same partition
>>> as selected on partition import. And it appears not to import user groups.
>>
>> I think it imports from the most recently booted linux system. I'm not
>> sure if it is using file system time stamps, or something else. And
>> yes, it does not import groups.
>
> Another thing that has not changed. It has always imported from the most
> recently accessed Linux.
Wouldn't it make sense to import from the same partition that it
imported fstab from?
>
>>> Default was network manager; this is a desktop machine.
>>
>> There's a place you can click to switch to "wicked", though I have not
>> tried that. If you select "Generic desktop" (or whatever it is called)
>> you get "wicked" and "Icewm".
>
> Yes, that default was changed after some discussions in the mailing
> lists. To make the change less painful an option to go back to wicked
> with a single click was added in the installation summary screen.
Ok.
>>> The installation setting display lacks a view of the affected
>>> partitions, for one last check before proceeding with installation.
>>
>> It's there, a choice near the bottom of the left column.
>
> If it's there I didn't find it. But again, this is NOT a change compared
> to Leap 42.3. That version didn't include the partitioning information
> in the installation summary either, as far as I can tell.
True.
>
>>> I did not notice where to select extra language :-?
>
> And where was that option in the past? It looks like another thing that
> has not changed since 42.3.
I don't remember, somewhere after choosing the timezone or in the
summary. I will try to find out, later.
>
> To be honest, I was a little bit worried reading the original mail to
> see some many things that has become worse than in the good old times.
> Now I feel much better after checking that most of those changes... had
> actually not changed anything if you really compare 42.3 and 15.1
> installation side by side.
Most of the things I mentioned are not that important, only details.
Thanks for looking and commenting.
--
Cheers / Saludos,
Carlos E. R.
(from openSUSE, Leap 15.1 x86_64 (ssd-test))
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
5 years, 7 months
[opensuse-factory] New Tumbleweed snapshot 20180524 released!
by Dominique Leuenberger
Please note that this mail was generated by a script.
The described changes are computed based on the x86_64 DVD.
The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading:
https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio…
When you reply to report some issues, make sure to change the subject.
It is not helpful to keep the release announcement subject in a thread
while discussing a specific problem.
Packages changed:
kernel-source (4.16.10 -> 4.16.11)
=== Details ===
==== kernel-source ====
Version update (4.16.10 -> 4.16.11)
Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms
- Linux 4.16.11 (bnc#1012628).
- xhci: Fix USB3 NULL pointer dereference at logical disconnect
(bnc#1012628).
- usbip: usbip_host: refine probe and disconnect debug msgs to
be useful (bnc#1012628).
- usbip: usbip_host: delete device from busid_table after rebind
(bnc#1012628).
- usbip: usbip_host: run rebind from exit when module is removed
(bnc#1012628).
- usbip: usbip_host: fix NULL-ptr deref and use-after-free errors
(bnc#1012628).
- usbip: usbip_host: fix bad unlock balance during stub_probe()
(bnc#1012628).
- ALSA: usb: mixer: volume quirk for CM102-A+/102S+ (bnc#1012628).
- ALSA: hda/realtek - Clevo P950ER ALC1220 Fixup (bnc#1012628).
- ALSA: hda: Add Lenovo C50 All in one to the power_save blacklist
(bnc#1012628).
- ALSA: control: fix a redundant-copy issue (bnc#1012628).
- spi: pxa2xx: Allow 64-bit DMA (bnc#1012628).
- spi: bcm-qspi: Avoid setting MSPI_CDRAM_PCS for spi-nor master
(bnc#1012628).
- spi: bcm-qspi: Always read and set BSPI_MAST_N_BOOT_CTRL
(bnc#1012628).
- KVM: vmx: update sec exec controls for UMIP iff emulating UMIP
(bnc#1012628).
- KVM: arm/arm64: Properly protect VGIC locks from IRQs
(bnc#1012628).
- KVM: arm/arm64: VGIC/ITS: Promote irq_lock() in update_affinity
(bnc#1012628).
- KVM: arm/arm64: VGIC/ITS save/restore: protect kvm_read_guest()
calls (bnc#1012628).
- KVM: arm/arm64: VGIC/ITS: protect kvm_read_guest() calls with
SRCU lock (bnc#1012628).
- hwmon: (k10temp) Fix reading critical temperature register
(bnc#1012628).
- hwmon: (k10temp) Use API function to access System Management
Network (bnc#1012628).
- vfio: ccw: fix cleanup if cp_prefetch fails (bnc#1012628).
- tracing/x86/xen: Remove zero data size trace events
trace_xen_mmu_flush_tlb{_all} (bnc#1012628).
- vsprintf: Replace memory barrier with static_key for
random_ptr_key update (bnc#1012628).
- x86/amd_nb: Add support for Raven Ridge CPUs (bnc#1012628).
- tee: shm: fix use-after-free via temporarily dropped reference
(bnc#1012628).
- netfilter: nf_tables: free set name in error path (bnc#1012628).
- netfilter: nf_tables: can't fail after linking rule into active
rule list (bnc#1012628).
- netfilter: nf_tables: nf_tables_obj_lookup_byhandle() can be
static (bnc#1012628).
- ARM64: dts: marvell: armada-cp110: Add clocks for the xmdio node
(bnc#1012628).
- ARM64: dts: marvell: armada-cp110: Add mg_core_clk for ethernet
node (bnc#1012628).
- i2c: designware: fix poll-after-enable regression (bnc#1012628).
- mtd: rawnand: marvell: Fix read logic for layouts with ->nchunks
> 2 (bnc#1012628).
- powerpc/powernv: Fix NVRAM sleep in invalid context when
crashing (bnc#1012628).
- drm: Match sysfs name in link removal to link creation
(bnc#1012628).
- cpufreq: armada-37xx: driver relies on cpufreq-dt (bnc#1012628).
- lib/test_bitmap.c: fix bitmap optimisation tests to report
errors correctly (bnc#1012628).
- radix tree: fix multi-order iteration race (bnc#1012628).
- mm: don't allow deferred pages with NEED_PER_CPU_KM
(bnc#1012628).
- drm/i915/gen9: Add WaClearHIZ_WM_CHICKEN3 for bxt and glk
(bnc#1012628).
- s390/qdio: fix access to uninitialized qdio_q fields
(bnc#1012628).
- s390/cpum_sf: ensure sample frequency of perf event attributes
is non-zero (bnc#1012628).
- s390/qdio: don't release memory in qdio_setup_irq()
(bnc#1012628).
- s390: remove indirect branch from do_softirq_own_stack
(bnc#1012628).
- bcache: return 0 from bch_debug_init() if CONFIG_DEBUG_FS=n
(bnc#1012628).
- x86/pkeys: Override pkey when moving away from PROT_EXEC
(bnc#1012628).
- x86/pkeys: Do not special case protection key 0 (bnc#1012628).
- efi: Avoid potential crashes, fix the 'struct
efi_pci_io_protocol_32' definition for mixed mode (bnc#1012628).
- ARM: 8771/1: kprobes: Prohibit kprobes on do_undefinstr
(bnc#1012628).
- x86/apic/x2apic: Initialize cluster ID properly (bnc#1012628).
- x86/mm: Drop TS_COMPAT on 64-bit exec() syscall (bnc#1012628).
- tick/broadcast: Use for_each_cpu() specially on UP kernels
(bnc#1012628).
- ARM: 8769/1: kprobes: Fix to use get_kprobe_ctlblk after
irq-disabed (bnc#1012628).
- ARM: 8770/1: kprobes: Prohibit probing on optimized_callback
(bnc#1012628).
- ARM: 8772/1: kprobes: Prohibit kprobes on get_user functions
(bnc#1012628).
- Btrfs: fix xattr loss after power failure (bnc#1012628).
- Btrfs: send, fix invalid access to commit roots due to
concurrent snapshotting (bnc#1012628).
- btrfs: property: Set incompat flag if lzo/zstd compression is
set (bnc#1012628).
- btrfs: fix crash when trying to resume balance without the
resume flag (bnc#1012628).
- btrfs: Split btrfs_del_delalloc_inode into 2 functions
(bnc#1012628).
- btrfs: Fix delalloc inodes invalidation during transaction abort
(bnc#1012628).
- btrfs: fix reading stale metadata blocks after degraded raid1
mounts (bnc#1012628).
- x86/nospec: Simplify alternative_msr_write() (bnc#1012628).
- x86/bugs: Concentrate bug detection into a separate function
(bnc#1012628).
- x86/bugs: Concentrate bug reporting into a separate function
(bnc#1012628).
- x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved
bits (bnc#1012628).
- x86/bugs, KVM: Support the combination of guest and host IBRS
(bnc#1012628).
- x86/bugs: Expose /sys/../spec_store_bypass (bnc#1012628).
- x86/cpufeatures: Add X86_FEATURE_RDS (bnc#1012628).
- x86/bugs: Provide boot parameters for the
spec_store_bypass_disable mitigation (bnc#1012628).
- x86/bugs/intel: Set proper CPU features and setup RDS
(bnc#1012628).
- x86/bugs: Whitelist allowed SPEC_CTRL MSR values (bnc#1012628).
- x86/bugs/AMD: Add support to disable RDS on Fam[15,16,17]h if
requested (bnc#1012628).
- x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest (bnc#1012628).
- x86/speculation: Create spec-ctrl.h to avoid include hell
(bnc#1012628).
- prctl: Add speculation control prctls (bnc#1012628).
- x86/process: Allow runtime control of Speculative Store Bypass
(bnc#1012628).
- x86/speculation: Add prctl for Speculative Store Bypass
mitigation (bnc#1012628).
- nospec: Allow getting/setting on non-current task (bnc#1012628).
- proc: Provide details on speculation flaw mitigations
(bnc#1012628).
- seccomp: Enable speculation flaw mitigations (bnc#1012628).
- x86/bugs: Make boot modes __ro_after_init (bnc#1012628).
- prctl: Add force disable speculation (bnc#1012628).
- seccomp: Use PR_SPEC_FORCE_DISABLE (bnc#1012628).
- seccomp: Add filter flag to opt-out of SSB mitigation
(bnc#1012628).
- seccomp: Move speculation migitation control to arch code
(bnc#1012628).
- x86/speculation: Make "seccomp" the default mode for Speculative
Store Bypass (bnc#1012628).
- x86/bugs: Rename _RDS to _SSBD (bnc#1012628).
- proc: Use underscores for SSBD in 'status' (bnc#1012628).
- Documentation/spec_ctrl: Do some minor cleanups (bnc#1012628).
- x86/bugs: Fix __ssb_select_mitigation() return type
(bnc#1012628).
- x86/bugs: Make cpu_show_common() static (bnc#1012628).
- x86/bugs: Fix the parameters alignment and missing void
(bnc#1012628).
- x86/cpu: Make alternative_msr_write work for 32-bit code
(bnc#1012628).
- KVM: SVM: Move spec control call after restore of GS
(bnc#1012628).
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
(bnc#1012628).
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
(bnc#1012628).
- x86/cpufeatures: Disentangle SSBD enumeration (bnc#1012628).
- x86/cpufeatures: Add FEATURE_ZEN (bnc#1012628).
- x86/speculation: Handle HT correctly on AMD (bnc#1012628).
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
(bnc#1012628).
- x86/speculation: Add virtualized speculative store bypass
disable support (bnc#1012628).
- x86/speculation: Rework speculative_store_bypass_update()
(bnc#1012628).
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
(bnc#1012628).
- x86/bugs: Expose x86_spec_ctrl_base directly (bnc#1012628).
- x86/bugs: Remove x86_spec_ctrl_set() (bnc#1012628).
- x86/bugs: Rework spec_ctrl base and mask logic (bnc#1012628).
- x86/speculation, KVM: Implement support for
VIRT_SPEC_CTRL/LS_CFG (bnc#1012628).
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
(bnc#1012628).
- x86/bugs: Rename SSBD_NO to SSB_NO (bnc#1012628).
- bpf: Prevent memory disambiguation attack (bnc#1012628).
- Refresh
patches.suse/0001-x86-speculation-Add-basic-IBRS-support-infrastructur.patch.
- Refresh
patches.suse/0002-x86-speculation-Add-inlines-to-control-Indirect-Bran.patch.
- commit f86282c
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
6 years, 5 months
[opensuse-factory] New Tumbleweed snapshot 20180517 released!
by Dominique Leuenberger
Please note that this mail was generated by a script.
The described changes are computed based on the x86_64 DVD.
The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading:
https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio…
When you reply to report some issues, make sure to change the subject.
It is not helpful to keep the release announcement subject in a thread
while discussing a specific problem.
Packages changed:
aria2 (1.33.1 -> 1.34.0)
bzr
freetype2 (2.9 -> 2.9.1)
ft2demos (2.9 -> 2.9.1)
libstorage-ng (3.3.272 -> 3.3.283)
libwmf
libyui (3.4.0 -> 3.4.1)
libyui-qt (2.49.3 -> 2.49.4)
patterns-yast (20180409 -> 20180427)
sblim-sfcb
yast2 (4.0.73 -> 4.0.74)
yast2-bootloader (4.0.32 -> 4.0.34)
yast2-control-center (4.0.2 -> 4.1.0)
yast2-country (4.0.20 -> 4.0.22)
yast2-installation (4.0.59 -> 4.0.60)
yast2-packager (4.0.60 -> 4.0.62)
yast2-pkg-bindings (4.0.9 -> 4.0.10)
yast2-storage-ng (4.0.179 -> 4.0.183)
yast2-trans (84.87.20180508.cec5a7a09 -> 84.87.20180514.157a0650d)
=== Details ===
==== aria2 ====
Version update (1.33.1 -> 1.34.0)
Subpackages: aria2-lang libaria2-0
- Update to version 1.34.0
* UnknownLengthPieceStorage: return piece length show something
in console status when downloading items with unknown content length
* Fix bug that signal handler does not work with libaria2 when
aria2::RUN_ONCE is passed to aria2::run().
* Retry on HTTP 502
- cleanup with spec-cleaner
==== bzr ====
Subpackages: bzr-lang
- Add bzr-2.7.0-ssh_hostnames-lp1710979 to avoid code execution
(boo#1058214, CVE-2017-14176)
==== freetype2 ====
Version update (2.9 -> 2.9.1)
Subpackages: freetype2-devel libfreetype6 libfreetype6-32bit
- Re-enable freetype-config, there is just too many fallouts.
- Update to version 2.9.1
* Type 1 fonts containing flex features were not rendered
correctly (bug introduced in version 2.9).
* CVE-2018-6942: Older FreeType versions can crash with certain
malformed variation fonts.
* Bug fix: Multiple calls to `FT_Get_MM_Var' returned garbage.
* Emboldening of bitmaps didn't work correctly sometimes, showing
various artifacts (bug introduced in version 2.8.1).
* The auto-hinter script ranges have been updated for Unicode 11.
No support for new scripts have been added, however, with the
exception of Georgian Mtavruli.
- freetype-config is now deprecated by upstream and not enabled
by default.
- Drop upstreamed patches:
* bnc1079600.patch
* psaux-flex.patch
* 0001-src-truetype-ttinterp.c-Ins_GETVARIATION-Avoid-NULL-.patch
* 0001-truetype-Better-protection-against-invalid-VF-data.patch
==== ft2demos ====
Version update (2.9 -> 2.9.1)
Subpackages: ftbench ftdiff ftdump ftgamma ftgrid ftinspect ftlint ftmulti ftstring ftvalid ftview
- Update to version 2.9.1
* No changelog upstream.
==== libstorage-ng ====
Version update (3.3.272 -> 3.3.283)
Subpackages: libstorage-ng-ruby libstorage-ng1
- Translated using Weblate (Italian)
- 3.3.283
- Translated using Weblate (Czech)
- 3.3.282
- Translated using Weblate (Dutch)
- 3.3.281
- Translated using Weblate (Japanese)
- 3.3.280
- Translated using Weblate (Catalan)
- 3.3.279
- merge gh#openSUSE/libstorage-ng#528
- added action to fix undersized GPT
- updated pot file
- merged po files
- 3.3.278
- merge gh#openSUSE/libstorage-ng#527
- Use stricter NTFS max label size (bsc#1084867)
- 3.3.277
- Translated using Weblate (Hungarian)
- 3.3.276
- merge gh#openSUSE/libstorage-ng#526
- improved error message (see bsc#1089554)
- 3.3.275
- merge gh#openSUSE/libstorage-ng#525
- Fix lt translation
- 3.3.274
- Translated using Weblate (Chinese (Taiwan))
- Translated using Weblate (Korean)
- Translated using Weblate (Chinese (China))
- Translated using Weblate (Lithuanian)
- 3.3.273
==== libwmf ====
Subpackages: libwmf-0_2-7 libwmf-tools
- Add use-pkg-config-for-freetype.patch to use pkgconfig to detect
Freetype libraries. Add BR autoconf, automake, libtool due to
above.
==== libyui ====
Version update (3.4.0 -> 3.4.1)
- Fix GCC 8 warning: -Werror=catch-value (boo#1084636).
- 3.4.1
==== libyui-qt ====
Version update (2.49.3 -> 2.49.4)
- Fix Gnome's display of titles/icons (boo#1092845)
- 2.49.4
==== patterns-yast ====
Version update (20180409 -> 20180427)
Subpackages: patterns-yast-x11_yast patterns-yast-yast2_basis patterns-yast-yast2_install_wf
- move yast2-fonts in the x11_yast pattern as it pulls in freetype and stuff
related to it (boo#1090189)
- remove kde and gnome conflicts in x11_yast pattern (boo#1090319)
- version 20180427
==== sblim-sfcb ====
- service_init_certs.patch: Certificates should be generated at
runtime, not during installation. The script should also take
config file values for certification locations, in case it was
adjusted by the user. (bsc#1092281)
- missing_makefile_dependencies.patch: fix Makefile.am dependencies
==== yast2 ====
Version update (4.0.73 -> 4.0.74)
- Replace the deprecated firewallctl command with firewall-cmd for
obtaining the firewalld state (bsc#1093111)
- 4.0.74
==== yast2-bootloader ====
Version update (4.0.32 -> 4.0.34)
- Extend fix for BIOS RAIDs to work with more complex setup when
system contain also physical partitions (bsc#1092417)
- 4.0.34
- Propose fips boot parameter if it is used for installation
on s390 (bsc#1043029)
- 4.0.33
==== yast2-control-center ====
Version update (4.0.2 -> 4.1.0)
Subpackages: yast2-control-center-qt
- Fixed crash when reading an invalid or incomplete .desktop file
(bsc#1090843)
- 4.1.0
- Fix Gnome's display of titles/icons (boo#1092845)
- 4.0.3
==== yast2-country ====
Version update (4.0.20 -> 4.0.22)
Subpackages: yast2-country-data
- Do not use opensuse ntp pool servers for SLE (bsc#1090168)
- 4.0.22
- handle setting locale in firstboot (bsc#1092979)
- 4.0.21
==== yast2-installation ====
Version update (4.0.59 -> 4.0.60)
- Do not try to set read-only property to default BTRFS subvolume
if the filesystem already existed on disk (needed for
bsc#1091047).
- 4.0.60
==== yast2-packager ====
Version update (4.0.60 -> 4.0.62)
- Fixed argument handling in the .desktop file for the
"Install/Remove Software" item (bsc#1087352)
- Properly process paths containing spaces or special shell
characters
- 4.0.62
- Adapted /dev cleanup at upgrade to work properly with the
registration rollback (bsc#1089643)
- 4.0.61
==== yast2-pkg-bindings ====
Version update (4.0.9 -> 4.0.10)
- Ignore notification exception for failed plugin services,
avoid errors when refreshing the zypp-plugin-spacewalk service
on a system not managed by spacewalk (SUSE Manager)
(bsc#1086768)
- 4.0.10
==== yast2-storage-ng ====
Version update (4.0.179 -> 4.0.183)
- Added to the installer a detailed description about the origin of
the partitioning layout, as discussed in bsc#1089274.
- 4.0.183
- Allow to consider MD RAIDs as BIOS RAIDs by using the env
variable LIBSTORAGE_MDPART (bsc#1092417).
- Fixed tests to avoid to require files provided by
yast-installation package (needed for bsc#1091047).
- Fixed detection of candidate disks for installation
(bsc#1091047).
- 4.0.182
- don't reuse prep partitions larger than 8 MiB (bsc#1090019)
- 4.0.181
- Partitioner: fix several translation issues (bsc#1081837 and
bsc#1081601).
- Expose the active flag of the MountPoint class (needed for the
definitive fix for bsc#1064437 in modern distributions).
- 4.0.180
==== yast2-trans ====
Version update (84.87.20180508.cec5a7a09 -> 84.87.20180514.157a0650d)
Subpackages: yast2-trans-af yast2-trans-ar yast2-trans-bg yast2-trans-bn yast2-trans-bs yast2-trans-ca yast2-trans-cs yast2-trans-cy yast2-trans-da yast2-trans-de yast2-trans-el yast2-trans-en yast2-trans-en_GB yast2-trans-en_US yast2-trans-es yast2-trans-et yast2-trans-fa yast2-trans-fi yast2-trans-fr yast2-trans-gl yast2-trans-gu yast2-trans-hi yast2-trans-hr yast2-trans-hu yast2-trans-id yast2-trans-it yast2-trans-ja yast2-trans-jv yast2-trans-ka yast2-trans-km yast2-trans-ko yast2-trans-lo yast2-trans-lt yast2-trans-mk yast2-trans-mr yast2-trans-nb yast2-trans-nl yast2-trans-pa yast2-trans-pl yast2-trans-pt yast2-trans-pt_BR yast2-trans-ro yast2-trans-ru yast2-trans-si yast2-trans-sk yast2-trans-sl yast2-trans-sr yast2-trans-sv yast2-trans-ta yast2-trans-th yast2-trans-tr yast2-trans-uk yast2-trans-vi yast2-trans-wa yast2-trans-xh yast2-trans-zh_CN yast2-trans-zh_TW yast2-trans-zu
- Update to version 84.87.20180514.157a0650d:
* Add initial sap-installation-wizard files
* Add sap-installation-wizard textdomain
* Added translation using Weblate (Dutch)
* Added translation using Weblate (German)
* Added translation using Weblate (Japanese)
* Added translation using Weblate (Portuguese (Brazil))
* Fixed string interpolation
* New POT for text domain 'autoinst'.
* New POT for text domain 'bootloader'.
* New POT for text domain 'control'.
* New POT for text domain 'installation'.
* New POT for text domain 'storage'.
* Translated using Weblate (Catalan)
* Translated using Weblate (Chinese (China))
* Translated using Weblate (Chinese (Taiwan))
* Translated using Weblate (Czech)
* Translated using Weblate (Dutch)
* Translated using Weblate (French)
* Translated using Weblate (German)
* Translated using Weblate (Indonesian)
* Translated using Weblate (Italian)
* Translated using Weblate (Japanese)
* Translated using Weblate (Korean)
* Translated using Weblate (Lithuanian)
* Translated using Weblate (Polish)
* Translated using Weblate (Portuguese (Brazil))
* Translated using Weblate (Slovak)
* Update sap-installation-wizard po files
* Update sap-installation-wizard pot file
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
6 years, 6 months
[opensuse-factory] New Tumbleweed snapshot 20200813 released!
by Dominique Leuenberger
Please note that this mail was generated by a script.
The described changes are computed based on the x86_64 DVD.
The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading:
https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio…
Please do not reply to this email to report issues, rather file a bug
on bugzilla.opensuse.org. For more information on filing bugs please
see https://en.opensuse.org/openSUSE:Submitting_bug_reports
Packages changed:
libreoffice (7.0.0.0.beta2 -> 7.0.0.3)
libvirt (6.5.0 -> 6.6.0)
perl-Mojolicious (8.57 -> 8.58)
php7 (7.4.8 -> 7.4.9)
python-cffi (1.14.0 -> 1.14.1)
python-dnspython (1.16.0 -> 2.0.0)
python-libvirt-python (6.5.0 -> 6.6.0)
python-mysqlclient
python-pymongo (3.10.1 -> 3.11.0)
python-pysmbc (1.0.19 -> 1.0.22)
python-reno (3.0.1 -> 3.1.0)
samba
transactional-update (2.23 -> 2.24.1)
yast2-isns (4.2.0 -> 4.3.0)
=== Details ===
==== libreoffice ====
Version update (7.0.0.0.beta2 -> 7.0.0.3)
Subpackages: libreoffice-base libreoffice-base-drivers-firebird libreoffice-calc libreoffice-draw libreoffice-filters-optional libreoffice-gnome libreoffice-gtk3 libreoffice-icon-themes libreoffice-impress libreoffice-l10n-cs libreoffice-l10n-da libreoffice-l10n-de libreoffice-l10n-el libreoffice-l10n-en libreoffice-l10n-en_GB libreoffice-l10n-es libreoffice-l10n-fr libreoffice-l10n-hu libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-pl libreoffice-l10n-pt_BR libreoffice-l10n-ru libreoffice-l10n-zh_CN libreoffice-l10n-zh_TW libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-qt5 libreoffice-writer libreofficekit
- Update to 7.0.0.3:
* Final stable release for 7.0.0 version
- Update to 7.0.0.2:
* RC2 7.0 series update
- Update to 7.0.0.1:
* RC1 7.0 series containing many additional fixes
- Remove merged patches:
* libreoffice-clipped-sidebar-paragraph-widget.patch
* libreoffice-select-correct-item-in-gallery.patch
* libreoffice-stuck-widgets-in-sidebar.patch
* pyuno-nopwd.patch
* poppler-0.86.patch
- Also contains fixes for bsc#1155141 and bsc#1136234
==== libvirt ====
Version update (6.5.0 -> 6.6.0)
Subpackages: libvirt-bash-completion libvirt-client libvirt-daemon libvirt-daemon-driver-interface libvirt-daemon-driver-libxl libvirt-daemon-driver-lxc libvirt-daemon-driver-network libvirt-daemon-driver-nodedev libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu libvirt-daemon-driver-secret libvirt-daemon-driver-storage libvirt-daemon-driver-storage-core libvirt-daemon-driver-storage-disk libvirt-daemon-driver-storage-gluster libvirt-daemon-driver-storage-iscsi libvirt-daemon-driver-storage-iscsi-direct libvirt-daemon-driver-storage-logical libvirt-daemon-driver-storage-mpath libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-scsi libvirt-daemon-lxc libvirt-daemon-qemu libvirt-daemon-xen libvirt-libs
- Update to libvirt 6.6.0
- CVE-2020-14339
- Many incremental improvements and bug fixes, see
https://libvirt.org/news.html
==== perl-Mojolicious ====
Version update (8.57 -> 8.58)
- updated to 8.58
see /usr/share/doc/packages/perl-Mojolicious/Changes
8.58 2020-08-05
- Improved app and lite_app generators to use templates with subroutine signatures.
- Updated all documentation to use subroutine signatures. (kiwiroy)
==== php7 ====
Version update (7.4.8 -> 7.4.9)
Subpackages: apache2-mod_php7 php7-ctype php7-dom php7-gd php7-gettext php7-iconv php7-json php7-mbstring php7-mysql php7-pdo php7-sqlite php7-tokenizer php7-xmlreader php7-xmlwriter
- updated to 7.4.9: This is a security release which also contains
several bug fixes. See https://www.php.net/ChangeLog-7.php#7.4.9
==== python-cffi ====
Version update (1.14.0 -> 1.14.1)
- update to 1.14.1:
* CFFI source code is now hosted on Heptapod.
* Improved support for typedef int my_array_t[...]; with an explicit dot-dot-dot in API mode (issue #453)
* Windows (32 and 64 bits): multiple fixes for ABI-mode call to functions that return a structure.
* Experimental support for MacOS 11 on aarch64.
* and a few other minor changes and bug fixes.
==== python-dnspython ====
Version update (1.16.0 -> 2.0.0)
- Disable four tests which fail on openssl 1.1.0i and lower
- Add missing dependency requests-toolkit, and recommend
cryptography
- remove test depending on trio, which depends on Python 3.7 if python >= 3.7 is not available.
- update to 2.0.0:
- Python 3.6 or newer is required.
- The license is now the ISC license.
- Rdata is now immutable. Use dns.rdata.Rdata.replace() to make a new Rdata based on an existing one.
- dns.resolver.resolve() has been added, allowing control of whether search lists are used. dns.resolver.query() is retained for backwards compatibility, but deprecated. The default for search list behavior can be set at in the resolver object with the use_search_by_default parameter. The default is False.
- DNS-over-TLS is supported with dns.query.tls().
- DNS-over-HTTPS is supported with dns.query.https(), and the resolver will use DNS-over-HTTPS for a nameserver which is an HTTPS URL.
- Basic query and resolver support for the Trio, Curio, and asyncio asynchronous I/O libraries has been added in dns.asyncquery and dns.asyncresolver. This API should be viewed as experimental as asynchronous I/O support in dnspython is still evolving.
- TSIG now defaults to using SHA-256.
- Basic type info has been added to some functions. Future releases will have comprehensive type info.
- from_text() functions now have a relativize_to parameter.
- python-cryptography is now used for DNSSEC.
- Ed25519 and Ed448 signatures are now supported.
- A helper for NSEC3 generating hashes has been added.
- SHA384 DS records are supported.
- Rdatasets and RRsets are much faster.
- dns.resolver.resolve_address() has been added, allowing easy address-to-name lookups.
- dns.reversename functions now allow an alternate origin to be specified.
- The repr form of Rdatasets and RRsets now includes the rdata.
- A number of standard resolv.conf options are now parsed.
- The nameserver and port used to get a response are now part of the resolver?s Answer object.
- The NINFO record is supported.
- The dns.hash module has been removed; just use Python?s native hashlib module.
- Rounding is done in the standard python 3 fashion; dnspython 1.x rounded in the python 2 style on both python 2 and 3.
- The resolver will now do negative caching if a cache has been configured.
- TSIG and OPT now have rdata types.
- The class for query messages is now QueryMessage. Class Message is now a base class, and is also used for messages for which we don?t have a better class. Update messages are now class UpdateMessage, though class Update is retained for compatibility.
- Support for Windows 95, 98, and ME has been removed.
==== python-libvirt-python ====
Version update (6.5.0 -> 6.6.0)
- Update to 6.6.0
- Add all new APIs and constants in libvirt 6.6.0
==== python-mysqlclient ====
- do mysql shutdown even if testsuite fails, exit 1 afterwards
==== python-pymongo ====
Version update (3.10.1 -> 3.11.0)
- update to 3.11.0:
* Version 3.11 adds support for MongoDB 4.4 and includes a number of bug fixes.
* Support for OCSP (Online Certificate Status Protocol).
* Support for PyOpenSSL as an alternative TLS implementation.
* Support for the MONGODB-AWS authentication mechanism.
* Support for the directConnection URI option and kwarg to MongoClient.
* Support for speculative authentication attempts in connection handshakes which reduces the number of network roundtrips needed to authenticate new connections on MongoDB 4.4+.
* Support for creating collections in multi-document transactions with create_collection() on MongoDB 4.4+.
* Added index hinting support to the ReplaceOne, UpdateOne, UpdateMany, DeleteOne, and DeleteMany bulk operations.
* Added support for bson.binary.UuidRepresentation.UNSPECIFIED and MongoClient(uuidRepresentation='unspecified') which will become the default UUID representation starting in PyMongo 4.0. See Handling UUID Data for details.
* Added the background parameter to pymongo.database.Database.validate_collection(). For a description of this parameter see the MongoDB documentation for the validate command.
* Added the allow_disk_use parameters to pymongo.collection.Collection.find().
* Added the hedge parameter to PrimaryPreferred, Secondary, SecondaryPreferred, Nearest to support disabling (or explicitly enabling) hedged reads in MongoDB 4.4+.
==== python-pysmbc ====
Version update (1.0.19 -> 1.0.22)
- update to 1.0.22
* Add File_seekable #52
* Rework some routines to fix holes in error checking #50
* Fix File_read when the current location is not zero #49
* Add File_flush #48
* Add File_tell #47
* Added SAMBA protocol version optional variable #41
==== python-reno ====
Version update (3.0.1 -> 3.1.0)
- update 3.1.0
* Set parallel\_read\_safe to True
* Handle empty config files
* Add cache support for release dates
* Remove future imports
* Keep scanning master branch after first shared commit
* Sort config options
* Add support for release dates
* sphinxext: Support rootdir discovery without git
* Use unittest.mock instead of third party mock
* tox: Suppress output
* do not include external svgs from readme in docs
* Update hacking for Python3
==== samba ====
Subpackages: libdcerpc-binding0 libdcerpc-binding0-32bit libdcerpc0 libdcerpc0-32bit libndr-krb5pac0 libndr-krb5pac0-32bit libndr-nbt0 libndr-nbt0-32bit libndr-standard0 libndr-standard0-32bit libndr1 libndr1-32bit libnetapi0 libnetapi0-32bit libsamba-credentials0 libsamba-credentials0-32bit libsamba-errors0 libsamba-errors0-32bit libsamba-hostconfig0 libsamba-hostconfig0-32bit libsamba-passdb0 libsamba-passdb0-32bit libsamba-policy0-python3 libsamba-util0 libsamba-util0-32bit libsamdb0 libsamdb0-32bit libsmbclient0 libsmbconf0 libsmbconf0-32bit libsmbldap2 libsmbldap2-32bit libtevent-util0 libtevent-util0-32bit libwbclient0 libwbclient0-32bit samba-client samba-client-32bit samba-doc samba-libs samba-libs-32bit samba-libs-python3 samba-python3 samba-winbind samba-winbind-32bit
- Don't install SuSEfirewall2 services, we don't have that package
anymore
==== transactional-update ====
Version update (2.23 -> 2.24.1)
Subpackages: transactional-update-zypp-config
- Version 2.24.1
- SELinux: adjust labels for etc, fstab and grub.cfg
- Version 2.24
- Add partial SELinux support
==== yast2-isns ====
Version update (4.2.0 -> 4.3.0)
- AutoYaST: Added supplements: autoyast(isns) into the spec file
in order to install this packages if the section has been defined
in the AY configuration file (bsc#1146494).
- 4.3.0
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
4 years, 3 months
Re: [opensuse-factory] Kernel Mode Setting (KMS) for openSUSE.
by Ken Schneider - Factory
On 12/03/2009 08:38 AM, Egbert Eich pecked at the keyboard and wrote:
>
> Folks -
>
> In yesterday's discussion about the future of SaX2 it has been requested
> that changes that will affect users in the future are communicated to
> the openSUSE community early. KMS (kernel mode setting) integration would
> be such a feature, thus I would like to announce this here and
> one step further dive into a technical discussion about a possible
> solution.
> Furthermore test packages are available to try things out on Factory.
> I would like to encourage people interested in development and technical
> discussions in general to participate in the discussion and the development
> efforts.
>
>
> Kernel Modesetting (KMS)
> ========================
>
> All of you who are using a graphical desktop on Linux have been using
> the X Window Sytem.
> The X Window System Server (XServer) is the instance which receives
> requests from your desktop applications to draw all the widgets (windows,
> buttons, images etc.) you see on your desktop. It also processes input
> from your keyboard and mouse and sends them to applications as events.
> Traditionally on Linux the XServer does not only draw images to the screen
> (ie writes them to some sort of frame buffer) but it is in charge of
> initializing, setting up and driving the graphics hardware.
>
> This paradigm which has been true since the X Window System has been
> ported to Linux is about to change: Much of the initialization, set up
> (video mode setting) and control of the graphics hardware is about to
> move to the Linux kernel.
>
> There are a number of advantages to this:
> - A central instance is in charge of the graphics hardware, other
> user mode applications (not just the Xserver) can take advantage of mode
> setting.
> - The Xserver will no longer require full root privileges as it doesn't
> talk to the hardware directly any more.
> - Faster boot process: The Xserver doesn't need to (re)initialize the graphics
> hardware any more, this is all done by the kernel very early in the boot
> cycle.
> - Smoother (flicker free) boot experience: The screen doesn't flicker and
> changes resolution any more when the Xserver starts.
> - One central entity is in charge and manages the resources of the graphics
> hardware - like the video memory which makes sharing of these resources
> between several applications (like Xserver and several DRI (Direct Rendering
> 3D) applications much easier.
>
> KMS is integrated in the DRM drivers.
> In the near future most graphics driver will switch to KMS:
> - Intel already ships a fully working KMS driver. Future Intel chipsets will
> be supported by the KMS driver only.
> - KMS in the Radeon DRM driver is still work in progress but it is already
> working well on some chipsets.
> - Noveau is relying heavily on KMS for their free 3D driver for NVIDIA
> chipsets.
> The proprietary ATI and NVIDIA drivers are unlikely to switch to KMS in the
> near future.
>
>
> Integration in openSUSE
> =======================
> Now this begs the question what we have to do to integrate it into openSUSE.
> Originall I had plans to look into this for openSUSE 11.2 already - but then
> I got side tracked by other stuff it fell on the floor and noone else beat me
> to it either ... oh well.
> Now I had the chance to play around with KMS a little and came up with some
> ideas and a proof of concept.
> It turned out that the changes to openSUSE needed to fully support KMS are
> quite small. Key is to load the KMS aware DRM driver as early as possible in
> the boot process to avoid video mode changes later in the boot cycle -
> preferrably in the initrd.
>
> The Boot Process
> ----------------
>
> On openSUSE the boot loader is configured for two boot scenarios: default
> and failsafe. The user can select the failsafe boot scenario in case the
> default scenario does not work for him. In the failsafe scenario certain
> features are deactivated which have shown to cause problems on some systems.
>
> Since KMS is a new feature it is a candidate for deactivation during a
> failsafe boot. Instead the system should then boot into the VESA framebuffer
> mode. Should this also fail the kernel will automatically fall back to a VGA
> text mode.
> To disable KMS on boot a new boot parameter is introduced: 'nomodeset'.
> This parameter is to the boot command line for the failsafe mode.
> The user may add this parameter by hand for any other boot mode.
>
> The kernel command line is parsed in initrd and an appropriate
> entry is created in /etc/modprobe.d/options. Furthermore the graphics
> driver module and - if required - the agp module(s) are added in the
> correct order (agp modules first) to the list of modules to be loaded
> initially.
>
> Changes to individual packages
> ==============================
>
> 1. yast2-bootloader & perl-Bootloader
> -------------------------------------
> The boot parameter 'nomodeset' is added to the failsafe boot
> paramter lists in each of the modules. (I have not been able
> to find out which module provides the entry relevant for which
> situation, therefore I've whacked both.)
> yast2-bootloader updates the variable FAILSAFE_APPEND in
> /etc/sysconfig/bootloader appropriately.
>
> 2. kernel-source
> ----------------
>
> To use KMS for a certain DRM driver the kernel config option
> CONFIG_DRM_<driver_name>_KMS needs to be set to 'y'.
> At the moment we will support KMS only for Intel hardware,
> thus only the variable CONFIG_DRM_I915_KMS needs to be changed.
>
> In the sample build this has been enabled for the -default,
> -desktop, -pae, -debug, -trace and -vanilla kernels for the
> i386 and x86_64 platforms.
>
> The kernel boot splash has already been fixed for KMS for
> openSUSE 11.2.
>
> 3. mkinitrd
> -----------
>
> This package writes the initrd file. To add KMS support to the initrd
> mkinitrd needs to perform the following tasks:
>
> 1. Check the sysconfig variable NO_KMS_IN_INITRD, if set, don't attempt to
> install a KMS DRM capable driver.
>
> 2. Obtain a list of PCI devices installed on the system.
>
> 3. a. In the list of PCI devices identify those devices which are of class VGA
> and look for a matching driver. b. Before a driver is matched check the
> PCI vendor, device, subvendor and
> subdevice ids against a blacklist in /etc/kms/blacklist should this file
> exist. This file contains one vendor, device, subvendor and subdevice
> id per line, '*' serves as a wildchar, trailing wildchars may be
> ommitted, '#' at the beginning of a line serves as a comment.
> c. Use the standard modprobe alias mechanism to find a matching DRM driver
> module. This way standard blacklistings of kernel modules will be
> honored and update modules will be searched if they are available. KMS
> capable DRM drivers provide an alias list (in contrast to non-KMS
> capable DRM drivers which are to be loaded explicitely by the Xserver).
> d. If a driver is found check for a black listing in
> /etc/kms/<driver_name>.blacklist. The same rules as in 3 b. apply.
>
> 4. If a KMS capable DRM driver is found search for an agp driver:
> a. Obtain a list of all known agp drivers for the specific kernel
> and collect their alias lists.
> b. Match all installed PCI devices against the alias lists of each
> agp driver. If a match is found add the driver to the lists of modules
> to be loaded. Make sure that this driver is loaded prior the the DRM
> driver.
>
> Two scripts setup-kms.sh and boot-kms.sh are added to mkinitrd.
> The former performs the tasks listed above, the latter provides the
> required module dependencies in the required order, parses the boot
> command line for the 'nomodeset' option and adds the apropriate entry to
> /etc/modprobe.d/options.
> The linuxrc script is extended to search the boot command line for
> <drivername>.<option>=* strings for each driver loaded in initrd and add
> the <option>=* part to /etc/modprobe.d/options.
>
> 4. udev
> -------
>
> Udev loads any modules which are not loaded by linuxrc scripts directly.
> It is possible to let udev load the required DRM and AGP modules provided
> it is made sure that this happens in the correct order. Since there is
> no explicit dependency of DRM modules to AGP drivers as there is no general
> one to one match between the two drivers a udev rule must exist to enforce
> the correct order for all cases where a AGP module is required.
> This is true for Intel DRM drivers and any other driver for an AGP graphics
> chip.
> For this a rule file 79-waitfor-agp.rules is added which is run before
> 80-drivers.rules. It checks if either an Intel graphics (class VGA) device
> is processed or if the graphics device is an AGP device. The latter condition
> is tested by an auxiliary tool (is_agp) which is passed the kernel name of
> the event device. If either condition is true udev will wait for /dev/agpgart
> to appear before proceeding to load a DRM driver module.
> 'is_agp' checks the capabilities flags in the PCI config space of this device
> for AGP.
I keep seeing reference to "DRM" here. Is that referring to Digital
Rights Management? If not, the acronym needs to be changed.
--
Ken Schneider
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
14 years, 11 months
Re: [opensuse-factory] M1 problem with backlisting nouveau
by Sid Boyce
On 12/06/11 18:21, Roelof Wobben wrote:
>
>
> ----------------------------------------
>> Date: Sun, 12 Jun 2011 17:27:35 +0100
>> Subject: Re: [opensuse-factory] M1 problem with backlisting nouveau
>> From: alinm.elena(a)gmail.com
>> To: rwobben(a)hotmail.com
>> CC: opensuse-factory(a)opensuse.org
>>
>> On 12 June 2011 17:21, Roelof Wobben wrote:
>>>
>>>
>>> ----------------------------------------
>>>> Date: Sun, 12 Jun 2011 15:49:01 +0100
>>>> From: sboyce(a)blueyonder.co.uk
>>>> To: opensuse-factory(a)opensuse.org
>>>> Subject: Re: [opensuse-factory] M1 problem with backlisting nouveau
>>>>
>>>> On 12/06/11 15:27, Roelof Wobben wrote:
>>>>>
>>>>>> Date: Sun, 12 Jun 2011 15:32:18 +0200
>>>>>> From: bruno(a)ioda-net.ch
>>>>>> To: opensuse-factory(a)opensuse.org
>>>>>> Subject: Re: [opensuse-factory] M1 problem with backlisting nouveau
>>>>>>
>>>>>> On 06/12/2011 03:17 PM, Roelof Wobben wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> When I want to blacklist nouveau with M1 and systemd I get this message :
>>>>>>>
>>>>>>> sudo echo "blacklist nouveau">> /etc/modprobe.d/50-blacklist.conf
>>>>>>> bash: /etc/modprobe.d/50-blacklist.conf: Toegang geweigerd
>>>>>>>
>>>>>>>
>>>>>>> Can this be solved on a way so I can enjoy Gnome3 with Gnome-shell
>>>>>>>
>>>>>>> Roelof
>>>>>>>
>>>>>>> --
>>>>>>> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
>>>>>>> For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
>>>>>>>
>>>>>> If you want to blacklist nouveau, then you want to use the nvidia proprio.
>>>>>> For getting latest drivers (275.09.04) actually installed and working use the following path
>>>>>>
>>>>>> Download the drivers from ftp://download.nvidia.com/XFree86/
>>>>>> then reboot with added to the boot line
>>>>>> nomodeset blacklist=nouveau 3
>>>>>>
>>>>>> Login as root, then build the new drivers
>>>>>> sh NVIDIA-Linux-x86_64-275.09.04.run
>>>>>>
>>>>>> Follow instructions, and add the 32bits compatibility
>>>>>> Then the installer push automatically a file
>>>>>> /etc/modprobe.d/nvidia-installer-disable-nouveau.conf
>>>>>>
>>>>>> For me I remove that one and replace it by
>>>>>>
>>>>>> /etc/modprobe.d/50-nvidia.conf
>>>>>> blacklist nouveau
>>>>>> options nouveau modeset=0
>>>>>> options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
>>>>>>
>>>>>> For xorg I didn't have a xorg.conf file I use the new xorg.conf.d layout
>>>>>> and have just added in 50-devices.conf
>>>>>> drivers "nvidia"
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Bruno Friedmann
>>>>>> Ioda-Net Sàrl www.ioda-net.ch
>>>>>>
>>>>>> openSUSE Member& Ambassador
>>>>>> GPG KEY : D5C9B751C4653227
>>>>>> irc: tigerfoot
>>>>>> --
>>>>>> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
>>>>>> For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
>>>>>>
>>>>>
>>>>> Oke,
>>>>>
>>>>> I did all the steps except replacing and get now these error messages when starting x :
>>>>>
>>>>> Fatal : inserting nvidia ….. no such device
>>>>> (EE) NVIDIA : Failed to load the nvidia kernel module. Please check the
>>>>> (EE) system's kernel log for additional errror messages.
>>>>> (EE) Failed to load module "nvidia" (module-specific error,0)
>>>>> (EE) No drivers found.
>>>>>
>>>>> Can i repair this one ?
>>>>>
>>>>> Roelof --
>>>>> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
>>>>> For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
>>>>>
>>>>>
>>>> Check /var/log/nvidia-installer.log to make sure the module was built.
>>>> If it was successful there should be a file "/lib/modules/`uname
>>>> -r`/kernel/drivers/video/nvidia.ko".
>>>> I'm about to reboot and run NVIDIA-Linux-x86_64-275.09.04.run to see if
>>>> there is a problem.
>>>> Regards
>>>> Sid.
>>>>
>>>>
>>> Anyone know how I can blacklist the nouveau driver in M1 ?
>>>
>>> Roelof
>>> --
>>> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
>>> For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
>>>
>>>
>> add this at boot time
>> rdblacklist=nouveau nouveau.modeset=0
>>
>> Alin
>> --
>> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
>> For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
>>
> Hello,
>
> That did the trick.
> I have now a desktop only problem is that it's the fall back gnome and not gnome3
> This says glxinfo about it :
>
> name of display: :0.0
> display: :0 screen: 0
> direct rendering: Yes
> server glx vendor string: NVIDIA Corporation
> server glx version string: 1.4
>
> So i hope that I get Gnome3 working?
>
> Roelof
>
> --
> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
> For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
>
>
I am surprised the script didn't sort it out.
> cat /usr/lib/nvidia/pre-install
#!/bin/sh
echo "blacklist nouveau" > /etc/modprobe.d/nvidia.conf
# recreate initrd without KMS, if the use of KMS is enabled in initrd
if grep -q NO_KMS_IN_INITRD=\"no\" /etc/sysconfig/kernel; then
sed -i 's/NO_KMS_IN_INITRD.*/NO_KMS_IN_INITRD="yes"/g' /etc/sysconfig/kernel
mkinitrd
fi
Another quick way would be to remove the modules from /etc/sysconfig/kernel
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
13 years, 5 months