archlinux

svntogit-packages

Shell2020–2023

archlinux / svntogit-packages · Archived

svntogit-packages

Automatic import of svn 'packages' repo (read-only mirror)

Explore on GitHub Read Hacker News discussions

18Distinct people

21Mentions

0Explicit recommenders

325GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Automatic import of svn 'packages' repo (read-only mirror)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month21 dated mentions

Observed mentions: 2020-09-05 18:39:58 UTC to 2023-02-08 23:17:39 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Sep 2020	2020-09-01 00:00:00 UTC	2020-10-01 00:00:00 UTC	1	1
Oct 2020	2020-10-01 00:00:00 UTC	2020-11-01 00:00:00 UTC	1	1
Nov 2020	2020-11-01 00:00:00 UTC	2020-12-01 00:00:00 UTC	2	2
Dec 2020	2020-12-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	3	3
Jan 2021	2021-01-01 00:00:00 UTC	2021-02-01 00:00:00 UTC	0	0
Feb 2021	2021-02-01 00:00:00 UTC	2021-03-01 00:00:00 UTC	0	0
Mar 2021	2021-03-01 00:00:00 UTC	2021-04-01 00:00:00 UTC	0	0
Apr 2021	2021-04-01 00:00:00 UTC	2021-05-01 00:00:00 UTC	1	1
May 2021	2021-05-01 00:00:00 UTC	2021-06-01 00:00:00 UTC	1	1
Jun 2021	2021-06-01 00:00:00 UTC	2021-07-01 00:00:00 UTC	2	2
Jul 2021	2021-07-01 00:00:00 UTC	2021-08-01 00:00:00 UTC	0	0
Aug 2021	2021-08-01 00:00:00 UTC	2021-09-01 00:00:00 UTC	0	0
Sep 2021	2021-09-01 00:00:00 UTC	2021-10-01 00:00:00 UTC	1	1
Oct 2021	2021-10-01 00:00:00 UTC	2021-11-01 00:00:00 UTC	2	2
Nov 2021	2021-11-01 00:00:00 UTC	2021-12-01 00:00:00 UTC	1	1
Dec 2021	2021-12-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	1	1
Jan 2022	2022-01-01 00:00:00 UTC	2022-02-01 00:00:00 UTC	0	0
Feb 2022	2022-02-01 00:00:00 UTC	2022-03-01 00:00:00 UTC	0	0
Mar 2022	2022-03-01 00:00:00 UTC	2022-04-01 00:00:00 UTC	1	1
Apr 2022	2022-04-01 00:00:00 UTC	2022-05-01 00:00:00 UTC	0	0
May 2022	2022-05-01 00:00:00 UTC	2022-06-01 00:00:00 UTC	0	0
Jun 2022	2022-06-01 00:00:00 UTC	2022-07-01 00:00:00 UTC	0	0
Jul 2022	2022-07-01 00:00:00 UTC	2022-08-01 00:00:00 UTC	2	2
Aug 2022	2022-08-01 00:00:00 UTC	2022-09-01 00:00:00 UTC	0	0
Sep 2022	2022-09-01 00:00:00 UTC	2022-10-01 00:00:00 UTC	1	1
Oct 2022	2022-10-01 00:00:00 UTC	2022-11-01 00:00:00 UTC	0	0
Nov 2022	2022-11-01 00:00:00 UTC	2022-12-01 00:00:00 UTC	0	0
Dec 2022	2022-12-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
Jan 2023	2023-01-01 00:00:00 UTC	2023-02-01 00:00:00 UTC	0	0
Feb 2023	2023-02-01 00:00:00 UTC	2023-03-01 00:00:00 UTC	1	1

What Hacker News says

21 sources

mananaysiempre·Feb 8, 2023

This is already mentioned in a different comment here[1], but for ease of reference, Arch Linux did ship a vulnerable version and released the fix on 2 February[2]. [1] https://news.ycombinator.com/item?id=34713862 [2] https://github.com/archlinux/svntogit-packages/commit/796878...

In OpenSSH Pre-Auth Double Free – Writeup and Proof-of-Concept

LukeShu·Sep 11, 2022

