profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/shibumi/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Christian Rebischke shibumi @archlinux Germany https://shibumi.dev Site Reliability Engineer and member of Arch Linux Security Team and Arch Linux Trusted User

archlinux/arch-boxes 147

Arch-boxes provides automated builds of the Arch Linux releases for different providers and post-processors (read-only mirror)

in-toto/in-toto-golang 17

A go implementation of in-toto verifylib

shibumi/cifs-exporter 8

SMB/CIFS Prometheus Exporter

shibumi/batteryd 7

The smallest battery daemon ever!

kgizdov/arch-installer 3

WIP: An installer for Arch Linux

shibumi/Arch-Linux-Catapult 3

Arch Linux Catapult (ALC) catapults your favourite Arch Linux image on your machine

shibumi/bachelor-thesis 2

My bachelor-thesis at TU Clausthal

shibumi/ansible-systemd-conf 1

Ansible role to setup systemd configs, networkd, timers and more

shibumi/aoc2019 1

Advent of Code 2019

shibumi/bachelor-kolloquium 1

The slides for my bachelor defense

issue commentvoxpupuli/puppet-corosync

Next tag after v6.0.1 ??

@igalic The initial question is now outdated (since 7.0.0 is already released), but in the meantime a new release would be great. What can we non-members to to get a release?

rgmoises

comment created time in an hour

PR opened voxpupuli/puppet-corosync

Enable Puppet 7 support enhancement

<!-- Thank you for contributing to this project!

  • This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
  • Please check that here is no existing issue or PR that addresses your problem.
  • Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

Pull Request (PR) description

<!-- Replace this comment with a description of your pull request. -->

This Pull Request (PR) fixes the following issues

<!-- Replace this comment with the list of issues or n/a. Use format: Fixes #123 Fixes #124 -->

+1 -1

0 comment

1 changed file

pr created time in 3 hours

PR merged voxpupuli/puppet-corosync

Drop Puppet 5 support; require Puppet 6.1.0 backwards-incompatible

<!-- Thank you for contributing to this project!

  • This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
  • Please check that here is no existing issue or PR that addresses your problem.
  • Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

Pull Request (PR) description

<!-- Replace this comment with a description of your pull request. -->

This Pull Request (PR) fixes the following issues

<!-- Replace this comment with the list of issues or n/a. Use format: Fixes #123 Fixes #124 -->

+2 -9

1 comment

3 changed files

bastelfreak

pr closed time in 3 hours

push eventvoxpupuli/puppet-corosync

Tim Meusel

commit sha e2dd25ebb75d9163822b39c435d23c1ada12e8a3

Drop Puppet 5 support; require Puppet 6.1.0

view details

Tim Meusel

commit sha ee5ea0ae00769a9ad50947a7f434289c38c688ac

Merge pull request #501 from bastelfreak/puppet5 Drop Puppet 5 support; require Puppet 6.1.0

view details

push time in 3 hours

startednetlify/netlify-cms

started time in 4 hours

startedtidyverse/dplyr

started time in 5 hours

startedhadley/plyr

started time in 5 hours

Pull request review commentvoxpupuli/puppet-corosync

Drop Puppet 5 support; require Puppet 6.1.0

       end        # Binary() behaves different in Puppet 5 and 6

This comment is no longer relevant

bastelfreak

comment created time in 7 hours

Pull request review commentvoxpupuli/puppet-corosync

Drop Puppet 5 support; require Puppet 6.1.0

       end        # Binary() behaves different in Puppet 5 and 6-      let(:expected_content) { facts[:puppetversion].to_i >= 6 ? "mysecretkey\n" : 'bXlzZWNyZXRrZXkK' }+      let(:expected_content) { "mysecretkey\n" }

It's only used once. Perhaps put it inline?

bastelfreak

comment created time in 7 hours

pull request commentvoxpupuli/puppet-corosync

Drop Puppet 5 support; require Puppet 6.1.0

puppet 7 support will be added in another PR

bastelfreak

comment created time in 9 hours

PR opened voxpupuli/puppet-corosync

Drop Puppet 5 support; require Puppet 6.1.0 backwards-incompatible

<!-- Thank you for contributing to this project!

  • This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
  • Please check that here is no existing issue or PR that addresses your problem.
  • Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

Pull Request (PR) description

<!-- Replace this comment with a description of your pull request. -->

This Pull Request (PR) fixes the following issues

<!-- Replace this comment with the list of issues or n/a. Use format: Fixes #123 Fixes #124 -->

