Re: x11/xterm: no coloured prompt and characters after update (BLIND!)
On Tue, 3 Jun 2014 21:02:47 +0200 O. Hartmann ohart...@zedat.fu-berlin.de wrote: After today's update of port x11/xterm from xterm-304 to xterm-305, the terminals I start on the desktop (windowmaker) do not show any coloured prompt or characters - they have the same colour as the background! Flying blind! This is somehow boring! The only way to get some coloured (and therefor visible) characters is to select from VT Font menu within the xterm Use True Type - then giant chars show up, but they are coloured as expected. can you try update to xterm-306 ? -- wbr, tiger ___ 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: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla
On 05.06.2014 02:19, Kevin Oberman wrote: On Wed, Jun 4, 2014 at 12:59 AM, John Marino freebsd.cont...@marino.st mailto:freebsd.cont...@marino.st wrote: On 6/4/2014 09:46, Torsten Zuehlsdorff wrote: I know for certain that people in the past have given up after submitting PRs that were never answered. While I know we don't have the manpower to deal with all of them, that should at least be our ideal. Yes. It is really frustrating to create a bug-report with a complete patch just to wait for some months and seeing that nothing happens. And even after offering help it is closed with timeout and the bug still exists. That's not what a timeout is. Timeout does not mean close the PR regardless after a certain about of time. PRs generally stay open indefinitely unless the problem has been resolved or the situation is obsolete. If what you said occurred, that was wrong. I'd have to see the actual PR to verify no misunderstanding though. I just want to nip in the bud some kind of misconcept about timeouts ... which means (for ports PRs) any committer can taken over the PR and the maintainer has no right to complain about that. The timeout is on the maintainer, not the PR. And yes: trivial bugs are important. If something trivial not work, why use it? So it should be very easy to submit a report. Non-sequitur. Besides trivial being an extremely loaded word that doesn't indicate the true cost of the fix, I see no relation of the severity of said bug versus the reporting process. It would logically follow that critical bugs should therefore be extremely difficult to report, which is, of course, absurd. The process should be the same regardless. John I think that there are two different timeouts involved. 1. Maintainer fails to respond to a port update PR and any committer can pick it up. PR is NOT closed. 2. Committer (possibly maintainer) looks at an old PR for a port that has been updated to a new port version. The commiter is unable to reproduce the problem and asks the submitter to confirm whether it has been fixed. If the submitter fails to respond, the PR is marked as timed out and closed. Neither was. It was a mistake by the comitter. We cleared the problem off-list. I wrote a new patch and it is already in the ports Greetings, Torsten ___ 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
what is https://phabric.freebsd.org/
And what is this file for:
$ cat /usr/ports/.arcconfig
{
project.name: P,
phabricator.uri : https://phabric.freebsd.org/;
}
Thanks
Anton
___
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: what is https://phabric.freebsd.org/
On 05 Jun 2014, at 10:49, Anton Shterenlikht me...@bris.ac.uk wrote:
And what is this file for:
$ cat /usr/ports/.arcconfig
{
project.name: P,
phabricator.uri : https://phabric.freebsd.org/;
}
See https://wiki.freebsd.org/CodeReview
Thanks
Anton
___
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
___
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
print/cups-base web interface broken unable to print
# service cupsd onestart, then http://localhost:631/ Not Found message on browser page. I can print through LPD, but cannot print through any cups defined printer. * print/cups-base enabled options: LIBPAPER, PYTHON, DBUS, XDG_OPEN, MDNSRESPONDER * I have completely removed /usr/local/etc/cups, deinstalled all cups-related binaries, then clean-installed those same binaries. * If I enable option PHP rebuild, compile finishes but install fails: make install -C print/cups-base === Installing for cups-base-1.7.2_1 === Checking if print/cups-base already installed === Registering installation for cups-base-1.7.2_1 pkg-static: lstat(/asp/obj/asp/git/ports/print/cups-base/work/stage/usr/local/lib/php/20121212-zts/phpcups.so): No such file or directory pkg-static: lstat(/asp/obj/asp/git/ports/print/cups-base/work/stage/usr/local/lib/php/20121212-zts/): No such file or directory *** Error code 74 * Log-Level is set to debug and shows: Listening to :631 (IPv6) Listening to 127.0.0.1:631 (IPv4) Listening to /var/run/cups.sock (Domain) Remote access is disabled. Using default TempDir of /var/spool/cups/tmp... Configured for up to 100 clients. Allowing up to 100 client connections per host. Using policy default as the default. Full reload is required. ... Cleaning out old files in /var/spool/cups/tmp. cupsdCleanFiles(path=/var/db/cups, pattern=*.ipp) Cleaning out old files in /var/db/cups. *Unable to open listen socket for address :631 - Address family not supported by protocol family.* Listening to 127.0.0.1:631 on fd 8... Listening to /var/run/cups.sock:631 on fd 9... Resuming new connection processing... [Client 12] Accepted from localhost:631 (IPv4) [Client 12] Waiting for request. [Client 12] GET / HTTP/1.1 cupsdSetBusyState: newbusy=Active clients, busy=Not busy *[Client 12] No authentication data provided.* [Client 12] Closing because Keep-Alive disabled [Client 12] Closing connection. cupsdSetBusyState: newbusy=Not busy, busy=Active clients - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/print-cups-base-web-interface-broken-unable-to-print-tp5918098.html Sent from the freebsd-ports mailing list archive at Nabble.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
pkg-fallout jaila
Hi, Can anyone please tell me what are the jails used in pkg-fallout-freebsd? I can see that 9.1 is still being used. Beside these what are the legacy versions those are used in the builder? Thanks in advance. BR, Muhammad ___ 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: pkg-fallout jaila
On Thu, Jun 05, 2014 at 03:35:49PM +0600, Muhammad Moinur Rahman wrote: Hi, Can anyone please tell me what are the jails used in pkg-fallout-freebsd? I can see that 9.1 is still being used. Beside these what are the legacy versions those are used in the builder? Thanks in advance. The packages are always built on the lowest supported version of a given branch, meaning 9.1 for 9 packages, 8.4 for 8 packages and 10.0 for 10 packages All with the latest security patches applied regards, Bapt pgpVFdKSKlxL4.pgp Description: PGP signature
Re: ejabberd update to 14.05 no longer runs
On 2014-06-04 19:03, Matthieu Volat wrote: On Wed, 04 Jun 2014 16:08:18 +0200 Neal Nelson nea...@nicandneal.net wrote: Hi. I've just updated ejabberd to the latest 14.05 version, but alas it no long runs. Normally I would do some debugging, but this is erlang, so all bets are off as I have no idea what to look at, hence the vague problem description. I'd be very grateful is anyone has any idea why a perfectly functional ejabber installation no longer works after the upgrade and how I might go about fixing it. Thanks. ___ Did you converted your configuration to yaml, or provided a fresh new one, before restarting the service? Ejabberd no longer use the erlang-based conf files... Thanks. That was indeed the problem. This should really be an entry in UPDATING though, as I had no idea and the result was catastrophic for the operation of the server. We also seem to be missing to convert_to_yaml command for ejabberdctl, but luckily it was not too difficult to convert manually. ___ 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
[QAT] 356235: 4x leftovers
Port is stage safe - Build ID: 20140602151200-43046 Job owner: pa...@freebsd.org Buildtime: 3 days Enddate: Thu, 05 Jun 2014 14:10:40 GMT Revision: 356235 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=356235 - Port:mail/kshowmail 4.1_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~pa...@freebsd.org/20140602151200-43046-345518/kshowmail-4.1_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~pa...@freebsd.org/20140602151200-43046-345519/kshowmail-4.1_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~pa...@freebsd.org/20140602151200-43046-345520/kshowmail-4.1_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~pa...@freebsd.org/20140602151200-43046-345521/kshowmail-4.1_2.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140602151200-43046 redports https://qat.redports.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
Re: To all port maintainers: libtool
On 5/8/14, 5:16 PM, Tijl Coosemans wrote: On Thu, 8 May 2014 21:27:56 +0200 Alexander Leidinger wrote: On Thu, 8 May 2014 00:24:20 +0200 Tijl Coosemans t...@freebsd.org wrote: USES=libtool modifiers :keepla and :oldver. You wasn't explicit, which may be beneficial for people which don't have English as their first language... Is it right that you tell everyone to replace USE_AUTOTOOLS=YES with USES=libtool:keepla:oldver now? No, it is either USES=libtool, USES=libtool:keepla or USES=libtool:oldver. Most ports will eventually use the first form but for the time being many may have to use :keepla or :oldver. To know which one to use you can follow these steps: If a port does not install any libraries always use USES=libtool. If it does, try USES=libtool:keepla. If this causes the major version number of a library to change, use USES=libtool:oldver. You can upgrade USES=libtool:oldver to USES=libtool:keepla if 1) an update to a new version of the port would have changed the library version anyway, or 2) you grep /usr/ports/INDEX-* for your port and find that only a dozen or so other ports depend on it so bumping PORTREVISION on them isn't that bad. You can upgrade USES=libtool:keepla to USES=libtool if you grep /usr/ports/INDEX-* for your port and verify that all of the ports that install .la files also have some form of USES=libtool in their Makefile. Unless the number of dependent ports is small I don't really recommend this. There's no harm in keeping .la files. And for ports with a large dependency chain behind you more or less suggest to keep the modifiers until the ports tree is converted (let's assume a port which is needed by all desktop environments, then we are roughly speaking at about 3k ports or more which depend upon it, which is close enough to the ports tree for this discussion ;-) )? Yes. At some point ports with :oldver will be converted to :keepla. Depending on how many ports these are, this will probably happen in batches of related ports and may need to be coordinated by portmgr. I don't expect this to be something that individual port maintainers will have to worry about. And at another point the dependency records of all .la files will be empty in all ports (currently about 1400 ports left). From then on it will be safe to replace USES=libtool:keepla with USES=libtool. I don't know what .la files are used for and have no time currently to research it. What is the impact to non-ports consumers of removing .la files? Do they also need patches to make them build? And if there is no impact, I am thoroughly confused on when to keep or not keep them. -- Regards, Bryan Drewery ___ 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
Portmaster -g no longer builds packages for dependencies?
I built a clean jail yesterday, portsnapped a new ports tree (i.e. fetch and extract) and built portmaster. Then I did portmaster -dgGH x11/xorg. It seemed to build Xorg properly, but there were no packages built for any of the many dependencies. I tried an older portmaster version that used to work and it seemed to have the same problem. Is this difficulty due to changes in the ports tree that broke dependent package building? Any suggestions? I have avoided poudriere so far because I like having no ports tree except in the jail. ___ 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
[Bug 129741] [patch] bsd.port.mk: support systems that have been built WITHOUT_INFO=yes (no makeinfo install-info)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129741 Baptiste Daroussin b...@freebsd.org changed: What|Removed |Added Status|In Discussion |Needs Help CC||b...@freebsd.org --- Comment #9 from Baptiste Daroussin b...@freebsd.org --- this is still needed, I to think having a USES=info might be a good idea -- You are receiving this mail because: You are on the CC list for the bug. ___ 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: To all port maintainers: libtool
On Thu, 05 Jun 2014 09:39:21 -0500 Bryan Drewery wrote: I don't know what .la files are used for and have no time currently to research it. What is the impact to non-ports consumers of removing .la files? Do they also need patches to make them build? Removing a .la file is somewhat like a library version bump. Anything that depends on it needs to be recompiled. e.g. externProgA links to externLibB which links to portsLibC The links between files are like this: progA - libB.so - libC.so - libC.so (due to libtool overlinking) libB.la - libC.la Linking progA with libB using libtool goes through libB.la. If libC.la disappears the link in libB.la goes stale and linking progA will fail. externLibB needs to be recompiled first. libB.la will then contain -lC instead of libC.la. And if there is no impact, I am thoroughly confused on when to keep or not keep them. Keeping them is a temporary measure. You can take the previous example but with A, B and C all in the ports tree. If you remove libC.la linking port A may fail unless for all ports B, libB.la does not exist or it contains no references to libC.la (for instance because port B has USES=libtool), or you bump PORTREVISION on port B to force recompilation. If you find you have to bump PORTREVISION on too many ports B then just keep the .la file for now. ___ 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: print/cups-base web interface broken unable to print
I reinstalled cups-base from the public FreeBSD repo rather than my poudriere repo. The web interface has started working once more, but printing continues to fail, with job state showing: stopped - Filter failed. Anyone per chance with insight into filter failed error? I have already removed and re-created the printer several times. Installed cups related packages: cups-base-1.7.2_1, cups-client-1.7.2, cups-filters-1.0.53_1, cups-pdf-2.6.1_1, cups-pstoraster-8.15.4_7, foomatic-db-20140425, gutenprint-5.2.8, gutenprint-base-5.2.8, gutenprint-cups-5.2.8_1, gutenprint-foomatic-5.2.8_1, gutenprint-ijs-5.2.8 - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/print-cups-base-web-interface-broken-unable-to-print-tp5918098p5918202.html Sent from the freebsd-ports mailing list archive at Nabble.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: FreeBSD ports you maintain which are out of date
I've submitted a patch updating graphics/sng and taking maintainership: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188775 Regards, BL On Thu, Jun 5, 2014 at 11:19 AM, portsc...@freebsd.org wrote: Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/dia2code | 0.8.5 | 0.8.6 +-+ graphics/sng| 1.0.5 | 1.0.6 +-+ www/webservices | 0.5.5 | 0.6.3 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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 ___ 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
Ports back to the heap
I've spent a few days trying to get these ports to support staging and to actually compile with any version of GCC or CLANG and I cannot. games/vegastrike-data games/vegastrike Currently the last release from the developer was 2 years ago. In reading threads, there are numerous patches flying around to get it to compile with clang or a more modern compiler. If/when the team behind vegastrike makes a new update, I might be up for taking over maintainership but for now, I think this port should be depricated and put back on the heap for possible deletion. Maybe someone else can pick this up but it is too much of a mess for my time. I still have one other port to beat into submission for staging. Thanks! Rusty Nejdl ___ 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
Who was the mental genius
That decided it was a good idea to completely break ports to force people
to upgrade? You couldn't come up with a warning system instead of outright
breaking ports? The idiots are apparently running the asylum. {{sigh}}
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
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: Ports back to the heap
On Thu, Jun 5, 2014 at 10:22 PM, Rusty Nejdl rne...@ringofsaturn.com wrote: I've spent a few days trying to get these ports to support staging and to actually compile with any version of GCC or CLANG and I cannot. games/vegastrike-data games/vegastrike Currently the last release from the developer was 2 years ago. In reading threads, there are numerous patches flying around to get it to compile with clang or a more modern compiler. If/when the team behind vegastrike makes a new update, I might be up for taking over maintainership but for now, I think this port should be depricated and put back on the heap for possible deletion. Maybe someone else can pick this up but it is too much of a mess for my time. I still have one other port to beat into submission for staging. Thanks for the notice, I have reset maintainership and marked the ports deprecated. Cheers, Antoine ___ 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: Who was the mental genius
On 6/06/2014 6:09 AM, Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
Are you referring to the /usr/ports/UIDs going away? I experienced a
ports build failure attributable to that. Fortunately the person
responsible redressed within 62 minutes. But it does raise the spectre
of change control over components that are effectively live.
It would be nice if /usr/ports/Mk experienced a change control regime
that the base operating system uses - beta testing, release testing,
deployment; and the files within /usr/ports should probably fall into
that category, not the directory tree which port maintainers and
commiters change to keep time variable applications up-to-date.
Regards, Dewayne.
___
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: Who was the mental genius
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force people to
upgrade? You couldn't come up with a warning system instead of outright
breaking ports? The idiots are apparently running the asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it that
broke?
AvW
--
I'm not completely useless, I can be used as a bad example.
pgpx61g2mLgqo.pgp
Description: PGP signature
Filezilla
Hi, Is it just me, or is Filezilla 3.8 currently unable to install?? I get messages like these: pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/vi_VN/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/vi_VN/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/uk_UA/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/uk_UA/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/th_TH/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/th_TH/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/sl_SI/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/sl_SI/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/sk_SK/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/sk_SK/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/ro_RO/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/ro_RO/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/pl_PL/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/pl_PL/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/nn_NO/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/nn_NO/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/nb_NO/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/nb_NO/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/mk_MK/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/mk_MK/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/lv_LV/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/lv_LV/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/lt_LT/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/lt_LT/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/ky/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/ky/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/ko_KR/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/ko_KR/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/km_KH/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/km_KH/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/kab/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/kab/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/ja_JP/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/ja_JP/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/id_ID/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/id_ID/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/hu_HU/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/hu_HU/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/he_IL/LC_MESSAGES/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/he_IL/): No such file or directory pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/gl_ES/LC_MESSAGES/): No such
Re: Who was the mental genius
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced to
upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
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: Who was the mental genius
On 6/5/2014 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it
that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced
to upgrade to a supported version.
You are wrong and as pleasant as usual. Stop believing what you read in
forums.
___
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: Who was the mental genius
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it
that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced
to upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
No it was not done deliberately
Newer freebsd version moved to a newer make utility, and support for the
old one has been dropped after support for all old releases containing
it was ceased.
Which releases are supported and for how long is well known, and
published in here when a new release is published:
http://www.freebsd.org/security/security.html#sup
The updates are free, as in no payment needed. What's keeping you from
performing a binary update of the base system every year or so?
Running such an old system as any of the unsupported releases is also
most probably exposing you to security vulnerabilities.
Sometimes to change things you need to break compatibility, the project
did wait till it was coherent with what was promised before doing this.
--
Guido Falsi m...@madpilot.net
___
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: Who was the mental genius
W dniu 2014-06-05 23:43, Paul Schmehl pisze:
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it
that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced
to upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
This change was needed 8 months ago, but was hold until the EOL of 8.3
arrived [1].
Freeze your ports on revision 352985 until you upgrade base system to
supported version.
[1] https://www.mail-archive.com/freebsd-ports@freebsd.org/msg57884.html
--
best regards,
Lukasz Wasikowski
___
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
[QAT] 356371: 2x depend (ignored: is only for amd64, while you are running i386 in devel/libe), 4x leftovers, 7x ???, 4x depend (??? in databases/mongodb), 39x success
Upgrade snappy to 1.1.1, and bump all related PORTREVISION to chase shared library version. PR: ports/190409 Submitted by: ports at robakdesign.com Approved by:portmgr@ (for NO_STAGE) - Build ID: 20140603143600-23875 Job owner: vani...@freebsd.org Buildtime: 2 days Enddate: Fri, 06 Jun 2014 00:32:44 GMT Revision: 356371 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=356371 - Port:archivers/snappy 1.1.1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346166/snappy-1.1.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346167/snappy-1.1.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346168/snappy-1.1.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346169/snappy-1.1.1.log - Port:databases/leveldb 1.15.0_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346170/leveldb-1.15.0_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346171/leveldb-1.15.0_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346172/leveldb-1.15.0_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346173/leveldb-1.15.0_1.log - Port:databases/mongodb 2.6.1_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: ??? Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346174/mongodb-2.6.1_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346175/mongodb-2.6.1_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: ??? Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346176/mongodb-2.6.1_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346177/mongodb-2.6.1_1.log - Port:databases/p5-Tie-LevelDB 0.07_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346178/p5-Tie-LevelDB-0.07_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346179/p5-Tie-LevelDB-0.07_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346180/p5-Tie-LevelDB-0.07_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346181/p5-Tie-LevelDB-0.07_2.log - Port:databases/pecl-leveldb 0.1.4_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346182/pecl-leveldb-0.1.4_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346183/pecl-leveldb-0.1.4_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346184/pecl-leveldb-0.1.4_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346185/pecl-leveldb-0.1.4_1.log - Port:databases/py-leveldb 0.1.20130428_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~vani...@freebsd.org/20140603143600-23875-346186/py27-leveldb-0.1.20130428_2.log Buildgroup: 8.4-QAT/i386
Re: Who was the mental genius
For me, I had to upgrade an 8.2 FreeBSD to 10.0 current. and got the same issue... What I did was: 1) copy the make program from the 10.0 series to replace the /usr/bin/make 2) copy via tar /usr/src /usr/obj from the 10.0 to the 8.2 cd /usr/src export KERNCONF to the config in /usr/src/sys/amd64/conf make installworld make installkernel save old /etc . make distribution this install the new rc.d and /etc/files than copy back /etc/profile, /etc/master.passwd, /etc/group, /etc/rc.conf... to /etc fix the /boot/loader.conf Than boot the system in 10.0 stable... After that... the ports and portmaster started working again... so I took a list of the packages... pkg info -qo /tmp/pkglist than delete all packages. pkg delete -fay than pkg install $(cat /tmp/pkglist), this will install all the packages direct from freebsd.org some will not install as they do not exists.. in freebsd.org so... using portmaster --no-confirm $(cat /tmp/pkglist) builds the system in complete order that is now running on 10.0 stable... the hole process took about 6 hours.. I did it remote during the night... Hope it can help ___ 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: Who was the mental genius
Hi,
On Thu, 05 Jun 2014 15:09:53 -0500
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system
instead of outright breaking ports? The idiots are apparently
running the asylum. {{sigh}}
this is the reason why I am asking for versions on the ports tree since
a decade. Ok, we have the revision now. Just go back in the revision
until it works. It is a good practice to make a note of the revision of
the running ports tree you have before updating it.
Erich
___
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: Who was the mental genius
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi m...@madpilot.net wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it
that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced
to upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
No it was not done deliberately
Newer freebsd version moved to a newer make utility, and support for the
old one has been dropped after support for all old releases containing
it was ceased.
So they dropped the support accidentally? Is this really the time to argue
semantics?
Which releases are supported and for how long is well known, and
published in here when a new release is published:
http://www.freebsd.org/security/security.html#sup
The updates are free, as in no payment needed. What's keeping you from
performing a binary update of the base system every year or so?
I have two hosts on the internet for which the backup system failed. I
didn't catch it right away, so now I'm several days behind on backups. I
need to install a new system, but it requires ports I don't yet have
installed. So now I have two options; upgrade with my fingers crossed and
hope it works or scramble to find some way to backup before I upgrade just
in case the upgrade fails.
Running such an old system as any of the unsupported releases is also
most probably exposing you to security vulnerabilities.
First of all, 8.3 is not an old system. Secondly, you used to be able to
run old systems for a long time after support was dropped without
encountering issues like this. Finally, I'm a port maintainer of a fair
number of ports, so FreeBSD isn't free for me. I put a lot of time into it.
When such a drastic change is made, it should be well advertised in advance
(think the pkgng announcement you get every time you install a port) and
not implemented in such a disruptive manner. It's clear from the forum
announcement that I linked to that I was not the only one caught by
surprise and that it didn't even work on supported versions when the change
was first implemented.
Sometimes to change things you need to break compatibility, the project
did wait till it was coherent with what was promised before doing this.
What you call the project is made up of people. SOMEONE should be
thinking through the impact on end users and helping to plan such major
transitions in a way that's least disruptive IF you want the system to
remain viable.
Perhaps this is part of the reason adoption of FreeBSD has dropped so
dramatically over the years. I'm retiring in 18 months. When I leave, the
last FreeBSD system goes with me. No one is even interested in learning it
any more. FreeBSD used to rule the web. Now it's Linux. There's a lesson
in there for those that are listening, but apparently the project is not.
Which is sad, because FreeBSD, IMNSHO, is a very good OS.
There's no need to respond to this. I'm just venting. And clearly my
opinion doesn't matter anyway.
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
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: Who was the mental genius
On 6/5/14, 7:32 PM, Paul Schmehl wrote:
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi m...@madpilot.net
wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system
instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it
that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced
to upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
No it was not done deliberately
Newer freebsd version moved to a newer make utility, and support for the
old one has been dropped after support for all old releases containing
it was ceased.
So they dropped the support accidentally? Is this really the time to
argue semantics?
Which releases are supported and for how long is well known, and
published in here when a new release is published:
http://www.freebsd.org/security/security.html#sup
The updates are free, as in no payment needed. What's keeping you from
performing a binary update of the base system every year or so?
I have two hosts on the internet for which the backup system failed.
I didn't catch it right away, so now I'm several days behind on
backups. I need to install a new system, but it requires ports I
don't yet have installed. So now I have two options; upgrade with my
fingers crossed and hope it works or scramble to find some way to
backup before I upgrade just in case the upgrade fails.
Running such an old system as any of the unsupported releases is also
most probably exposing you to security vulnerabilities.
First of all, 8.3 is not an old system. Secondly, you used to be able
to run old systems for a long time after support was dropped without
encountering issues like this. Finally, I'm a port maintainer of a
fair number of ports, so FreeBSD isn't free for me. I put a lot of
time into it.
When such a drastic change is made, it should be well advertised in
advance (think the pkgng announcement you get every time you install a
port) and not implemented in such a disruptive manner. It's clear from
the forum announcement that I linked to that I was not the only one
caught by surprise and that it didn't even work on supported versions
when the change was first implemented.
Sometimes to change things you need to break compatibility, the project
did wait till it was coherent with what was promised before doing this.
What you call the project is made up of people. SOMEONE should be
thinking through the impact on end users and helping to plan such
major transitions in a way that's least disruptive IF you want the
system to remain viable.
Perhaps this is part of the reason adoption of FreeBSD has dropped so
dramatically over the years. I'm retiring in 18 months. When I
leave, the last FreeBSD system goes with me. No one is even
interested in learning it any more. FreeBSD used to rule the web.
Now it's Linux. There's a lesson in there for those that are
listening, but apparently the project is not. Which is sad, because
FreeBSD, IMNSHO, is a very good OS.
There's no need to respond to this. I'm just venting. And clearly my
opinion doesn't matter anyway.
I think your opinion matters.
I agree I would be rudely surprised by such a breakage myself. That
said we need to find a way to desupport things eventually.
Any ideas on what should have been done that can be done in a short
amount of code as possible? Perhaps there's some way to determine
between the old and new makes and just add some kind of target like:
# psuedo make(1) code:
.ifndef THIS_IS_NEW_MAKE
.BEGIN:
echo your system is running an unsupported version of FreeBSD the
last version to support this is r232423
echo please run svn update -r232423 to get a working ports tree as
of that date or upgrade to a more recent
echo freebsd release using freebsd-update [[insert link to
freebsd-update]]
exit 1
.endif
-Alfred
___
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: Who was the mental genius
--On June 5, 2014 at 8:08:35 PM -0700 Alfred Perlstein alf...@freebsd.org
wrote:
On 6/5/14, 7:32 PM, Paul Schmehl wrote:
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi m...@madpilot.net
wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system
instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it
that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced
to upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
No it was not done deliberately
Newer freebsd version moved to a newer make utility, and support for the
old one has been dropped after support for all old releases containing
it was ceased.
So they dropped the support accidentally? Is this really the time to
argue semantics?
Which releases are supported and for how long is well known, and
published in here when a new release is published:
http://www.freebsd.org/security/security.html#sup
The updates are free, as in no payment needed. What's keeping you from
performing a binary update of the base system every year or so?
I have two hosts on the internet for which the backup system failed.
I didn't catch it right away, so now I'm several days behind on
backups. I need to install a new system, but it requires ports I
don't yet have installed. So now I have two options; upgrade with my
fingers crossed and hope it works or scramble to find some way to
backup before I upgrade just in case the upgrade fails.
Running such an old system as any of the unsupported releases is also
most probably exposing you to security vulnerabilities.
First of all, 8.3 is not an old system. Secondly, you used to be able
to run old systems for a long time after support was dropped without
encountering issues like this. Finally, I'm a port maintainer of a
fair number of ports, so FreeBSD isn't free for me. I put a lot of
time into it.
When such a drastic change is made, it should be well advertised in
advance (think the pkgng announcement you get every time you install a
port) and not implemented in such a disruptive manner. It's clear from
the forum announcement that I linked to that I was not the only one
caught by surprise and that it didn't even work on supported versions
when the change was first implemented.
Sometimes to change things you need to break compatibility, the project
did wait till it was coherent with what was promised before doing this.
What you call the project is made up of people. SOMEONE should be
thinking through the impact on end users and helping to plan such
major transitions in a way that's least disruptive IF you want the
system to remain viable.
Perhaps this is part of the reason adoption of FreeBSD has dropped so
dramatically over the years. I'm retiring in 18 months. When I
leave, the last FreeBSD system goes with me. No one is even
interested in learning it any more. FreeBSD used to rule the web.
Now it's Linux. There's a lesson in there for those that are
listening, but apparently the project is not. Which is sad, because
FreeBSD, IMNSHO, is a very good OS.
There's no need to respond to this. I'm just venting. And clearly my
opinion doesn't matter anyway.
I think your opinion matters.
I agree I would be rudely surprised by such a breakage myself. That said
we need to find a way to desupport things eventually.
Any ideas on what should have been done that can be done in a short
amount of code as possible? Perhaps there's some way to determine
between the old and new makes and just add some kind of target like:
# psuedo make(1) code:
.ifndef THIS_IS_NEW_MAKE
.BEGIN:
echo your system is running an unsupported version of FreeBSD the
last version to support this is r232423
echo please run svn update -r232423 to get a working ports tree as
of that date or upgrade to a more recent
echo freebsd release using freebsd-update [[insert link to
freebsd-update]]
exit 1
.endif
Something like that would have been more than adequate. As I pointed out,
the warning you get about pkgng and the 9/1/2014 deadline is perfect. It's
been there for a couple of months, and it pops up ever time you do a port.
If you miss that and don't convert, you don't have anyone but yourself to
blame.
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There