> Those are not provided by GNU grep, they are an Arch thing No, they're a GNU grep thing. GNU grep 3.7: https://git.savannah.gnu.org/cgit/grep.git/tree/src/egrep.sh... GNU grep 3.8 (with the warning): https://git.savannah.gnu.org/cgit/grep.git/tree/src/egrep.sh... And you can see that the Arch package isn't doing anything special to add it: https://github.com/archlinux/svntogit-packages/blob/packages... In general, Arch avoids doing Arch-specific things and prefers to provide vanilla upstream packages, a lot more than other distros avoid doing distro-specific things.

In (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8

danuker·Jul 20, 2022

Google pushes Noto, which is a requirement on Arch for Firefox. I ignore its updates, because they're large and quite frequent. https://github.com/archlinux/svntogit-packages/commits/packa...

In TeamViewer installs suspicious font only useful for web fingerprinting

frankjr·Jul 17, 2022

Is there actually someone who builds the official source as is? Arch: https://github.com/archlinux/svntogit-packages/tree/packages... Alpine: https://git.alpinelinux.org/aports/tree/community/rust?h=mas... FreeBSD: https://cgit.freebsd.org/ports/tree/lang/rust/files

In Debian Violating Rust Trademark

dhx·Mar 18, 2022

These builds still have distribution-specific in-built API keys for some of the built-in services such as Google Safebrowsing, Google Location Services and Mozilla Location Services. See [1], [2], [3], [4], [5] and [6] for details and examples. Additionally, upon first launch of Firefox, a unique client identifier is created, and this is sent to Mozilla by default probably before you get a chance to disable telemetry features within the preferences dialogs. See [2], [7], [8] and [9]. As these privacy impacting features are enabled by default, before first launch of Firefox on Linux, you should disable these third party and telemetry features and also lock down other security and privacy settings. See [10] and [11] for the method of doing so, and an example user.js that contains decent documentation on well over a 100+ recommended configur

Read the rest

ation changes to make Firefox more respectful of privacy and security. If you don't reconfigure a user.js before first launch, at least the "New Profile" event will be notified to Mozilla with the unique client ID after a delay of only 30 minutes from creation of the first Firefox profile[9] (first launch). [1] https://glandium.org/blog/?p=3923 [2] https://github.com/mozilla/gecko-dev/blob/HEAD/build/moz.con... [3] resource://gre/modules/URLFormatter.jsm (use within Firefox URI bar) [4] resource://gre/modules/AppConstants.jsm (use within Firefox URI bar) [5] https://gitweb.gentoo.org/repo/gentoo.git/tree/www-client/fi... [6] https://github.com/archlinux/svntogit-packages/blob/packages... [7] resource://gre/modules/ClientID.jsm (use within Firefox URI bar) [8] resource:///modules/BrowserUsageTelemetry.jsm (use within Firefox URI bar) [9] https://github.com/mozilla/gecko-dev/blob/c3ec016fafa4cea6a0... [10] https://kb.mozillazine.org/User.js_file [11] https://github.com/arkenfox/user.js/

In Each Firefox download has a unique identifier

bscphil·Dec 7, 2021

Looks like Arch Linux is building it themselves with --with-wasi-sysroot. The changes they made to the build script for the 95.0 release are pretty instructive: https://github.com/archlinux/svntogit-packages/commit/532ac4... Hopefully Fedora manage to implement this to their satisfaction in the near future, although requiring extremely recent releases of build tools might be a blocker for some distros.

In WebAssembly and Back Again: Fine-Grained Sandboxing in Firefox 95

pxc·Nov 6, 2021

> That's interesting. In what ways are these resolvers superior to pacman? One good example is that even though PKGBUILDs can contain version constraints (see an example here[1]), that metadata is not always present and so it is underutilized. Pacman doesn't support ‘partial upgrades’[2] (once you refresh your package lists, installing anything is ‘unsupported’ until you upgrade everything), and this is why. (I also think that paper's notion of ‘completeness’ could probably be enriched somehow, because I've seen situations where `apt-get` will crap out but `aptitude` will offer a ‘compromise’ solution which involves downgrading some packages or removing some, and generally package managers based on libsolv do even better IME. Here Arch likely falls flatter.) Another depsolver related issue in Pacman (related to the lack of partial upgrade

Read the rest

s) is the lack of distinction between upgrades and dist-upgrades. In apt and dnf, upgrades are non-destructive by default, meaning that they don't offer solutions that involve removing or downgrading user-selected packages. Pacman has no such distinction. > I never had dependency resolution issues. Can you help me understand with concrete examples? One fairly common case is that Arch just ignores the dependencies of AUR-installed packages at install time, freely upgrading packages without respect to reverse-dependencies that aren't declared in a repo.[4] Hence, ‘if packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries’... every single time you upgrade, if you've installed anything from the AUR, it can leave your system with broken packages. Apt and dnf, in contrast, treat every package you install the same way. Additionally, Arch packages don't always declare version constraints for their library dependencies, and there's no CI that tests for ABI changes (there is some in Debian, although such tools can't work perfectly). So you have to use another tool (apparently one popular choice is some script from the Arch forums in 2005, lol[5]) to scan for such breakages, or else just discover them when packages don't work. On the other hand, when Arch does consider the version constraints of installed packages, the lack of partial upgrades can be problematic for downstream distros. Any version constraints placed by downstream repos on dependencies shared with upstream can just leave you totally unable to upgrade anything at all for a while.[6] — 1: https://github.com/archlinux/svntogit-packages/blob/master/d... 2: https://wiki.archlinux.org/title/System_maintenance#Partial_... 3: https://wiki.archlinux.org/title/Pacman/Rosetta#Basic_operat... 4: https://wiki.archlinux.org/title/Arch_User_Repository#Instal... 5: https://bbs.archlinux.org/viewtopic.php?id=13882 6: https://superuser.com/questions/1497098/pacman-unable-to-upd...

