profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/juhp/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.
Jens Petersen juhp Red Hat Singapore

haskell/cabal 1287

Official upstream development repository for Cabal and cabal-install

gelisam/hawk 320

Haskell text processor for the command-line

juhp/cabal-rpm 25

Haskell Cabal RPM packaging tool

fpco/stackage-curator 10

DEPRECATED Tools for curating Stackage package sets and building reusable package databases

jamesni/zanata-python-client 6

a python client for Flies server

juhp/aeson 1

A fast Haskell JSON library

juhp/barley 1

Get going with Haskell ASAP

juhp/bodhi-cli 1

Bodhi CLI client outputing JSON

juhp/bodhi-hs 1

Fedora Bodhi REST client library

juhp/cabal 1

Official upstream development repository for Cabal and cabal-install

issue commenthaskell/haskell-language-server

ghc support deprecation schedule

Just for reference these are the versions of ghc in some current Linux distro releases:

Arch: 8.10.5 Debian: 8.8.4 Fedora: 8.8.4 (devel has 8.10.5) Manjaro: 8.10.5 openSUSE: 8.10.4 Ubuntu: 8.8.4

jneira

comment created time in 15 minutes

GollumEvent

startedpodenv/podenv

started time in 6 hours

issue commentcommercialhaskell/stackage

miso 1.8.0.0

I don't think jsaddle has been in for quite a while... I am not the maintainer though.

alexeyzab

comment created time in a day

issue commentfedora-silverblue/issue-tracker

[RFE] add open SSL to the base system

Do you mean /usr/bin/openssl?

allaeddineomc

comment created time in a day

CommitCommentEvent

push eventjuhp/beginning-rust-programming

Jens Petersen

commit sha 54bf593a1377817bcbd97dd23c9080728f58cb2f

ch5: cargo.lock

view details

Jens Petersen

commit sha e71b86d24be6c90e78381aafa262488dce7130fa

ch6: if let for conn.write

view details

Jens Petersen

commit sha 2a0ee65bcfccc1a556b529d4696d5f51ee3935c4

ch6: use iterator in get_file_list

view details

Jens Petersen

commit sha 86f2f96605babf8e9844306767f710e878d8897e

ch6: handle_req use BufStream like book

view details

push time in a day

push eventjuhp/beginning-rust-programming

Jens Petersen

commit sha 2d753bb6eec14f796a48df6079d773d7b94fb794

ch6: fixup handle_req warnings about initial unread response also clippy drop final borrow for write

view details

Jens Petersen

commit sha 31fd06611d7f0ce93a462a634d3731be09353a8e

ch6: rustfmt

view details

push time in 2 days

push eventjuhp/get-programming-with-haskell

Jens Petersen

commit sha 7d72a45bc55721e77881f8f60ed65bd9b8ec3ffd

unit2 crypto capstone

view details

Jens Petersen

commit sha bfba7e998a63dc1968ad54968b6c821c0f673fe9

Bits: use Word to avoid negative Int's They do not terminate

view details

push time in 2 days

PR opened containers/toolbox

create: always offer to pull and don't mention 500MB

This PR addresses 2 common user issues with toolbox create:

  • users need to manually download newer images themselves
  • the hardcoded "500MB download" is misleading

I have tested this locally and it seems to work okay for me.

+4 -6

0 comment

1 changed file

pr created time in 3 days

push eventjuhp/toolbox

Jens Petersen

commit sha 89596de727b965e3325181966505f8577211a6e3

