Re: make reinstall does not work

2017-12-09 Thread Greg 'groggy' Lehey
On Saturday,  9 December 2017 at 12:04:02 +0100, Walter Schwarzenfeld wrote:
> Thanks, this explains and solved the problem.

What?  And how?

Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature


Re: The ports@ list is now subscriber-post only

2017-12-09 Thread Dave Horsfall

On Sun, 10 Dec 2017, Tilman Keskinöz wrote:

I must be living in a parallel universe, checking 
https://lists.freebsd.org/pipermail/freebsd-ports/2017-December/thread.html 
there has been one (1) spam message getting through so far this month. 
That's a really tremendous amount of spam.


Sigh...  Confined yourself to just this month, eh?  Let's see:

aneurin% grep "^From owner-freebsd-ports" mail/spam
From owner-freebsd-po...@freebsd.org Sat Nov 22 17:36:08 2014
From owner-freebsd-po...@freebsd.org Tue Dec  2 03:52:59 2014
From owner-freebsd-po...@freebsd.org Thu Dec 11 04:01:46 2014
From owner-freebsd-po...@freebsd.org Fri Dec 19 12:00:36 2014
From owner-freebsd-po...@freebsd.org Thu Dec 25 22:54:27 2014
From owner-freebsd-po...@freebsd.org Wed Dec 31 21:38:16 2014
From owner-freebsd-po...@freebsd.org Sun Jan  4 10:06:49 2015
From owner-freebsd-po...@freebsd.org Tue Jan 20 04:03:42 2015
From owner-freebsd-po...@freebsd.org Tue Jan 20 04:03:42 2015
From owner-freebsd-po...@freebsd.org Tue Jan 20 04:05:03 2015
From owner-freebsd-po...@freebsd.org Wed Jan 21 20:47:55 2015
From owner-freebsd-po...@freebsd.org Wed Jan 21 22:57:46 2015
From owner-freebsd-po...@freebsd.org Tue Feb  3 22:03:43 2015
From owner-freebsd-po...@freebsd.org Wed Feb 11 00:35:37 2015
From owner-freebsd-po...@freebsd.org Fri Feb 13 17:17:16 2015
From owner-freebsd-po...@freebsd.org Mon Feb 16 15:22:30 2015
From owner-freebsd-po...@freebsd.org Mon Feb 16 16:11:29 2015
From owner-freebsd-po...@freebsd.org Mon Feb 16 19:11:56 2015
From owner-freebsd-po...@freebsd.org Thu Feb 26 03:14:22 2015
From owner-freebsd-po...@freebsd.org Sun Mar  1 11:26:28 2015
From owner-freebsd-po...@freebsd.org Tue Mar  3 01:01:43 2015
From owner-freebsd-po...@freebsd.org Tue Mar  3 04:53:38 2015
From owner-freebsd-po...@freebsd.org Fri Mar 13 20:27:26 2015
From owner-freebsd-po...@freebsd.org Mon Mar 16 16:10:13 2015
From owner-freebsd-po...@freebsd.org Fri Mar 20 22:29:08 2015
From owner-freebsd-po...@freebsd.org Mon Mar 23 23:35:03 2015
From owner-freebsd-po...@freebsd.org Tue Mar 24 05:26:46 2015
From owner-freebsd-po...@freebsd.org Tue Mar 24 19:44:31 2015
From owner-freebsd-po...@freebsd.org Tue Mar 24 21:34:22 2015
From owner-freebsd-po...@freebsd.org Wed Mar 25 18:22:43 2015
From owner-freebsd-po...@freebsd.org Thu Mar 26 16:31:13 2015
From owner-freebsd-po...@freebsd.org Thu Apr  2 18:53:42 2015
From owner-freebsd-po...@freebsd.org Fri Apr  3 16:30:36 2015
From owner-freebsd-po...@freebsd.org Sat Apr  4 22:51:52 2015
From owner-freebsd-po...@freebsd.org Wed Apr  8 07:03:19 2015
From owner-freebsd-po...@freebsd.org Wed Apr  8 09:50:52 2015
From owner-freebsd-po...@freebsd.org Fri Apr 17 06:44:32 2015
From owner-freebsd-po...@freebsd.org Mon Apr 20 16:14:55 2015
From owner-freebsd-po...@freebsd.org Thu Apr 23 15:07:29 2015
From owner-freebsd-po...@freebsd.org Fri Apr 24 15:50:07 2015
From owner-freebsd-po...@freebsd.org Sun Apr 26 17:08:52 2015
From owner-freebsd-po...@freebsd.org Tue Apr 28 04:43:05 2015
From owner-freebsd-po...@freebsd.org Sun May  3 14:20:03 2015
From owner-freebsd-po...@freebsd.org Wed May 13 18:03:20 2015
From owner-freebsd-po...@freebsd.org Sat May 16 09:14:07 2015
From owner-freebsd-po...@freebsd.org Sun May 17 18:12:52 2015
From owner-freebsd-po...@freebsd.org Sun May 17 18:13:37 2015
From owner-freebsd-po...@freebsd.org Sun May 17 18:14:41 2015
From owner-freebsd-po...@freebsd.org Sun May 17 18:29:11 2015
From owner-freebsd-po...@freebsd.org Sun May 17 18:29:27 2015
From owner-freebsd-po...@freebsd.org Thu Jun  4 01:06:06 2015
From owner-freebsd-po...@freebsd.org Wed Jun 10 13:24:49 2015
From owner-freebsd-po...@freebsd.org Wed Jun 17 00:06:35 2015
From owner-freebsd-po...@freebsd.org Sat Jun 20 03:38:51 2015
From owner-freebsd-po...@freebsd.org Sun Jun 21 13:57:18 2015
From owner-freebsd-po...@freebsd.org Wed Jun 24 16:35:07 2015
From owner-freebsd-po...@freebsd.org Wed Jun 24 18:12:26 2015
From owner-freebsd-po...@freebsd.org Fri Jun 26 04:17:51 2015
From owner-freebsd-po...@freebsd.org Sat Jun 27 15:20:54 2015
From owner-freebsd-po...@freebsd.org Mon Jun 29 23:46:52 2015
From owner-freebsd-po...@freebsd.org Thu Jul 16 06:14:12 2015
From owner-freebsd-po...@freebsd.org Tue Jul 21 12:17:33 2015
From owner-freebsd-po...@freebsd.org Thu Jul 23 01:34:27 2015
From owner-freebsd-po...@freebsd.org Mon Jul 27 19:28:20 2015
From owner-freebsd-po...@freebsd.org Tue Jul 28 02:21:15 2015
From owner-freebsd-po...@freebsd.org Tue Jul 28 21:42:17 2015
From owner-freebsd-po...@freebsd.org Tue Jul 28 23:30:16 2015
From owner-freebsd-po...@freebsd.org Thu Jul 30 17:20:58 2015
From owner-freebsd-po...@freebsd.org Mon Aug 17 09:09:15 2015
From 

