From owner-freebsd-ruby@FreeBSD.ORG Sun Jun 5 22:20:28 2011 Return-Path: Delivered-To: ruby@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2818A1065673; Sun, 5 Jun 2011 22:20:28 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F390F8FC13; Sun, 5 Jun 2011 22:20:27 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p55MKRvi094311; Sun, 5 Jun 2011 22:20:27 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p55MKRr5094307; Sun, 5 Jun 2011 22:20:27 GMT (envelope-from edwin) Date: Sun, 5 Jun 2011 22:20:27 GMT Message-Id: <201106052220.p55MKRr5094307@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, ruby@FreeBSD.org From: edwin@FreeBSD.org Cc: Subject: Re: ports/157644: [MAINTAINER] devel/rubygem-ncursesw (install bug fix) X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2011 22:20:28 -0000 Synopsis: [MAINTAINER] devel/rubygem-ncursesw (install bug fix) Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: edwin Responsible-Changed-When: Sun Jun 5 22:20:27 UTC 2011 Responsible-Changed-Why: ruby@ wants this port PRs (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=157644 From owner-freebsd-ruby@FreeBSD.ORG Mon Jun 6 11:08:41 2011 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AFBC106566B for ; Mon, 6 Jun 2011 11:08:41 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 210B18FC1B for ; Mon, 6 Jun 2011 11:08:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p56B8fBn038972 for ; Mon, 6 Jun 2011 11:08:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p56B8eX6038970 for ruby@FreeBSD.org; Mon, 6 Jun 2011 11:08:40 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 6 Jun 2011 11:08:40 GMT Message-Id: <201106061108.p56B8eX6038970@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: ruby@FreeBSD.org Cc: Subject: Current problem reports assigned to ruby@FreeBSD.org X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 11:08:41 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/157644 ruby [MAINTAINER] devel/rubygem-ncursesw (install bug fix) o ports/157536 ruby [MAINTAINER UPDATE] sysutils/rubygem-bundler: update t o ports/156066 ruby [NEW PORT] databases/rubygem-xapian-full (self contain o ports/154958 ruby [REPOCOPY] databases/rubygem-sqlite3 --> databases/rub o ports/154210 ruby ports-mgmt/portupgrade 2.4.8_1,2: cross-thread violati o ports/152387 ruby ports-mgmt/portupgrade: portinstall with bash completi o ports/151662 ruby ports-mgmt/portupgrade: upgrade of autoconf leaves old o ports/151510 ruby ports-mgmt/portupgrade: circular dependencies breaks p o ports/149817 ruby ports-mgmt/portupgrade: portinstall -p option doesn't o ports/147242 ruby ports-mgmt/portupgrade incorrectly remove old port whe o ports/144769 ruby [PATCH] ports-mgmt/portupgrade should have a configura o ports/144605 ruby [PATCH] Get ports-mgmt/portupgrade to build under Ruby o ports/140880 ruby ports-mgmt/portupgrade: portversion confused with ezm3 o ports/140364 ruby ports-mgmt/portupgrade-devel: #! line substitution is o ports/140273 ruby ports-mgmt/portupgrade-devel chokes on bsdpan pkgs o ports/140008 ruby ports-mgmt/portupgrade: many papercut omissions on por o ports/137958 ruby ports-mgmt/portupgrade fails with recursive dependency o ports/137708 ruby ports-mgmt/portupgrade: portupgrade -cRn is broken o ports/135691 ruby ports-mgmt/portupgrade Wrong example in man page of pk o ports/134714 ruby ports-mgmt/portupgrade deletes user data without quest o ports/134182 ruby ports-mgmt/portupgrade incorrectly handles manual reje o ports/131111 ruby ports-mgmt/portupgrade-devel: completely removes packa o ports/129930 ruby ports-mgmt/portupgrade - portinstall tries to install o ports/129891 ruby ports-mgmt/portupgrade fails to recognize variations o o ports/128881 ruby ports-mgmt/portupgrade backtrace o ports/127889 ruby ports-mgmt/portupgrade detects spurious failures and s o ports/127019 ruby ports-mgmt/portupgrade does not recognize fail conditi o ports/126140 ruby ports-mgmt/portupgrade runtime error o ports/125936 ruby ports-mgmt/portupgrade -R fails if BUILD_DEP's are not o ports/112818 ruby ports-mgmt/portupgrade -a fails with database error 30 problems total. From owner-freebsd-ruby@FreeBSD.ORG Mon Jun 6 16:36:15 2011 Return-Path: Delivered-To: ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F31B1065670 for ; Mon, 6 Jun 2011 16:36:15 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from 23.mail-out.ovh.net (23.mail-out.ovh.net [91.121.28.222]) by mx1.freebsd.org (Postfix) with SMTP id E80028FC12 for ; Mon, 6 Jun 2011 16:36:14 +0000 (UTC) Received: (qmail 29975 invoked by uid 503); 6 Jun 2011 16:06:52 -0000 Received: from marvin.blogreen.org (178.33.173.42) by 23.mail-out.ovh.net with SMTP; 6 Jun 2011 16:06:52 -0000 Received: by marvin.blogreen.org (Postfix, from userid 1001) id 4D728202E9; Mon, 6 Jun 2011 18:09:31 +0200 (CEST) Date: Mon, 6 Jun 2011 18:09:31 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: ruby@freebsd.org Message-ID: <20110606160931.GA17343@blogreen.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline X-PGP-Key: http://romain.blogreen.org/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) X-Ovh-Tracer-Id: 18094337404831910484 Cc: Subject: Fixing gem files permissions X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 16:36:15 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello I would like to know if there is some 'standard' way for the rubygems-* ports for fixing wrong files permissions. It appears that getopt-declare (not in the ports tree, it's a dependency of another port I would like to push) install files in a weird fashion: ------------------------------8<--------------------------- =3D=3D=3D> SECURITY REPORT:=20 This port has installed the following world-writable files/directorie= s. /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /getopt-declare.gemspec /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /samples/cmdline_singles.rb /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /samples/cmdline_array.rb /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /samples/cmdline_usage.rb /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /test/test_cmdline_parameters.rb /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /README.txt [...] ------------------------------8<--------------------------- My current workaround is: ------------------------------8<--------------------------- post-install: @${FIND} ${PREFIX}/${GEM_LIB_DIR} -type f -exec ${CHMOD} 444 '{}' ';' ------------------------------8<--------------------------- I am not really happy with this. Is there a better way to fix this? I am not used with Ruby gems packaging, and I would like to be sure that this is a problem that should be signaled upstream before acting: is it? Thanks! Romain --DocE+STaALJfprDB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQGcBAEBAgAGBQJN7Pu4AAoJELpNHZVREjNv1/UMAKmq4OwtnVWfctzAM/+Tf9Vy MJB1XuB+/LNDtGP5p9VFiTxS9PSoOhgVhJsrpA4XSyyFVSNbvP4H44ekcENwIAze irAuIXQXt6zlI0znloxLIC/tlva4DpZ1PSO2iq1Yho35yz61SqWzRUlgqKAwijyt mtAeUzhWH2QAN+5gVqVeqzrVLHxuAbL7hYR+4uI8s3qGNBg8w9rul2yPU+mff3dj Y3CqhWU94zQRREr6xX3ZlWGdhVNWudTWwFQB8Qrpr8qdiK5av/6NFewYVe94sYoD O+V1dhLOHG6hGmg//d5n5Pjj6wMXo2Uvid6hczKqTxQB1PyhAhFAuGC25MiannOB UpU9UVCwSiS+rIMs054yAasNxfVRL9U0wRx7u2zfG9mOf+Y1qlwp6XXOWL/gaUnm /yqG6tPNGgxnDtqMo+YZ4kcOqR9v9z5Gt1s2tkd4D3N8m4FsG4vqa4+e3zeEbK62 NoFZkqFzAtge2RiLbmi+aIacKLPiCk7oenPonPzZsw== =N6sR -----END PGP SIGNATURE----- --DocE+STaALJfprDB-- From owner-freebsd-ruby@FreeBSD.ORG Tue Jun 7 18:31:23 2011 Return-Path: Delivered-To: ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C800106566B for ; Tue, 7 Jun 2011 18:31:23 +0000 (UTC) (envelope-from freebsdlists-ruby@chillibear.com) Received: from mail.sundive.org (mail.sundive.org [212.13.197.214]) by mx1.freebsd.org (Postfix) with ESMTP id C62F38FC15 for ; Tue, 7 Jun 2011 18:31:22 +0000 (UTC) Received: from [46.208.32.91] (helo=[192.168.0.44]) by sundive.org with esmtpsa (TLSv1:DES-CBC3-SHA:168) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QU159-000FRE-Hh; Tue, 07 Jun 2011 19:32:53 +0100 User-Agent: Microsoft-Entourage/12.29.0.110113 Date: Tue, 07 Jun 2011 19:31:13 +0100 From: Eric To: Romain =?ISO-8859-1?B?VGFydGnocmU=?= , Message-ID: Thread-Topic: Fixing gem files permissions Thread-Index: AcwlQRRDRqP5Kw3g1kqWed8yZMBk4w== In-Reply-To: <20110606160931.GA17343@blogreen.org> Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-Spam: No X-bounce-key: sundive.org-1; freebsdlists-ruby@chillibear.com; 1307471574; 7ced5612; Cc: Subject: Re: Fixing gem files permissions X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 18:31:23 -0000 > From: Romain Tarti=E8re > I would like to know if there is some 'standard' way for the rubygems-* > ports for fixing wrong files permissions. Not that I'm personally aware of, but other more experienced people on this list may know better. > It appears that > getopt-declare (not in the ports tree, it's a dependency of another port > I would like to push) install files in a weird fashion: >=20 > ------------------------------8<--------------------------- > =3D=3D=3D> SECURITY REPORT: > This port has installed the following world-writable files/director= ies. > /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.= 29/ge > topt-declare.gemspec > /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.= 29/sa > mples/cmdline_singles.rb > /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.= 29/sa > mples/cmdline_array.rb > /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.= 29/sa > mples/cmdline_usage.rb > /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.= 29/te > st/test_cmdline_parameters.rb > /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.= 29/RE > ADME.txt > [...] > ------------------------------8<--------------------------- >=20 > My current workaround is: >=20 > ------------------------------8<--------------------------- > post-install: > @${FIND} ${PREFIX}/${GEM_LIB_DIR} -type f -exec ${CHMOD} 444 '{}' = ';' > ------------------------------8<--------------------------- >=20 > I am not really happy with this. Is there a better way to fix this? I don't think there is an easy place other than the post-install target where you can 'patch' gems since the other stages of the port build process do little for a gem, given it's mainly a wrapper for the gem installer itself. I remember had to do similar things with a couple of gems I use personally (can't remember if I've submitted those as ports yet). The only thing I'd say is to restrict your 'fix' to just those files your 'getopt-declare' gem installs rather than make all the contents of the Gem lib dir 444 and potentially cause a headache somewhere else. So something more like (I not= e from a quick glance in my own Gem libs that they tend to be root/wheel and 644) post-install: @${FIND} ${PREFIX}/${GEM_LIB_DIR}/${PORTNAME}-${PORTVERSION} -type f -exe= c ${CHMOD} 644 '{}' ';' I'd also pop a comment in the Makefile so someone following knows why you'v= e done it. =20 > I am not used with Ruby gems packaging, and I would like to be sure that > this is a problem that should be signaled upstream before acting: is it? I've never looked at the Gem internals to see how it determines file permissions of those files it installs, but given it *appears* to be a bug you'd do well to flag it to upstream and see what they say. Regards Eric From owner-freebsd-ruby@FreeBSD.ORG Tue Jun 7 21:36:45 2011 Return-Path: Delivered-To: freebsd-ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7D81106566C for ; Tue, 7 Jun 2011 21:36:45 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from 23.mail-out.ovh.net (23.mail-out.ovh.net [91.121.28.222]) by mx1.freebsd.org (Postfix) with SMTP id 4F1E28FC1B for ; Tue, 7 Jun 2011 21:36:44 +0000 (UTC) Received: (qmail 25088 invoked by uid 503); 7 Jun 2011 21:07:24 -0000 Received: from marvin.blogreen.org (178.33.173.42) by 23.mail-out.ovh.net with SMTP; 7 Jun 2011 21:07:24 -0000 Received: by marvin.blogreen.org (Postfix, from userid 1001) id E190A515A; Tue, 7 Jun 2011 23:10:00 +0200 (CEST) Date: Tue, 7 Jun 2011 23:10:00 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: freebsd-ruby@freebsd.org Message-ID: <20110607211000.GA58324@blogreen.org> References: <20110606160931.GA17343@blogreen.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://romain.blogreen.org/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) X-Ovh-Tracer-Id: 10595844024939760316 Subject: Re: Fixing gem files permissions X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 21:36:46 -0000 --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 07, 2011 at 07:31:13PM +0100, Eric wrote: > > From: Romain Tarti=E8re > > My current workaround is: > >=20 > > ------------------------------8<--------------------------- > > post-install: > > @${FIND} ${PREFIX}/${GEM_LIB_DIR} -type f -exec ${CHMOD} 444 '{}= ' ';' > > ------------------------------8<--------------------------- > >=20 > > I am not really happy with this. Is there a better way to fix this? >=20 > I don't think there is an easy place other than the post-install target > where you can 'patch' gems since the other stages of the port build proce= ss > do little for a gem, given it's mainly a wrapper for the gem installer > itself. >=20 > I remember had to do similar things with a couple of gems I use personally > (can't remember if I've submitted those as ports yet). The only thing I'd > say is to restrict your 'fix' to just those files your 'getopt-declare' g= em > installs rather than make all the contents of the Gem lib dir 444 and > potentially cause a headache somewhere else. So something more like (I n= ote > from a quick glance in my own Gem libs that they tend to be root/wheel and > 644) AFAICS, ${GEM_LIB_DIR} expends to the gem directory: | % make -V GEM_LIB_DIR | lib/ruby/gems/1.8/gems/getopt-declare-1.29 BTW, I changed the mode from 444 to 644 as it is the permissions of other gem files as you said. > I'd also pop a comment in the Makefile so someone following knows why you= 've > done it. Yep! > > I am not used with Ruby gems packaging, and I would like to be sure that > > this is a problem that should be signaled upstream before acting: is it? >=20 > I've never looked at the Gem internals to see how it determines file > permissions of those files it installs, but given it *appears* to be a bug > you'd do well to flag it to upstream and see what they say. I'll do so. Thanks! Romain --=20 Romain Tarti=E8re http://people.FreeBSD.org/~romain/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQGcBAEBAgAGBQJN7pOmAAoJELpNHZVREjNvc7sL/AqoSM1WDWAkrDNTKWWp4EvP QNij0mbs9hC8eFz+yqoEZlRS8jJtd6ksKyp8WNBFrRi6IR8hwKSgMGHE9K0nINNf 6OT5SkoISHyCydLUdNtiNRDzxqQAYn+PQD1HRIUgM66KHet2CA/ISIPwDqZzPHkk xEjSioz/857oIPCDwDxb+UCBYdIOJjTt1PHL4Wi4f3iJI9Lrk9yIFMJlaS3bQOSm DzvEFmfX3/qH+WUnPIDIVPQnzjWVBLhcLppNFPu8/4NSx4TGrxUM6gCyOL+7jmqG OSjsVJi3iuIAGwc1M4qZPFVCVZxNzeIViURP645ODnKdfTldagUXL+uJiN1NfAJp 4Q0v9W5KBG+CyqCU9vAxcXAC94qzfRj+hNf4JGyRJBBRLAQw1Rjl72LNBqjg0WL2 TLPSWMwNhUMrRa+9M7DCuDJdhSteb3aZ6rOyTrjZIVfB3X8TpkIg2CnrK04yN8TK qvvnCdrSu+GNPP3fhOLiaCUgFNYtCar6CTVAi0Lwiw== =NEHB -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- From owner-freebsd-ruby@FreeBSD.ORG Wed Jun 8 18:30:28 2011 Return-Path: Delivered-To: ruby@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90143106564A; Wed, 8 Jun 2011 18:30:28 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 682828FC1D; Wed, 8 Jun 2011 18:30:28 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p58IUShk071283; Wed, 8 Jun 2011 18:30:28 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p58IUSCo071272; Wed, 8 Jun 2011 18:30:28 GMT (envelope-from edwin) Date: Wed, 8 Jun 2011 18:30:28 GMT Message-Id: <201106081830.p58IUSCo071272@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, ruby@FreeBSD.org From: edwin@FreeBSD.org Cc: Subject: Re: ports/157713: [patch][maintainer-update] graphics/rubygem-dragonfly: update to 0.9.3 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 18:30:28 -0000 Synopsis: [patch][maintainer-update] graphics/rubygem-dragonfly: update to 0.9.3 Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: edwin Responsible-Changed-When: Wed Jun 8 18:30:27 UTC 2011 Responsible-Changed-Why: ruby@ wants this port PRs (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=157713 From owner-freebsd-ruby@FreeBSD.ORG Thu Jun 9 23:10:12 2011 Return-Path: Delivered-To: ruby@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54001106564A for ; Thu, 9 Jun 2011 23:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2B58F8FC15 for ; Thu, 9 Jun 2011 23:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p59NAB0w075917 for ; Thu, 9 Jun 2011 23:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p59NABq6075914; Thu, 9 Jun 2011 23:10:11 GMT (envelope-from gnats) Date: Thu, 9 Jun 2011 23:10:11 GMT Message-Id: <201106092310.p59NABq6075914@freefall.freebsd.org> To: ruby@FreeBSD.org From: Evren Yurtesen Cc: Subject: Re: ports/140273: ports-mgmt/portupgrade-devel chokes on bsdpan pkgs X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Evren Yurtesen List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 23:10:12 -0000 The following reply was made to PR ports/140273; it has been noted by GNATS. From: Evren Yurtesen To: bug-followup@FreeBSD.org, dokas@oitsec.umn.edu Cc: Subject: Re: ports/140273: ports-mgmt/portupgrade-devel chokes on bsdpan pkgs Date: Fri, 10 Jun 2011 01:37:26 +0300 I just faced with this problem and I can confirm that it still exist. Why nobody is fixing it? From owner-freebsd-ruby@FreeBSD.ORG Sat Jun 11 10:11:22 2011 Return-Path: Delivered-To: ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86F1B1065676 for ; Sat, 11 Jun 2011 10:11:22 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from 23.mail-out.ovh.net (23.mail-out.ovh.net [91.121.28.222]) by mx1.freebsd.org (Postfix) with SMTP id DB6EB8FC0C for ; Sat, 11 Jun 2011 10:11:21 +0000 (UTC) Received: (qmail 20952 invoked by uid 503); 11 Jun 2011 10:08:47 -0000 Received: from marvin.blogreen.org (178.33.173.42) by 23.mail-out.ovh.net with SMTP; 11 Jun 2011 10:08:47 -0000 Received: by marvin.blogreen.org (Postfix, from userid 1001) id 42ED21AB25; Sat, 11 Jun 2011 12:11:17 +0200 (CEST) Date: Sat, 11 Jun 2011 12:11:17 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: ruby@FreeBSD.org Message-ID: <20110611101116.GA74274@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline X-PGP-Key: http://romain.blogreen.org/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) X-Ovh-Tracer-Id: 4516828952648600148 Cc: Subject: rubygem-sqlite3 1.3.3 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 10:11:22 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello ruby@, PR ports/154958 [1] seems to have been opened for allowing an update of databases/rubygem-sqlite3 to 1.3.3. While the PR is not closed, I think it could be, and an update is now possible. Can you please check that the PR can be closed and tell me if an update is pending? Thanks! Romain References: 1. http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/154958 --=20 Romain Tarti=E8re http://people.FreeBSD.org/~romain/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQGcBAEBAgAGBQJN8z88AAoJELpNHZVREjNvGqUL/2B6jrDPU+EsWXVXy8es6A64 pRjjrKH8kdHNT6r7jZLIOGpxTHz0Thpcxl7wdCYQoq/EDm2Z/g0OByPu3p7n3xZM OqbNFEqOjyE/vUf1TTPtwkF6IlfoIAplHQ6+xxxhBuQcr/Ug58iaqm0ERypgOdIY raaaJKXYOW36sH30A2HpoZBdeUfbsUMzGGhWHlcp0OMkktY3bM94V4erHAMpfGiy H1Q7X7Q71VVYdHBOR6NSDK9+wYMEINsRzURBkZOGsUhbC6aBBdzKLkhK/qGkrc1M 8HjmKGK2Tu91gNapiZkg/zw5+W9mvLsySXpNHwwJN28WJooZzdJ+OZPmgSjGfXyW 4moCcJLLcBSCEjpU/4bZz8+4EGqeMXDtDVpOCy38ggSl0karuuSVBQ5klnUetE06 igW76UYxq+kGBqTejRfYSfA2emPwECTw9I+2cqdUwMynIemPL3YaZkxovcpBTk1r W5fWur1fUtMsTwEdBehGbVSyVQuaeNdNgYzRXGn8ww== =wq2+ -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO--