[gentoo-dev] Last 24h for voting in council election

[Andreas K . Hüttel]

Hi all, 

the last 24 for voting in the council election start soon...

GO VOTE :)

Cheers -A

-- 
Andreas K. Hüttel
dilfri...@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)

signature.asc
Description: This is a digitally signed message part.

[gentoo-dev] Last rites: dev-python/algopy

[Michał Górny]

# Michał Górny  (2020-07-04)
# Unmaintained.  Requires scipy-python2.  Current version is from 2015,
# latest upstream release from 2017.  The only revdep is masked
# for removal.
# Removal in 30 days.  Bug #730760.
dev-python/algopy

-- 
Best regards,
Michał Górny



signature.asc
Description: This is a digitally signed message part

[gentoo-dev] Last rites: net-misc/termpkg

[Jonas Stein]

Dead upstream, no homepage, no maintainer, no reverse dependencies.
https://bugs.gentoo.org/730640

--
Best regards,
Jonas Stein



















signature.asc
Description: OpenPGP digital signature

Re: [gentoo-dev] UTF-8 in ebuild descriptions

[Michał Górny]

On Sat, 2020-07-04 at 17:47 +0300, nlhow...@gmail.com wrote:
> I would like the ebuild short description to refer to these languages
> by their names, instead of by e.g. ISO-639-3 codes.
> 

I can't answer the other points (because I don't know) but I think you
can transliterate it into 'Apurina' rather than using codes, can't you?

-- 
Best regards,
Michał Górny



signature.asc
Description: This is a digitally signed message part

[gentoo-dev] UTF-8 in ebuild descriptions

[nlhowell]

Hello all,

I'm packaging a handful of dictionaries for various languages; some
of them have non-ASCII names in English. Example:
```
DESCRIPTION="Giellatekno morphological dictionaries for Apurinã."
```

Repoman complains:
```
  variable.invalidchar [fatal]  5
   app-dicts/giella-apu/giella-apu-.ebuild: DESCRIPTION variable
   contains non-ASCII character at position 50
```

A brief discussion in #gentoo-dev-help found GLEP 31:

>  Only ASCII is permitted in code which is parsed by bash
> and output:
> .

>From GLEP31:
> Ebuild and Eclass Character Sets
> 
> For the same reasons as previously, it is proposed that UTF-8 is
> used as the official encoding for ebuild and eclass files.
> 
> However, developers should be warned that any code which is parsed
> by bash (in other words, non-comments), and any output which is
> echoed to the screen (for example, einfo messages) or given to
> portage (for example any of the standard global variables) must not
> use anything outside the regular ASCII 0..127 range for
> compatibility purposes.

What does "compatibility purposes" mean here? Non-unicode locales and
terminal state corruption? Other tools?

I would like the ebuild short description to refer to these languages
by their names, instead of by e.g. ISO-639-3 codes.

Thoughts?

Cheers,
Nick


signature.asc
Description: OpenPGP digital signature

[gentoo-dev] Last rites: media-gfx/uniconvertor

[Michał Górny]

# Michał Górny  (2020-07-04)
# Unmaintained.  Python 2 only.  Effectively depends on vulnerable
# version of dev-python/pillow.  No revdeps.  Multiple bugs open.
# Removal in 30 days.  Bug #715682.
media-gfx/uniconvertor

-- 
Best regards,
Michał Górny



signature.asc
Description: This is a digitally signed message part