Re: The ports@ list is now subscriber-post only

2017-12-09 Thread Lowell Gilbert
Adam Weinberger  writes:

>> On 9 Dec, 2017, at 9:27, Adam Weinberger  wrote:
> I'll pass along a tip that I just sent to postmaster@: in the past (for
> other lists @FreeBSD.org), some folks have subscribed to receive the
> list mail at some address, but tried to post from a different address.

For my part, I may have to change my configuration slightly for the
mailbox in which I read this list. But if so, I should have done it
long ago in any case, for more-or-less unrelated reasons.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: The ports@ list is now subscriber-post only

2017-12-09 Thread Douglas Thrift
On 12/9/2017 3:13 PM, Tilman Keskinöz wrote:
> On 12/09/2017 17:27, Adam Weinberger wrote:
>> The po...@freebsd.org (aka freebsd-ports@) mailing list now requires you
>> to subscribe to the list before posting. This brings us two important
>> benefits:
>>
>> * This should cut back tremendously on spam coming through the list.
> 
> I must be living in a parallel universe, checking
> https://lists.freebsd.org/pipermail/freebsd-ports/2017-December/thread.html
> there has been one (1) spam message getting through so far this month.
> That's a really tremendous amount of spam.
> 
>> * Users are more likely to find better answers to their questions: The
>> first three times a question is asked, it gets detailed replies. The
>> fourth through nth times usually get a one sentence reply.
> 
> Is a moderator ensuring that messages from unsubscribed users, who just
> sent a mail to the maintainer of an unmaintained port get through?
> 
> Otherwise we will probably miss a lot of bug reports from Users who
> don't bother to subscribe.
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> 

