[opensuse-factory] It's not possible to update/install qmapshack together with qgis
Hi, qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't be updated or installed together anymore due to conflict of file names: File /usr/bin/gdal2tiles.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_calc.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_contour from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_edit.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_fillnodata.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_grid from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_polygonize.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_rasterize from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_retile.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdal_translate from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdaladdo from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdalbuildvrt from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdaldem from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdalenhance from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdalinfo from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdallocationinfo from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdalmanage from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdalserver from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdalsrsinfo from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdaltindex from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdaltransform from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gdalwarp from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gnmanalyse from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/gnmmanage from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/nearblack from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/ogr2ogr from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/ogrinfo from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/ogrlineref from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/ogrmerge.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/ogrtindex from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/bin/testepsg from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/gdal/epsg.wkt from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/gdal/gdalvrt.xsd from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/gdal/pds4_template.xml from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/gdal/plscenesconf.json from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal2tiles.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_calc.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_contour.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_edit.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_fillnodata.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_grid.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_merge.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_pansharpen.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_polygonize.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_proximity.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_rasterize.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_retile.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_sieve.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_translate.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdal_utilities.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdaladdo.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdalbuildvrt.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdalcompare.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdaldem.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdalinfo.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdallocationinfo.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdalmanage.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdalmove.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdalsrsinfo.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdaltindex.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdaltransform.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gdalwarp.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gnm_utilities.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gnmanalyse.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/gnmmanage.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/nearblack.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/ogr2ogr.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/ogr_utilities.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/ogrinfo.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/ogrlineref.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/ogrmerge.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/ogrtindex.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/pct2rgb.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) File /usr/share/man/man1/rgb2pct.1.gz from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo) My "geo" repository points to <http://download.opensuse.org/repositories/ Application:/Geo/openSUSE_Tumbleweed/> What I have available: zypper se -s qgis qmapshack gdal Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+------------------------------------+------------ +--------------------------------+--------+----------- | gdal | package | 3.0.1-1.4 | x86_64 | tw-oss | gdal | package | 3.0.1-1.4 | i586 | tw-oss | gdal | package | 3.0.1-112.6 | x86_64 | science | gdal | package | 3.0.1-108.7 | x86_64 | geo | gdal | package | 3.0.1-112.6 | i586 | science | gdal | package | 3.0.1-108.7 | i586 | geo | gdal | srcpackage | 3.0.1-112.6 | noarch | science | gdal | srcpackage | 3.0.1-108.7 | noarch | geo | gdal-debuginfo | package | 3.0.1-112.6 | x86_64 | science | gdal-debuginfo | package | 3.0.1-108.7 | x86_64 | geo | gdal-debuginfo | package | 3.0.1-112.6 | i586 | science | gdal-debuginfo | package | 3.0.1-108.7 | i586 | geo | gdal-debugsource | package | 3.0.1-112.6 | x86_64 | science | gdal-debugsource | package | 3.0.1-108.7 | x86_64 | geo | gdal-debugsource | package | 3.0.1-112.6 | i586 | science | gdal-debugsource | package | 3.0.1-108.7 | i586 | geo | gdal-devel | package | 3.0.1-1.4 | x86_64 | tw-oss | gdal-devel | package | 3.0.1-1.4 | i586 | tw-oss | gdal-devel | package | 3.0.1-112.6 | x86_64 | science | gdal-devel | package | 3.0.1-108.7 | x86_64 | geo | gdal-devel | package | 3.0.1-112.6 | i586 | science | gdal-devel | package | 3.0.1-108.7 | i586 | geo | gdal2 | package | 2.4.2-12.5 | x86_64 | geo | gdal2 | package | 2.4.2-12.5 | i586 | geo | gdal2 | srcpackage | 2.4.2-12.5 | noarch | geo | gdal2-debuginfo | package | 2.4.2-12.5 | x86_64 | geo | gdal2-debuginfo | package | 2.4.2-12.5 | i586 | geo | gdal2-debugsource | package | 2.4.2-12.5 | x86_64 | geo | gdal2-debugsource | package | 2.4.2-12.5 | i586 | geo | gdal2-devel | package | 2.4.2-12.5 | x86_64 | geo | gdal2-devel | package | 2.4.2-12.5 | i586 | geo | libgdal20 | package | 2.4.2-12.5 | x86_64 | geo | libgdal20 | package | 2.4.2-12.5 | i586 | geo | libgdal20-debuginfo | package | 2.4.2-12.5 | x86_64 | geo | libgdal20-debuginfo | package | 2.4.2-12.5 | i586 | geo | libgdal26 | package | 3.0.1-1.4 | x86_64 | tw-oss | libgdal26 | package | 3.0.1-1.4 | i586 | tw-oss | libgdal26 | package | 3.0.1-112.6 | x86_64 | science | libgdal26 | package | 3.0.1-108.7 | x86_64 | geo | libgdal26 | package | 3.0.1-112.6 | i586 | science | libgdal26 | package | 3.0.1-108.7 | i586 | geo | libgdal26-debuginfo | package | 3.0.1-112.6 | x86_64 | science | libgdal26-debuginfo | package | 3.0.1-108.7 | x86_64 | geo | libgdal26-debuginfo | package | 3.0.1-112.6 | i586 | science | libgdal26-debuginfo | package | 3.0.1-108.7 | i586 | geo | perl-gdal | package | 3.0.1-1.4 | x86_64 | tw-oss | perl-gdal | package | 3.0.1-1.4 | i586 | tw-oss | perl-gdal | package | 3.0.1-112.6 | x86_64 | science | perl-gdal | package | 3.0.1-108.7 | x86_64 | geo | perl-gdal | package | 3.0.1-112.6 | i586 | science | perl-gdal | package | 3.0.1-108.7 | i586 | geo | perl-gdal-debuginfo | package | 3.0.1-112.6 | x86_64 | science | perl-gdal-debuginfo | package | 3.0.1-108.7 | x86_64 | geo | perl-gdal-debuginfo | package | 3.0.1-112.6 | i586 | science | perl-gdal-debuginfo | package | 3.0.1-108.7 | i586 | geo | perl-gdal2 | package | 2.4.2-12.5 | x86_64 | geo | perl-gdal2 | package | 2.4.2-12.5 | i586 | geo | perl-gdal2-debuginfo | package | 2.4.2-12.5 | x86_64 | geo | perl-gdal2-debuginfo | package | 2.4.2-12.5 | i586 | geo | python2-GDAL | package | 3.0.1-1.4 | x86_64 | tw-oss | python2-GDAL | package | 3.0.1-1.4 | i586 | tw-oss | python2-GDAL | package | 3.0.1-112.6 | x86_64 | science | python2-GDAL | package | 3.0.1-108.7 | x86_64 | geo | python2-GDAL | package | 3.0.1-112.6 | i586 | science | python2-GDAL | package | 3.0.1-108.7 | i586 | geo | python2-GDAL-debuginfo | package | 3.0.1-112.6 | x86_64 | science | python2-GDAL-debuginfo | package | 3.0.1-108.7 | x86_64 | geo | python2-GDAL-debuginfo | package | 3.0.1-112.6 | i586 | science | python2-GDAL-debuginfo | package | 3.0.1-108.7 | i586 | geo | python2-GDAL2 | package | 2.4.2-12.5 | x86_64 | geo | python2-GDAL2 | package | 2.4.2-12.5 | i586 | geo | python2-GDAL2-debuginfo | package | 2.4.2-12.5 | x86_64 | geo | python2-GDAL2-debuginfo | package | 2.4.2-12.5 | i586 | geo | python3-GDAL | package | 3.0.1-1.4 | x86_64 | tw-oss | python3-GDAL | package | 3.0.1-1.4 | i586 | tw-oss | python3-GDAL | package | 3.0.1-112.6 | x86_64 | science | python3-GDAL | package | 3.0.1-108.7 | x86_64 | geo | python3-GDAL | package | 3.0.1-112.6 | i586 | science | python3-GDAL | package | 3.0.1-108.7 | i586 | geo | python3-GDAL-debuginfo | package | 3.0.1-112.6 | x86_64 | science | python3-GDAL-debuginfo | package | 3.0.1-108.7 | x86_64 | geo | python3-GDAL-debuginfo | package | 3.0.1-112.6 | i586 | science | python3-GDAL-debuginfo | package | 3.0.1-108.7 | i586 | geo | python3-GDAL2 | package | 2.4.2-12.5 | x86_64 | geo | python3-GDAL2 | package | 2.4.2-12.5 | i586 | geo | python3-GDAL2-debuginfo | package | 2.4.2-12.5 | x86_64 | geo | python3-GDAL2-debuginfo | package | 2.4.2-12.5 | i586 | geo | qgis | package | 3.8.2-1.2 | x86_64 | geo | qgis | package | 3.8.2-1.2 | i586 | geo | qgis | srcpackage | 3.8.2-1.2 | noarch | geo | qgis-debuginfo | package | 3.8.2-1.2 | x86_64 | geo | qgis-debuginfo | package | 3.8.2-1.2 | i586 | geo | qgis-debugsource | package | 3.8.2-1.2 | x86_64 | geo | qgis-debugsource | package | 3.8.2-1.2 | i586 | geo | qgis-devel | package | 3.8.2-1.2 | x86_64 | geo | qgis-devel | package | 3.8.2-1.2 | i586 | geo | qgis-ltr | package | 3.4.8-1.1 | x86_64 | geo | qgis-ltr | package | 3.4.8-1.1 | i586 | geo | qgis-ltr | srcpackage | 3.4.8-1.1 | noarch | geo | qgis-ltr-debuginfo | package | 3.4.8-1.1 | x86_64 | geo | qgis-ltr-debuginfo | package | 3.4.8-1.1 | i586 | geo | qgis-ltr-debugsource | package | 3.4.8-1.1 | x86_64 | geo | qgis-ltr-debugsource | package | 3.4.8-1.1 | i586 | geo | qgis-ltr-devel | package | 3.4.8-1.1 | x86_64 | geo | qgis-ltr-devel | package | 3.4.8-1.1 | i586 | geo | qgis-ltr-plugin-grass | package | 3.4.8-1.1 | x86_64 | geo | qgis-ltr-plugin-grass | package | 3.4.8-1.1 | i586 | geo | qgis-ltr-plugin-grass-debuginfo | package | 3.4.8-1.1 | x86_64 | geo | qgis-ltr-plugin-grass-debuginfo | package | 3.4.8-1.1 | i586 | geo | qgis-ltr-sample-data | package | 3.4.8-1.1 | x86_64 | geo | qgis-ltr-sample-data | package | 3.4.8-1.1 | i586 | geo | qgis-master | package | 0~git. 20190405.8b3f97fa19-1.31 | x86_64 | geo | qgis-master | srcpackage | 0~git. 20190405.8b3f97fa19-1.31 | noarch | geo | qgis-master-debuginfo | package | 0~git. 20190405.8b3f97fa19-1.31 | x86_64 | geo | qgis-master-debugsource | package | 0~git. 20190405.8b3f97fa19-1.31 | x86_64 | geo | qgis-master-devel | package | 0~git. 20190405.8b3f97fa19-1.31 | x86_64 | geo | qgis-master-plugin-grass | package | 0~git. 20190405.8b3f97fa19-1.31 | x86_64 | geo | qgis-master-plugin-grass-debuginfo | package | 0~git. 20190405.8b3f97fa19-1.31 | x86_64 | geo | qgis-master-sample-data | package | 0~git. 20190405.8b3f97fa19-1.31 | x86_64 | geo | qgis-otb-plugin | package | 1.4.2-1.1 | x86_64 | geo | qgis-otb-plugin | package | 1.4.2-1.1 | i586 | geo | qgis-otb-plugin | srcpackage | 1.4.2-1.1 | noarch | geo | qgis-plugin-grass | package | 3.8.2-1.2 | x86_64 | geo | qgis-plugin-grass | package | 3.8.2-1.2 | i586 | geo | qgis-plugin-grass-debuginfo | package | 3.8.2-1.2 | x86_64 | geo | qgis-plugin-grass-debuginfo | package | 3.8.2-1.2 | i586 | geo | qgis-sample-data | package | 3.8.2-1.2 | x86_64 | geo | qgis-sample-data | package | 3.8.2-1.2 | i586 | geo | qmapshack | package | 1.13.1-1.2 | x86_64 | geo | qmapshack | package | 1.13.1-1.2 | i586 | geo | qmapshack | srcpackage | 1.13.1-1.2 | noarch | geo | qmapshack-debuginfo | package | 1.13.1-1.2 | x86_64 | geo | qmapshack-debuginfo | package | 1.13.1-1.2 | i586 | geo | qmapshack-debugsource | package | 1.13.1-1.2 | x86_64 | geo | qmapshack-debugsource | package | 1.13.1-1.2 | i586 | geo My "science" repository points to <http://download.opensuse.org/repositories/ science/openSUSE_Tumbleweed/> Anyway, the problem doesn't seem to be solvable right now by me... -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/
On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote:
Hi, qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't be updated or installed together anymore due to conflict of file names:
File /usr/bin/gdal2tiles.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo)
So disable geo. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote:
On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote:
Hi, qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't be updated or installed together anymore due to conflict of file names:
File /usr/bin/gdal2tiles.py
from install of
gdal-3.0.1-1.4.x86_64 (tw-oss)
conflicts with file from install of
gdal2-2.4.2-12.5.x86_64 (geo)
So disable geo.
Won't help - qgis requires gdal2 via python3-GDAL2, and qmapshack requires gdal (any version). gdal and gdal2 conflict (same files), and gdal2 does not provide gdal (although it is gdal==2.x). Kind regards, Stefan
On Monday 2019-08-26 22:23, Brüns, Stefan wrote:
On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote:
On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote:
Hi, qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't be updated or installed together anymore due to conflict of file names:
File /usr/bin/gdal2tiles.py
from install of
gdal-3.0.1-1.4.x86_64 (tw-oss)
conflicts with file from install of
gdal2-2.4.2-12.5.x86_64 (geo)
So disable geo.
gdal and gdal2 conflict (same files), and gdal2 does not provide gdal (although it is gdal==2.x).
My point was that it is not a Factory problem. It is, as every so often, a problem with, hm, 2.5nd-party repositories. Conversely, if gdal2 were in Factory, there would be no problem because some bot would have caught that early on. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne pondělí 26. srpna 2019 22:43:15 CEST, Jan Engelhardt napsal(a):
On Monday 2019-08-26 22:23, Brüns, Stefan wrote:
On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote:
On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote:
qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't be updated or installed together anymore due to conflict of file names: File /usr/bin/gdal2tiles.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo)
So disable geo.
I have it as there are packages I use which are missing from Factory...
gdal and gdal2 conflict (same files), and gdal2 does not provide gdal (although it is gdal==2.x).
Then I wonder what changed as qmapshack could well live with QGIS...
My point was that it is not a Factory problem. It is, as every so often, a problem with, hm, 2.5nd-party repositories.
Depends on point of view... For me, without these "2.5nd-party repositories", openSUSE would not be that useful...
Conversely, if gdal2 were in Factory, there would be no problem because some bot would have caught that early on.
So... How to solve it? Extend the smart bot? Submit everything to Factory? Something else? -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/
On Tuesday 2019-08-27 09:25, Vojtěch Zeisek wrote:
Conversely, if gdal2 were in Factory, there would be no problem because some bot would have caught that early on.
So... How to solve it? Submit everything to Factory?
Every software that is useful to anyone on a daily basis (and which is not "blacklisted" for legal reasons or whatever) definitely should be in openSUSE:Factory. At the very least, just to get a bit of free maintenance if there is low-hanging fruit. ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 8/27/19 4:55 PM, Vojtěch Zeisek wrote:
Dne pondělí 26. srpna 2019 22:43:15 CEST, Jan Engelhardt napsal(a):
On Monday 2019-08-26 22:23, Brüns, Stefan wrote:
On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote:
On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote:
qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't be updated or installed together anymore due to conflict of file names: File /usr/bin/gdal2tiles.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo)
So disable geo.
I have it as there are packages I use which are missing from Factory...
gdal and gdal2 conflict (same files), and gdal2 does not provide gdal (although it is gdal==2.x).
Then I wonder what changed as qmapshack could well live with QGIS...
My point was that it is not a Factory problem. It is, as every so often, a problem with, hm, 2.5nd-party repositories.
Depends on point of view... For me, without these "2.5nd-party repositories", openSUSE would not be that useful...
Unfortunately this list isn't really for discussing these "2.5nd-party repo's" as pointed out by Jan we also can't run tests on them to ensure breakages like this don't happen. Rather then posting here you will need to create bug reports on those packages in obs as while they are not in factory they are not really part of openSUSE. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne úterý 27. srpna 2019 14:30:43 CEST, Simon Lees napsal(a):
On 8/27/19 4:55 PM, Vojtěch Zeisek wrote:
Dne pondělí 26. srpna 2019 22:43:15 CEST, Jan Engelhardt napsal(a):
On Monday 2019-08-26 22:23, Brüns, Stefan wrote:
On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote:
On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote:
qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't be updated or installed together anymore due to conflict of file names: File /usr/bin/gdal2tiles.py from install of gdal-3.0.1-1.4.x86_64 (tw-oss) conflicts with file from install of gdal2-2.4.2-12.5.x86_64 (geo)
So disable geo.
I have it as there are packages I use which are missing from Factory...
gdal and gdal2 conflict (same files), and gdal2 does not provide gdal (although it is gdal==2.x).
Then I wonder what changed as qmapshack could well live with QGIS...
My point was that it is not a Factory problem. It is, as every so often, a problem with, hm, 2.5nd-party repositories.
Depends on point of view... For me, without these "2.5nd-party repositories", openSUSE would not be that useful...
Unfortunately this list isn't really for discussing these "2.5nd-party repo's" as pointed out by Jan we also can't run tests on them to ensure breakages like this don't happen.
OK, what is good place to discuss such issues, then?
Rather then posting here you will need to create bug reports on those packages in obs as while they are not in factory they are not really part of openSUSE.
https://bugzilla.opensuse.org/show_bug.cgi?id=1148375 https://bugzilla.opensuse.org/show_bug.cgi?id=1148376 I wonder what it is then when the package is build under build.*opensuse*.org, findable via software.*opensuse*.org and fetchable via download.*opensuse*.org... This is really confusing... -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/
On 27. Aug 2019, at 15:49, Vojtěch Zeisek
wrote: Dne úterý 27. srpna 2019 14:30:43 CEST, Simon Lees napsal(a):
On 8/27/19 4:55 PM, Vojtěch Zeisek wrote: Dne pondělí 26. srpna 2019 22:43:15 CEST, Jan Engelhardt napsal(a):
On Monday 2019-08-26 22:23, Brüns, Stefan wrote:
On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote: > On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote: > qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't > be updated or installed together anymore due to conflict of > file names: > File /usr/bin/gdal2tiles.py > from install of > gdal-3.0.1-1.4.x86_64 (tw-oss) > conflicts with file from install of > gdal2-2.4.2-12.5.x86_64 (geo)
So disable geo.
I have it as there are packages I use which are missing from Factory...
gdal and gdal2 conflict (same files), and gdal2 does not provide gdal (although it is gdal==2.x).
Then I wonder what changed as qmapshack could well live with QGIS...
My point was that it is not a Factory problem. It is, as every so often, a problem with, hm, 2.5nd-party repositories.
Depends on point of view... For me, without these "2.5nd-party repositories", openSUSE would not be that useful...
Unfortunately this list isn't really for discussing these "2.5nd-party repo's" as pointed out by Jan we also can't run tests on them to ensure breakages like this don't happen.
OK, what is good place to discuss such issues, then?
That’s a question best directed to the maintainer (or if you’re lucky, plural, maintainers) of the repository
Rather then posting here you will need to create bug reports on those packages in obs as while they are not in factory they are not really part of openSUSE.
https://bugzilla.opensuse.org/show_bug.cgi?id=1148375 https://bugzilla.opensuse.org/show_bug.cgi?id=1148376 I wonder what it is then when the package is build under build.*opensuse*.org, findable via software.*opensuse*.org and fetchable via download.*opensuse*.org... This is really confusing...
Is it? You wouldn’t expect a Windows OS development list to be the right place to discuss issues with an EXE randomly downloaded off the internet, or even from the Microsoft Store, which has a .microsoft.com address You wouldn’t expect a OSX or iOS development list to be the right place to discuss issues with an Apple app even if it comes from the apple.com store Why do you expect openSUSE to be responsible for any random project on OBS that doesn’t follow openSUSEs rigorous code review, legal review and QA standards? openSUSE is only responsible for the software openSUSE includes in its distribution. Anything else is not the responsibility of the openSUSE project and best not discussed on this list
-- Vojtěch Zeisek
Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 8/27/19 11:19 PM, Vojtěch Zeisek wrote:
Dne úterý 27. srpna 2019 14:30:43 CEST, Simon Lees napsal(a):
On 8/27/19 4:55 PM, Vojtěch Zeisek wrote:
Dne pondělí 26. srpna 2019 22:43:15 CEST, Jan Engelhardt napsal(a):
On Monday 2019-08-26 22:23, Brüns, Stefan wrote:
On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote:
On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote: > qmapshack and qgis require gdal-3.0.1 and gdal2-2.4.2 can't > be updated or installed together anymore due to conflict of > file names: > File /usr/bin/gdal2tiles.py > from install of > gdal-3.0.1-1.4.x86_64 (tw-oss) > conflicts with file from install of > gdal2-2.4.2-12.5.x86_64 (geo)
So disable geo.
I have it as there are packages I use which are missing from Factory...
gdal and gdal2 conflict (same files), and gdal2 does not provide gdal (although it is gdal==2.x).
Then I wonder what changed as qmapshack could well live with QGIS...
My point was that it is not a Factory problem. It is, as every so often, a problem with, hm, 2.5nd-party repositories.
Depends on point of view... For me, without these "2.5nd-party repositories", openSUSE would not be that useful...
Unfortunately this list isn't really for discussing these "2.5nd-party repo's" as pointed out by Jan we also can't run tests on them to ensure breakages like this don't happen.
OK, what is good place to discuss such issues, then?
Rather then posting here you will need to create bug reports on those packages in obs as while they are not in factory they are not really part of openSUSE.
https://bugzilla.opensuse.org/show_bug.cgi?id=1148375 https://bugzilla.opensuse.org/show_bug.cgi?id=1148376 I wonder what it is then when the package is build under build.*opensuse*.org, findable via software.*opensuse*.org and fetchable via download.*opensuse*.org... This is really confusing...
The openSUSE project offers its buildservice as a service to the broader open source community (in a similar way to how github offers its hosting services). If the software you are looking for is findable in yast or on software.opensuse.org without looking at the packages clearly marked as "experimental" or "community". Then that package has been reviewed and tested in a way that means it won't break the rest of your distro and is part of openSUSE. If the package is marked "Experimental" or "Community" on software.o.o then it is not a part of the openSUSE Project and doesn't meet our standards (even if some packages in the experimental category are well on there way to doing so). Maybe we need to mark the Experimental / Community stuff to more clearly label it as unofficial, although we do clearly mark the official stuff as official. If there are packages you use that are not official then maybe you can ask the maintainer if they would be willing to push it into the official repositories, maybe you could even offer to help. Such work normally isn't hard and is a great way to get started packaging. There are also plenty of people who are willing to help you learn. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne středa 28. srpna 2019 11:08:44 CEST, Simon Lees napsal(a):
On 8/27/19 11:19 PM, Vojtěch Zeisek wrote:
Dne úterý 27. srpna 2019 14:30:43 CEST, Simon Lees napsal(a):
Dne pondělí 26. srpna 2019 22:43:15 CEST, Jan Engelhardt napsal(a):
On Monday 2019-08-26 22:23, Brüns, Stefan wrote:
On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote: > On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote: Rather then posting here you will need to create bug reports on
On 8/27/19 4:55 PM, Vojtěch Zeisek wrote: those packages in obs as while they are not in factory they are not really part of openSUSE.
https://bugzilla.opensuse.org/show_bug.cgi?id=1148375 https://bugzilla.opensuse.org/show_bug.cgi?id=1148376 I wonder what it is then when the package is build under build.*opensuse*.org, findable via software.*opensuse*.org and fetchable via download.*opensuse*.org... This is really confusing...
The openSUSE project offers its buildservice as a service to the broader open source community (in a similar way to how github offers its hosting services).
Might be the confusion cames from the fact, that OBS compiles the software, produces the final package. Github doesn't do so, neither common app stores.
If the software you are looking for is findable in yast or on software.opensuse.org without looking at the packages clearly marked as "experimental" or "community". Then that package has been reviewed and tested in a way that means it won't break the rest of your distro and is part of openSUSE. If the package is marked "Experimental" or "Community" on software.o.o then it is not a part of the openSUSE Project and doesn't meet our standards (even if some packages in the experimental category are well on there way to doing so). Maybe we need to mark the Experimental / Community stuff to more clearly label it as unofficial, although we do clearly mark the official stuff as official.
This could indeed help.
If there are packages you use that are not official then maybe you can ask the maintainer if they would be willing to push it into the official repositories, maybe you could even offer to help. Such work normally isn't hard and is a great way to get started packaging. There are also plenty of people who are willing to help you learn.
I tried to compile in OBS some software I use, I failed. OK, I should restart and devote more time to play with packaging... -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/
On 28. Aug 2019, at 13:23, Vojtěch Zeisek
wrote: Dne středa 28. srpna 2019 11:08:44 CEST, Simon Lees napsal(a):
On 8/27/19 11:19 PM, Vojtěch Zeisek wrote: Dne úterý 27. srpna 2019 14:30:43 CEST, Simon Lees napsal(a):
> On Monday 2019-08-26 22:23, Brüns, Stefan wrote: >> On Montag, 26. August 2019 21:24:15 CEST Jan Engelhardt wrote: >> On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote: Rather then posting here you will need to create bug reports on
On 8/27/19 4:55 PM, Vojtěch Zeisek wrote: Dne pondělí 26. srpna 2019 22:43:15 CEST, Jan Engelhardt napsal(a): those packages in obs as while they are not in factory they are not really part of openSUSE.
https://bugzilla.opensuse.org/show_bug.cgi?id=1148375 https://bugzilla.opensuse.org/show_bug.cgi?id=1148376 I wonder what it is then when the package is build under build.*opensuse*.org, findable via software.*opensuse*.org and fetchable via download.*opensuse*.org... This is really confusing...
The openSUSE project offers its buildservice as a service to the broader open source community (in a similar way to how github offers its hosting services).
Might be the confusion cames from the fact, that OBS compiles the software, produces the final package. Github doesn't do so, neither common app stores.
This statement is incorrect. https://github.com/features/package-registry GitHub is used to deliver binaries to users all the time. And if you’d like another similar example - Docker containers are provided by hub.docker.com but no reasonable person would go to the docker runtime developers when a container has unfulfilled dependencies
Dne středa 28. srpna 2019 17:10:40 CEST jste napsal(a):
On 28. Aug 2019, at 13:23, Vojtěch Zeisek wrote: Dne středa 28. srpna 2019 11:08:44 CEST, Simon Lees napsal(a):
On 8/27/19 11:19 PM, Vojtěch Zeisek wrote: Dne úterý 27. srpna 2019 14:30:43 CEST, Simon Lees napsal(a):
On 8/27/19 4:55 PM, Vojtěch Zeisek wrote: Dne pondělí 26. srpna 2019 22:43:15 CEST, Jan Engelhardt napsal(a): > > On Monday 2019-08-26 22:23, Brüns, Stefan wrote: > > > On Montag, 26. August 2019 21:24:15 CEST Jan > > > Engelhardt wrote: > > > On Monday 2019-08-26 16:40, Vojtěch Zeisek wrote: Rather then posting here you will need to create bug reports on those packages in obs as while they are not in factory they are not really part of openSUSE.
https://bugzilla.opensuse.org/show_bug.cgi?id=1148375 https://bugzilla.opensuse.org/show_bug.cgi?id=1148376 I wonder what it is then when the package is build under build.*opensuse*.org, findable via software.*opensuse*.org and fetchable via download.*opensuse*.org... This is really confusing...
The openSUSE project offers its buildservice as a service to the broader open source community (in a similar way to how github offers its hosting services).
Might be the confusion cames from the fact, that OBS compiles the software, produces the final package. Github doesn't do so, neither common app stores.
This statement is incorrect. https://github.com/features/package-registry GitHub is used to deliver binaries to users all the time. And if you’d like another similar example - Docker containers are provided by hub.docker.com but no reasonable person would go to the docker runtime developers when a container has unfulfilled dependencies
OK, good point. Case closed. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/
participants (5)
-
Brüns, Stefan
-
Jan Engelhardt
-
Richard Brown
-
Simon Lees
-
Vojtěch Zeisek