Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Sun, 24 Apr 2011 12:29:43 -0300, Sergio de Almeida Lenzi wrote: > For me it is working... > running windows XP dnd linux over an old(4.0.2) image it is ok... > very stable... > > Only a problem remains (that is not still fixed): > it is the problem with the vnc in VBoxHeadless > the cursor is not in sync (the vnc cursor) is not > in sync with the XP cursor.. although the sync > is better (compared with 4.0.2 but is still out of sync)... > How to reproduce: > VBoxHeadless --vnc --vncport 5901 --startvm XPimg > then goto another machine and execute: > vncviewer x.x.x.x:5901, the system opens works but the > mouse cursor is not in sync... > > Question: Will there be a fix??? Don't know if that is a bug or a problem of the implementation. I would recommend waiting for the VNC extpack. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: OpenNMS link/port
On 22 April 2011 17:31, Sevan / Venture37 wrote: > On 21 April 2011 17:40, Sevan / Venture37 wrote: >> I've shoved all the revisions of the port I created into a mercurial >> repo & pushed it up to bitbucket. >> https://bitbucket.org/sevan/opennms/overview > > Another repo for the unstable branch of OpenNMS > https://bitbucket.org/sevan/opennms-dev/overview > v1.8.11 port http://www.geeklan.co.uk/files/opennms/opennms-1811-freebsd-port.tgz v1.9.7 port http://www.geeklan.co.uk/files/opennms/opennms-dev-197-freebsd-port.tgz ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On Mon 25 Apr 2011 at 22:55:10 PDT Ade Lovett wrote: On Apr 25, 2011, at 21:41 , Charlie Kester wrote: Maybe freshports could implement a voting system like the one at osx.iusethis.com? "Voting" implies some kind of democracy. I just thought it might be useful to get some actual data to support the inference that an unmaintained port is likely to be an unused and therefore unneeded port. I have no objection to your argument that what gets done is what someone is willing to do. And I am sensitive to the fact that every port imposes some additional burden on the system. I'm all for cleaning out the cruft. I'm not a web programmer and don't have access to the freshports sourcecode. So all I can do there is make a suggestion. But perhaps I'll take some time to go through the list of unmaintained ports and manually check them against the popularity ratings on a site like freshmeat. It's a bit of a leap to assume that a program that's popular on Linux will be as popular on BSD, but it's the best data we have for the time being. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Why archivers/thunar-archive plugin is broken
Hi, I noticed port, archivers/thunar-archive-plugin is marked as broken. I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. May I have log, please ? -- olivier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why archivers/thunar-archive plugin is broken
Olivier Duchateau píše v út 26. 04. 2011 v 19:23 +0200: > Hi, > > I noticed port, archivers/thunar-archive-plugin is marked as broken. > I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. > > May I have log, please ? Sure, http://portsmon.freebsd.org/portoverview.py?category=&portname=thunar-archive-plugin Missing dependency most probably. -- -- Pav Lucistnik Two sausages are in a frying pan. One says, "Geez, it's hot in here isn't it?" And the other one says, "Aah! A talking sausage!" signature.asc Description: This is a digitally signed message part
Re: saving a few ports from death
On Tue, 26 Apr 2011 09:34:24 -0700 Charlie Kester articulated: > It's a bit of a leap to assume that a program that's popular on Linux > will be as popular on BSD, but it's the best data we have for the time > being. If you want to definitively ascertain the popularity of an application, just remove it from the ports structure and see how many users complain. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
Quoth Jerry on Tuesday, 26 April 2011: > On Tue, 26 Apr 2011 09:34:24 -0700 > Charlie Kester articulated: > > > It's a bit of a leap to assume that a program that's popular on Linux > > will be as popular on BSD, but it's the best data we have for the time > > being. > > If you want to definitively ascertain the popularity of an application, > just remove it from the ports structure and see how many users complain. > There could be quite a delay in that reaction -- it might not hit home until the port needs to be rebuilt. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpyiCaUBhmgH.pgp Description: PGP signature
Re: Why archivers/thunar-archive plugin is broken
26.04.2011 21:49, Pav Lucistnik пишет: Olivier Duchateau píše v út 26. 04. 2011 v 19:23 +0200: Hi, I noticed port, archivers/thunar-archive-plugin is marked as broken. I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. May I have log, please ? Sure, http://portsmon.freebsd.org/portoverview.py?category=&portname=thunar-archive-plugin Missing dependency most probably. This patch should work. -- Regards, Ruslan --- Makefile.orig 2011-04-26 01:55:55.0 +0400 +++ Makefile2011-04-26 23:13:30.0 +0400 @@ -22,7 +22,7 @@ USE_XFCE= configenv libexo thunar USE_GETTEXT= yes INSTALLS_ICONS=yes -USE_GNOME= desktopfileutils +USE_GNOME= desktopfileutils intltool USE_GMAKE= yes .include ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich wrote:
> On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote:
>> PBIs for PC-BSD are currently worked on and will hopefully be available
>> in a few days.
>
> Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts
> to provide the PBIs!
>
> PC-BSD 8.x 32bit:
> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi
> ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi
>
> PC-BSD 8.x 64bit:
> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi
> ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi
>
>
> Feedback (positive and negative) from PC-BSD users is very welcome!
>
I installed the 64-bit PBI on my PC-BSD 8.2 machine, but I am unable
to start any virtual machines(both pre-existing VMs or a new VM that I
tried to create). I get the following error dialog:
Failed to open a session for the virtual machine RELENG_8_amd64.
Failed to load VMMR0.r0
(VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
Unknown error creating VM
(VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
Details:
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Tue, 26 Apr 2011 15:42:29 -0400, Ryan Stone wrote:
> On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich
> wrote:
>> On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote:
>>> PBIs for PC-BSD are currently worked on and will hopefully be available
>>> in a few days.
>>
>> Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts
>> to provide the PBIs!
>>
>> PC-BSD 8.x 32bit:
>> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi
>> ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi
>>
>> PC-BSD 8.x 64bit:
>> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi
>> ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi
>>
>>
>> Feedback (positive and negative) from PC-BSD users is very welcome!
>>
>
> I installed the 64-bit PBI on my PC-BSD 8.2 machine, but I am unable
> to start any virtual machines(both pre-existing VMs or a new VM that I
> tried to create). I get the following error dialog:
>
> Failed to open a session for the virtual machine RELENG_8_amd64.
>
> Failed to load VMMR0.r0
> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
>
> Unknown error creating VM
> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
>
> Details:
>
> Result Code:
> NS_ERROR_FAILURE (0x80004005)
> Component:
> Console
> Interface:
> IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
Yeah, thanks we already know. They added some strict hardening checks
in virtualbox 4.0 that fail on PC-BSD. Kris Moore is currently
rebuilding the PBIs with some modifications.
That's exactly why we have call for testers so find such weird problems
that nobody could think of.
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Why archivers/thunar-archive plugin is broken
Ruslan Mahmatkhanov píše v út 26. 04. 2011 v 23:14 +0400: > 26.04.2011 21:49, Pav Lucistnik пишет: > > Olivier Duchateau píše v út 26. 04. 2011 v 19:23 +0200: > >> Hi, > >> > >> I noticed port, archivers/thunar-archive-plugin is marked as broken. > >> I'm using it, and it works fine under FreeBSD 8.2-RELEASE i386. > >> > >> May I have log, please ? > > > > Sure, > > > > http://portsmon.freebsd.org/portoverview.py?category=&portname=thunar-archive-plugin > > > > Missing dependency most probably. > > This patch should work. It does. -- -- Pav Lucistnik It also explains why paper clips just lie there while you look at them, but as soon as you turn your back, they run away, giggling wildly, and transform themselves into coat hangers. signature.asc Description: This is a digitally signed message part
Re: saving a few ports from death
Chip Camden writes: > > If you want to definitively ascertain the popularity of an application, > > just remove it from the ports structure and see how many users complain. > > There could be quite a delay in that reaction -- it might not hit > home until the port needs to be rebuilt. It is also possible it is only important to a fairly small number ... but to those it is absolutely crucial. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On Tue 26 Apr 2011 at 09:34:24 PDT Charlie Kester wrote: I'm not a web programmer and don't have access to the freshports sourcecode. So all I can do there is make a suggestion. But perhaps I'll take some time to go through the list of unmaintained ports and manually check them against the popularity ratings on a site like freshmeat. It's a bit of a leap to assume that a program that's popular on Linux will be as popular on BSD, but it's the best data we have for the time being. FWIW, here are some popularity/vitality stats from freshmeat for unmaintained ports in the sysutils category. Freshmeat calculates these stats as follows: popularity = ((record hits + URL hits) * (subscriptions + 1))^(1/2) where record hits = hits on the freshmeat project page, url hits = clickthroughs to author's projectpage or download site, and subscriptions = freshmeat users following the project. vitality = ((announcements * age) / (last_announcement))^(1/2) "The number of announcements a project has made is multiplied by the number of days it has existed in the database, which is then divided by the days passed since the last release. This way, projects with lots of announcements that have been around for a long time and have recently come out with a new release earn a high vitality score, and old projects that have only been announced once get a low vitality score." For comparison and to give a sense of scale, here are the stats for some well-known projects: NamePopularity Vitality mplayer 3,995.2045.16 MySQL 3,310.5573.39 mutt1,032.7142.53 conky 173.67 3.60 exaile 64.48 3.75 In the attached file, ports listed with popularity and vitality scores = 0 are those where there is no entry in the freshmeat database. I made no effort to verify that a freshmeat project with the same name as the port is in fact the same program, so there might be some false positives in the data. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On Tue 26 Apr 2011 at 14:27:47 PDT Charlie Kester wrote: On Tue 26 Apr 2011 at 09:34:24 PDT Charlie Kester wrote: I'm not a web programmer and don't have access to the freshports sourcecode. So all I can do there is make a suggestion. But perhaps I'll take some time to go through the list of unmaintained ports and manually check them against the popularity ratings on a site like freshmeat. It's a bit of a leap to assume that a program that's popular on Linux will be as popular on BSD, but it's the best data we have for the time being. FWIW, here are some popularity/vitality stats from freshmeat for unmaintained ports in the sysutils category. Freshmeat calculates these stats as follows: popularity = ((record hits + URL hits) * (subscriptions + 1))^(1/2) where record hits = hits on the freshmeat project page, url hits = clickthroughs to author's projectpage or download site, and subscriptions = freshmeat users following the project. vitality = ((announcements * age) / (last_announcement))^(1/2) "The number of announcements a project has made is multiplied by the number of days it has existed in the database, which is then divided by the days passed since the last release. This way, projects with lots of announcements that have been around for a long time and have recently come out with a new release earn a high vitality score, and old projects that have only been announced once get a low vitality score." For comparison and to give a sense of scale, here are the stats for some well-known projects: NamePopularity Vitality mplayer 3,995.2045.16 MySQL 3,310.5573.39 mutt1,032.7142.53 conky 173.67 3.60 exaile 64.48 3.75 In the attached file, ports listed with popularity and vitality scores = 0 are those where there is no entry in the freshmeat database. I made no effort to verify that a freshmeat project with the same name as the port is in fact the same program, so there might be some false positives in the data. Drat, the mailinglist rejected the attachment. If anyone wants to see it, send me a private email and I'll reply with a copy. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On 04/26/2011 14:18, Robert Huff wrote: It is also possible it is only important to a fairly small number ... but to those it is absolutely crucial. Fair enough, then one of them needs to step forward to maintain the port. :) FWIW, I think that the person who suggested deleting the port as a way to gain a metric of its popularity was joking ... Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On Tue 26 Apr 2011 at 14:34:00 PDT Charlie Kester wrote: On Tue 26 Apr 2011 at 14:27:47 PDT Charlie Kester wrote: FWIW, here are some popularity/vitality stats from freshmeat for unmaintained ports in the sysutils category. Drat, the mailinglist rejected the attachment. If anyone wants to see it, send me a private email and I'll reply with a copy. Here are the top ten most "popular" unmaintained ports from this category, in case someone's looking for one to adopt: "name""popularity" "vitality" "k3b" 754.12 120.91 "sg3_utils" 444.46 41.9 "LPRng" 303.65 5.13 "afio"292.62 2.44 "anteater"237.11 4.26 "bchunk" 215.97 2.71 "userinfo"211.26 23.51 "ddrescue"210.72 8.82 "cpuburn" 207.73 1 "cw" 207.28 11.25 k3b looks like an obvious choice. I restricted my search to this category while hammering out my approach. Now that I have my code proved out, I'm going to expand it to look at all unmaintained ports regardless of category. Any suggestions for where I should post the results? (That is, unless you think the bitbucket is the only suitable place for it.) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On Tue, 26 Apr 2011 14:54:05 -0700 Doug Barton articulated: > On 04/26/2011 14:18, Robert Huff wrote: > > It is also possible it is only important to a fairly small > > number ... but to those it is absolutely crucial. > > Fair enough, then one of them needs to step forward to maintain the > port. :) > > FWIW, I think that the person who suggested deleting the port as a > way to gain a metric of its popularity was joking ... Sorry, but I was dead serious. "Don't Know What You Got (Till It's Gone)" "Cinderella" If no one steps up claiming to need the port, then good riddance. If on the other hand a user claims a valid use of the port, let them take responsibility for it or find someone who will. Leaving intact ports that either don't build, cannot be fetched, etcetera does not really make a lot of sense. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On Tue 26 Apr 2011 at 15:15:54 PDT Jerry wrote: If no one steps up claiming to need the port, then good riddance. If on the other hand a user claims a valid use of the port, let them take responsibility for it or find someone who will. Leaving intact ports that either don't build, cannot be fetched, etcetera does not really make a lot of sense. No disagreement here. Just now I ran a query on freshports and found almost 5000 ports with maintainer=po...@freebsd.org. That's way too many! My search for "popularity" metrics is intended to point me, as a maintainer, to ports I might want to adopt now, rather than wait for someone to complain about them. Everything *I* use is already maintained, so I've moved on to looking for things other people might need. But I don't want to waste my time on something that nobody uses. :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On 04/26/2011 15:09, Charlie Kester wrote: Now that I have my code proved out, I'm going to expand it to look at all unmaintained ports regardless of category. Any suggestions for where I should post the results? (That is, unless you think the bitbucket is the only suitable place for it.) As a matter of curiosity, sure, put it on a web site somewhere, no worries. Meanwhile, I think you might be missing the point. :) We should not be looking for reasons to save unmaintained ports. We should be providing resources for those that would like to adopt them, pointing users to suitable alternatives, marking them deprecated so as to encourage maintainers to come forward, etc. In other words, exactly what we have been doing. Yes, there will likely be a period after the ports actually disappear where some of them will need to be resurrected because someone will finally be motivated to step forward. But that's easily done. Meanwhile, let's nuke as much as we can, as fast as we can. We're rapidly closing in on 23,000 ports, which is already an unmanageable mess. We need to be able to delete the cruft if we have any hope of keeping the ship afloat. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Dropping maintainership of my ports
Well, due to some serious philosophical differences re these deprecation campaigns and what seems to be resistance to any further discussion, I don't think I can continue working with the committers. So I'm stepping down. If no one else wants to maintain them, please reset the maintainer of the following ports to po...@freebsd.org: audio/mcplay deskutils/osmo deskutils/teapot devel/argtable devel/egypt devel/gengetopt devel/libXGP devel/libYGP finance/xinvest finance/xquote graphics/box graphics/boxer graphics/fly graphics/sng math/ised misc/vifm misc/xsw multimedia/gpodder multimedia/openshot multimedia/photofilmstrip security/beecrypt security/ccrypt security/nettle security/ranpwd sysutils/dircomp sysutils/gaffitter sysutils/iextract sysutils/lookat sysutils/moreutils sysutils/moreutils-parallel sysutils/ncdu sysutils/rdup textproc/tdhkit x11/fbpanel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
On 4/25/11 8:28 PM, martinko wrote: Ok, I skimmed through the list of deprecated ports Speaking of which, I haven't noticed the old lists of "FreeBSD unmaintained ports which are currently marked broken" and "FreeBSD ports which are currently scheduled for deletion" show up recently. I did have some mixup in my email account for a short period, so I assume I just missed an announcement on how that is handled now. Where is the current list of deprecated ports? -- Garance Alistair Drosehn= g...@gilead.netel.rpi.edu Senior Systems Programmer or g...@freebsd.org Rensselaer Polytechnic Instituteor dro...@rpi.edu ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
Garance A Drosehn writes: > Speaking of which, I haven't noticed the old lists of > "FreeBSD unmaintained ports which are currently marked broken" > and > "FreeBSD ports which are currently scheduled for deletion" > > show up recently. I did have some mixup in my email account > for a short period, so I assume I just missed an announcement > on how that is handled now. I get regular e-mails for "marked as broken". Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: expiration of net/skype ?!
martinko, Hi, Ive read your post below and the following two messages on this among other messages regarding the deprecation of ports. One thing that should be noted is that once the deprecation process is done and over and the port nolonger becomes part of the tree, you are still more than able and welcome to keep the distfiles you have as well checkout just the port directory in question that you are worried about to a seperate place other than the ports tree to maintain it locally. The port may not exactly be in the snapshot tree but just because of that does not mean it will not work for you from a different location. Also note that it may actually be good practice for those that need to use those ports but are unsure of exactly what it involves to upkeep them. It could lead you to another time where you might be interested in being the maintainer for that port. On Tue, Apr 26, 2011 at 01:47:30AM +0200, martinko wrote: >Hi all, > >So what is this deprecation and expiration of net/skype port please ?? >I'm asking because I've been using it successfully for more than a year >and installed it again just this weekend without any issue. And I've >read in the mailing lists many others use it too. So why all that >black-listing ? Should I copy the port to my home folder for future >installations ? Or can I / we do something about keeping it in the >ports tree ? I would surely appreciate if it could stay there. > -- Regards, (jhell) Jason Hellenthal pgpEgF7qh4JeD.pgp Description: PGP signature
Re: saving a few ports from death
On Tue, Apr 26, 2011 at 10:41 PM, Robert Huff wrote: > > Garance A Drosehn writes: > > > Speaking of which, I haven't noticed the old lists of > > "FreeBSD unmaintained ports which are currently marked broken" > > and > > "FreeBSD ports which are currently scheduled for deletion" > > > > show up recently. I did have some mixup in my email account > > for a short period, so I assume I just missed an announcement > > on how that is handled now. > > I get regular e-mails for "marked as broken". > Last one I have is from Jan 21, prior to that it was twice monthly. -- Adam Vande More ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: saving a few ports from death
Adam, On Tue, Apr 26, 2011 at 10:51:39PM -0500, Adam Vande More wrote: >On Tue, Apr 26, 2011 at 10:41 PM, Robert Huff wrote: > >> >> Garance A Drosehn writes: >> >> > Speaking of which, I haven't noticed the old lists of >> > "FreeBSD unmaintained ports which are currently marked broken" >> > and >> > "FreeBSD ports which are currently scheduled for deletion" >> > >> > show up recently. I did have some mixup in my email account >> > for a short period, so I assume I just missed an announcement >> > on how that is handled now. >> >> I get regular e-mails for "marked as broken". >> > >Last one I have is from Jan 21, prior to that it was twice monthly. > Must be they were scheduled for deletion ;) last ones I received here for the two first listed subjects above were recieved January. -- Regards, (jhell) Jason Hellenthal pgpcLCljljQNW.pgp Description: PGP signature
Re: saving a few ports from death
I need to migrate portsmon to another server so that we can start up these periodic emails again. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Dropping maintainership of my ports
27.04.2011 05:43, Charlie Kester пишет: Well, due to some serious philosophical differences re these deprecation campaigns and what seems to be resistance to any further discussion, I don't think I can continue working with the committers. So I'm stepping down. If no one else wants to maintain them, please reset the maintainer of the following ports to po...@freebsd.org: I'm interesting in maintaing of this ports: multimedia/gpodder sysutils/rdup -- Regards, Ruslan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Dropping maintainership of my ports
On Tue, Apr 26, 2011 at 8:43 PM, Charlie Kester wrote: > > Well, due to some serious philosophical differences re these > deprecation campaigns and what seems to be resistance to any further > discussion, I don't think I can continue working with the committers. > So I'm stepping down. > > If no one else wants to maintain them, please reset the maintainer of the > following ports to po...@freebsd.org: > > audio/mcplay > deskutils/osmo > deskutils/teapot > devel/argtable > devel/egypt > devel/gengetopt > devel/libXGP > devel/libYGP > finance/xinvest > finance/xquote > graphics/box > graphics/boxer > graphics/fly > graphics/sng > math/ised > misc/vifm > misc/xsw > multimedia/gpodder > multimedia/openshot > multimedia/photofilmstrip > security/beecrypt > security/ccrypt > security/nettle > security/ranpwd > sysutils/dircomp > sysutils/gaffitter > sysutils/iextract > sysutils/lookat > sysutils/moreutils > sysutils/moreutils-parallel > sysutils/ncdu > sysutils/rdup > textproc/tdhkit > x11/fbpanel O-o-ok... philosophical differences. audio/mcplay and the 3 multimedia-related ports, + fbpanel, have many users, AFAIK, and require much works. We need to someone to take them soon. > > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Dropping maintainership of my ports
On Tue 26 Apr 2011 at 22:15:58 PDT Zhihao Yuan wrote: On Tue, Apr 26, 2011 at 8:43 PM, Charlie Kester wrote: Well, due to some serious philosophical differences re these deprecation campaigns and what seems to be resistance to any further discussion, I don't think I can continue working with the committers. So I'm stepping down. If no one else wants to maintain them, please reset the maintainer of the following ports to po...@freebsd.org: audio/mcplay deskutils/osmo deskutils/teapot devel/argtable devel/egypt devel/gengetopt devel/libXGP devel/libYGP finance/xinvest finance/xquote graphics/box graphics/boxer graphics/fly graphics/sng math/ised misc/vifm misc/xsw multimedia/gpodder multimedia/openshot multimedia/photofilmstrip security/beecrypt security/ccrypt security/nettle security/ranpwd sysutils/dircomp sysutils/gaffitter sysutils/iextract sysutils/lookat sysutils/moreutils sysutils/moreutils-parallel sysutils/ncdu sysutils/rdup textproc/tdhkit x11/fbpanel O-o-ok... philosophical differences. audio/mcplay and the 3 multimedia-related ports, + fbpanel, have many users, AFAIK, and require much works. We need to someone to take them soon. I don't know what you mean by "requires much works". The only ones of these ports that are not up-to-date are xquote and nettle. There is already an open PR to update nettle. All it needs is some attention from a committer. Frankly, xquote should be deprecated, as it's an old-style Motif app that's so ugly I'll bet no one uses it. I only took it (and the related xinvest) because they got reinstated after I pointed out they were still fetchable at a new location. Everything else is in good shape. I've been told that we shouldn't be looking for reasons to save any unmaintained port, and I was specifically told this in response to my efforts to identify ports that have a lot of users. So I don't think current policy supports the conclusion that "we need to find someone to take them soon." There, in a nutshell, you have the philosophical disagreement which led to my decision to be done with ports. If the powers-that-be want to deprecate all of these and lighten the load on the system and themselves, I no longer care. I know how to download a tarball and run through the configure/make/install routine, so I'll still be able to run the software I need. I thought I'd lend a hand to those who don't have those skills, but it doesn't seem that this contribution is welcomed or appreciated. "There are too many ports!" (Sorry if I'm ranting, I am still very angry about all this.) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Dropping maintainership of my ports
sorry for the top post, but shouolder is killing me. idea 1: can the 'summer of code' guys help us out with this. idea 2. why oh why can we not live with the fbsd and debian paradigm? the reason i've kept my domain here at home is because i like the flexibility i see. but keeping ports current is getting to be impossible. there are too many distros of every open src os and maybe if net and free [RE]-hjoined arms that 3rd idea would work. i'm sure that many of you guys kno w that aristotle was a polymath; he was as sharp as anybody i have ever studied. his highest 'virtue' was pragmatism.given the headaches with maintaining ports, and much more, isn' t it time to look in new directions? idea 4. axe the number of ports. if person x or y want to maintain a port of his ow n , outstanding. he can post a note to the lists. idea 5. beging a completely separate, independent group for orphaned ports [ for free, net, debian, ubuntu, redhat, foobar opsys. a last note: i started out as a porter. loved i t and excelled at it. but it never was easy. it's still 3/2 * bear|bitch|swine. ergo, i know why many of this list and org are slowing or dropping out. Enuf, -g . On Tue, Apr 26, 2011 at 06:43:43PM -0700, Charlie Kester wrote: > Date: Tue, 26 Apr 2011 18:43:43 -0700 > From: Charlie Kester > Subject: Dropping maintainership of my ports > To: freebsd-ports@freebsd.org > Mail-Followup-To: freebsd-ports@freebsd.org > X-Mailer: Mutt 1.4.2.3i > > > Well, due to some serious philosophical differences re these > deprecation campaigns and what seems to be resistance to any further > discussion, I don't think I can continue working with the committers. > So I'm stepping down. > > If no one else wants to maintain them, please reset the maintainer > of the following ports to po...@freebsd.org: > > audio/mcplay > deskutils/osmo > deskutils/teapot > devel/argtable > devel/egypt > devel/gengetopt > devel/libXGP > devel/libYGP > finance/xinvest > finance/xquote > graphics/box > graphics/boxer > graphics/fly > graphics/sng > math/ised > misc/vifm > misc/xsw > multimedia/gpodder > multimedia/openshot > multimedia/photofilmstrip > security/beecrypt > security/ccrypt > security/nettle > security/ranpwd > sysutils/dircomp > sysutils/gaffitter > sysutils/iextract > sysutils/lookat > sysutils/moreutils > sysutils/moreutils-parallel > sysutils/ncdu > sysutils/rdup > textproc/tdhkit > x11/fbpanel > > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 7.98a release of Jottings: http://jottings.thought.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
How are [MAINTAINER] patches handled and why aren't PRs FIFO?
Since we're already in the mood to discuss FreeBSD ports issues, maybe somebody can clear something up for me. Several days ago, I submitted a patch for a port I maintain: ports/156541 "[MAINTAINER] Upgrade lang/gnat-aux to release version and add C++" Nobody has touched it, but many other PRs after that submission have been assigned, etc. So I have two questions: 1) What's involved with processing a patch from a maintainer? Is it simply a committer commits it on behalf of the maintainer (iow very easy?). Or is it the other end of the spectrum where it has to go through Tinderbox? I would assume the maintainer is trusted and the patch is applied without testing. 2) I have very well aware that people dedicate their own time, etc, and I think that explains why the PRs are getting cherry picked. But seriously, shouldn't there be a policy to process these PRs in order? I'm sure it's been like this for years, but it doesn't seem like the best approach to me. Or at least the fairest. Maybe if an interesting PR is submitted it will give extra incentive to process the waiting PRs to get to it. -- John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Dropping maintainership of my ports
On 4/27/2011 8:09 AM, Charlie Kester wrote: I've been told that we shouldn't be looking for reasons to save any unmaintained port, and I was specifically told this in response to my efforts to identify ports that have a lot of users. So I don't think current policy supports the conclusion that "we need to find someone to take them soon." There, in a nutshell, you have the philosophical disagreement which led to my decision to be done with ports. I skimmed the entire conversation this morning. The summary is you have an opinion that apparently nobody else shares. I maintain 7 ports. The majority of these ports had already been deleted years ago, or should have already been deprecated. So after years, somebody (me) showed up with enough motivation to resurrect the ports. That's all people are saying: If the port is important enough, somebody will step up to save it or resurrect it. If that doesn't happen, then it doesn't deserve to be in the tree once it doesn't build anymore. If the powers-that-be want to deprecate all of these and lighten the load on the system and themselves, I no longer care. I know how to download a tarball and run through the configure/make/install routine, so I'll still be able to run the software I need. I thought I'd lend a hand to those who don't have those skills, but it doesn't seem that this contribution is welcomed or appreciated. "There are too many ports!" (Sorry if I'm ranting, I am still very angry about all this.) Obviously the maintenance of ports is appreciated and welcomed. You're just sulking because your idea of identifying popular ports wasn't met with enthusiasm. If the port really is popular, somebody will take it over, I'm sure. I don't know you, or your history of contributions, etc, so all I can judge is what I read today. I don't think this reaction shows a lot of character. Anyway, I'm sure your wish of returning all the ports to nobody will be granted and life will go on. As a FreeBSD user, thanks for effort that you did in the past. Regards, John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