Even ports with maintainers have a CC for ports@ in the email links at
https://www.freebsd.org/ports/index.html.
-- 
Douglas William Thrift

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: The ports@ list is now subscriber-post only

2017-12-09 Thread Tilman Keskinöz
On 12/09/2017 17:27, Adam Weinberger wrote:
> The po...@freebsd.org (aka freebsd-ports@) mailing list now requires you
> to subscribe to the list before posting. This brings us two important
> benefits:
> 
> * This should cut back tremendously on spam coming through the list.

I must be living in a parallel universe, checking
https://lists.freebsd.org/pipermail/freebsd-ports/2017-December/thread.html
there has been one (1) spam message getting through so far this month.
That's a really tremendous amount of spam.

> * Users are more likely to find better answers to their questions: The
> first three times a question is asked, it gets detailed replies. The
> fourth through nth times usually get a one sentence reply.

Is a moderator ensuring that messages from unsubscribed users, who just
sent a mail to the maintainer of an unmaintained port get through?

Otherwise we will probably miss a lot of bug reports from Users who
don't bother to subscribe.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: The ports@ list is now subscriber-post only

2017-12-09 Thread Dave Horsfall

On Sat, 9 Dec 2017, Adam Weinberger wrote:


* This should cut back tremendously on spam coming through the list.


