Re: [gentoo-user] unable to do world update --problem may be caused by mailman

2020-12-07 Thread John Covici
On Mon, 07 Dec 2020 02:11:20 -0500,
Arve Barsnes wrote:
> 
> On Mon, 7 Dec 2020 at 00:11, John Covici  wrote:
> > hmmm, I am running a ~ setup, but I do need to keep mailman, so how to
> > tell which packages to keep, exactly?
> 
> Then you should be able to update to the latest version in the tree?
> Maybe you have masked newer versions somewhere? Maybe there's a manual
> upgrade job that you've put off until you had time.

I updated a month ago with no problems but I cannot update now.  If I
remove the ebuild I have from my local ebuild repository and just try
to do it plain, I get the following:

emerge: there are no ebuilds to satisfy
"dev-python/dnspython[python_targets_python2_7(-)]".
(dependency required by "net-mail/mailman-2.1.33::gentoo" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])


Should I change the ebuild so the compat line includes python27?.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com



Re: [gentoo-user] unable to do world update --problem may be caused by mailman

2020-12-07 Thread tastytea
On 2020-12-07 08:11+0100 Arve Barsnes  wrote:

> On Mon, 7 Dec 2020 at 00:11, John Covici 
> wrote:
> > hmmm, I am running a ~ setup, but I do need to keep mailman, so how
> > to tell which packages to keep, exactly?  
> 
> Then you should be able to update to the latest version in the tree?
> Maybe you have masked newer versions somewhere? Maybe there's a manual
> upgrade job that you've put off until you had time.

The upgrade is not gonna be easy: .

There is a repo with mailman2 + dependencies, but that is only intended
for a short timeframe: .

Kind regards, tastytea

-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgpUcZoKmaeHV.pgp
Description: Digitale Signatur von OpenPGP


Re: [gentoo-user] unable to do world update --problem may be caused by mailman

2020-12-06 Thread Arve Barsnes
On Mon, 7 Dec 2020 at 00:11, John Covici  wrote:
> hmmm, I am running a ~ setup, but I do need to keep mailman, so how to
> tell which packages to keep, exactly?

Then you should be able to update to the latest version in the tree?
Maybe you have masked newer versions somewhere? Maybe there's a manual
upgrade job that you've put off until you had time.

Regards,
Arve



Re: [gentoo-user] unable to do world update --problem may be caused by mailman

2020-12-06 Thread John Covici
On Sun, 06 Dec 2020 16:57:46 -0500,
Arve Barsnes wrote:
> 
> On Sun, 6 Dec 2020 at 22:28, John Covici  wrote:
> > So, since mailman 2.1.33 seems to be the latest version in the tree
> 
> The opposite seems to be true? 2.1.33 was removed from the tree in
> September, and the latest version in the tree is 3.3.2. It is only
> keyworded ~amd64 though, so I expect your problem here is that you run
> a stable setup.
> 
> Either you need to keep local copies of the old mailman ebuild, as
> well as its dependencies, or you need to keyword the new version.

hmmm, I am running a ~ setup, but I do need to keep mailman, so how to
tell which packages to keep, exactly?

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com



Re: [gentoo-user] unable to do world update --problem may be caused by mailman

2020-12-06 Thread Arve Barsnes
On Sun, 6 Dec 2020 at 22:28, John Covici  wrote:
> So, since mailman 2.1.33 seems to be the latest version in the tree

The opposite seems to be true? 2.1.33 was removed from the tree in
September, and the latest version in the tree is 3.3.2. It is only
keyworded ~amd64 though, so I expect your problem here is that you run
a stable setup.

Either you need to keep local copies of the old mailman ebuild, as
well as its dependencies, or you need to keyword the new version.

Regards,
Arve