+1 -5

0 comment

2 changed files

pr created time in 9 hours

push eventvoxpupuli/puppet-corosync

Damian Lukowski

commit sha 37d0c043706af0d0e4082a3eaf653c202a0a08bd

Pre-realign parameters

view details

Damian Lukowski

commit sha de92e0506de10dc591b1fdd789a47d0fe2c2d6cf

Add possibility to define watchdog_device resource

view details

dlucredativ

commit sha 2be23c6960d67c9832f54306b771093b3dee2719

Apply suggestions from code review Co-authored-by: Ewoud Kohl van Wijngaarden <ewoud@kohlvanwijngaarden.nl>

view details

Ewoud Kohl van Wijngaarden

commit sha 9bef54358c920cb33a35e95979dd77d9bf919a8b

Merge pull request #454 from dlucredativ/master Add possibility to define watchdog_device resource

view details

push time in 10 hours

PR merged voxpupuli/puppet-corosync

Add possibility to define watchdog_device resource enhancement

This pull request allows to define a watchdog_device resource for corosync.

In early corosync versions, watchdog usage had to be explicitly turned off via the "off" keyword, while in recent versions its usage needs to be explicitly turned on via the device name e.g. "/dev/watchdog". Hence an Optional[String] seems a better choice than a Boolean.

Related to https://github.com/voxpupuli/puppet-corosync/pull/451

+97 -68

14 comments

3 changed files

dlucredativ

pr closed time in 10 hours

pull request commentvoxpupuli/puppet-corosync

Add possibility to define watchdog_device resource

Merging now that CI has completed. Thanks!

dlucredativ

comment created time in 10 hours

pull request commentvoxpupuli/puppet-corosync

Add possibility to define watchdog_device resource

@ekohl do you prefer your suggestions to remain in a separate commit or should I fixup them into de92e050?

dlucredativ

comment created time in 11 hours

Pull request review commentvoxpupuli/puppet-corosync

Add possibility to define watchdog_device resource

 #   Whether we should test new configuration files with `corosync -t`. #   (requires corosync 2.3.4) #+# @param watchdog_device+#   Watchdog device to use, for example '/dev/watchdog' or 'off'.+#   Its presence (or lack thereof) shifted with corosync versions.+#   Default: undef

Nit: we don't document defaults since puppet-strings can figure that out already

dlucredativ

comment created time in 11 hours

Pull request review commentvoxpupuli/puppet-corosync

Add possibility to define watchdog_device resource

 nodelist { } <% end -%> <% end -%>++<% unless @watchdog_device.nil? -%>

If you write it like this, there is no diff for existing users when they don't use a watchdog device:

<% unless @watchdog_device.nil? -%>

I'm not sure if that diff shows up well, but the idea is to include the empty line inside the block.

dlucredativ

comment created time in 11 hours

Pull request review commentvoxpupuli/puppet-corosync

Add possibility to define watchdog_device resource

       end     end +    context 'with undefined watchdog_device' do+      it 'does not configure watchdog_device resource' do+        is_expected.to contain_file('/etc/corosync/corosync.conf').without_content(+          %r{watchdog_device:}+        )+      end+    end++    context 'with defined watchdog_device' do+      before do+        params.merge!(+          watchdog_device: 'off'+        )+      end

This is a bad practice and it's better to override it like this:

      let(:params) { super().merge(watchdog_device: 'off') }
dlucredativ

comment created time in 11 hours

created tagarchlinux/archlinux-docker

tagv20210302.0.16468

Docker Base Image for Arch Linux (read-only mirror)

created time in 11 hours

push eventarchlinux/archlinux-docker

Arch Linux Docker release bot

commit sha 9f0020e4a5d45b90700a7fbe83b3eafb2239156d

Release 20210302.0.16468

view details

push time in 11 hours

issue commentnspawn/mkosi-definitions

Add a standard --root-size value (maybe 2GB?) to all mkosi default files

This was fixed in https://github.com/systemd/mkosi/pull/462

q2dg

comment created time in 12 hours

fork Edu4rdSHL/mkosi

Build Legacy-Free OS Images

fork in 12 hours

pull request commentvoxpupuli/puppet-corosync

Add possibility to define watchdog_device resource

Thanks @dlucredativ, that was fast!

@ekohl Can this be merged and released now?

dlucredativ

comment created time in 12 hours

issue commentnspawn/mkosi-definitions