In From macOS to Arch Linux

lipnitsk·Oct 31, 2021

It does now: https://github.com/archlinux/svntogit-packages/commits/packa...

In Firefox 94 to start using EGL on Linux

bscphil·Oct 10, 2021

They do not. You can check their build files yourself here: https://github.com/archlinux/svntogit-packages/tree/packages... Indeed, it would be rather surprising if they did, as I'm an Arch user as well and they have not disabled the sponsored new tab suggestions or the Pocket article recommendations. Hard to say what would be beyond the pale for the Arch maintainers. From what I can tell from this thread, they are currently selectively enabling this for certain users. Maybe it just hasn't been enabled for you yet, or you're in a region (non-US) that doesn't get it enabled?

In Waterfox Browser

nly·Sep 23, 2021

I can't add much to this really. The Qt Company obviously don't think app developers using slightly old versions of their software provide any value to their shareholders, even though you're helping to grow the broader Qt ecosystem (libraries available, product awareness, knowledge sharing, growing the job market, etc). As far as the Qt company are concerned if you're a FOSS app developer, and not on bleeding edge Qt 6 and actively contributing bug reports (i.e. acting as their outsourced QA), then you're just a worthless leech. The feeling is the Qt library is only FOSS at this point because their hands are tied contractually by the KDE foundation. This has lead the KDE foundation to create a surprisingly active fork of Qt 5.15: https://invent.kde.org/qt/qt/qtbase/-/commits/kde/5.15 which is now the default Qt 5 base package on Arch Lin

Read the rest

ux: https://github.com/archlinux/svntogit-packages/blob/packages...

In Delphi 11 Alexandria

johnisgood·Jun 22, 2021

Thankfully I do save all of the microcodes, so I can just use an early version by simply rebuilding the initramfs. I also hold that package back on Arch, so it does not get upgraded. Might want to look for them here: https://github.com/intel/Intel-Linux-Processor-Microcode-Dat... As to how to actually use those files to get your "intel-ucode.img", just take a look at: https://archlinux.org/packages/extra/any/intel-ucode/ For the "iucode_tool": https://gitlab.com/iucode-tool/iucode-tool/-/wikis/home The actual PKGBUILD for it on Arch Linux: https://github.com/archlinux/svntogit-packages/blob/packages... --- cd Intel-Linux-Processor-Microcode-Data-Files-microcode-${pkgver/./} rm -f intel-ucode{,-with-caveats}/list mkdir -p kernel/x86/microcode iucode_tool --write-earlyfw=intel-ucode.img intel-ucode{,-with-caveats}/ The above gives

Read the rest

you "intel-ucode.img". Copy it to "/boot/". Run "mkinitcpio -p linux" or the like.