create: always offer to pull latest image (fixes: #873)

view details

Jens Petersen

commit sha 7e0cede1e5a3d3c8b4dc1984fbb28c8b88c869af

create: drop mention of "500MB" (#752) The download in particular and diskspace are less.

view details

push time in 3 days

push eventjuhp/skopedate

Jens Petersen

commit sha 5cecae4acf3cdd5368e8c520fa819b711763c490

update .cabal to latest hkgr

view details

Jens Petersen

commit sha a45e65daf16b9eb77e8d59c403680385fb3dd53c

qualify Data.List

view details

Jens Petersen

commit sha 5bc4ff4fa883aca87fa6984eb1e96ce4b1e869da

pad fedora container rel

view details

push time in 3 days

delete branch juhp/toolbox

delete branch : master

delete time in 3 days

push eventjuhp/toolbox

Ondřej Míchal

commit sha 259afdf815e718b76872a217f784a94e5640c30b

test/system: Adjust asserts for broken test The output of `podman build` has changed a bit. Each line of log describing the build is now in the format of: - STEP i/n: msg instead of: - STEP i: msg where i is the current step and n the maximum number of steps. The exact format is not important for the purpose of testing Toolbox, so we may fallback to partial string testing. Also the latest step ("COMMIT") seems to no longer be considered a step, so just check for the word. https://github.com/containers/toolbox/pull/846

view details

Oliver Gutierrez

commit sha 1f0c6d51002e5d0d39c5da5c0cb945ed44c1634c

tests: Added a verbose test for container starting https://github.com/containers/toolbox/pull/831

view details

Ondřej Míchal

commit sha d9147fff8c8fbf68df111a931e618cc45f90c342

pkg/utils: Streamline functions https://github.com/containers/toolbox/pull/847

view details

Ondřej Míchal

commit sha 16b0c5d88fcc404d52c6e37a7f46bd430b352369

test/system: Check whole lines instead of partials The 'toolbox run' command has one downside: all newlines contain a carriage return (CR). This is caused by the unconditional use of the --tty option in `podman exec`[0]. In these particular tests this can be worked around by not printing a newline at all. Another quirk around partial is to check the last line of the output. [0] https://github.com/containers/podman/issues/9718 https://github.com/containers/toolbox/pull/843

view details

Ondřej Míchal

commit sha 6c2cd0e929208c2c58e03992cd33f599a544a956

test/system: Drop hack around unknown dirs in containers This hack should not be needed since v0.0.99.2[0]. [0] https://github.com/containers/toolbox/releases/tag/0.0.99.2 https://github.com/containers/toolbox/pull/843

view details

Jens Petersen

commit sha d9945a650558af69e4fad063595400cf727b1ab6

utils: bump the fallback Fedora version to 34 https://github.com/containers/toolbox/pull/845

view details

Ondřej Míchal

commit sha 2594199fef5ff593c91f3f35c0f310d43d64937a

test/system: Track bats libs as submodules & install them better This will make it easier to work with system tests. https://github.com/containers/toolbox/pull/842

view details

Ondřej Míchal

commit sha 0ff01977d690cbd37cf05d476911953f296d740b

playbooks: Stop cloning bats libraries The libraries are now provided as submodules. There's no need to clone them separately. https://github.com/containers/toolbox/pull/842

view details

Ondřej Míchal

commit sha b0beb68255374392d0ba10a3d36ccf6be1a948c0

test/system: Fix flaky test This is a naive attempt to solve the flaking. It could be caused by what is going inside of the run function.

view details

Debarshi Ray

commit sha 6a37695086c176ed0449209c15e64ce116e63253

pkg/utils: Mark a private function as such Figuring out the default toolbox image for a given distribution only needs to happen as part of resolving the final toolbox image name from the given command line options. Fallout from c990fb43cad5f1704584f119ba4f57074c1d0bc9 https://github.com/containers/toolbox/pull/828 https://github.com/containers/toolbox/pull/851

view details

Debarshi Ray

commit sha 5824f0adcbb3e7e184a6cec979f4d2253ac083ff

cmd/create, pkg/utils: Simplify hint after creating a container A subsequent commit will add support for configuration files, which can override the default toolbox image. Since this override affects all commands, it effectively ends up adding a fourth option to the 'enter' command, other than the existing options to change the distribution, release and container. This makes it a lot more difficult to reason when only 'toolbox enter --release N' is enough to enter the created container. https://github.com/containers/toolbox/pull/828 https://github.com/containers/toolbox/pull/851

view details

Ondřej Míchal

commit sha ffdfaa74100615713d2f99f66f0d6a4da703272d

data/config: Add reference configuration file The file format is TOML[0] but the file extension is .conf to follow the convention set by Podman. https://github.com/containers/toolbox/pull/828 https://github.com/containers/toolbox/pull/851

view details

Ondřej Míchal

commit sha 20f4f68c4e015f4943148979a9a0ebb0bfff1cb3

cmd/root, pkg/utils: Add support for configuration files It looks like there are some oddities with Viper [1]. The errors can't be examined with errors.As [2] and Viper doesn't actually throw ConfigFileNotFoundError if a configuration file is not found. Secondly, there's no way to find out if a key was actually specified in a configuration file. The InConfig API doesn't return 'true' even if a key was mentioned in a configuration file, and the IsSet API returns 'true' even if the key was only set via SetDefault in the code. Some changes by Debarshi Ray. [1] https://pkg.go.dev/github.com/spf13/viper [2] https://blog.golang.org/go1.13-errors https://github.com/containers/toolbox/pull/828 https://github.com/containers/toolbox/pull/851

view details

Debarshi Ray

commit sha 660b6970e99873f713e2d0eb7d5c6f8b2d6113e2

cmd/create: Mention that private images require 'podman login' It's not possible to programmatically detect when an image requires logging into the registry [1]. Therefore, instead of trying to handle 'podman pull' failures due to lack of authorization, just mention that private images require 'podman login' and that further details of the failure can be found by using the --verbose option. [1] https://github.com/containers/podman/issues/10858 https://github.com/containers/toolbox/issues/754 https://github.com/containers/toolbox/pull/852

view details

Ondřej Míchal

commit sha 9820550c82bba5e71ebc799892f3c99b1ed7879d

test/system: Use BATS_RUN_TMPDIR for image cache Using the current working directory for cache is not a good solution since the test files may reside in a location that is unwritable (e.g., /usr/share). The `BATS_RUN_TMPDIR` variable should point to a location that is sure to be writeable from the test suite. https://github.com/containers/toolbox/pull/850

view details

Ondřej Míchal

commit sha 04c673dd06056630a957fc776739da9fb0eef80b

test/system: Test pull failure Follow-up to https://github.com/containers/toolbox/pull/852 https://github.com/containers/toolbox/pull/854

view details

Oliver Gutierrez

commit sha 09fb2377272b196f6422f85f54ea2c60be474c22

tests: Changed container image source for busybox Due to docker rate limiting we can not rely in docker.io for retrieving the images. This was detected when executing our tests for podman fedora gating pipeline. Our busybox image was not downloaded and one of the list tests was failing.

view details

Oliver Gutierrez

commit sha 075b9a8d27792944e76361404293da4a44d5e2f5

tests: Fix tests to setup the XDG_RUNTIME_DIR variable when empty https://github.com/containers/toolbox/pull/857 When the XDG_RUNTIME_DIR variable is empty toolbox is not able to initialize the container correctly and fails to run.

view details

Alex Jia

commit sha 26ae0bb8960b25d3e9b141ef87dcc5dbf4216bd7

test/system: fix typo in 102-list.bats Signed-off-by: Alex Jia <chuanchang.jia@gmail.com>

view details

push time in 3 days

push eventjuhp/toolbox

Debarshi Ray

commit sha f16b408cadeef6e43dd9722350397c1313267738

Use variables to refer to the profile.d-toolbox.lock file https://github.com/debarshiray/toolbox/issues/196

view details

Debarshi Ray

commit sha 0db54946b43e04023134f6381b97b768894bfef0

Don't use 'podman cp' to copy toolbox.sh to old containers Copying files into a running container is considered inherently hacky. Rootful Podman can pause a container using 'podman cp --pause ...' during the copy, but that's not possible when used rootless. Secondly 'podman cp' has suffered from a series of regressions lately. First there was the problem with how the --pause flag was handled [1], and then /etc/profile.d/toolbox.sh was getting created as a directory [2], not regular file, by: $ podman cp \ --pause=false \ /etc/profile.d/toolbox.sh \ "$container":/etc/profile.d Try to side-step all that by using $XDG_RUNTIME_DIR as a conduit to share the file with the container and using plain cp(1) to place it in the toolbox container's /etc/profile.d. [1] Commit e715ff2f9b231271 https://github.com/debarshiray/toolbox/pull/193 [2] https://github.com/containers/libpod/issues/3384 https://github.com/debarshiray/toolbox/issues/196

view details

Debarshi Ray

commit sha 5601bb48e5f453aeca691945bc018180929eedb8

Create /run/.toolboxenv inside the toolbox container's entry point too Creating /run/.toolboxenv in run(), outside the entry point, has the advantage of automatically working with older toolbox containers. However, at some point those containers are going to get end-of-lifed. Then it would be nice to have this bit of initialization tucked away inside the entry point. https://github.com/debarshiray/toolbox/pull/206

view details

Debarshi Ray

commit sha adbb9f90fd7b6cdf722daf58caae37dd2bfc33fc

Tweak the debug output

view details

Debarshi Ray

commit sha 4ab9c2e3153f8cbcd4adee51ed16f98992a2d59b

Make it easier to debug the 'toolbox init-container' entry point This makes it easier to follow what the 'toolbox init-container' entry point is doing. https://github.com/debarshiray/toolbox/pull/207

view details

Debarshi Ray

commit sha 049bb92e64427c759e002c53137a6d3ed569cb05

Unbreak /etc/localtime & /etc/timezone if /run/host/monitor is absent Toolbox containers created prior to commit 8db414ddc2d73719 didn't have /run/host/monitor inside them. Therefore, those containers were having their /etc/localtime and /etc/timezone redirected to locations that didn't exist. Instead of selectively checking locations that were added later, it's more manageable to handle all bind mounted target locations the same. https://github.com/debarshiray/toolbox/pull/207

view details

Colin Walters

commit sha e8f72f1e76bdfa943c6b0bef19c8a81380ce1954

Drop the "immutable" term I'm still waging a fight against this. Please stop saying "immutable" for this, it's more misleading than useful. Previously e.g. https://github.com/debarshiray/toolbox/pull/43 https://github.com/debarshiray/toolbox/pull/221

view details

Debarshi Ray

commit sha c8aba029a3519d5e5aafe107d29178f73d353662

Prepare 0.0.12

view details

Debarshi Ray

commit sha 0dee71b13f71fca9a37c1595f73a71727cafb67f

images: Drop PackageKit-command-not-found It connects to the host's PackageKit instance, and tries to install the packages on the host instead of inside the toolbox container. Remove it unless there's a proper solution. https://github.com/debarshiray/toolbox/issues/158

view details

Michael Nguyen

commit sha c6e37cdef37e2276207b34a42919f1e0ac4a04dc

profile.d: Tighten the Silverblue check The Silverblue welcome message was being displayed incorrectly on other OSTree based OS's (Fedora Atomic Host, Fedora CoreOS, etc). Note that none of the stable Silverblue releases that have shipped so far (ie., until Silverblue 30) have had 'silverblue' as the VARIANT_ID. This makes the check a bit more convoluted that it should have been. https://github.com/debarshiray/toolbox/pull/236

view details

Harry Míchal

commit sha 6b8593ec1dd2220563866469fa53610e343d6a29

doc/toolbox: Shorten the description of the --verbose flag https://github.com/debarshiray/toolbox/pull/200

view details

Harry Míchal

commit sha 5e63e9ec9bc420da3ba766494d23cc032cf317da

Improve the help or usage output A new help command has been added which either shows the toolbox(1) manual or a manual page for a specific command. The '--help' flag is now identical to the help command and can be placed after the COMMAND segment in the list of command line arguments. Due to a bizarre quirk in less(1) [1], the default pager used to render manuals on most systems, the man(1) invocations need the standard error stream to point to the controlling terminal, if any, to work. This interferes with the global redirection of standard error to /dev/null in the absence of the '--verbose' flag, and is worked around by redirecting to standard output instead. [1] It turns out that less(1) tries to open the controlling terminal device /dev/tty to get to the keyboard for accepting input. However, it doesn't have a controlling terminal when invoked via D-Bus to render a manual on the host. It then strangely falls back to using the standard error stream to get to the keyboard. https://github.com/debarshiray/toolbox/pull/200

view details

Dusty Mabe

commit sha f1524260eb5278c2e3df3f9f06c9c8a43eab89e9

Simplify code by taking advantage of 'podman create --userns=keep-id' This lets podman do the calculations for mapping the host UID into the user namespace within the container. See cfcf4eb31e14b3a3 for original context. The '--userns=keep-id' option was introduced in Podman 1.4.0, which is old enough to be in even RHEL 7. https://github.com/debarshiray/toolbox/issues/244

view details

Debarshi Ray

commit sha 20dcd81d12f574f75dab577f841c5d2fd5c2313d

Simplify code by taking advantage of 'podman exec --workdir ...' The '--workdir ...' option was added to 'podman exec' in Podman 1.0.0, which is within the current minimum required Podman version of 1.4.0. https://github.com/debarshiray/toolbox/pull/254

view details

Debarshi Ray

commit sha cc448a2fb8c5f775b8cdb58b620b502feb2cfeac

Prepare 0.0.13

view details

Akira TAGOH

commit sha 05544fb2714ec096843129ceca2dc9e4860fb700

Work around 'podman exec' resetting the terminal size to 80x24 See: https://github.com/containers/libpod/issues/3946 COLUMNS and LINES may not be set in the user's environment. Hence the existing mechanism for preserving environment variables don't work. Note that for things to keep working when invoked via D-Bus from inside a toolbox container, the terminal size needs to be queried using the standard input stream, instead of explicitly mentioning the controlling terminal device /dev/tty. This is because stty(1) doesn't have the notion of a controlling terminal when invoked via D-Bus, but flatpak-spawn(1) ensures that the standard input stream still points to the user's interactive terminal. https://github.com/debarshiray/toolbox/issues/242

view details

Debarshi Ray

commit sha b2e3cbf661675352c0a4909c66e671be8b22137e

Give access to the system Flatpak directory This is helpful when running a development build of GNOME Shell from within a toolbox container. It enables populating the application grid with Flatpak applications installed system-wide on the host. https://github.com/debarshiray/toolbox/pull/256

view details

Debarshi Ray

commit sha 50432df0d63f1d33c898fa9cb3455613cba5e631

Give access to the system libvirt instance This is useful when the session libvirt instance doesn't offer all the bells and whistles needed for running virtual machines. https://github.com/debarshiray/toolbox/pull/257

view details

Debarshi Ray

commit sha 4f8759f759923998107dd096e5063e3f903040fd

Suppress error output unless --verbose is being used https://github.com/debarshiray/toolbox/pull/258

view details

Harry Míchal

commit sha 49163a89aab8dd9f415cd80fe8da961a90b761bd

Don't exit with a non-zero code from 'toolbox list -i' When listing only images, 'exit' was picking up the non-zero exit code from the following (failing) statement meant for containers. An explicit 'if' branch prevents the exit code of the condition from leaking out. Fallout from 5e4e63a11b21de97be65c4c7ec4a62c943084287 https://github.com/debarshiray/toolbox/pull/258

view details

push time in 3 days

push eventjuhp/hs-string-bench

Jens Petersen

commit sha 76e70ef79b70e1c5031fb143bc1248c0c5eca7a3

readme clarifications

view details

push time in 5 days

create barnchjuhp/hs-string-bench

branch : main

created branch time in 5 days

created repositoryjuhp/hs-string-bench

created time in 5 days

issue commentcontainers/toolbox

Invalid entrypoint on later versions of Toolbox

Can we add toolbox to fedora-toolbox??

So I tried this for fun actually: patched toolbox to not copy /usr/bin/toolbox into the toolbox container and created a localhost/fedora-toolbox:34 with toolbox preinstalled and it starts fine on F35! A gentler approach would be to not bind mount the host toolbox binary into the container if the file already exists.

Though I appreciate this is a tricky thing to bootstrap, while it looks like the right thing to do.

TheEvilSkeleton

comment created time in 5 days

issue commentcontainers/toolbox

Invalid entrypoint on later versions of Toolbox

I have been seeing this for quite a while too.

Can we add toolbox to fedora-toolbox??

TheEvilSkeleton

comment created time in 6 days

issue commentcontainers/podman

[RFE] Adding CI checks for toolbox in podman

fedora-toolbox:36 should in the stable fedora registry now.

travier

comment created time in 6 days

issue commentfjvallarino/monomer

install failure on mac m1

ghc-8.10.7 (lts-18.9) doesn't help enough, right?

simonmichael

comment created time in 6 days

issue openedcontainers/toolbox

always offer to pull latest image when creating a toolbox

Is your feature request related to a problem? Please describe. We frequently see bug reports caused by people having an old toolbox image cached locally.

Describe the solution you'd like toolbox create should either offer to pull or always pull down the latest image being requested . For extra points it could check if a newer image exists first.

Additional context I am imagining something like this:

$ toolbox create
A newer fedora-toolbox:34 image is available, do you want to download it? [Y/n]

I think this is the least surprising behavior (though personally I would always want to pull the latest image). A more conservative solution could be to add a --pull flag.

created time in 6 days

pull request commentcontainers/toolbox

images: Add Arch Linux image

Just for reference/FYI: https://github.com/toolbox-images/toolbox-images/tree/main/images/arch

erazemk

comment created time in 6 days

delete branch haskell/cabal

delete branch : juhp-patch-1

delete time in 6 days

pull request commenthaskell/cabal

cabal-install.cabal: use -fhide-source-paths for ghc-8.2+

I am going to try using the option for all Fedora builds.

juhp

comment created time in 6 days

PR closed haskell/cabal

cabal-install.cabal: use -fhide-source-paths for ghc-8.2+

This should only affect builds of cabal-install

+2 -0

2 comments

1 changed file

juhp

pr closed time in 6 days

issue commentcontainers/toolbox

Error: invalid entry point PID of container

There is a new candidate-registry.fedoraproject.org/fedora-toolbox:35 image now and also fedora-toolbox:36 finally.

kuba3351

comment created time in 7 days

PR opened haskell/cabal

cabal-install.cabal: use -fhide-source-paths for ghc-8.2+

This should only affect builds of cabal-install

+2 -0

0 comment

1 changed file

pr created time in 7 days

create barnchhaskell/cabal

branch : juhp-patch-1

created branch time in 7 days