Date: Sun, 30 Sep 2012 11:31:14 -0500 From: Boniek <desshi66@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: freebsd-ports Digest, Vol 488, Issue 9 Message-ID: <CANS5nXoZ0oCJNtSKQ96%2BeTH4Hrq37PRY2cjmZkY8px1jSpOnuA@mail.gmail.com> In-Reply-To: <20120930120040.E125110656B9@hub.freebsd.org> References: <20120930120040.E125110656B9@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
GIMP 2.8 is new version for installer with gratulation that is very easy , first deinstall png 1.4.x dependecy of graphic,kde,firefox,etc.. and muches modules.. next install GIMP 2.8 more png-1.5 and then finish .011001100110. 2012/9/30 <freebsd-ports-request@freebsd.org> > Send freebsd-ports mailing list submissions to > freebsd-ports@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > or, via email, send a message with subject or body 'help' to > freebsd-ports-request@freebsd.org > > You can reach the person managing the list at > freebsd-ports-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-ports digest..." > > > Today's Topics: > > 1. huge distfiles policy (????? ?????????) > 2. graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? (O. Hartmann) > 3. Re: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? > (Heino Tiedemann) > 4. Re: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? > (Ruslan Mahmatkhanov) > 5. Re: huge distfiles policy (Eitan Adler) > 6. Re: Wanted ports razor-qt (Cpet Services) > 7. Re: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? (O. Hartmann) > 8. Re: Question about postgresql 9 and pg_upgrade (Axel Rau) > 9. Re: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? > (Heino Tiedemann) > 10. Re: huge distfiles policy (Chris Rees) > 11. Re: Question about postgresql 9 and pg_upgrade (Palle Girgensohn) > 12. Re: huge distfiles policy (Kevin Oberman) > 13. Re: huge distfiles policy (Baptiste Daroussin) > 14. Re: CFT: x11/nvidia-driver major update to 304.xx series > (Lawrence K. Chen, P.Eng.) > 15. Problems submitting patch containing UTF-8 characters > (Michael Gmelin) > 16. Installing non-ports software into /usr/local (Jamie Paul Griffin) > 17. Re: Installing non-ports software into /usr/local (Chris Rees) > 18. Re: CFT: x11/nvidia-driver major update to 304.xx series (Jerry) > 19. Re: huge distfiles policy (Jerry) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 29 Sep 2012 17:22:36 +0400 > From: ????? ????????? <bsam@passap.ru> > Subject: huge distfiles policy > To: Ports FreeBSD <freebsd-ports@freebsd.org> > Message-ID: <5066F61C.5050704@passap.ru> > Content-Type: text/plain; charset=3DUTF-8; format=3Dflowed > > Hi All, > > I'm about to commit print/texlive ports (PR/171571). One of it's ports > (print/texlive-texmf) has size approx. 1.4 Gb. > > What is the current policy upon huge ports? Should I restrict someting > to not build at, say, pointyhat? Something else? > > Thanks! > -- > WBR, Boris Samorodov (bsam) > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > > > ------------------------------ > > Message: 2 > Date: Sat, 29 Sep 2012 16:44:24 +0200 > From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> > Subject: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? > To: Ports FreeBSD <freebsd-ports@freebsd.org> > Message-ID: <50670948.9040401@zedat.fu-berlin.de> > Content-Type: text/plain; charset=3D"iso-8859-15" > > I'm wondering why FreeBSD ports takes so long to update quite oldish > gimp-2.6 to gimp-2.8. Does anyone know what the stoppers are and where > solutions needed? > > Some of the prerequisites for GIMP 2.8 are compiling well (as isolated > packages, not in combination with gimp 2.8), like graphics/gegel (0.2.0) > or x11/bab; 0.1.10 (port has still 0.1.6). > > Oliver > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 488 bytes > Desc: OpenPGP digital signature > Url : > http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20120929/bf4= e7a54/signature-0001.pgp > > ------------------------------ > > Message: 3 > Date: Sat, 29 Sep 2012 17:20:59 +0200 > From: Heino Tiedemann <rotkaps_spam_trap@gmx.de> > Subject: Re: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? > To: freebsd-ports@freebsd.org > Message-ID: <r7gjj9-mc5.ln1@news.hansenet.de> > Content-Type: text/plain > > "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote: > > > I'm wondering why FreeBSD ports takes so long to update quite oldish > > gimp-2.6 to gimp-2.8. Does anyone know what the stoppers are and where > > solutions needed? > > Mee too. gimp 2.8 is from march(!) 2012 - now it is olmost october und > nothing happened.. > > This - and sometime the old graphics/rawtherapee port - makes FreeBSD > a litle unusable for foto-editing > > > Heino > > > > ------------------------------ > > Message: 4 > Date: Sat, 29 Sep 2012 20:11:55 +0400 > From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> > Subject: Re: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? > To: rotkap@gmx.de > Cc: "O. Hartmann" <ohartman@zedat.fu-berlin.de>, > freebsd-ports@freebsd.org > Message-ID: <50671DCB.8050200@yandex.ru> > Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed > > Hi! > > Heino Tiedemann wrote on 29.09.2012 19:20: > > "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote: > > > >> I'm wondering why FreeBSD ports takes so long to update quite oldish > >> gimp-2.6 to gimp-2.8. Does anyone know what the stoppers are and where > >> solutions needed? > > > > Mee too. gimp 2.8 is from march(!) 2012 - now it is olmost october und > > nothing happened.. > > > > This - and sometime the old graphics/rawtherapee port - makes FreeBSD > > a litle unusable for foto-editing > > > > > > Heino > > As far I know, the gimp and gnome update will not be done until FreeBSD > 9.1 will be released (a couple of weeks at minimum). But in a mean time > you can update the required ports manually, using this archive: > > http://people.freebsd.org/~rm/gimp.tgz > > Note: please do not just copy them over the current ports, because there > is some patches, that should be removed first to make things working! > > And. What is wrong with rawtherapee? It's on it's latest version as far > I understand. > > -- > Regards, > Ruslan > > Tinderboxing kills... the drives. > > > ------------------------------ > > Message: 5 > Date: Sat, 29 Sep 2012 12:46:41 -0400 > From: Eitan Adler <lists@eitanadler.com> > Subject: Re: huge distfiles policy > To: ????? ????????? <bsam@passap.ru> > Cc: Ports FreeBSD <freebsd-ports@freebsd.org> > Message-ID: > <CAF6rxg=3D_ > j6Tw51musYVknB3fUH6b5hr27iHXWJz-UzKsVrHTBA@mail.gmail.com> > Content-Type: text/plain; charset=3DUTF-8 > > On 29 September 2012 09:22, =D0=91=D0=BE=D1=80=D0=B8=D1=81 =D0=A1=D0=B0= =D0=BC=D0=BE=D1=80=D0=BE=D0=B4=D0=BE=D0=B2 <bsam@passap.ru> wrote: > > Hi All, > > > > I'm about to commit print/texlive ports (PR/171571). One of it's ports > > (print/texlive-texmf) has size approx. 1.4 Gb. > > > > What is the current policy upon huge ports? Should I restrict someting > > to not build at, say, pointyhat? Something else? > > I believe others have set MANUAL_PACKAGE_BUILD=3D huge though I'm not > certain if this is because the distfile is large, or the final package > is large (although in this case both are true) > > -- > Eitan Adler > > > ------------------------------ > > Message: 6 > Date: Sat, 29 Sep 2012 11:47:21 -0500 > From: Cpet Services <cpetservice@gmail.com> > Subject: Re: Wanted ports razor-qt > To: Pawel Pekala <pawel@freebsd.org> > Cc: freebsd-ports@freebsd.org > Message-ID: > <CA+hK6Zk30OMd_BeL+SwLa5X214v=3D > gD4gSOHRALQK14oQpULvqQ@mail.gmail.com> > Content-Type: text/plain; charset=3DUTF-8 > > Ok, thank you for the heads up. > > On Fri, Sep 28, 2012 at 10:46 AM, Pawel Pekala <pawel@freebsd.org> wrote: > > > Dnia 2012-09-27, o godz. 01:47:23 > > Cpet Services <cpetservice@gmail.com> napisa=C5=82(a): > > > > >Anyone working on this, thinking of working on this or has plans to > > >work on this? > > > > I started work on it, but I'm getting razor-desktop segfaults on > > startup, maybe someone else will have better luck fixing this. > > Here's my efforts so far: > > > > http://people.freebsd.org/~pawel/razorqt-20120928.shar > > > > -- > > pozdrawiam / with regards > > Pawe=C5=82 P=C4=99kala > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org= " > > > > > > -- > -------------------------------------------------------- > Chris Petrik > FreeBSD Contributor > Reincarnated > cpet on irc > > > ------------------------------ > > Message: 7 > Date: Sat, 29 Sep 2012 18:53:57 +0200 > From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> > Subject: Re: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? > To: Ruslan Mahmatkhanov <cvs-src@yandex.ru> > Cc: freebsd-ports@freebsd.org > Message-ID: <506727A5.5060608@zedat.fu-berlin.de> > Content-Type: text/plain; charset=3D"iso-8859-1" > > Am 09/29/12 18:11, schrieb Ruslan Mahmatkhanov: > > Hi! > > > > Heino Tiedemann wrote on 29.09.2012 19:20: > >> "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote: > >> > >>> I'm wondering why FreeBSD ports takes so long to update quite oldish > >>> gimp-2.6 to gimp-2.8. Does anyone know what the stoppers are and wher= e > >>> solutions needed? > >> > >> Mee too. gimp 2.8 is from march(!) 2012 - now it is olmost october und > >> nothing happened.. > >> > >> This - and sometime the old graphics/rawtherapee port - makes FreeBSD > >> a litle unusable for foto-editing > >> > >> > >> Heino > > > > As far I know, the gimp and gnome update will not be done until FreeBSD > > 9.1 will be released (a couple of weeks at minimum). But in a mean time > > you can update the required ports manually, using this archive: > > > > http://people.freebsd.org/~rm/gimp.tgz > > > > Note: please do not just copy them over the current ports, because ther= e > > is some patches, that should be removed first to make things working! > > > > And. What is wrong with rawtherapee? It's on it's latest version as far > > I understand. > > > > > Thank you very much. > > As I saw at www.gimp.org, there are several ports which need updates. > > Thanks for the link and patches. > > Regards, > Oliver > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 488 bytes > Desc: OpenPGP digital signature > Url : > http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20120929/daf= f2053/signature-0001.pgp > > ------------------------------ > > Message: 8 > Date: Sat, 29 Sep 2012 19:43:07 +0200 > From: Axel Rau <Axel.Rau@chaos1.de> > Subject: Re: Question about postgresql 9 and pg_upgrade > To: Palle Girgensohn <girgen@FreeBSD.org> > Cc: freebsd-ports@freebsd.org, Alexander Pyhalov <alp@rsu.ru>, Chris > Rees <utisoft@gmail.com>, pgsql@FreeBSD.org > Message-ID: <49D19A07-C83D-4966-B8DE-03D09CA42401@chaos1.de> > Content-Type: text/plain; charset=3Dutf-8 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Am 29.09.2012 um 12:34 schrieb Palle Girgensohn: > > > You should be able to install into a chrooted/jailed environment as per > > > > 1. install new version to a chroot/jail > > > > 2. stop postgres > > > > 3. use pgupgrade and use chrooted installation as the new binary > > installation > > > > 4. upgrade the "real" postgresql to the new major version > > > > 5. start postgres > > > > This is a bit of a hassle with the chroot stuff, but it should work in > > theory. > > > > Or perhaps you could just take a package of the new postgresql version > > and untar is somewhere. For pg_upgrade, all you need is both binaries > > available at the same time on you hard disk. You could build the packag= e > > somewhere else. > > > > Sadly though, the wet dream if installing different versions side by > > side has the draw back that it hard to come up with a scheme that won't > > require current setups to migrate at upgrade, as Chris points out. > > > > As my server itself runs in a jail, this won't work, I think. > > Axel > - --- > PGP-Key:29E99DD6 =E2=98=80 +49 151 2300 9283 =E2=98=80 computing @ chao= s claudius > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.19 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iQEcBAEBAgAGBQJQZzMyAAoJEMFz9+6bacTRM+oH/19S/o6TGvgkjcEp+aQn+AKb > XvPqIiG8T05Lyb7o50dCp178VTgy4Iz/RqehhDNNy3No5Eb6u0ADXELIJ5f4yDbQ > 2/PuFQw3mkD3GzeajF2KsgvdV3fVpu4qP3U0XnXaCjTVauuwIHwOq4/6eowclRtH > 2gw+6Y+0yivOmAqm8yESdhVe0+aM87+YzH8ySDXJZavGBl7pu2MPvGJSDvf6QvRB > LLnnknsmypHXlEQ9Q4RGRwCwKfZIkN/E5L3NsA1yRGZUChTtZFy44yo+JuIWK2Is > lX5JudQjHrrpkPVr9EuiFONa4z4KMW6LWsSm/hjnViuzcWYEi8PZt78B6uEAJMk=3D > =3Dw8pQ > -----END PGP SIGNATURE----- > > > ------------------------------ > > Message: 9 > Date: Sat, 29 Sep 2012 21:12:53 +0200 > From: Heino Tiedemann <rotkaps_spam_trap@gmx.de> > Subject: Re: graphics/gimp: What are the stoppers moving from port's > covered version 2.6 to recent and modern version 2.8? > To: freebsd-ports@freebsd.org > Message-ID: <lqtjj9-hs5.ln1@news.hansenet.de> > Content-Type: text/plain > > Ruslan Mahmatkhanov <cvs-src@yandex.ru> wrote: > > > And. What is wrong with rawtherapee? It's on it's latest version as > > far I understand. > > At the momant it is fine. > > > Heino > > > > ------------------------------ > > Message: 10 > Date: Sat, 29 Sep 2012 21:36:30 +0100 > From: Chris Rees <utisoft@gmail.com> > Subject: Re: huge distfiles policy > To: Eitan Adler <lists@eitanadler.com> > Cc: Boris Samorodov <bsam@passap.ru>, FreeBSD Mailing List > <freebsd-ports@freebsd.org> > Message-ID: > <CADLo839bNBF2A8vCMfjcN=3D > ZTaKXnoOd0P4HkceChOOKFZD2x7Q@mail.gmail.com> > Content-Type: text/plain; charset=3DKOI8-R > > On 29 Sep 2012 17:48, "Eitan Adler" <lists@eitanadler.com> wrote: > > > > On 29 September 2012 09:22, =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=C3=93 = =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=C3= =97 <bsam@passap.ru> wrote: > > > Hi All, > > > > > > I'm about to commit print/texlive ports (PR/171571). One of it's port= s > > > (print/texlive-texmf) has size approx. 1.4 Gb. > > > > > > What is the current policy upon huge ports? Should I restrict sometin= g > > > to not build at, say, pointyhat? Something else? > > > > I believe others have set MANUAL_PACKAGE_BUILD=3D huge though I'm not > > certain if this is because the distfile is large, or the final package > > is large (although in this case both are true) > > If you do, you should also chose NO_CDROM and disable distfile mirroring > too! > > Chris > > > ------------------------------ > > Message: 11 > Date: Sat, 29 Sep 2012 23:50:31 +0200 > From: Palle Girgensohn <girgen@pingpong.net> > Subject: Re: Question about postgresql 9 and pg_upgrade > To: Axel Rau <Axel.Rau@chaos1.de> > Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>, Palle > Girgensohn <girgen@FreeBSD.org>, Alexander Pyhalov < > alp@rsu.ru>, Chris > Rees <utisoft@gmail.com>, "pgsql@FreeBSD.org" > <pgsql@FreeBSD.org> > Message-ID: <F7215046-55B7-43B5-A82C-71479A2A339F@pingpong.net> > Content-Type: text/plain; charset=3Dus-ascii > > > > 29 sep 2012 kl. 19:43 skrev Axel Rau <Axel.Rau@chaos1.de>: > > > As my server itself runs in a jail, this won't work, I think. > > You could try just unpacking a package tarball as I suggested at the end > of the mail? > > ------------------------------ > > Message: 12 > Date: Sat, 29 Sep 2012 15:15:01 -0700 > From: Kevin Oberman <kob6558@gmail.com> > Subject: Re: huge distfiles policy > To: Chris Rees <utisoft@gmail.com> > Cc: Eitan Adler <lists@eitanadler.com>, Boris Samorodov > <bsam@passap.ru>, FreeBSD Mailing List < > freebsd-ports@freebsd.org> > Message-ID: > <CAN6yY1sijdnwMTOMnev0xdDL9XeF8=3D > zAKoUOTGuiHGyfxRYn6Q@mail.gmail.com> > Content-Type: text/plain; charset=3DUTF-8 > > On Sat, Sep 29, 2012 at 1:36 PM, Chris Rees <utisoft@gmail.com> wrote: > > On 29 Sep 2012 17:48, "Eitan Adler" <lists@eitanadler.com> wrote: > >> > >> On 29 September 2012 09:22, =D0=91=D0=BE=D1=80=D0=B8=D1=81 =D0=A1=D0= =B0=D0=BC=D0=BE=D1=80=D0=BE=D0=B4=D0=BE=D0=B2 <bsam@passap.ru> wrote: > >> > Hi All, > >> > > >> > I'm about to commit print/texlive ports (PR/171571). One of it's por= ts > >> > (print/texlive-texmf) has size approx. 1.4 Gb. > >> > > >> > What is the current policy upon huge ports? Should I restrict someti= ng > >> > to not build at, say, pointyhat? Something else? > >> > >> I believe others have set MANUAL_PACKAGE_BUILD=3D huge though I'm not > >> certain if this is because the distfile is large, or the final package > >> is large (although in this case both are true) > > > > If you do, you should also chose NO_CDROM and disable distfile mirrorin= g > > too! > > But, based on the current available storage sizes. what is big enough > for these? And, should they be the same? CDROMs are not getting > bigger, but the size of disks just continue to increase. I don't know > how close to being an issue a 1.4GB distfile is with modern systems. > With multi-terabyte drives, 1.4G is not much space. > -- > R. Kevin Oberman, Network Engineer > E-mail: kob6558@gmail.com > > > ------------------------------ > > Message: 13 > Date: Sun, 30 Sep 2012 00:17:03 +0200 > From: Baptiste Daroussin <bapt@FreeBSD.org> > Subject: Re: huge distfiles policy > To: ????? ????????? <bsam@passap.ru> > Cc: hrs@FreeBSD.org, romain@FreeBSD.org, Ports FreeBSD > <freebsd-ports@FreeBSD.org> > Message-ID: <20120929221703.GA70616@ithaqua.etoilebsd.net> > Content-Type: text/plain; charset=3D"utf-8" > > On Sat, Sep 29, 2012 at 05:22:36PM +0400, =D0=91=D0=BE=D1=80=D0=B8=D1=81 = =D0=A1=D0=B0=D0=BC=D0=BE=D1=80=D0=BE=D0=B4=D0=BE=D0=B2 wrote: > > Hi All, > > > > I'm about to commit print/texlive ports (PR/171571). One of it's ports > > (print/texlive-texmf) has size approx. 1.4 Gb. > > > > What is the current policy upon huge ports? Should I restrict someting > > to not build at, say, pointyhat? Something else? > > > > Thanks! > > Hi, > > First I want to say I really want to see texlive in and our old teTex > going out > and I appreciate all the work that are going on in the area recently. > > I have two concerns about this, first one is I would hate to see texlive > has > restricted to avoided to be build as a package because: > > 1/ people would love to just be able to install the package > 2/ lots of ports are currently depending on teTex and if teTex is replace= d > by > texlive which it should that means we will not anymore be able to provide > packages for those packages, I don't have the complete list but I think > this > will impact at least kde and gnome. > > My second concern was discussed when Dominic Fandrey called for testing > this > port: at least 2 people have been working on texlive with different > approach: > hrs and romain. > > In particular Romain and I discussed on merging texlive to the ports tree > based > on http://code.google.com/p/freebsd-texlive/ he has been contacted some > company > to mirror the splitted distfiles for us, and was suppose to resumer his > work on > this when back from vacations which should be the case now given that he > has > done some commit last week :D > > I CCed both hrs and romain so they can give their opinion and the status = of > their work. > > Thanks all for your work on texlive! > > regards, > Bapt > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 196 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20120929/d86= 90b62/attachment-0001.pgp > > ------------------------------ > > Message: 14 > Date: Sat, 29 Sep 2012 18:21:16 -0400 (EDT) > From: "Lawrence K. Chen, P.Eng." <lkchen@ksu.edu> > Subject: Re: CFT: x11/nvidia-driver major update to 304.xx series > To: freebsd-ports@freebsd.org > Message-ID: > <2038073558.11093674.1348957276346.JavaMail.root@k-state.edu> > Content-Type: text/plain; charset=3Dutf-8 > > > > ----- Original Message ----- > > On Fri, 28 Sep 2012 18:22:29 -0400 (EDT) > > Lawrence K. Chen, P.Eng. articulated: > > > > > Well, I had to a bunch of reboots yesterday....so I tried > > > 304.51....no joy. I then tried 295.75, and that works. > > > > In the past, I have had problems that occurred when I updated a port > > and > > failed to rebuild the ports that were dependent upon that port. It is > > rare, but it does happen. In such instances, I find that > > "portmanager" > > used with the "-p" flag comes in extremely handy. I might suggest > > that > > you first update your ports tree and then run something like: > > "portmanager -u -l -y -p" It will do all of that automatically for > > you > > and provide you with a log file should something not work as > > expected. > > Just a thought. > > > > I mentioned in my first post that I already tried rebuilding everything o= n > up. > > -- > Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator > For: Enterprise Server Technologies (EST) -- & SafeZone Ally > Snail: Computing and Telecommunications Services (CTS) > Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 > Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkchen@ksu.edu > Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library > > > ------------------------------ > > Message: 15 > Date: Sun, 30 Sep 2012 05:08:03 +0200 > From: Michael Gmelin <freebsd@grem.de> > Subject: Problems submitting patch containing UTF-8 characters > To: freebsd-ports@freebsd.org > Message-ID: <20120930050803.7914caf6@bsd64.grem.de> > Content-Type: text/plain; charset=3DUS-ASCII > > Hi, > > I recently ran into a problem submitting a PR containing UTF-8 > characters, they ended up garbled, so the maintainer couldn't apply the > patch cleanly. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D171645 > > The characters included were 0xe4 0xb8 0xad and 0xe5 0x9b 0xbd (two > three byte characters). The code affected is about testing utf-8, so > the characters are required. And even if not, patching them away would > require stating them as part of the patch. > > The original e-mail was created using porttools and therefore had no > character set specification, which usually shouldn't be a problem. The > patch was just inline as part of the body. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D171645&getpatch=3D1 > > The character sequence had been recoded to > 0xc3 0xa4 0xc2 0xb8 0xc2 0xad 0xc3 0xa5 0xc2 0x9b 0xc2 0xbd > > It seems like it had been interpreted as latin1 on receipt and then > reencoded as utf-8: > 0xe4 =3D> 0xc3 0xa4 > 0xb8 =3D> 0xc2 0xb8 > 0xad =3D> 0xc2 0xad > 0xe5 =3D> 0xc3 0xa5 > 0x9b =3D> 0xc2 0x9b > 0xbd =3D> 0xc2 0xbd > > Which is obviously not what should happen. The recipient shouldn't make > any assumptions about the character set used. > > The next attempt was sending the patch as a bug-followup through a > graphical MUA. The patch was attached and had been encoded as > quoted-printable (no specific charset specification): > > +-configPath =3D3D u"./config/=3DE4=3DB8=3DAD=3DE5=3D9B=3DBD_client.confi= g" > ++configPath =3D3D > u"./config/=3DE4=3DB8=3DAD=3DE5=3D9B=3DBD_client.config".encode("utf-8=3D= ") > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D171645&getpatch=3D2 > > Unfortunately the results are the same. I did not try forcing a charset > by manually modifying the email (not sure if this will work, I'm > willing to test, but I don't want to further litter that PR). > > At this point I figured, that sending the patch in gzipped format might > help. Said and done, the patch shows up as base64 in the PR. When > copy and pasting and decoding the base64 text, the resulting .gz can be > decompressed correctly and the content is what I expected. When > clicking the download link though: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D171645&getpatch=3D3 > > The resulting .gz file has the correct file size, but is corrupted. > Checking it using the hex editor it looks like it has been reencoded as > utf-8 (and then truncated at the expected file size): > > Hex of the original file (first 16 bytes): > 1f 8b 08 08 ad 79 65 50 00 03 70 79 32 37 2d 49 > > Hex of the file downloaded by using the link: > 1f c2 8b 08 08 c2 ad 79 65 50 00 03 70 79 32 37 > > As you can see, all non 7bit characters have been utf-8 encoded, which > is pretty suboptimal in a binary file. > > 0x8b =3D> 0xc2 0x8b > 0xad =3D> 0xc2 0xad > ... > > As a result the truncated and utf-8 encoded gzip file cannot be > decompressed. > > I'm relatively certain that this has worked at some point in the past. > > Ideas anyone? > > Thanks, > > -- > Michael Gmelin > > > ------------------------------ > > Message: 16 > Date: Sun, 30 Sep 2012 11:16:14 +0100 > From: Jamie Paul Griffin <jamie@kode5.net> > Subject: Installing non-ports software into /usr/local > To: FreeBSD Ports <freebsd-ports@freebsd.org> > Message-ID: <20120930101614.GA13820@kontrol.kode5.net> > Content-Type: text/plain; charset=3Dus-ascii > > Hi > > I am having an issue with mutt 1.5.21. I have set up different colour > schemes, etc. as people do. Anyway, I reinstalled it 2 days ago using the > ports system, because I wanted to link mutt to the ncurses port rather th= an > the system ncurses installation. After soing non of my colours show, only > those that are set from within my terminal emulator which is urxvt. > Initially, I had a problem during make(1) which related to the iconv > library. I have iconv set as an option in my kernel configuration. the > error suggested something about using libiconv instead. > > Anyway, I managed to overcome that and build it and istall it again but > without colour. I'm wondering if I could/should build it my self from > source and install it into /usr/local to see if that makes any difference= . > Would doing that cause problems for the ports system? > > Any comments and advice are welcome. Best wishes, Jamie > > > ------------------------------ > > Message: 17 > Date: Sun, 30 Sep 2012 11:47:52 +0100 > From: Chris Rees <crees@FreeBSD.org> > Subject: Re: Installing non-ports software into /usr/local > To: Jamie Paul Griffin <jamie@kode5.net>, udo.schweigert@siemens.com > Cc: FreeBSD Ports <freebsd-ports@freebsd.org> > Message-ID: > <CADLo838sQ5rZ1j=3Dz9eu5jrToYR2NgntLuVRBx0HdS=3D > q6oUxnDA@mail.gmail.com> > Content-Type: text/plain; charset=3DISO-8859-1 > > On 30 September 2012 11:16, Jamie Paul Griffin <jamie@kode5.net> wrote: > > Hi > > > > I am having an issue with mutt 1.5.21. I have set up different colour > schemes, etc. as people do. Anyway, I reinstalled it 2 days ago using the > ports system, because I wanted to link mutt to the ncurses port rather th= an > the system ncurses installation. After soing non of my colours show, only > those that are set from within my terminal emulator which is urxvt. > Initially, I had a problem during make(1) which related to the iconv > library. I have iconv set as an option in my kernel configuration. the > error suggested something about using libiconv instead. > > > > Anyway, I managed to overcome that and build it and istall it again but > without colour. I'm wondering if I could/should build it my self from > source and install it into /usr/local to see if that makes any difference= . > Would doing that cause problems for the ports system? > > > > Any comments and advice are welcome. Best wishes, Jamie > > As long as you don't install it from the port, which would overwrite > your version, there would be no trouble with this. > > If you come up with a solution, please send a PR in which the > maintainer will I'm sure be glad to look at :) > > Chris > > > ------------------------------ > > Message: 18 > Date: Sun, 30 Sep 2012 07:34:20 -0400 > From: Jerry <jerry@seibercom.net> > Subject: Re: CFT: x11/nvidia-driver major update to 304.xx series > To: freebsd-ports@freebsd.org > Message-ID: <20120930073420.24820e22@scorpio> > Content-Type: text/plain; charset=3DUTF-8 > > On Sat, 29 Sep 2012 18:21:16 -0400 (EDT) > Lawrence K. Chen, P.Eng. articulated: > > > I mentioned in my first post that I already tried rebuilding > > everything on up. > > >From your original post: > > <quote> > Tried rebuilding a bunch of other things, but didn't help. > </quote> > > The word "bunch" !=3D "build or run dependencies" in my vocabulary. > Nor does it indicate, or at least not to me anyway, that you > actually rebuilt all required run or build dependencies. Sorry about > the misunderstanding. I'll leave you to figure out the problem yourself. > > -- > Jerry =E2=99=94 > > Disclaimer: off-list followups get on-list replies or get ignored. > Please do not ignore the Reply-To header. > __________________________________________________________________ > All the evidence concerning the universe > has not yet been collected, so there's still hope. > > > ------------------------------ > > Message: 19 > Date: Sun, 30 Sep 2012 07:43:14 -0400 > From: Jerry <jerry@seibercom.net> > Subject: Re: huge distfiles policy > To: freebsd-ports@freebsd.org > Message-ID: <20120930074314.013e793a@scorpio> > Content-Type: text/plain; charset=3DUTF-8 > > On Sat, 29 Sep 2012 15:15:01 -0700 > Kevin Oberman articulated: > > > CDROMs are not getting bigger, but the size of disks just continue to > > increase. > > However, DVD's can easily handle a paltry 1.4GB. All modern systems > come with DVD's so perhaps it is time to embrace progress and move > forward with our thinking and not chain ourselves to the past. > > -- > Jerry =E2=99=94 > > Disclaimer: off-list followups get on-list replies or get ignored. > Please do not ignore the Reply-To header. > __________________________________________________________________ > TLC announced that "Honey Boo Boo" will have a Halloween special. Their > neighbors are planning to give them a scare by dressing up as child > protective services. > > > ------------------------------ > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > End of freebsd-ports Digest, Vol 488, Issue 9 > ********************************************* >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANS5nXoZ0oCJNtSKQ96%2BeTH4Hrq37PRY2cjmZkY8px1jSpOnuA>