Please! Do not add this to portage UNTIL Gallery 2.1 is released! Should be out 3/18 - 3/20-ish if all is according to plan. This is a major update to G2, adding lots of features. See the site if you care what :) The changes to the ebuild: 1) added dcraw use flag (used by RAW module) 2) moved jhead into netpbm's use flag, because jhead is only used by netpbm 3) created zip and unzip use flags because they are optional 4) added warning and information on backing up G2's db and g2data dir because this upgrade makes a downgrade w/o a backup very very difficult.
Created attachment 82450 [details] gallery-2.1.ebuild G2.1 has not actually been released yet. Currently at RC2, expected to release sometime this weekend (3/18-3/20'ish).
For testification, I downloaded the gallery-2.1-rc2a-full.tar.gz file and renamed it to gallery-2.1-full.tar.gz
Update: Release of G2.1 is due 3/19 @ ~7:30PM PST
Gallery 2.1 has been released as of Thursday, March 23, 2006. Hopefully this ebuild will get pushed up to the tree soon.
2.1 is in CVS. the dcraw flag will have to wait until media-gfx/dcraw is marked ~alpha, ~amd64, and ~hppa.
Make that ~alpha and ~hppa
This ebuild seems to have a problem performing the actual upgrade. I had to manually do the cp -R * command in order to upgrade. I'm not sure why though since it all looks fine to me.
I personally don't see how there could be any issue, as it is literally a copy of the 2.0 ebuild with some USE flag changes and a warning added at the end. The only change to anything pertaining to copy/build portion was the removal of an epatch line. But I honestly only emerge it, I don't use it for my G2 and once emerged I don't use it with webapp-config. Since i have "vhost" flag, it means all I end up with is a copy in /usr/share/webapps/.
"2.1 is in CVS. the dcraw flag will have to wait until media-gfx/dcraw is marked ~alpha, ~amd64, and ~hppa." "Make that ~alpha and ~hppa" I don't know the policy on use flags, but for something to be in a stable (ie, x86, etc) ebuild it can't have any ~unstable use flags? Where might one find out about the problems moving dcraw to stable?
(In reply to comment #7) > This ebuild seems to have a problem performing the actual upgrade. I had to > manually do the cp -R * command in order to upgrade. I'm not sure why though > since it all looks fine to me. Could you post the actual command you had to do?
(In reply to comment #9) > I don't know the policy on use flags, but for something to be in a stable (ie, > x86, etc) ebuild it can't have any ~unstable use flags? All dependencies of an ebuild stable on a particular arch must also be stable. In this case, gallery is ~alpha, but dcraw is not keyworded ~alpha. > Where might one find > out about the problems moving dcraw to stable? Bug #127432, which I filed yesterday.
I'm also having the Problem that an existing 2.04 Installation isn't actually upgraded. I'm running it on AMD64.
My upgrade with `webapp-config -U` worked without any problems (x86).
Shouldn't that be done automatically with the emerge of the new Version?
(In reply to comment #14) > Shouldn't that be done automatically with the emerge of the new Version? Afaik that depends if you have USE flag vhosts set: if yes, then it's not automatically upgraded (and you're told at the end of the merge), but requires you to use webapp-config manually instead.
(In reply to comment #15) > (In reply to comment #14) > > Shouldn't that be done automatically with the emerge of the new Version? > > Afaik that depends if you have USE flag vhosts set: if yes, then it's not > automatically upgraded (and you're told at the end of the merge), but requires > you to use webapp-config manually instead. > I haven't set the vhost USE flag and the only output at the end of the emerge i get is: " * You are strongly encouraged to back up your database * and the g2data directory, as upgrading to 2.1.x will make * irreversible changes to both. * * g2data dir: cp -Rf /path/to/g2data/ /path/to/backup * mysql: mysqldump --opt -u username -h hostname -p database > /path/to/backup.sql * postgres: pg_dump -h hostname --format=t database > /path/to/backup.sql"
Hm. Do you get a "vhosts USE flag not set - auto-installing using webapp-config" anywhere at the end of the merge? The corresponding code for the installation is in the webapp eclass: http://www.gentoo.org/cgi-bin/viewcvs.cgi/eclass/webapp.eclass?rev=1.40&view=auto And the installed app is not in /var/www/localhost/htdocs/gallery?
(In reply to comment #17) > Hm. Do you get a "vhosts USE flag not set - auto-installing using > webapp-config" anywhere at the end of the merge? > The corresponding code for the installation is in the webapp eclass: > http://www.gentoo.org/cgi-bin/viewcvs.cgi/eclass/webapp.eclass?rev=1.40&view=auto > > And the installed app is not in /var/www/localhost/htdocs/gallery? > The output above is all i get after the emerge. And in /var/www/localhost/htdocs/gallery is only the 2.0.4 Version. Should the ebuild make the upgrade itself or is this behaviour wanted by the Devs?
This was indeed a small bug in the ebuild. Either run w-c -U manually or upgrade to gallery-2.1-r1.
I'm curious what the bug is, if I introduced it or what not. :)
(In reply to comment #20) > I'm curious what the bug is, if I introduced it or what not. :) I'll ask a leading question - what function is responsible for calling w-c when vhosts is unset? Answer to today's question of the day is hidden in the commit message on http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-apps/gallery/
(In reply to comment #19) > This was indeed a small bug in the ebuild. Either run w-c -U manually or > upgrade to gallery-2.1-r1. > The new Version works fine for me.
Did it really need a revbump to -r1? Fix and tell early adopters to re-emerge if they can't work out how to upgrade.
Gallery 2.1 has been relaesed :-D http://gallery.menalto.com/gallery_2.1_released
Yes, it sure has been! You'll notice the bug was file on the 18th of March, before it was released. And if you check portage, you'll notice that it is there, arriving I think on the 28th of March! :)
stale
