Hey,

>Quoting Florian Klink (2025-01-21 13:17 CET):
>> I'm not sure it's feasible for you to appropriately maintain these
>> packages without using your GitHub account.
>>
>> People will open issues or PR, and probably expect you to give feedback
>> there.
>
>I'm in the process of detaching myself from GitHub.
>Is it possible to still contribute meaningfully to the nixpkgs repository
>without being present on that platform?

I don't think it's effectively possible, for the reasons mentioned

Hey euxane,

On Thu, Jan 16, 2025 at 11:34:00PM +0100, euxane wrote:
>This series adds a package for euporie (a program which allows editing and
>running Jupyter notebooks in the terminal) as well as a few other Python
>packages it depends on.
>
>    [PATCH 1/4] python3Packages.sixelcrop: init at 0.1.9
>    [PATCH 2/4] python3Packages.timg: init at 1.1.6
>    [PATCH 3/4] python3Packages.flatlatex: init at 0.15
>    [PATCH 4/4] python3Packages.euporie: init at 2.8.2

I'm not sure it's feasible for you to appropriately maintain these
packages without using your GitHub account.

Opened https://github.com/NixOS/nixpkgs/pull/366143.

Unfortunately, 4f0dadbf38ee4cf4cc38cbc232b7708fddf965bc did cause this
to apply only with conflicts. Can you send a v2?

Thanks,
flokli

On Thu, Dec 05, 2024 at 10:58:23PM +0100, euxane wrote:
>---
> maintainers/maintainer-list.nix                      | 12 ++++++------
> nixos/modules/programs/msmtp.nix                     |  2 +-
> .../services/backup/postgresql-wal-receiver.nix      |  2 +-
> nixos/modules/services/mail/stalwart-mail.nix        |  2 +-
> nixos/modules/services/matrix/appservice-discord.nix |  2 +-
> nixos/modules/services/matrix/mautrix-telegram.nix   |  2 +-

Don't know what your rebased against, certainly not after
0c00ad14acbef5f64476b473e9ba035ad504d3a1, but it still didn't apply.

I now manually applied the patch and sent out
https://github.com/NixOS/nixpkgs/pull/336704.

On Thu, Aug 22, 2024 at 01:28:15PM GMT, Adam Joseph wrote:
>Since version 2.0.0, proc-macro-crate has assumed it can exec()
>`env::var("CARGO")` in order to run `cargo locate-project`.
>
>This commit adds a crate override to proc-macro-crate which simply writes the
>path to buildPlatform.cargo into the proc-macro-crate sources.
>
>This way we don't need to set `env.CARGO` for every build that depends on

Hey,

On Mon, Aug 19, 2024 at 10:57:03AM GMT, Adam Joseph wrote:
>Since version 2.0.0, proc-macro-crate has assumed it can exec()
>`env::var("CARGO")` in order to run `cargo locate-project`.
>
>This commit adds a crate override to proc-macro-crate which simply writes the
>path to buildPlatform.cargo into the proc-macro-crate sources.
>
>This way we don't need to set `env.CARGO` for every build that depends on
>proc-macro-crate -- if we do that, the $CARGO environment variable would be
>visible to the entire build.  This could potentially lead to incredibly
>hard-to-troubleshoot heisenbugs if there is some other crate that expects
>`env::var("CARGO")` to exist -- that other crate would mysteriously work only

https://github.com/NixOS/nixpkgs/pull/329863

On Wed, Jul 24, 2024 at 03:01:12PM GMT, Adam Joseph wrote:
>When a dependency references a github *release* URL, that dependency must be
>fetched using https rather than git, since github does not require that
>release tarballs have any relationship whatsoever to the git history.
>
>This commit causes them to be fetched using https, not git.
>
>A test case (which fails prior to this commit, and passes afterwards) is included.
>---
> pkgs/build-support/node/fetch-yarn-deps/index.js         | 9 ++++++---
> .../build-support/node/fetch-yarn-deps/tests/default.nix | 4 ++++
> .../node/fetch-yarn-deps/tests/github-release.lock       | 6 ++++++

https://github.com/NixOS/nixpkgs/pull/329863

On Wed, Jul 24, 2024 at 02:59:35PM GMT, Adam Joseph wrote:
>When the hash of an url being fetched does not match the expected value, this
>commit will cause fetch-yarn-deps to include the url in the error message to
>assist debugging.
>---
> pkgs/build-support/node/fetch-yarn-deps/index.js | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/pkgs/build-support/node/fetch-yarn-deps/index.js b/pkgs/build-support/node/fetch-yarn-deps/index.js
>index e60fdeb54330..91e3d1014661 100755
>--- a/pkgs/build-support/node/fetch-yarn-deps/index.js
>+++ b/pkgs/build-support/node/fetch-yarn-deps/index.js

On Tue, Apr 16, 2024 at 10:57:24PM +0300, Florian Klink wrote:
>I tried building `pkgsCross.aarch64-multiplatform.pcsc-tools` from
>a `x86_64-linux` system.
>
>At least on master, there was a cross regression for gnupg (which I hit
>when building pcsc-tools with systemd support, as systemd (or importd more
>specifically) uses gnupg.
>
>Though if I disable that, it successfully builds, it's unrelated to
>your patchset anyways (and maybe fixed in staging, didn't check).
>
>On Mon, Apr 15, 2024 at 01:09:16PM -0700, Adam Joseph wrote:
>>Changes from v1:
>>

On Thu, Apr 18, 2024 at 04:44:15PM +0200, sternenseemann wrote:
>
>
>On 4/15/24 01:11, Adam Joseph wrote:
>>+  src = (fetchFromGitHub {
>>+    owner = "wfr";
>>+    repo = "ricochet-irc";
>>+    rev = "irc-v${finalAttrs.version}";
>>+    sha256 = "sha256-hN2XaKGurPVx1rbfBPFvvOYyh1CuPFfycPee/MGrkak=";
>>+    fetchSubmodules = false;
>>+    forceFetchGit = true;
>>+  }).overrideAttrs (previousAttrs: {
>>+    env = (previousAttrs.env or {}) // {
>>+      # We need to fetch the `src/extern/tor` git submodule, but it