In Your CPU may have slowed down on Wednesday

heftig·Jun 13, 2021

Oh, I see. I only vaguely remembered some changeset regarding it. I must have been mistaken, then, and it's still in use. In any case, sneakily using nightly features can make using a different Rust version problematic, since these features are free of any stability guarantees. Arch Linux carries a rather large patch updating some vendored dependency in order to make Firefox 78 compile with a newer Rust. https://github.com/archlinux/svntogit-packages/tree/packages...

In Rust 1.x seems to not always be backward compatible in practice

vngzs·May 19, 2021

Yeah, sorry, the openjdk situation sucks. It's an "extra" package, which means the maintainer is a community member rather than being part of the Arch core group. The nice thing about Arch packages, though, is that they're basically just bash scripts. And if all you need is a simple version bump, it's usually quite easy: download the package tarball from [0] and change [1] to the version you want, then do a `makepkg -s` in the directory of the package. It will build the package in a (usually reproducible) chroot. If it builds without errors, then you'll end up with a tarball that you can `pacman -U ${pkg}.tar.zst` to install the produced files. If you need help, makepkg documentation on the wiki[2] is pretty great. And don't forget to send a patch to arch-dev-public[3] and CC the maintainer. At the very least, it'll kick off a discussion

Read the rest

that will get the package updated. Rolling your own packages is easy in contrast to, say, Red Hat - where compiling an RPM is easy if you've done it a bunch, but really difficult to get bootstrapped on. [0]: https://archlinux.org/packages/extra/x86_64/jdk-openjdk/ [1]: https://github.com/archlinux/svntogit-packages/blob/packages... [2]: https://wiki.archlinux.org/title/Makepkg [3]: https://lists.archlinux.org/listinfo/arch-dev-public

In Improving Firefox stability on Linux

nly·Apr 19, 2021

Sadly Qt 5, due to the Qt Company pushing FOSS "freeloaders" on to bleeding edge and unstable versions of Qt 6[0], is becoming less and less viable for non-commercial, cross-platform app development. Arch Linux now compiles Qt from KDEs fork[1] The only ray of sunshine here is that, with Qt 5.15 being the last 5.x release, we may eventually see all distros shipping it instead of the horrible version fragmentation you see now (Ubuntu 20.04 LTS and CentOS Stream are still on 5.12, Debian 10 is on 5.11, RHEL 7 is on 5.9). The rift being created between Qt 5 and Qt 6, and the lack of any stability for FOSS with respect to upstream support for Qt 6, means we will likely see lots more fragmentation on the KDE/Qt side in years to come. Qt 5 will eventually end up like Qt 4, which has been dropped from Archs main repos[2], despite having over 500

Read the rest

packages in AUR depending on it[3]. Of course, depending on a single fork likely won't work either. The KDE fork is going to be naturally Linux focused, and probably won't care to tend to any Windows or macOS that arise. GTK+ on other platforms sucks, but at least on FOSS platforms it's not a mess. [0] https://www.theregister.com/2021/01/05/qt_lts_goes_commercia... [1] https://github.com/archlinux/svntogit-packages/blob/packages... [2] https://lists.archlinux.org/pipermail/arch-dev-public/2019-A... [3] https://aur.archlinux.org/packages/qt4/

In Gnome 40 – The anti-desktop desktop

chrismorgan·Dec 14, 2020

You can set a few variables to change where these files go: • 'directory' controls where swap files go, toggled by 'swapfile' (default on), filenames like […].swp; ~/.cache/vim/swap// is a good choice. • 'undodir' controls where undo files go, toggled by 'undofile' (default off), filenames […].un~; ~/.cache/vim/undo// is a good choice. • 'backupdir' controls where backup files go, toggled by 'backup' (default off), filename […]~; ~/.cache/vim/backup// is an interesting choice. Arch Linux actually ships a runtime file that sets these paths, creating the directories if they don’t exist: https://github.com/archlinux/svntogit-packages/blob/packages.... (Note that the double trailing slashes are significant and necessary if you’re using a central location for these files. Refer to the help for explanation.)

In Five lines I put in a blank .vimrc

Showing the 15 most recent of 21 sources. Enable JavaScript to search and browse every indexed mention.