Hi,
I found a quite interesting tool called Overcommit [1].
It provides an easy way for setting up Git commit hooks and provides
some basic checking plugins.
The nice feature of the Git commit hooks is that you can run some checks
automatically and early in the development. For example with the commit hooks you can
run Rubocop check automatically whenever a commit is created. And if the check fails
the commit is not created.
I can see "make Rubocop happy" commits quite often (happens to me as well),
with Overcommit you can easily avoid that.
I have tried several Overcommit checks:
- Rubocop - runs Rubocop at "commit"
- Rspec - runs the tests before "push"
- Branch blacklist - can forbid direct commits to configured branches,
e.g. "master" (forces using pull requests, avoids commits to master my mistake)
- Commit message spellcheck - warns when there is a possible typo
Check my blog post [2] for the details, esp. watch the recorded screencast where
I wanted to show some mistakes which it can catch.
The tool looks promising, I'll try using it for some time. If you want to try it
as well check the blog post for the installation steps.
Enjoy!
[1] https://github.com/brigade/overcommit
[2] http://blog.ladslezak.cz/2016/06/06/overcommit/
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
some time ago we discussed where and how we should share
"Tips&Tricks" for YaST users and developers.
IIRC there was no clear conclusion so I decided to start
a wiki [1] to collect all our tricks we know or use.
For now it's just a place for dumping your ideas, links, short
howtos, etc... When we collect enough data we can probably
split it to several categories or move it somewhere else.
We just need the data first.
I have added there some my tricks from my personal "knowledgebase"
file. If you have better tricks or find something wrong simply
change it, it's a wiki ;-)
Ladislav
[1] https://github.com/yast/yast.github.io/wiki/YaST-Tips-and-Tricks
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
please add the new YaST package yast2-usbauth from
https://github.com/kochstefan/yast-usbauth or
https://build.opensuse.org/package/show/home:kochstefan/yast2-usbauth to
openSUSE Tumbleweed.
This work was initially created for SUSE in 2015. Part of it was the USB
interface authorization for the Linux kernel. It's contained in Linux
since kernel version 4.4. The packages libusbauth-configparser, usbauth
and usbauth-notifier are already part of openSUSE Tumbleweed.
packages from the usbauth development:
- libusbauth-configparser is a library that is used to parse the usbauth
config file.
- usbauth is a firewall against BadUSB attacks. It allows/denies USB
interfaces using a config file. The needed USB interface authorization
is part of Linux 4.4 and newer.
- usbauth-notifier is a graphical notifier for user interaction to allow
or deny USB devices.
- yast2-usbauth: is a YaST module to edit the usbauth configuration file
Thank you.
Best regards
Stefan Koch
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet.
Pending requests in repository yast-bootloader:
- patch to not show popup when editenv list failed (73 days)
https://github.com/yast/yast-bootloader/pull/537
- [no merge] More logging sle12 (160 days)
https://github.com/yast/yast-bootloader/pull/523
Pending requests in repository yast-devtools:
- [RFC] Update the Rubocop config to version 0.59.2 (28 days)
https://github.com/yast/yast-devtools/pull/134
ERROR: API query limit exceeded
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Forwarding this message from the Factory mailing list since it contains
some interesting feedback about how YaST handles the conflicts reported
by libzypp.
On 11/22/18 6:51 PM, Brüns, Stefan wrote:
> On Donnerstag, 22. November 2018 17:35:20 CET Ludwig Nussel wrote:
>> Am 20.11.18 um 18:04 schrieb Brüns, Stefan:
>>> On Dienstag, 20. November 2018 17:36:10 CET Ancor Gonzalez Sosa wrote:
>>>> YaST development keeps rolling. Check the latest report at
>>>> https://lizards.opensuse.org/2018/11/20/yast-sprint-67/
>>>
>>>> with a lot of information about new features in the installer, like:
>>> [...]
>>>
>>>> - Easing the network configuration and the usage of online
>>>>
>>>> repositories in openSUSE.
>>>
>>> -- Tumbleweed: Add Online Repositories during Installation --
>>>
>>> Is it also possible to add community repos (e.g. packman) during the
>>> installation? This would avoid the repeated confirmation for repository
>>> changes for all the affected packages, which can be a lot.
>>
>> That is not the goal. The feature is more useful for Leap anyways
>> where the update repo may be included during installation already to
>> avoid having to download packages twice. Once the original from the
>> release and then again an updated one.
>> Anways, why does Packman replace lots of packages? I thought it
>> mostly adds supplemental packages?
>
> This is not always possible. For gstreamer, addon packages are used, but e.g.
> the ffmpeg libraries (libavcoded, libavutil, libavdevice ...) are monolitic
> and have to be exchanged.
>
> E.g. the vlc-codecs package requires libavcodec<version>(unrestricted), which
> is only provided by the libavcodec package from packman. When the packman repo
> is added after some of the ffmpeg libraries have been installed, this leads to
> a vendor change.
>
> The current conflict resolution dialog is not very user friendly, but quite
> low level (and it even has an "Expert mode" button on top).
>
> One problem is the grouping of conflicts (in Yast), each conflict has to be
> solved indiviually, although the solution may be the same for all (in this
> case, a vendor change). One can avoid solving some of the conflicts by
> selecting a solution for one conflict and clicking "Ok - retry", but thats not
> very intuitive.
>
> If the dialog instead stated:
> ---
> Warning - for installing "vlc-codecs" from "packman", some of your currently
> installed packages have to be replaced with packages from the "packman"
> repository.
>
> Following packages needs to be replaced:
> - libavcodec57
> - libavdevice57
> ...
>
> [x] Show details
>
> [Allow replacement] [Expert mode] [Cancel]
> ---
> it would be much more comprehensible for beginners.
>
> Expert mode could show the current dialog. "Show details" would show e.g.
> versions, repository URLs. Allow replacement would rerun the solver with the
> accepted changes, and eventually show the next conflict.
>
> Prerequisite for using/showing the dialog would be existance of a common
> conflict resolution. But a required vendor change is the conflict resolution
> which I have seen most often, and which is typically the wanted one (On TW,
> there is the occasional package downgrade, or an incomplete package rename -
> missing provides/obsoletes - but these are very seldom).
The idea of grouping conflicts to not have to reply the same over and
over makes sense. We can claim YaST is not the right place for such
grouping, that it should come from libzypp. But maybe there is something
we can do about it, like an "apply same decision" checkbox. I don't know.
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet.
Pending requests in repository yast-bootloader:
- patch to not show popup when editenv list failed (72 days)
https://github.com/yast/yast-bootloader/pull/537
- [no merge] More logging sle12 (159 days)
https://github.com/yast/yast-bootloader/pull/523
Pending requests in repository yast-devtools:
- [RFC] Update the Rubocop config to version 0.59.2 (27 days)
https://github.com/yast/yast-devtools/pull/134
Pending requests in repository yast-installation:
- Demo: eager mode of zombie-killer 0.5 (17 days)
https://github.com/yast/yast-installation/pull/761
- Sp4 merge (179 days)
https://github.com/yast/yast-installation/pull/708
ERROR: API query limit exceeded
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org