| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
- `-A`: Comment out the `Include = /etc/pacman.d/*.conf` line that is
present in the /usr/share/pacman/defaults/ files since pacman
5.1.1-1.parabola4
- Pass --hookdir="$copydir/etc/pacman.d/hooks" to mkarchroot's pacman to
avoid inheriting the host's hooks.
https://bugs.archlinux.org/task/49347
I should maybe add tests for both of those things, but they both rely on
the actual contents of /etc/pacman.d/...
|
|
The librefetch-install program will stick around for a while (1 year;
2019-08-26) so that it can be used from a post_upgrade hook to remove the
old edits, in order to seamlessly migrate people.
https://git.parabola.nu/abslibre.git/commit/?id=73982c5ad7057ce2fdec669d962aec6c9caf28c8
|
|
|
|
This results in user confusion, like https://labs.parabola.nu/issues/1938
|
|
|
|
I realized that it was missing. While we're at it, organize the defaults
by their "origin".
|
|
This avoids something like a dep on 'systemd-tools' from resolving to
'notsystemd', causing a conflict with 'systemd' in 'base-devel', which
had the 'systemd-tools' dep already filled.
On the downside, this is much slower.
|
|
|
|
Objectives:
- Once the source package has been created, never run makepkg with
networking enabled again, so that we can be 100% sure that the source
package has all of the sources that we need.
- Don't let makepkg edit the PKGBUILD (eg. by evaluating pkgver())
User-facing changes:
- libremakepkg now disables networking during prepare()
- libremakepkg no longer runs pkgver()
- chcleanup (and thus `librechroot clean-pkgs`) now also installs packages
Technical description of changes:
- In devtools (and not really in this commit):
* No longer split /chrootprepare off of /chrootbuild. The point of
splitting it was that we'd have prepare() run from /chrootprepare
and the rest later run from /chrootbuild, so that we could leave
networking enabled during prepare() but not the rest. Now that we're
disabling networking during prepare(), that's pointless.
* Have download_sources create a source package (rather than having
/chrootbuild create the source package at the same time that we create
the binary package). We adjust the caller to temporarily set
SRCPKGDEST to a temporary directory, so that we can get the file and
control the filename when we move it in to the real SRCPKGDEST.
- Have chcleanup install the dependencies. If we used the traditional
`makepkg --sync` to install the dependencies, then we'd be breaking the
"no networking for makepkg after source package creation" objective.
chcleanup already has all of the logic necessary to accomplish this.
If there's a discrepancy in chcleanup behavior and makepkg behavior, and
makepkg thinks it needs to install something, then that just means we'll
have to fix the bug in chcleanup, instead of letting it go for more than
a year (*cough* https://labs.parabola.nu/issues/1311 *cough*).
- Use files extracted from the source package (rather than files found in
the current directory) to build the package.
- We mount the temporary directory containing the extracted source package
files read-only, to be sure that makepkg doesn't modify the PKGBUILD.
This is necessary because --holdver only disables pkgver() if it's a VCS
package.
|
|
This results in a few fuzzy entries; it's just changing from %s to %q; I
can merge those.
|
|
|
|
This screws up the line-by-line translation (sorry!) But msgmerge without
it is just not worth the time/effort.
https://savannah.gnu.org/bugs/?53457
|
|
|
|
|
|
|
|
po/es/librelib.po: Use the "fuzzy" attribute to indicate that a translation
needs updated, not a "FIXME" comment.
|
|
There are quite a few places where a line ends `foo"`, and the next line
picks up `"bar`; with neither line containing a space separating "foo" from
"bar". The results in the words getting munged together in to "foobar"
rather than "foo bar".
Here's how I searched for these:
cat *.po|ruby -e 'puts STDIN.read().gsub(/"\n\s*"/, "\"\"")'|sed -r 's/^msg(str|id) """/msg\1 "/'|grep -vE '^msgstr\s+"Project-Id-Version:'|grep '\S""\S'
There are 5 false-positives that are reflections of where msguniq decided
to split a flag or path in the .pot file.
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The have been at the current locations since 5c7b1e0 (2014-06-20).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The blacklist allows referring to a number of trusted bug trackers to
complement the information given in the reason field. However,
maintainable shorthand identifiers are used instead of full
URLs. Printing the latter based on the former is the job of this new
functionality.
This also introduces corresponding test cases and l10n strings
(together with translations for the `es` locale).
|
|
|
|
|
|
I ran `msgmerge -UFi xbs.po ../xbs.pot` for each message domain, but used
git gui to only stage substansive changes; not any changes to
line-wrapping.
|
|
|
|
|
|
|
|
There are two places where the punctuation was on the outside of the
end-quote; leading to syntax errors. There's one place where the msgid
was partially translated.
|
|
This means that the new `po/files.generate` target can be used to build the
`.pot` files without doing anything else; we can stop requiring translators
to install ruby-ronn. It also means that we can put the `.pot` files in
the source tarball, to make it even easier for translators.
Unfortunately, it does add the extra step of having to create another
symlink when adding a new locale.
|
|
|
|
|
|
It's the longest one, it will take time, but from bit to bit it works :)
|
|
|
