Hi Jan, all,
I'd like to carry our OBS dicussion to a wider audience
(https://build.opensuse.org/request/show/672510).
The question is whether we can assume that "/bin/sh" links to bash,
in particular whether rpm scriptlets without explicit -p interpreter
can be assumed to interpreted by bash.
I'm aware that, in principle, /bin/sh is supposed to be the Bourne
shell on Unix systems. But as a matter of fact, on current openSUSE, it
is not. Unless it's tampered with, /bin/sh is a symlink to /bin/bash.
bash is not started in full POSIX mode if invoked as /bin/sh, and even
if it's in POSIX mode, it supports some extensions over the POSIX shell
spec (e.g. the [[ ]] construct), which makes it behave differently than
another shell not supporting [[ ]] would (*). Problably there are more
differences, I can't claim to know them all.
Here are some arguments why I think it'd be reasonable to assume that
/bin/sh is bash on openSUSE:
1. patterns-base-minimal_base depends on bash, and the /bin/sh symlink
is a non-configurable part of the "bash" package.
2. we could handle /bin/sh via /etc/alternatives, but we don't.
3. our Wiki suggests testing failing scriplets using "bash -xv"
(https://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets)
4. /bin/sh has pointed to bash for a long time (not sure how long
exactly).
FTR, Fedora basically guarantees (sh == bash) for the purpose of rpm
scriptlets (https://fedoraproject.org/wiki/Packaging:Scriptlets). So
Fedora <-> openSUSE portability may also be an issue to consider.
If we can't assume that /bin/sh is bash, what else can we assume? I
recall from earlier work that writing really 100% compatible shell code
for all kinds of environments is really hard. E.g., "[" isn't 100%
portable either, even though it's part of the POSIX "test" standard
(http://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html).
We should have clear rules which syntax expressions can be used in rpm
scriptlets, and which can't. IMO we should define one of the various
existing shells as a reference by saying "if it's supported
by this shell, it's valid scriptlet code". That'd be easier (especially
for testing compliance) than referring to a spec. That reference shell
doesn't have to be bash, of course.
Thanks
Martin
(*) For example:
# ln -s /usr/bin/echo '/usr/bin/[['
# ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Feb 8 10:38 /bin/sh -> bash
# /bin/sh --posix -c '[[ 2 = 1 ]] && echo yes'
# dash -c '[[ 2 = 1 ]] && echo yes'
2 -eq 1 ]]
yes
--
Dr. Martin Wilck <mwilck(a)suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
our experimental git mirror of openSUSE:Factory
got a new feature:
It now makes single commits from most individual updates with some
useful info in the commit message.
This makes the whole history much nicer to read:
https://github.com/bmwiedemann/openSUSE/commits/master
In the usual case of SRs it links back to the SR on OBS, because that is
where most of the discussion might have happened:
https://github.com/bmwiedemann/openSUSE/commit/d1afc9699
but sometimes direct commits happen and they are shown with the commit
message and a link to the OBS change
https://github.com/bmwiedemann/openSUSE/commit/b2786e5c8
Ideas for future work:
In theory we could also track these packages' devel projects on a
'devel' branch
In a similar fashion we could also track openSUSE:Leap:15.* on
stable/leap15_N branches to allow offline diff
We could try to enable osc build to work from such git dirs. Either this
uses the OBS server-side logic to resolve dependencies to get the usual
.osc/_buildinfo* and .osc/_buildconfig* files or we re-implement or
re-use OBS server logic to allow builds when offline.
And then (in the foggy far future) it would be possible to make a
gateway back from
github pull-requests or gitlab merge-requests to submitting SRs in OBS.
Or we re-think how OBS handles its source files until then. See
https://www.youtube.com/watch?v=iY_ADUQiiQI&t=787
Ciao
Bernhard M.
I'm not sure, if this is bug or feature... After few days, update applet (TW,
KDE) says there are 6843 new updates (TeX, R, ... ;-). When I click to
"Install updates" error "Too many packages to process (6843/5200)" appears.
Zypper handles it well. Is it worth of bug report? To b.o.o?
Yours,
V.
--
Vojtěch Zeisek
Komunita openSUSE GNU/Linuxu
Community of the openSUSE GNU/Linux
https://www.opensuse.org/https://trapa.cz/
Hello community members,
Lubos noticed that "openSUSE way" talk [1] got some views (~500) [2] and
thus maybe community is interested about it.
I am not sure, maybe it is just fancy and attractive name
Anyway I found couple of ppl that would like to follow up and check if
we could have more easy install and config for complete Sway desktop.
During preparation to the talk I have created github project to track
progress for it and ToDo for the future of my setup [3]. In the same
repo you could find example of dotfiles for config presented in the talk.
If you are interested in this project, create cards, issues and work on
them.
Next steps are to create good pattern [4] and branding [5].
And to push more packages to Factory (wofi).
Maybe we even could move that repo/project under openSUSE github org ?
So try, migrate and have some fun with Sway and tell us if we could make
it better.
https://en.opensuse.org/Sway
1. https://denisok.github.io/oSC20-openSUSEway/index.html
2. https://www.youtube.com/watch?v=dSMxJKSNSjo
3. https://github.com/denisok/openSUSEway/projects/1
4. https://github.com/denisok/openSUSEway/issues/1
5. https://github.com/denisok/openSUSEway/issues/2
Thanks,
--
Denis Kondratenko
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
On 26 May 21:14 2020, Hans Petter Jansson wrote:
> On Sun, 2020-05-24 at 18:53 +0200, İsmail Dönmez wrote:
> > On 24 May 12:36 2020, Michael Ströder wrote:
> > > On 5/24/20 1:17 PM, Alin Marin Elena wrote:
> > > > Are there any plans to have openssh updated to version 8.2?
> > >
> > > Purely out of curiosity:
> > > Any specific requirement for you wanting this upgrade?
> >
> > openssh 8.3 is about to be released and I myself want it for easier
> > Yubikey
> > integration.
>
> Would you be fine with an update directly to 8.3? If it's a short wait,
> I can do this once it's out.
I'd wait for 8.3 indeed to prevent double work, thanks a lot!
- ismail
--
In ancient times cats were worshipped as gods; they have not forgotten this.
SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
last month's status:
https://lists.opensuse.org/opensuse-factory/2020-03/msg00014.html
Last months' reproducible builds project updates (including my work):
https://reproducible-builds.org/reports/2020-02/
I uploaded https://rb.zq1.de/compare.factory-20200402/ today
and rbstats are:
total-packages: 12781 (+89)
build-tried: 12772 (+89)
build-failed: 54 (+14)
build-n-a: 86 (+1)
build-succeeded: 12632 (+74)
build-official-failed+na: 135 (+43)
build-compare-failed: 408 (+17)
build-compare-succeeded: 12224 (+57)
verify-failed: 526 (+7)
verified-semi-reproducible: 11458 (+87)
verified-bit-identical: 0 (+0)
bit-by-bit-identical: 11862 (+58)
not-bit-by-bit-identical: 764 (+17)
not-bit-by-bit-identicalcheck: 770 (+16)
https://rb.zq1.de/compare.factory-20200402/graph.png
shows the change over time
https://rb.zq1.de/compare.factory-20200402/unreproduciblerings.txt
lists very unreproducible core packages (bootstrap+DVD)
Of the badly unreproducible packages,
4 were in ring0
44 were in ring1
That makes it 48/2901 => 1.65 %
which is below the overall average of
408/12632 => 3.23 %
764/12632 => 6.05 % of packages are not perfectly reproducible
newly unreproducible core packages:
cri-o
parallelism causes go buildid to vary - same problem as in many of
our go packages (since go1.10)
python3
filesystem readdir order influences .pyc file marshalling
https://bugs.python.org/issue34033
Ciao
Bernhard M.
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQRk4KvQEtfG32NHprVJNgs7HfuhZAUCXoXALgAKCRBJNgs7Hfuh
ZI5NAJ92/xS9ZDT7FQBg0HwnAHfO46lBYACgsvlwixFNKxHssknMR1089KXD1qY=
=kxCI
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello,
I'd like to submit to Factory 'ruqola' [1] package I've packaged and
been using for a long time now but pondering the right moment since the
upstream hasn't done actual releases. Now I feel it's a good time not to
delay getting more users to it. In recent months it has felt stable and
had good progress on features.
[1] https://cgit.kde.org/ruqola.git
It's a native Rocket Chat client, an alternative to use if one feels
that this trend of embedded browsers (electron apps) is a too bloated
trend. It starts up very fast and uses less resources.
Ruqola was a topic during Hackweek as well and we got a 2FA improvement
back then upstreamed by Christian Dywan while I worked on the packaging.
I'm submitting it to KDE:Extra first.
--
Best Regards,
Timo Jyrinki
HI!
I'm trying to use an autoyast.xml for installing Tumbleweed which IIRC
worked before.
But it now fails with this message:
None or wrong base product has been defined in the
AutoYaST configuration file. Please check the products
entry in the software section.
Following base products are available:
openSUSE-MicroOS (openSUSE MicroOS)
openSUSE (openSUSE Tumbleweed)
I cannot figure out what's missing.
Is that an additional option introduced recently?
Any hint is appreciated.
Ciao, Michael.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Leap:15.2 have been failing to build for at
least 4 weeks. We tried to send out notifications to the
configured bugowner/maintainers of the package(s), but so far no
fix has been submitted. This probably means that the
maintainer/bugowner did not yet find the time to look into the
matter and he/she would certainly appreciate help to get this
sorted.
- nut
Unless somebody is stepping up and submitting fixes, the listed
package(s) are going to be removed from openSUSE:Leap:15.2.
Kind regards,
openSUSE release team <opensuse-releaseteam(a)opensuse.org>
Dear Package maintainers and hackers.
Below package(s) in openSUSE:Factory have been failing to build for at
least 4 weeks. We tried to send out notifications to the
configured bugowner/maintainers of the package(s), but so far no
fix has been submitted. This probably means that the
maintainer/bugowner did not yet find the time to look into the
matter and he/she would certainly appreciate help to get this
sorted.
- archivemail
- cram
- dee
- geda-gaf
- libayatana-appindicator
- libunity
- mailnag
- marisa
- python-Pweave
- python-jupyter-packaging
- python-jupyter_console
- python-suds-jurko
- python-volatility
- python-xyzpy
- sc-controller
- treeline
- unity-gtk-module
- uwsgi
- vpp
- xzgv
- zramcfg
Unless somebody is stepping up and submitting fixes, the listed
package(s) are going to be removed from openSUSE:Factory.
Kind regards,
DimStar / Dominique Leuenberger <dimstar(a)opensuse.org>
N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