Skip site navigation (1)Skip section navigation (2)


2017/freebsd-ports/20170702.freebsd-ports

Messages: 108, old messages first
Last update: Mon Feb 13 14:22:30 2023

home | archive sorted by: subject | author | date | reverse date
  1. Jun 25 Mark Millard               lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gc
  2. Jun 25 Ben Woods                  pkg(8) fails to upgrade to different branches of software
  3. Jun 25 Thomas Mueller             Re: [RFC] Why FreeBSD ports should have branches by OS version
  4. Jun 25 Michelle Sullivan          Re: [RFC] Why FreeBSD ports should have branches by OS version
  5. Jun 25 Kurt Jaeger                Re: clamav-unofficial-sigs
  6. Jun 25 portscout@FreeBSD.org      FreeBSD ports you maintain which are out of date
  7. Jun 25 Carmel NY                  Re: clamav-unofficial-sigs
  8. Jun 25 Carmel NY                  "clamav-unofficial-sigs" error message
  9. Jun 25 =?utf-8?Q?Martin_Waschb=C3 Re: "clamav-unofficial-sigs" error message
 10. Jun 25 Matthias Fechner           Which license should be used for as-id
 11. Jun 25 Grzegorz Junka             Re: [RFC] Why FreeBSD ports should have branches by OS version
 12. Jun 25 Carmel NY                  Re: "clamav-unofficial-sigs" error message
 13. Jun 25 Richard Gallamore          USE_GCC usage
 14. Jun 25 Peter Jeremy               Re: security/libressl not API-compatible with OpenSSL, breaks www/apache24
 15. Jun 25 Dave Hayes                 Re: [RFC] Why FreeBSD ports should have branches by OS version
 16. Jun 26 Jov                        Re: USE_GCC usage
 17. Jun 26 Guido Falsi                Re: [RFC] Why FreeBSD ports should have branches by OS version
 18. Jun 26 Guido Falsi                Re: [RFC] Why FreeBSD ports should have branches by OS version
 19. Jun 26 Kurt Jaeger                Re: [RFC] Why FreeBSD ports should have branches by OS version
 20. Jun 26 Franco Fichtner            Re: [RFC] Why FreeBSD ports should have branches by OS version


