Re: Any point to building separate 8.2 and 8.3 packages?
On Fri, Nov 2, 2012 at 1:17 AM, Martin Gignac wrote: > Hi, > > I currently have some 8.2 and 8.3 servers which I cannot upgrade to > 9.0 yet. I am looking at building packages with Poudriere and pkgng > for these 8.2/8.3 servers. > > My question is this: do I need to create separate 8.2 and 8.3 jails on > Poudriere and build discreet packages for each of these minor > releases, or will packages built for a given 8.X release run on any > 8.Y release? In other words, are there any compilation/repackaging > requirements of ports/packages when one upgrades from one minor > version number to the next? > A package built on 8.2 will continue to work on 8.3. The only thing that may not work are ports that require kernel sources to build or install kernel modules. Scot ___ 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: bsd.gcc.mk: USE_FORTRAN.
Hi Ruslan, On Mon, 17 Sep 2012, Ruslan Mahmatkhanov wrote: > is there any possibility to also add something like > USE_FORTRAN_BUILD=[yes|g77|ifort] to make fortran build dependency > only? Many ports will benefit from this - anything, that depend on > math/py-numpy for example. we definitely can look into this. But, how about the run-time dependency? Those ports that you have in mind, don't they have any dependency on one of the GCC run-time libraries? Gerald ___ 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: tk85 Port Maintenance
On 2012-Oct-31, 12:41, Joseph a Nagy Jr wrote:
> On 10/31/12 11:55, Pietro Cerutti wrote:
> > On 2012-Oct-31, 11:28, Joseph a Nagy Jr wrote:
>
> >> New diff[0], undoing some of the earlier changes even though portlint
> >> complains:
> >>
> >> portlint ~/port-maintenance/tk85/
> >> WARN: Makefile: unless this is a master port, COMMENT has to be set by
> >> "=", not by "?=".
> >
> > This *is* a master port, so it's ok to have COMMENT?=
> >
> >> WARN: Makefile: "LIB_DEPENDS" has to appear earlier.
> >
> > This should be fixed as portlint suggests.
> >
> >> WARN: Makefile: no port directory
> >> /usr/ports/lang/tcl${SHORT_TK_VER}-thread found, even though it is
> >> listed in LIB_DEPENDS.
> >
> > I would try and use USE_TCL instead of LIB_DEPENDS here
> >
> >> WARN: Makefile: LIB_DEPENDS don't specify the ABI version number .2 in
> >> Xft.2 unless it is really necessary.
> >
> > This should be fixed as portlint suggests.
> >
> >> 0 fatal errors and 4 warnings found.
> >>
> >> [0]: http://pastebin.com/apf1Y9H0
> >
> > I'll have a look at it on Friday, thanks!
> >
> >
>
> Going ahead to make those changes, old pastebin link is defunct.
>
> New diff with all changes:
> http://pastebin.com/iwhpXfcp
This won't apply, either. Could you provide a diff as dumped by svn diff
in tk85's directory?
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgphqntzhLdqz.pgp
Description: PGP signature
Re: Any point to building separate 8.2 and 8.3 packages?
> A package built on 8.2 will continue to work on 8.3. The only thing > that may not work are ports that require kernel sources to build or > install kernel modules. Thanks for that clarification. I'll have to pay special attention then to ports that do so. -Martin ___ 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"
INDEX build failed for 7.x
INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. make_index: cfv-1.18.3: no entry for /usr/ports/security/py-fchksum Committers on the hook: ak bf crees lwhsu olgeni pawel rm Most recent SVN update was: Updating '.': Udevel/jenkins/distinfo Udevel/jenkins/Makefile Usysutils/webmin/distinfo Usysutils/webmin/Makefile Usysutils/virtualmin/distinfo Usysutils/virtualmin/pkg-plist Usysutils/virtualmin/Makefile Utextproc/py-chardet/pkg-descr Utextproc/py-chardet/Makefile Ugraphics/tesseract/distinfo Dsecurity/py-fchksum Usecurity/Makefile UMOVED Unet-p2p/transmission-gtk2/Makefile Dgames/zephulor/pkg-plist Ugames/zephulor/pkg-descr Agames/zephulor/files Agames/zephulor/files/zephulor.in Ugames/zephulor/Makefile Ugames/qmars/Makefile UU mail/cucipop/Makefile Uemulators/catapult/distinfo Uemulators/catapult/Makefile Updated to revision 306846. ___ 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: INDEX build failed for 7.x
On Fri, Nov 02, 2012 at 12:53:06PM +, Erwin Lansing wrote: > INDEX build failed with errors: > Generating INDEX-7 - please wait.. Done. > make_index: cfv-1.18.3: no entry for /usr/ports/security/py-fchksum > > Committers on the hook: > ak bf crees lwhsu olgeni pawel rm > > Most recent SVN update was: > Updating '.': > Udevel/jenkins/distinfo > Udevel/jenkins/Makefile > Usysutils/webmin/distinfo > Usysutils/webmin/Makefile > Usysutils/virtualmin/distinfo > Usysutils/virtualmin/pkg-plist > Usysutils/virtualmin/Makefile > Utextproc/py-chardet/pkg-descr > Utextproc/py-chardet/Makefile > Ugraphics/tesseract/distinfo > Dsecurity/py-fchksum Sorry, my fault. -- Alex ___ 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: tk85 Port Maintenance
On 11/02/12 06:21, Pietro Cerutti wrote:
> This won't apply, either. Could you provide a diff as dumped by svn diff
> in tk85's directory?
>
from within /usr/ports/x11-toolkits/tk85 on the "original"
root@alex-laptop#> svn diff Makefile
Index: Makefile
===
--- Makefile(revision 306478)
+++ Makefile(working copy)
@@ -12,7 +12,7 @@
PKGNAMESUFFIX?=${THREADS_SUFFIX}
DISTNAME= ${PORTNAME}${PORTVERSION}-src
-MAINTAINER=po...@freebsd.org
+MAINTAINER=jnagyjr1...@gmail.com
COMMENT?= Graphical toolkit for Tcl
LICENSE= BSD
I can't svn diff the new Makefile (with the license and other updates)
--
Yours in Christ,
Joseph A Nagy Jr
"Whoever loves instruction loves knowledge, But he who hates correction
is stupid." -- Proverbs 12:1
Emails are not formal business letters, whatever businesses may want.
Original content CopyFree (F) under the OWL http://owl.apotheon.org
signature.asc
Description: OpenPGP digital signature
Re: Dropping maintainership of science/gramps!
On 1 November 2012 23:27, Da Rock wrote: > On 11/01/12 17:19, Anders Troback wrote: >> >> I do not use FreeBSD any more (I feel in love with >> OpenBSD:-)) so please remove me as maintainer of the science/gramps >> port. >> > I can take it over unless someone else is better suited (and actually uses > the program). How do you go about doing this, though? Exactly as you just did. Done - you are now the maintainer! -- Eitan Adler ___ 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 science/gramps!
On 11/02/12 09:27, Eitan Adler wrote: > On 1 November 2012 23:27, Da Rock > wrote: >> On 11/01/12 17:19, Anders Troback wrote: >>> >>> I do not use FreeBSD any more (I feel in love with >>> OpenBSD:-)) so please remove me as maintainer of the science/gramps >>> port. >>> >> I can take it over unless someone else is better suited (and actually uses >> the program). How do you go about doing this, though? > > Exactly as you just did. Done - you are now the maintainer! > > that all being said, I've pointed out some issues earlier on this list that are worth taking a look at, imo. -- Yours in Christ, Joseph A Nagy Jr "Whoever loves instruction loves knowledge, But he who hates correction is stupid." -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org signature.asc Description: OpenPGP digital signature
INDEX now builds successfully on 7.x
___ 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: poudriere amassing fetch errors
Hi, unfortunately I have the same problem. A lot of fetch and checksum errors. I have set RESOLV_CONF=/etc/resolv.conf in /usr/local/etc/poudriere.conf, resolv.conf is copied to the poudriere jail and manual fetching of the ports is working. On every run of poudriere bulk different ports are failing due to fetch or checksum errors. Sometimes no file is fetched, sometimes a small one and then I get a checksum failure, sometimes the file is about two times bigger and I get a checksum failure, too. Normal make install clean is running fine on that machine. I'm using FreeBSD 9.1-rc2 and poudriere 2.2 (2.1. had the same issue) I have some other problems as well: - poudriere bulk doesn't exit; after building all pkgs it sleeps forever - I have two errors several times, but I don't know to which ports they belong: perl: not found "Makefile", line 86: warning: "/bin/sh -c 'case `perl --version` in *freebsd-thread*) echo yes ;; esac'" returned non-zero status and /usr/local/bin/apr-1-config: not found "Makefile.common", line 115: warning: "/usr/local/bin/apr-1-config --includedir" returned non-zero status Could anybody help me? Thanks Wolfgang Am Samstag, 20. Oktober 2012, 16:14:28 schrieb Christopher J. Ruwe: > On Fri, 19 Oct 2012 22:29:51 +0200 > Patrick Lamaiziere wrote: > > > Le Sun, 14 Oct 2012 03:57:20 +0200, > > "Christopher J. Ruwe" a écrit : > > > > Hello, > > > > > for some time I have noticed that poudriere bulk build amass fetch > > > errors, i.e., the corresponding distfile(s) cannot be fetched by the > > > build jail and I have to fetch these manually. > > > > > > Does anybody know a fix to this unnerving condition? > > > > I don't see this problem. > > > > Missing resolv.conf ? > > /usr/local/etc/poudriere.conf > > # By default the jails have no /etc/resolv.conf, you will need to set > > # REVOLV_CONF to a file on your hosts system that will be copied has > > # /etc/resolv.conf for the jail, except if you don't need it (using an > > http # proxy for example) > > RESOLV_CONF=/etc/resolv.conf > > > > > My apolgies for that absolutly crappy discription of the error I was > witnessing. Upon reading my post anew, I just do not know what hit me > posting that. > > Anyways, I did not have a /etc/resolv.conf entry in my poudriere.conf, > as it has been working for some time without. The error was rather > byzanthine ... sometimes, the sources were fetched correctly, sometimes > not. Regrettably, I do not have any fetch error messages around any > more, so I cannot supply the information I should have included in my > first post. > > Anyways, setting the entry in poudriere.conf seems to have solved the > issue. Interesting how any fetching could have occured without ... > > Thanks and cheers, > ___ 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 you maintain which are out of date
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 +-+ astro/py-astLib | 0.6.1 | 0.17.1 +-+ astro/viking| 1.3.1 | 1.3.2.1 +-+ audio/calf | 0.0.18.6| 0.0.19 +-+ audio/hexter| 0.6.2 | 1.0.0 +-+ audio/icecast | 1.3.12 | 2.3.3 +-+ audio/libmtp| 1.1.4 | 1.1.5 +-+ audio/pd| 0.43-3 | 0.43-4 +-+ audio/py-xmms | 2.02| 2.07 +-+ audio/qsynth| 0.3.4 | 0.3.6 +-+ audio/rio500| 0.7 | 0.8.1 +-+ audio/soundtouch| 1.6.0 | 1.7.0 +-+ audio/spiralsynth | 0.1.7 | 2.0.0 +-+ audio/spiralsynthmodular| 0.2.2a | 0.2.2 +-+ audio/timidity++| 2.13.2 | 2.14.0 +-+ audio/timidity++-emacs | 2.13.2 | 2.14.0 +-+ audio/timidity++-gtk| 2.13.2 | 2.14.0 +-+ audio/timidity++-motif | 2.13.2 | 2.14.0 +-+ audio/timidity++-slang | 2.13.2 | 2.14.0 +-+ audio/timidity++-tcltk | 2.13.2 | 2.14.0 +-+ audio/timidity++-xaw| 2.13.2 | 2.14.0 +-+ audio/timidity++-xskin | 2.13.2 | 2.14.0 +-+ benchmarks/postmark | 1.51| 1.53 +-+ biology/avida | 2.12.3 | 2.12.4 +-+ biology/blat| 34 | 35 +-+ biology/molden | 4.6 | 5.0.2 +-+ biology/rasmol | 2.7.2.1.1 | 2.7.5.2 +-+ biology/tinker | 5.1.09 | 6.1.01 +-+ cad/electric-ng | 8.11| 9.03 +-+ cad/
SalesSBR chinachem shared photos with you
Hello Sir/Mam: Happy to contact you ! We would like to introudce our company.Our company is a large scale pertrochemical enterprise with synthetic rubber as the main product. We could supply SBR 1502 and 1712. It is manufactured by SINOPEC YANGZI. The following is the SBR quotation : * SBR 1502: USD 2500.00/TON FOB China port SBR 1712: USD 2350.00/TON FOB China port * packing : 35kg ppbag * quantity: 21ton/20'container * price validity: within 3 days . * payment terms : TT in advance or LC at sight . * delivery time: within 20 days . Any other question, contact me freely ! best wishes Adelle Liang sales manage rXuzhou Yizhengyuan Chemical Technology Co., Ltd email:chem...@163.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: bsd.gcc.mk: USE_FORTRAN.
Hi! Gerald Pfeifer wrote on 02.11.2012 13:26: Hi Ruslan, On Mon, 17 Sep 2012, Ruslan Mahmatkhanov wrote: is there any possibility to also add something like USE_FORTRAN_BUILD=[yes|g77|ifort] to make fortran build dependency only? Many ports will benefit from this - anything, that depend on math/py-numpy for example. we definitely can look into this. But, how about the run-time dependency? Those ports that you have in mind, don't they have any dependency on one of the GCC run-time libraries? Gerald Hmm, you are right... I just deinstalled gcc-4.6.3 and got this when calling py-numpy: ImportError: Shared object "libgfortran.so.3" not found, required by "lapack_lite.so". I think that numpy will run fine w/o gcc, it's a C python extension in first place. Maybe that math/lapack dependency may be turned into an option. PS. And py-game failed to load too because it imports py-numpy. Chromium too. But deluge is runs fine w/o gcc, while I can't see where it grap this dependency... The same with chromium - it working Anyway, I think this will be a useful feature, so it worth to implement. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: bsd.gcc.mk: USE_FORTRAN.
Ruslan Mahmatkhanov wrote on 02.11.2012 23:18: Hi! Gerald Pfeifer wrote on 02.11.2012 13:26: Hi Ruslan, On Mon, 17 Sep 2012, Ruslan Mahmatkhanov wrote: is there any possibility to also add something like USE_FORTRAN_BUILD=[yes|g77|ifort] to make fortran build dependency only? Many ports will benefit from this - anything, that depend on math/py-numpy for example. we definitely can look into this. But, how about the run-time dependency? Those ports that you have in mind, don't they have any dependency on one of the GCC run-time libraries? Gerald Hmm, you are right... I just deinstalled gcc-4.6.3 and got this when calling py-numpy: ImportError: Shared object "libgfortran.so.3" not found, required by "lapack_lite.so". I think that numpy will run fine w/o gcc, it's a C python extension in first place. Maybe that math/lapack dependency may be turned into an option. PS. And py-game failed to load too because it imports py-numpy. Chromium too. But deluge is runs fine w/o gcc, while I can't see where it grap this dependency... The same with chromium - it working Need some sleep. Please read the paragraph above as: """ PS. And py-game failed to load too because it imports py-numpy. Chromium failing to start too. But deluge runs fine w/o gcc, while I can't see where it grabbed this dependency... """ Anyway, I think this will be a useful feature, so it worth to implement. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: [HEADSUP] current switched by default to pkgng
Hello, Baptiste. You wrote 10 октября 2012 г., 17:44:21: BD> Make sure to read UPDATING (from ports) to correctly migrate your system or find BD> instruction to make your system still running with legacy pkg_install tools. Did somebody update nanobsd scripts? ;-) -- // Black Lion AKA Lev Serebryakov ___ 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: poudriere amassing fetch errors
On 11/2/2012 11:52 AM, Wolfgang Riegler wrote: > Hi, > > unfortunately I have the same problem. A lot of fetch and checksum errors. I > have set RESOLV_CONF=/etc/resolv.conf in /usr/local/etc/poudriere.conf, > resolv.conf is copied to the poudriere jail and manual fetching of the ports > is working. > On every run of poudriere bulk different ports are failing due to fetch or > checksum errors. Sometimes no file is fetched, sometimes a small one and then > I get a checksum failure, sometimes the file is about two times bigger and I > get a checksum failure, too. > This doesn't sound like a poudriere-specific issue. There may be a general fetching issue with bsd.port.mk, that I plan to investigate further. > Normal make install clean is running fine on that machine. > > I'm using FreeBSD 9.1-rc2 and poudriere 2.2 (2.1. had the same issue) > > > I have some other problems as well: > - poudriere bulk doesn't exit; after building all pkgs it sleeps forever This issue should be fixed in poudriere-devel. > - I have two errors several times, but I don't know to which ports they > belong: > perl: not found > "Makefile", line 86: warning: "/bin/sh -c 'case `perl --version` in > *freebsd-thread*) echo yes ;; esac'" returned non-zero status > and > /usr/local/bin/apr-1-config: not found > "Makefile.common", line 115: warning: "/usr/local/bin/apr-1-config > --includedir" returned non-zero status > The first I'm not sure about. The 2nd are apache ports incorrectly depending on apr to be installed, which does not work in a fresh jail. If you run ports-mgmt/poudriere-devel bulk with -J1 you should see which port is causing these issues, so they can be reported to the maintainers. The specific problem as that the ports do not build properly within clean jails. > > Could anybody help me? > > Thanks > > Wolfgang > Bryan ___ 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: [HEADSUP] current switched by default to pkgng
Hello, Lev. You wrote 2 ноября 2012 г., 23:24:28: BD>> Make sure to read UPDATING (from ports) to correctly migrate your system or find BD>> instruction to make your system still running with legacy pkg_install tools. LS> Did somebody update nanobsd scripts? ;-) Simple replacing "pkg_add" with "pkg add" doesn't work ;-) -- // Black Lion AKA Lev Serebryakov ___ 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: [HEADSUP] current switched by default to pkgng
On Sat, Nov 03, 2012 at 12:41:31AM +0400, Lev Serebryakov wrote: > Hello, Lev. > You wrote 2 ноября 2012 г., 23:24:28: > > BD>> Make sure to read UPDATING (from ports) to correctly migrate your system > or find > BD>> instruction to make your system still running with legacy pkg_install > tools. > LS> Did somebody update nanobsd scripts? ;-) > Simple replacing "pkg_add" with "pkg add" doesn't work ;-) > I know some people have some patches for nanobsd that should work with pkgng, but I don't know much about it. regards, Bapt pgpwaRqFMWr1n.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Sat, Nov 03, 2012 at 12:41:31AM +0400, Lev Serebryakov wrote: > Hello, Lev. > You wrote 2 ноября 2012 г., 23:24:28: > > BD>> Make sure to read UPDATING (from ports) to correctly migrate your system > or find > BD>> instruction to make your system still running with legacy pkg_install > tools. > LS> Did somebody update nanobsd scripts? ;-) > Simple replacing "pkg_add" with "pkg add" doesn't work ;-) > > -- > // Black Lion AKA Lev Serebryakov > > ___ > freebsd-curr...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" The BSDmc project (http://code.google.com/p/bsdmc/) uses nanobsd and pkgng, have a look in particular at the following diff: http://code.google.com/p/bsdmc/source/detail?r=75 Maybe you can find something helpful for you in there :) regards, Bapt pgpU82W9MAEWP.pgp Description: PGP signature
Re: Poudriere not registering OPTIONS changes?
On Nov 2, 2012, at 1:10 AM, Martin Gignac wrote: > Hi, > > I've recently discovered Poudriere and have begun using it to build my > own local pkgng PACKAGESITE for my FreeBSD 8 and 9 servers. > > Based on information I read on the web I was under the impression that > whenever a new bulk build was launched, Poudriere would notice any > port with changed OPTIONS and rebuild these ports, even if the ports' > version number hadn't changed. > > After building my local port list for the first time I realized that I > needed a Samba34 package with ADS support enabled (it is off by > default) so I decided to try the OPTIONS change feature; I used > Poudriere's 'options' command and modified the OPTIONS for the samba34 > port. I then issued a bulk build command; however, even though > Poudriere reported "Mounting /var/db/ports from: > /usr/local/etc/poudriere.d/options" it did not make any comment about > changed options and ended shortly thereafter with no new packages > built. > > I then tried using the 'options' command by specifying a jail and > re-issued a bulk build, but got the same result. > > Have I misunderstood how OPTIONS changes are tracked? Did I make a > mistake or omit a crucial step in order to have the OPTIONS changes > recognized? This all sounds correct. Make sure you have this in your /usr/local/etc/poudriere.conf: CHECK_CHANGED_OPTIONS=yes or CHECK_CHANGED_OPTIONS=verbose Using verbose instead of yes will display the differences in OPTIONS that it detects. > > Thank you, > -Martin > > System: Poudriere 2.2 on FreeBSD 9.0 Bryan ___ 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"
Where is best place to log pkg bugs?
The mailing lists don't seem to be a good place to send bugs and get attention, and I've found a few that I want to report and have in a bug system somewhere. Should I use gnats? 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"
Re: Where is best place to log pkg bugs?
On 2 November 2012 21:53, Adam McDougall wrote: > The mailing lists don't seem to be a good place to send bugs > and get attention, and I've found a few that I want to report > and have in a bug system somewhere. > Should I use gnats? yes please. Log then as "bin" category for now (we really should have a separate category). -- Eitan Adler ___ 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: Where is best place to log pkg bugs?
On 11/2/2012 9:56 PM, Eitan Adler wrote: On 2 November 2012 21:53, Adam McDougall wrote: The mailing lists don't seem to be a good place to send bugs and get attention, and I've found a few that I want to report and have in a bug system somewhere. Should I use gnats? yes please. Log then as "bin" category for now (we really should have a separate category). Thanks. I filed 3 plus one for poudriere at http://fossil.etoilebsd.net/poudriere/tktview/9636c6f78a14dff32a6553b9a58a8912a1b13843 ___ 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: Where is best place to log pkg bugs?
On 11/2/2012 9:39 PM, Adam McDougall wrote: > On 11/2/2012 9:56 PM, Eitan Adler wrote: >> On 2 November 2012 21:53, Adam McDougall wrote: >>> The mailing lists don't seem to be a good place to send bugs >>> and get attention, and I've found a few that I want to report >>> and have in a bug system somewhere. >>> Should I use gnats? >> yes please. Log then as "bin" category for now (we really should have >> a separate category). >> >> >> >> > Thanks. I filed 3 plus one for poudriere at > http://fossil.etoilebsd.net/poudriere/tktview/9636c6f78a14dff32a6553b9a58a8912a1b13843 > IMHO these should be ports PR for ports-mgmt/pkg, not bin/pkg, since it's a ports project. Bryan ___ 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: Where is best place to log pkg bugs?
On 2 November 2012 23:55, Bryan Drewery wrote: > On 11/2/2012 9:39 PM, Adam McDougall wrote: >> On 11/2/2012 9:56 PM, Eitan Adler wrote: >>> On 2 November 2012 21:53, Adam McDougall wrote: The mailing lists don't seem to be a good place to send bugs and get attention, and I've found a few that I want to report and have in a bug system somewhere. Should I use gnats? >>> yes please. Log then as "bin" category for now (we really should have >>> a separate category). >>> >>> >>> >>> >> Thanks. I filed 3 plus one for poudriere at >> http://fossil.etoilebsd.net/poudriere/tktview/9636c6f78a14dff32a6553b9a58a8912a1b13843 >> > > IMHO these should be ports PR for ports-mgmt/pkg, not bin/pkg, since > it's a ports project. good call; I was thinking 'ports' wasn't a good option because it was source related, but I forgot we had a port for it. :-\ Blame me replying when I am half asleep. I'll fix the ones already submitted. -- Eitan Adler ___ 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"
