[gentoo-dev] Last rites: dev-ruby/ferret

2022-12-15 Thread Hans de Graaff
# Hans de Graaff  (2022-12-16)
# ruby27-only package. No longer maintained upstream.
# No reverse dependencies. Masked for removal in 30 days.
dev-ruby/ferret


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


[gentoo-dev] Last rites: games-puzzle/mindless

2022-12-15 Thread Michał Górny
# Michał Górny  (2022-12-16)
# Not installable since at least Dec 2020 due to checksum mismatch.
# Ebuild not touched since 2018.
# Removal on 2023-01-15.  Bug #759121.
games-puzzle/mindless

-- 
Best regards,
Michał Górny




[gentoo-dev] Last rites: dev-python/lunr, dev-python/nltk, dev-python/nltk-data

2022-12-15 Thread Michał Górny
# Michał Górny  (2022-12-16)
# NTLK relies on a large number of corpora that either have unknown
# license, a non-free license or that may be in violation of copyright.
# We have been rubber stamping over this in dev-python/nltk-data
# via LICENSE=all-rights-reserved + RESTRICT=bindist but this
# is not a feasible long-term solution.
#
# dev-python/lunr is the only revdep and has no reverse dependencies
# itself.
#
# Removal on 2023-01-15.  Bug #886203.
dev-python/lunr
dev-python/nltk
dev-python/nltk-data

-- 
Best regards,
Michał Górny




[gentoo-dev] Re: Current portage will now truncate your repo's git history to 1

2022-12-15 Thread Duncan
Florian Schmaus posted on Thu, 15 Dec 2022 21:40:19 +0100 as excerpted:

> On 15/12/2022 21.10, Toralf Förster wrote:
>> On 12/15/22 20:22, Florian Schmaus wrote:
>>> o use PORTDIR_OVERLAY and multiple repositories on their system: a
>>> system-wide, managed by portage, and a dev repository (in your HOME),
>>> scoped in via PORTDIR_OVERLAY.
>> 
>> Isn't this covered by /etc/portage/repos.conf/*
> 
> Absolutely, but this requires a manual intervention from the user. And,
> of course, you can totally opt-out from portage managing (syncing) the
> repository, but then you have to take care of syncing yourself.
> 
> The point is that with the new portage release, portage's behavior
> changes. And I would argue that portage should not, in its effort to
> become more user friendly, disregard ebuild-developer friendliness.
> Assuming it is achievable with a reasonable amount of additional code
> complexity.

This bit me too, and making things worse, the truncate killed the git 
history that presumably had the answer I needed to fix it up. 
=:^(  Fortunately I had a bit of a clue due to preemptively following the 
portage changelog where I had seen a hint, so I was able to dig it up 
again without the git log help that's definitely now my first instinct.

Long story short and for the record, manual intervention indeed and I wish 
it had at least come with a news item, but here's the magic that fixed it 
for me.

I had one of these previously, IIRC clone depth, but both are now needed.  
I put these in the [DEFAULT] section here because I run several overlays 
and I "want" access to proper git logs and history by default. (FWIW 
"want" is the polite, cooled down, version; the situation was considerably 
more sweary when I lost that history and instinctively I tried to look in 
the git history for why, but of course it was GONE!)

repos.conf, [DEFAULT] (or [gentoo]) section:

clone-depth = 0
sync-depth  = 0

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




Re: [gentoo-dev] Current portage will now truncate your repo's git history to 1

2022-12-15 Thread Florian Schmaus

On 15/12/2022 21.10, Toralf Förster wrote:

On 12/15/22 20:22, Florian Schmaus wrote:
o use PORTDIR_OVERLAY and multiple repositories on their system: a 
system-wide, managed by portage, and a dev repository (in your HOME), 
scoped in via PORTDIR_OVERLAY.


Isn't this covered by /etc/portage/repos.conf/*


Absolutely, but this requires a manual intervention from the user. And, 
of course, you can totally opt-out from portage managing (syncing) the 
repository, but then you have to take care of syncing yourself.


The point is that with the new portage release, portage's behavior 
changes. And I would argue that portage should not, in its effort to 
become more user friendly, disregard ebuild-developer friendliness. 
Assuming it is achievable with a reasonable amount of additional code 
complexity.


- Flow




Re: [gentoo-dev] Current portage will now truncate your repo's git history to 1

2022-12-15 Thread Toralf Förster

On 12/15/22 20:22, Florian Schmaus wrote:
o use PORTDIR_OVERLAY and multiple repositories on their system: a 
system-wide, managed by portage, and a dev repository (in your HOME), 
scoped in via PORTDIR_OVERLAY.


Isn't this covered by /etc/portage/repos.conf/*

eg here's my config:

cat /etc/portage/repos.conf/all.conf
[DEFAULT]
main-repo = gentoo

[gentoo]
location = /var/db/repos/gentoo
auto-sync = yes
sync-type = git
sync-uri = https://github.com/gentoo-mirror/gentoo.git
#sync-git-verify-commit-signature = true
priority = 10

[local]
location = /var/db/repos/local
auto-sync = no
priority = 99

[tgro]
location = /var/db/repos/tgro
auto-sync = no

priority = 90

--
Toralf
PGP 23217DA7 9B888F45



OpenPGP_signature
Description: OpenPGP digital signature


[gentoo-dev] Re: Current portage will now truncate your repo's git history to 1

2022-12-15 Thread Florian Schmaus

On 15/12/2022 20.22, Florian Schmaus wrote:
As everyone knows, there is nothing better than to change the workflow 
that has served you well over multiple years. But apparently the 
PORTDIR_OVERLAY approach works well for others, so I am confident that I 
(and others) will be able to make the transition with a minimal amount 
of ranting. ;)