Many many thanks!  Now if I can just get some other lists I'm on to see 
the light of day (Debian, I'm looking at you)...


Half-seriously, I'll probably stick with FreeBSD after all now (yes, that 
would've been a major factor in my decision to flee elsewhere).


--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Odd index issue with misc/compat ports

2017-12-09 Thread Kevin Oberman
Since the day FLAVORS appeared, I have had an odd issue with the compatible
library ports. Specificaly, they have been missing from the downloadable
INDEX. If I build the index myself (make index), all is well, but I
normally download the index from a cron job right after I update my ports
tree with svn (make fetchindex). When I check for updated ports and other
issues, I see the compat ports as "orphaned".
# pkg version -vL=
compat10x-amd64-10.3.1003000.20170608 ?   orphaned: misc/compat10x
compat9x-amd64-9.3.903000.20170608 ?   orphaned: misc/compat9x

The ports are still in the repository and in my ports tree, but seem to be
missing from the regularly generated INDEX. I have confirmed that they are
missing from the downloaded file.

I can't see how this could be unique to me, but I have seen no other
reports. I something messed up or is the INDEX somehow missing them? Did
something about changes made to support FLAVORS trigger this or is it just
c coincidence that the problem appeared that day?
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: The ports@ list is now subscriber-post only

2017-12-09 Thread Adam Weinberger

On 9 Dec, 2017, at 9:27, Adam Weinberger  wrote:

The po...@freebsd.org (aka freebsd-ports@) mailing list now requires you  
to subscribe to the list before posting. This brings us two important  
benefits:


* This should cut back tremendously on spam coming through the list.

* Users are more likely to find better answers to their questions: The  
first three times a question is asked, it gets detailed replies. The  
fourth through nth times usually get a one sentence reply.


This ONLY affects sending messages to the list. It does NOT affect:
- Receiving messages or replies
- Viewing the archives  
(https://www.freebsd.org/community/mailinglists.html)

- Searching the archives

If you have any questions about this, don't hesitate to ask!


From dhw:

I'll pass along a tip that I just sent to postmaster@: in the past (for
other lists @FreeBSD.org), some folks have subscribed to receive the
list mail at some address, but tried to post from a different address.

To mitigate that, my suggestion has usually been for the affected folks
to *also* subscribe for the "posting" address, but use Mailman
facilities to set that subscription to "nomail."



--
Adam Weinberger
ad...@adamw.org
https://www.adamw.org

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


The ports@ list is now subscriber-post only

2017-12-09 Thread Adam Weinberger
The po...@freebsd.org (aka freebsd-ports@) mailing list now requires you to  
subscribe to the list before posting. This brings us two important benefits:


* This should cut back tremendously on spam coming through the list.

* Users are more likely to find better answers to their questions: The  
first three times a question is asked, it gets detailed replies. The fourth  
through nth times usually get a one sentence reply.


This ONLY affects sending messages to the list. It does NOT affect:
- Receiving messages or replies
- Viewing the archives (https://www.freebsd.org/community/mailinglists.html)
- Searching the archives

If you have any questions about this, don't hesitate to ask!

# Adam


--
Adam Weinberger
ad...@adamw.org
https://www.adamw.org

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: ports tree and upgrading errors

2017-12-09 Thread Adam Weinberger



On 9 Dec, 2017, at 6:20, tech-lists  wrote:

Hi,

I get this when trying to upgrade ports:

[Reading data from pkg(8) ... - 620 packages found - done]
** Port directory not found: devel/py-setuptools@py27
** Port directory not found: devel/py-setuptools@py36

[...]

--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
- devel/py-setuptools@py27 (port directory error)
- devel/py-setuptools@py36 (port directory error)

I use svnlite to update the ports tree and portupgrade to upgrade ports.
There is nothing specific in UPDATING that addresses this, other than
portupgrade not handling FLAVORS right now.

Do I have to worry about this error? Can I correct it?


@py27 is a flavor, so what you're seeing is portupgrade being unable to
handle FLAVORS. Work is actively underway on portupgrade, but there's
no target date. In the meantime you can use poudriere, synth, or plain
make commands.

# Adam


--
Adam Weinberger
ad...@adamw.org
https://www.adamw.org

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Procmail Vulnerabilities check

2017-12-09 Thread George Mitchell
On 12/09/17 00:42, Chris H wrote:
> [...] So I'd like to respectfully request that Sendmail stays.
> All those in favor, say aye!
> [...]

  A   Y   Y E !
 A A   Y Y  E !
A   Y   EEE   !
A   A   Y   E
A   A   Y   E !  -- George



signature.asc
Description: OpenPGP digital signature


ports tree and upgrading errors

2017-12-09 Thread tech-lists
Hi,

I get this when trying to upgrade ports:

[Reading data from pkg(8) ... - 620 packages found - done]
** Port directory not found: devel/py-setuptools@py27
** Port directory not found: devel/py-setuptools@py36

[...]

--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
- devel/py-setuptools@py27 (port directory error)
- devel/py-setuptools@py36 (port directory error)

I use svnlite to update the ports tree and portupgrade to upgrade ports.
There is nothing specific in UPDATING that addresses this, other than
portupgrade not handling FLAVORS right now.

Do I have to worry about this error? Can I correct it?
-- 
J.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: make reinstall does not work

2017-12-09 Thread Walter Schwarzenfeld

Thanks, this explains and solved the problem.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: make reinstall does not work

2017-12-09 Thread Walter Schwarzenfeld

After upgrade to 10.4, the same problem.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Working on FLAVOR support in portmaster

2017-12-09 Thread Chris H

On Sat, 9 Dec 2017 10:25:17 +0100 "Matthieu Volat"  said


On Fri, 8 Dec 2017 14:18:28 +0100
Baptiste Daroussin  wrote:

> On Fri, Dec 08, 2017 at 02:13:09PM +0100, Alexander Leidinger wrote:
> > Quoting Baptiste Daroussin  (from Thu, 7 Dec 2017
> 14:54:27
> > +0100):
> >   
> > > On Thu, Dec 07, 2017 at 02:49:45PM +0100, Alexander Leidinger wrote:  
> >   
> > > > Alternatively, how would a FreeBSD committer like Stefan or

> > > > Torsten or me or whoever gain write access to
> > > > https://github.com/freebsd/portmaster/ so get some progress in
> > > > the official portmaster location and create a new release
> > > > (sorry my ignorance for github and how it works, I'm used to
> > > > CVS/SVN workflows)?  
> > > 
> > > They just need to ask git admins to get access, I have already asked

> > > Stefan (not
> > > reply yet)
> > > 
> > > They can also ask me directly if they want given I am part of the git
> admins  
> > 
> > And I see that I'm already part of the FreeBSD organisation on github, so

> I
> > should have access. So... currently portmaster is wild-wild-west
> territory?
> > No real owner, anyone willing to fix/improve is free to do so, and it's up
> > to each individual to wear his fireproof-suite (after flavours is settled
> I
> > would be interested to have a look at the local packages installation pull
> > request)?
> >   
> 
> The official maintainer is tz@ for now, he just handed the maintainership to

> se@
> 
> As for push access for now, only git-admin (which I am part of) and bdrewery

> (who use to maintain portmaster) have access. I'll be glad to give push acces
> to
> more people.
> 
> For now I have pushed patches from Stefan in the repo (not the flavor

> support
> but the preliminary to it)
> 
> Best regards,

> Bapt


Would it be possible to have some page to track/show the changes/progress to
the code? For some times, we had a lot of "i'm working on it but behind
closed doors".

For that kind of tools, it would be nice to see the process of upgrading
portmaster (or any other tool for that matter) and get a bit more familiar
with the code.

Even a wip branch would be great to involve more people, and that way, people
would be a bit less in the dark, but that is just my 2 cents...


Doesn't the GitHub activity graphs, diffs, and commit logs already provide
this information? Or have I just misunderstood the question?

--Chris


Have a nice day,

--
Matthieu Volat 



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Working on FLAVOR support in portmaster

2017-12-09 Thread Matthieu Volat
On Fri, 8 Dec 2017 14:18:28 +0100
Baptiste Daroussin  wrote:

> On Fri, Dec 08, 2017 at 02:13:09PM +0100, Alexander Leidinger wrote:
> > Quoting Baptiste Daroussin  (from Thu, 7 Dec 2017 14:54:27
> > +0100):
> >   
> > > On Thu, Dec 07, 2017 at 02:49:45PM +0100, Alexander Leidinger wrote:  
> >   
> > > > Alternatively, how would a FreeBSD committer like Stefan or
> > > > Torsten or me or whoever gain write access to
> > > > https://github.com/freebsd/portmaster/ so get some progress in
> > > > the official portmaster location and create a new release
> > > > (sorry my ignorance for github and how it works, I'm used to
> > > > CVS/SVN workflows)?  
> > > 
> > > They just need to ask git admins to get access, I have already asked
> > > Stefan (not
> > > reply yet)
> > > 
> > > They can also ask me directly if they want given I am part of the git 
> > > admins  
> > 
> > And I see that I'm already part of the FreeBSD organisation on github, so I
> > should have access. So... currently portmaster is wild-wild-west territory?
> > No real owner, anyone willing to fix/improve is free to do so, and it's up
> > to each individual to wear his fireproof-suite (after flavours is settled I
> > would be interested to have a look at the local packages installation pull
> > request)?
> >   
> 
> The official maintainer is tz@ for now, he just handed the maintainership to 
> se@
> 
> As for push access for now, only git-admin (which I am part of) and bdrewery
> (who use to maintain portmaster) have access. I'll be glad to give push acces 
> to
> more people.
> 
> For now I have pushed patches from Stefan in the repo (not the flavor support
> but the preliminary to it)
> 
> Best regards,
> Bapt


Would it be possible to have some page to track/show the changes/progress to 
the code? For some times, we had a lot of "i'm working on it but behind closed 
doors".

For that kind of tools, it would be nice to see the process of upgrading 
portmaster (or any other tool for that matter) and get a bit more familiar with 
the code.

Even a wip branch would be great to involve more people, and that way, people 
would be a bit less in the dark, but that is just my 2 cents...

Have a nice day,

--
Matthieu Volat 


pgprKFsRC8yIM.pgp
Description: OpenPGP digital signature