21. Jun 26 Marko Njezic Re: "clamav-unofficial-sigs" error message 22. Jun 26 portscout@FreeBSD.org FreeBSD ports you maintain which are out of date 23. Jun 26 Torsten Zuehlsdorff Re: [RFC] Why FreeBSD ports should have branches by OS version 24. Jun 26 Carmel NY Re: "clamav-unofficial-sigs" error message 25. Jun 26 Marko Njezic Re: "clamav-unofficial-sigs" error message 26. Jun 26 Miroslav Lachman Re: sysutils/tmux - strange behaviour with new version 2.4 / 2.5 27. Jun 26 Patrick Powell Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lan 28. Jun 26 Mathieu Arnold Re: USE_GCC usage 29. Jun 26 Andre Goree Re: NEW APR/APR-Utils 30. Jun 26 Mark Millard Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lan 31. Jun 26 Grzegorz Junka Re: [RFC] Why FreeBSD ports should have branches by OS version 32. Jun 26 Dave Hayes Re: [RFC] Why FreeBSD ports should have branches by OS version 33. Jun 26 =?utf-8?Q?Martin_Waschb=C3 PRs in need of some TLC 34. Jun 26 Dave Cottlehuber Re: perl problem 35. Jun 26 Greg 'groggy' Lehey Re: PRs in need of some TLC 36. Jun 26 Kurt Jaeger Re: PRs in need of some TLC 37. Jun 27 Technical Support E-mail account blacklisted 38. Jun 27 Thomas Mueller Re: [RFC] Why FreeBSD ports should have branches by OS version 39. Jun 27 =?utf-8?Q?Martin_Waschb=C3 Re: PRs in need of some TLC 40. Jun 27 =?utf-8?Q?Martin_Waschb=C3 Re: PRs in need of some TLC
41. Jun 27 Julian H. Stacey Re: [RFC] Why FreeBSD ports should have branches by OS version 42. Jun 27 portscout@FreeBSD.org FreeBSD ports you maintain which are out of date 43. Jun 27 Kurt Jaeger Re: PRs in need of some TLC 44. Jun 27 <scratch65535@att.net> Re: [RFC] Why FreeBSD ports should have branches by OS version 45. Jun 27 Aryeh Friedman best way to handle GCC version detection 46. Jun 27 Dimitry Andric Re: best way to handle GCC version detection 47. Jun 27 Matthias Fechner Should a package restart on upgrade itself 48. Jun 27 Franco Fichtner Re: Should a package restart on upgrade itself 49. Jun 27 Baptiste Daroussin Re: Should a package restart on upgrade itself 50. Jun 27 Vlad K. Re: Should a package restart on upgrade itself 51. Jun 27 David Wolfskill Re: Should a package restart on upgrade itself 52. Jun 27 Miroslav Lachman Re: Should a package restart on upgrade itself 53. Jun 27 Mark Linimon Re: [RFC] Why FreeBSD ports should have branches by OS version 54. Jun 27 Mark Linimon Re: [RFC] Why FreeBSD ports should have branches by OS version 55. Jun 27 Matthias Fechner Re: Should a package restart on upgrade itself 56. Jun 27 Vlad K. Re: Should a package restart on upgrade itself 57. Jun 27 Miroslav Lachman Re: Should a package restart on upgrade itself 58. Jun 27 Michael Gmelin Re: Should a package restart on upgrade itself 59. Jun 27 Miroslav Lachman Re: Should a package restart on upgrade itself 60. Jun 27 Vlad K. Re: Should a package restart on upgrade itself
61. Jun 27 <scratch65535@att.net> Re: [RFC] Why FreeBSD ports should have branches by OS version 62. Jun 27 Thomas Mueller Re: [RFC] Why FreeBSD ports should have branches by OS version 63. Jun 27 Mark Linimon Re: [RFC] Why FreeBSD ports should have branches by OS version 64. Jun 27 Mark Linimon Re: [RFC] Why FreeBSD ports should have branches by OS version 65. Jun 27 Grzegorz Junka Re: [RFC] Why FreeBSD ports should have branches by OS version 66. Jun 28 Thomas Mueller Re: [RFC] Why FreeBSD ports should have branches by OS version 67. Jun 28 Torsten Zuehlsdorff Re: Should a package restart on upgrade itself 68. Jun 28 Guido Falsi Re: Should a package restart on upgrade itself 69. Jun 28 Torsten Zuehlsdorff Re: [RFC] Why FreeBSD ports should have branches by OS version 70. Jun 28 Torsten Zuehlsdorff Re: [RFC] Why FreeBSD ports should have branches by OS version 71. Jun 28 Gerald Pfeifer Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lan 72. Jun 28 Andy Farkas 'pkg version' strangeness - No valid entries found 73. Jun 28 portscout@FreeBSD.org FreeBSD ports you maintain which are out of date 74. Jun 28 Adam Weinberger Re: 'pkg version' strangeness - No valid entries found 75. Jun 28 David Wolfskill math/R: Build failure after PORTREVISION for shlib change 76. Jun 28 <scratch65535@att.net> Re: [RFC] Why FreeBSD ports should have branches by OS version 77. Jun 28 Andy Farkas Re: 'pkg version' strangeness - No valid entries found 78. Jun 28 Mark Millard Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lan 79. Jun 28 Matthias Fechner Re: Should a package restart on upgrade itself 80. Jun 28 David Wolfskill Re: math/R: Build failure after PORTREVISION for shlib change
81. Jun 28 Dirk Meyer Re: [RFC] Why FreeBSD ports should have branches by OS version 82. Jun 28 Joseph Mingrone Re: math/R: Build failure after PORTREVISION for shlib change 83. Jun 28 Helen Koike review of google-compute-engine: better quality of the GCE image 84. Jun 29 Mark Millard /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling err 85. Jun 29 Mark Millard Re: /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling 86. Jun 29 Yuri What to do when the port fails in poudriere with "Too many open files" ? 87. Jun 29 Emmanuel Vadot Re: /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling 88. Jun 29 Matt Smith Re: What to do when the port fails in poudriere with "Too many open files" ? 89. Jun 29 Gerald Pfeifer Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lan 90. Jun 29 portscout@FreeBSD.org FreeBSD ports you maintain which are out of date 91. Jun 29 Mark Millard Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lan 92. Jun 29 Joseph Mingrone Re: math/R: Build failure after PORTREVISION for shlib change 93. Jun 29 David Wolfskill Re: math/R: Build failure after PORTREVISION for shlib change 94. Jun 29 Susan Mullins Re: New Healthcare Industry Email List 2017 95. Jun 30 Gerald Pfeifer Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lan 96. Jun 30 Jov PostgreSQL related NEW PORTS need committers 97. Jun 30 Torsten Zuehlsdorff Re: PostgreSQL related NEW PORTS need committers 98. Jun 30 Jov Re: PostgreSQL related NEW PORTS need committers 99. Jun 30 Jos Chrispijn Vulnerability 100. Jun 30 Adam Weinberger Re: Vulnerability
101. Jun 30 Carlos Jacobo Puga Medina Re: Vulnerability 102. Jul 1 Jos Chrispijn Re: Vulnerability 103. Jul 1 Jos Chrispijn Re: Vulnerability 104. Jul 1 portscout@FreeBSD.org FreeBSD ports you maintain which are out of date 105. Jul 1 David Wolfskill Re: math/R: Build failure after PORTREVISION for shlib change 106. Jul 1 =?UTF-8?Q?Ren=c3=a9_Ladan? New 2017Q3 branch 107. Jul 1 Larry Rosenman Re: New 2017Q3 branch 108. Jul 1 Adam Weinberger Re: New 2017Q3 branch


home | archive sorted by: subject | author | date | reverse date