Add a standard --root-size value (maybe 2GB?) to all mkosi default files

Hello, I've checked the ArchLinux raw image today and I can't reproduce this issue as all raw images are created with a 2.9G root size by default. When I import and boot the image, I got:

archlinux login: root
Password: 
Last login: Tue Mar  2 03:09:29 on pts/0
[root@archlinux ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop0p2    2.9G  732M  2.1G  27% /
/dev/loop0p1    253M   39M  214M  16% /efi
tmpfs           3.2G     0  3.2G   0% /tmp
tmpfs           4.0M     0  4.0M   0% /dev
tmpfs           3.2G     0  3.2G   0% /dev/shm
tmpfs           6.3G   64K  6.3G   1% /run
/dev/nvme0n1p5   98G   22G   72G  24% /run/host/os-release
run              16G  1.4M   16G   1% /run/host/incoming
tmpfs           3.2G     0  3.2G   0% /run/user/0

and I can also install packages as well:

[root@archlinux ~]# pacman -Syu pacman-contrib
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (5) db-5.3.28-5  fakeroot-1.25.3-2  gdbm-1.19-2  perl-5.32.1-1
             pacman-contrib-1.4.0-1

Total Download Size:   16.53 MiB
Total Installed Size:  64.90 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 fakeroot-1.25.3-...    70.7 KiB  1178 KiB/s 00:00 [######################] 100%
 gdbm-1.19-2-x86_64    210.7 KiB  2.29 MiB/s 00:00 [######################] 100%
 db-5.3.28-5-x86_64   1098.0 KiB  2.02 MiB/s 00:01 [######################] 100%
 perl-5.32.1-1-x86_64   15.1 MiB  3.70 MiB/s 00:04 [######################] 100%
 pacman-contrib-1...    37.7 KiB  3.68 MiB/s 00:00 [######################] 100%
(5/5) checking keys in keyring                     [######################] 100%
(5/5) checking package integrity                   [######################] 100%
(5/5) loading package files                        [######################] 100%
(5/5) checking for file conflicts                  [######################] 100%
(5/5) checking available disk space                [######################] 100%
:: Processing package changes...
(1/5) installing fakeroot                          [######################] 100%
(2/5) installing gdbm                              [######################] 100%
(3/5) installing db                                [######################] 100%
(4/5) installing perl                              [######################] 100%
(5/5) installing pacman-contrib                    [######################] 100%
Optional dependencies for pacman-contrib
    findutils: for pacdiff --find [installed]
    mlocate: for pacdiff --locate
    sudo: privilege elevation for several scripts
    vim: default merge program for pacdiff
:: Running post-transaction hooks...
(1/3) Reloading system manager configuration...
(2/3) Arming ConditionNeedsUpdate...
(3/3) Warn about old perl modules
[root@archlinux ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop0p2    2.9G  820M  2.0G  30% /
/dev/loop0p1    253M   39M  214M  16% /efi
tmpfs           3.2G     0  3.2G   0% /tmp
tmpfs           4.0M     0  4.0M   0% /dev
tmpfs           3.2G     0  3.2G   0% /dev/shm
tmpfs           6.3G   64K  6.3G   1% /run
/dev/nvme0n1p5   98G   22G   72G  24% /run/host/os-release
run              16G  1.4M   16G   1% /run/host/incoming
tmpfs           3.2G     0  3.2G   0% /run/user/0

same with Debian:

Debian GNU/Linux 10 buster console

buster login: root
Password: 
Linux buster 5.11.2-128-tkg-MuQSS #1 TKG SMP PREEMPT Sun, 28 Feb 2021 17:05:15 +0000 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@buster:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop0p1    2.9G  200M  2.6G   8% /
tmpfs           3.2G     0  3.2G   0% /tmp
tmpfs           4.0M     0  4.0M   0% /dev
tmpfs           3.2G     0  3.2G   0% /dev/shm
tmpfs           6.3G   68K  6.3G   1% /run
/dev/nvme0n1p5   98G   22G   72G  24% /run/host/os-release
run              16G  1.4M   16G   1% /run/host/incoming
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           3.2G     0  3.2G   0% /run/user/0

@shibumi can you confirm if what I just wrote is what the issue was referring to?

q2dg

comment created time in 12 hours

startedfgsect/BaseSAFE

started time in 17 hours

startedoantolin/orderless

started time in 17 hours

startedoantolin/embark

started time in 17 hours

startedwolfSSL/wolfssl

started time in 18 hours