As it was pointed out that some consider my wording here inappropriate 
and/or rude, I want to apologize to everyone who was offended by the 
prior paragraph. I had


https://xkcd.com/1172/

in mind when writing it.

I was also criticized for not providing a rationale for the behavior 
change in portage. The motivation is driven by the noble goal to make 
portage more user friendly and robust. Which I fully support. Just like 
I support shallow clones per default. I just believe portage should do a 
better job figuring out if it potentially messes with a "user-owned" 
repository and adjust its behavior accordingly. In a similar spirit I 
submitted https://github.com/gentoo/portage/pull/960


- Flow





[gentoo-dev] Current portage will now truncate your repo's git history to 1

2022-12-15 Thread Florian Schmaus
This is a public service announcement that the recently stabilized 
portage version will truncate you repo's git history to 1.


While this is a good thing for the majority of Gentoo users, it affects 
developers that develop in a git known to portage (like me). If I 
understand the portage maintainers vision correctly, then future portage 
will assume full control over its configured repositories and 
potentially perform destructive operations on them, for example "git 
clean" [1].


I personally would prefer portage simply adjusting its behavior based on 
the owner of the repository. That is, if it's the 'portage' user then 
assume full control, and if it is a different user, then fall back to a 
preserving, conservative mode of operation. Unfortunately, for me, this 
idea was received skeptically at best in a recent discussion in 
#gentoo-portage.


So this is a heads up for fellow developers using a similar workflow 
like me, that they are probably required to change their workflow to use 
PORTDIR_OVERLAY and multiple repositories on their system: a 
system-wide, managed by portage, and a dev repository (in your HOME), 
scoped in via PORTDIR_OVERLAY.


As everyone knows, there is nothing better than to change the workflow 
that has served you well over multiple years. But apparently the 
PORTDIR_OVERLAY approach works well for others, so I am confident that I 
(and others) will be able to make the transition with a minimal amount 
of ranting. ;)


- Flow



1: https://github.com/gentoo/portage/pull/939



[gentoo-dev] MATE project is now empty

2022-12-15 Thread Michał Górny
Hello, everyone.

The Gentoo MATE project [1] does not have any developers anymore. 
Please consider joining to keep it alive.

That said, the packages don't look bad and there seems to be an active
contributor submitting pull requests for them.  According to repology
[2], a few packages need version bumps.  There's also 30 bugs reported
against them [3].

[1] https://wiki.gentoo.org/wiki/Project:MATE
[2] 
https://repology.org/projects/?maintainer=mate%40gentoo.org&inrepo=gentoo&outdated=1
[3] https://bugs.gentoo.org/buglist.cgi?quicksearch=assignee%3Amate%40gentoo.org

Full list of packages maintained by mate@:

app-arch/engrampa
app-editors/pluma-plugins
app-editors/pluma
app-text/atril
dev-libs/libmateweather
dev-python/python-caja
eclass/mate-desktop.org.eclass
eclass/mate.eclass
mate-base/caja
mate-base/libmatekbd
mate-base/mate-applets-meta
mate-base/mate-applets
mate-base/mate-common
mate-base/mate-control-center
mate-base/mate-desktop
mate-base/mate-menus
mate-base/mate-panel
mate-base/mate-session-manager
mate-base/mate-settings-daemon
mate-base/mate
mate-extra/caja-actions
mate-extra/caja-admin
mate-extra/caja-dropbox
mate-extra/caja-extensions
mate-extra/caja-hide
mate-extra/mate-calc
mate-extra/mate-indicator-applet
mate-extra/mate-media
mate-extra/mate-netbook
mate-extra/mate-polkit
mate-extra/mate-power-manager
mate-extra/mate-screensaver
mate-extra/mate-sensors-applet
mate-extra/mate-system-monitor
mate-extra/mate-user-guide
mate-extra/mate-user-share
mate-extra/mate-utils
media-gfx/eom
media-libs/libmatemixer
x11-misc/mate-notification-daemon
x11-misc/mozo
x11-terms/mate-terminal
x11-themes/mate-backgrounds
x11-themes/mate-icon-theme-faenza
x11-themes/mate-icon-theme
x11-themes/mate-themes-meta
x11-themes/mate-themes
x11-wm/marco

-- 
Best regards,
Michał Górny




[gentoo-dev] Last rites: sci-astronomy/skycat

2022-12-15 Thread Michał Górny
# Michał Górny  (2022-12-15)
# Fails to build since 2019.  Last bumped in 2017.
# Removal on 2023-01-14.  Bug #688950.
sci-astronomy/skycat

-- 
Best regards,
Michał Górny




Re: [gentoo-dev] last-rite: net-print/{apsfilter,kyocera-mita-ppds}

2022-12-15 Thread Joonas Niilola
On 14.12.2022 22.20, Marco Scardovi wrote:
> Hi everyone,
> 
> I'm gonna propose to l-r these packages as both are dead upstream and on
> our side
> 
> # Marco Scardovi  (2022-12-14)
> # We are literally the only distro that still have
> # an installation option for that package.
> # It still uses EAPI 6 and no real support since
> # years.
> # Removal on 2023-01-14. Bug #885605
> net-print/kyocera-mita-ppds
> 
> # Marco Scardovi  (2022-12-14)
> # Dead upstream, dead homepage, dead symlinks,
> # no revdeps and no version bump since 2011
> # Removal on 2023-01-14. Bug #884307
> net-print/apsfilter
> 
> Please see https://github.com/gentoo/gentoo/pull/28606 too.
> 
> Best regards, Marco Scardovi (scardracs)
> 
> 

This mask has been applied.

-- juippis


OpenPGP_signature
Description: OpenPGP digital signature