nd its way into
stable. We should either seek to move that into stable, or seek to
move the current working version in testing (1.1.0-4) -- with a more
comprehensive systemd patch[0], into stable.
[0]:
https://sources.debian.org/patches/fail2ban/1.1.0-4/update_backend_system.diff/
Thanks,
M
FWIW, the debian/watch file also needs to be changed to reflect the
move to GitHub.
```
version=4
opts=filenamemangle=s/.+\/v?(\d\S+)\.tar\.gz/-$1\.tar\.gz/ \
https://github.com/ya-mouse/fatresize/tags .*/v?(\d\+S+)\.tar\.gz
```
Regards,
Mingye Wang
-backport pipeline.
[1]: https://github.com/ya-mouse/fatresize/issues/11
Regards,
Mingye Wang (Artoria2e5)
me four-byte code
will help.
[0]:
https://github.com/MirBSD/mksh/blob/81a25f2a80f1a1f8e8149635b9f03587cb7cc953/expr.c#L833
The same problem is repeated in the utf_mbtowc, although the author
does appear aware of the "BMP" concept here.
Regards,
Mingye Wang (Artoria2e5)
Hi Adam,
Apologies for taking so long to respond to your message. Our current
proposed translation is available at [1], although I must warn you that
it contains some tabs that needs to be filtered through things like "sed
-e 's/\\t/\t/g' | expand" to remove. Time really flies...
[1]:
http
Package: grub-common
Version: 2.02-2
Version: 2.02~beta3-5
Version: 2.02~beta2-18
Since 2.02~beta2-18 Debian introduced a "quick_boot.patch" from Ubuntu,
which allows for the bypass of boot menu. Quoting from its commit message:
> If other operating systems are installed, then automatically un
Package: fonts-crosextra-caladea
Version: 20130214-1
Hello,
The current version of Caladea's description is simply copied from
Carlito with find-and-replaces. As a result, it incorrectly states that:
a) Caladea is a sans-serif (It should be a serif)
b) Caladea is based on Lato (Carlito is
Package: e2fsprogs
Version: 1.43.4-2
The current version of e2fsprogs ships a complete Chinese translation.
This is normally good news, just not quite so with badblocks which
miscounts columns and gives too few `\b`'s for stepping back.
In zh_CN.po, badblock's status text is translated as:
Far far ago, someone in Launchpad[1] talked about including some
(presumably ancient) text in traditional Chinese (zh-hant), since
zh-hans transliteration (simplification) for such text loses information.
[1]: https://bugs.launchpad.net/ubuntu/+source/fortune-zh/+bug/499663
Despite being most
Package: fortune-zh
Version: 2.1
Version: 2.0
fortune-zh's shijing.gb seems to use a white square ("\xa1\xa5") for
characters missing from the gb encoding used at that time (gb2312?).
These "white square" blocks passes down into the UTF-8 version (shijing)
as U+25A1 characters, that is, an act
(Sorry for bringing this up after two years, but indeed some
shebang/binfmt support can be convenient.)
On 1/3/2014 14:38, sri...@marirs.net.in wrote:
> If bash script is run like "./script_name" only bash is understands and
> starts interpreting it as a script.
#! (shebang/hashbang) is a magic nu
Hello,
Sorry for that previous CC-ed message with very long quotes. I made a
mistake when checking the Bug ID and the existence of that quoted reply.
:/
--
Regards,
Arthur2e5
signature.asc
Description: OpenPGP digital signature
ng
all your message and CC'ing it back to the bug so your reply will be
visible on the bug info page for others.
>
> On Wed Apr 20, 2016 at 12:04:37 -0400, Mingye Wang (Arthur2e5) wrote:
>> Package: minicom
>> Version: 2.7-1
>>
>> // omitted
>>
>> wcs
> Version: 1.0.0
> PS: The homepage should be changed to https://pygccxml.rtfd.org, or use
> https://github.com/gccxml/pygccxml if you prefer GitHub repo URLs.
>
Just noticed that lots of new releases have happened in that new
upstream. The latest tag is 1.7.3.
PyPI records consistent with GitHu
Package: pygccxml
Version: 1.0.0
According to gccxml documentation, gccxml is deprecated in favor of
castxml. pygccxml has castxml support too according to its doc.
So the Depends item should be something like `gccxml | castxml`.
PS: The homepage should be changed to https://pygccxml.rtfd.org, o
Package: minicom
Version: 2.7-1
A few months ago I was doing some minicom zh_CN l10n on
TranslationProject.org. Since the work is has been assigned to someone
else, I was not able to submit the done files. Interestingly, the
coordinator of the zh_CN language actually presented me with an extra
rea
LP #1566651 doesn't seem to be caused by font cache --
teddybeermaniac@lp reported that force-regenerating the cache didn't
solve the blurry bitmap problem.
It appears that 2.11.94 doesn't show the problem, so the fix should be
somewhere upstream. After some commit-log grepping
(https://cgit.free
When looking at
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566651 I
realized that the commit message in 3cd573f suggests manual re-caching.
A extra cache version bump should be done when backporting, or 'weird
thing[s]' may happen.
--
Regards,
Arthur2e5
signature.asc
Descripti
Package: fontconfig
Version: 2.11.0-6.4
Version: 2.11.0-6.3
Fontconfig <= 2.11.1 uses a segmented approach to map font weights. This
breaks on fonts like Noto Sans CJK, where Demilight (OS/2 weight=350)
and Regular (OS/2 weight=400) are both treated as Regular (FC
weight=80). So if you install the
Package: apt
Version: 1.1.3
In apt's `apt-key` script (cmdline/apt-key.in), there are multiple calls
to the external program `which`, which is often supplied by the
`debianutils` package on Debianish systems.
However, apt's control file (debian/control) doesn't claim it to be
dependent on the pac
Package: w3m
Version: 0.5.3-25+b1
Sorry, I forgot to change the Accept-Language string for zh_TW. Take
this patch instead.
On 2015/11/10 19:20, Mingye Wang wrote:
> Package: w3m
> Version: 0.5.3-25+b1
>
> Please note that the zh_TW translation is machine-converted using
> OpenCC
+
po/zh_TW.po | 892 +
3 files changed, 1785 insertions(+), 1 deletion(-)
create mode 100644 po/zh_CN.po
create mode 100644 po/zh_TW.po
--
Regards,
Arthur2e5 (0x222D7BDA)
From: "Mingye Wang (Arthur2e5)&q
22 matches
Mail list logo
