Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #11025

M

~mgorny

Personal blog · mgorny.pl/articlesprogrammingsystems

~mgorny is a personal blog at mgorny.pl about programming and systems. Since 2020, 7 different Hacker News readers have linked it 7 times, most often “Problems faced when downstream testing Python packages”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
7mentions?
7HN people?
2020–2026first – last linked?
Links on Hacker News per year · peak 3 in 2023

Too few sampled comments (2) to say how often HN recommends it.?

Why HN links it

HN readers link these articles as technical references on tar format portability, such as which extended-attribute encodings GNU tar, BSD tar and libarchive support. Comments cite them as sources.

Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Gentoo developer since 2010, conda-forge since 2024, Free Software developer and contributor, and quite likely a feline.

Most-linked posts?

  1. Problems faced when downstream testing Python packages
    3 people · 3 mentions · first linked 2023-06-19
  2. Portability of Tar Features
    3 people · 3 mentions · first linked 2020-12-11

What Hacker News says?

  1. I once foolishly thought, I'll write a tar parser because, "how hard can it be" [1]. I simply tried to follow the tar(5) man page[2], and got a reference test set from another website posted previously on HN[3]. Along the way I discovered that NetBSD pax apparently cannot handle the PAX format[3] and my parser inadvertently uncovered that git-archive was storing the checksums wrong, but nobody noticed because other…

    Comment linking /articles/portability-of-tar-features.html

    on “Tar is an ill-specified format (2015)”
  2. Submitted Portability of Tar Features as a story · 40 points

    HN discussion
  3. Per this 2018 page, GNU tar seems to work with SCHILY.* encoded xattrs, but not LIBARCHIVE.* ones: * https://mgorny.pl/articles/portability-of-tar-features.html#... * Via: https://github.com/mxmlnkn/ratarmount/issues/145 bsdtar ≥3.7.2 apparently adds both types to its files for maximum portability: * https://github.com/libarchive/libarchive/pull/691/files#diff... AFAICT, bsdtar will default to "ustar" format, but wi…

    Comment linking /articles/portability-of-tar-features.html

    on “Tar files made in macOS generate "xattr" errors when expanded in Linux”
  4. Submitted Portability of Tar Features as a story · 2 points

    HN discussion
  5. Submitted Problems faced when downstream testing Python packages as a story · 1 points

    HN discussion
  6. Submitted Problems faced when downstream testing Python packages as a story · 1 points

    HN discussion
  7. Submitted Problems faced when downstream testing Python packages as a story · 1 points

    HN discussion

Search all of HN for mgorny.pl