Hello List ,
Okular seems to have lost ability read PNG format : perhaps something
gone wrong with
Konsole output
calligra-extras-okular
- did anyone else experience this ?
I have tried re-installing okular but no joy - still
unable read png format
.........
thanks
regards
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
during our Hackweek at SUSE I spent a day or two to improve my tool to
help finding the maintainer for software in Factory, which comes in
handy for bugzilla-screening (getting bugs to the right people).
You can use the tool at
http://maintainer.zq1.de/
You can give it command names, full filepath, or package names
(exact matches (including case) only)
If you want to run or extend it,
the code is all open on https://github.com/bmwiedemann/susepkginfo
and the databases can be fetched from http://aw.zq1.de/db.suse/
The actual maintainer information comes from OBS, so is always current.
Ciao
Bernhard M.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Dear all,
does for the upcomming version 42.1 a 32 bit version will be available?
Nor for milestone 1 I only can find a x64 version.
If 32 bit will be availalbe later on which stage of the development it
is to be expected?
Beta? RC?
Best Regards
Andreas
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello,
I just updated from rev. 13.2 to tumbleweed. It doesn't work as I
expected but with plasma5 it should show differences. For my more or
less privete developing work i am using kdevelop quite often. And with
KDE4 it worked well.
Now after the upgrade to tumbleweed it crashes when kdevelp is calling
drkonqi. It looks like that kdevelop is calling kdeinit and after that
drkonqi fails to start.
I am attaching a crash.txt which reports the crash
--
greetings
Hartmut Rosch
Delmenhorst
-----------
Dear Tumbleweed users and hackers,
In good tradition I am pleased to also give you an overview of the
last week on what happened in Tumbleweed.
We had 'only' two snapshots released this week (0425 & 0430). The main
reason was that the update of parted to version 3.2 managed to sneak
through the staging area, yet had a negative impact on the full post
-integration test runs (resizing partitions while installing openSUSE
side-by-side of Windows is not properly handled).
So, parted 3.2 is currently taken out of Tumbleweed again - but of
course scheduled to reach you later: once YaST has been adjusted to
handle the changes.
On the side of things that DID happen:
* As discussed on the -factory mailinglist, a couple packages have
been converted from GStreamer 0.10 to 1.0 (banshee, gnac)
* The kernel has been updated to version 4.0
What can we expect in the upcoming period?
* The KDE Team is hard at work to make Plasma 5.3 the default for
openSUSE. Work is still going on, but the staging areas are looking
promising already.
* The switch of GCC 5 as default version is also still work in
progress. This is not forgotten yet.
* Progress on Ruby 2.2 seems to have stalled - there hasn't been any
progress in a while now. Volunteers to step up and work on the
fallouts in Staging:H are welcome [0]
[0] https://build.opensuse.org/project/show/openSUSE:Factory:Staging:H
--
Have a lot of fun,
Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org>
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
> snip
>
>
> IMO, Tumbleweed is for experts :-)
>
> - --
> Cheers / Saludos,
>
> Carlos E. R.
>
> No it's not. I'm running it successfully and am far from an expert.
> Yes. It's for experienced users
> snip
>
> Steven
Thank you very much Carlos, Dimstar, Dsant, Jim, Jimmy, Ken, Lars,
Richard, Roman, Steven for your inputs.
Summary
##########
The above is valid: TW in its current form is for experts / experienced
users / users following this list. That is exactly why I started this
discussion:
subject: "A users wishlist to make zypper up/dup & suse noob-friendly"
See? I said implicitly that zypper is too complicated and my wish is,
that it - or another update mechanism - would make TW beginner-friendly.
And most of the improvements could also work for Leap, but that would be
a side-effect.
Results
###########
a) on installation user opt-in to packman-repo
=> legaly not possible, however one suggestion was not yet commented:
"There could be a supplementary screen :
* If you live in US click here (open-sources repositories, DMCA ok...).
* If you live in UK/Germany/Europe... click here (Packman repository added)
[...]
Dsant"
b) default to packman priority 98 & auto vendor change
=> implementation possible through .repo parameter priority, but
concerns about a race of lowest priorities & untested packages & not
needing the whole repo.
=> solutions:
- the noob does not know which subset of packman he needs to get
multimedia working, thus just do the vendor change per default.
- implement openQA also for packman to test & thus to allow automatical
vendor change for this one repo only.
- there is no race for lowest priority if only one repo==packman gets
the 98 priority as the default.
Can we agree that packman is the most important user repo of openSUSE so
that it should be treated special?
c) after adding packman do auto zypper dup or up with vendor change once:
PackageKit / Apper cannot handle conflicts and thus is not supported in TW.
=> solutions:
1) enhance Apper to handle conflicts
2) automatizing zypper: noobs cannot use cron, nor command line /
yast-gui, nor can they decide between "no / vendor change", "up / dup"
=> further comments:
A users confirmation to install the automatically proposed update is
desired, agreed.
A password will be needed for new software only, as this is already the
way PackageKit/Apper & Win7 (just tested) are doing it from user accounts.
d) install recommends only once during installation as default, so that
uninstalled apps do not come back
=> so far +1 for this
e) I would update the whole wiki with the changes
Thank you, thomas
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello List ,
TW : Okular,Version 0.22.2
- in case of interest : Okular has not yet re-gained its ability to
read .PNG image format ,
which it earlier possessed .
...........
regards
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
I heard about the development model for the next openSUSE release
Leap 42.1.
What are the proposed guidelines for security relevant packages?
(I mean base security libraries like OpenSSL and security sensitive
application packages like Apache or Sendmail.)
Personally I prefer up-to-dateness over maturity for such packages.
I would like to explain my rating with an example:
Ever since the Poodle attack it's clear, that SSL 3 should be
disabled. On http://disablessl3.com/ I found instructions to disable
SSL 3 on Sendmail. Unfortunately the Sendmail packages of
distributions like Ubuntu 14.04 are not recent enough and the
proposed SSL settings are missing. So administrators have two bad
alternatives: staying with mature, but more or less insecure
software or switching to fresh secure, unsupported and sometimes
unstable packages.
The example is about Ubuntu 14.04. But will openSuSE go in the same
direction?
Greetings,
Björn
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi all,
Since there is no Geo specific mailing list, I decided to bring some
issues to the factory list:
1. GRASS 7 has been released some time now. We are still maintaining 2
versions in Geo repository: grass (6.4.x) and grass7 (7.x). I think we
need to merge grass7 into grass package. The question is: should we
create a grass6 package for 6.x users? I am sure those users exist out
there...
2. PostGIS 2 is out for quite a long time. We have postgis and postgis2
packages in our repository.
postgis is disabled and all binaries are wiped out for some time now
(since we removed RedHat based repositories). Question: should we merge
postgis2 to postgis? and drop postgis2 package?
3. openSUSE 42 has been added to the Geo project. There are some
dependencies missing, but things look good in general. Should we add the
needed packages in Geo repository or submit the needed packages to 42?
4. QGIS 2 is out for at least 2 years. There is no point to keep qgis
and qgis2 packages anymore. Otto has proposed to have qgis package
(latest stable release - 2.10.1), qgis-master (nightly build from git,
as we already have) and qgis-ltr (Long Time Supported Release - 2.8.3).
I agree to drop QGIS 1.x package.
5. Several Geo packages are now in Factory so we should be very careful
with what is enabled to build in Geo repository. Those packages should
be used from the upstream openSUSE release (eg. geos, hdf5, proj). I
made some adjustments to fix this issue.
6. GDAL made it to Factory but was never released as part of a stable
openSUSE release (it would be released in 13.3, so we need to submit it
to 42). Also GDAL 2.0 was released some days ago. I am sure that most
downstream projects are not ready for the switch. Should we create a
gdal2 package or just wait a few months?
Best,
Angelos
--
Angelos Tzotsos, PhD
OSGeo Charter Member
http://users.ntua.gr/tzotsos
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org