| Summary: | Stabilize =sci-geosciences/grass-6.3.0 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
| Component: | Current packages | Assignee: | Steve Arnold <nerdboy> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caleb, dev-zero, esigra, sci |
| Priority: | High | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 270916, 285475 | ||
| Bug Blocks: | 266066 | ||
|
Description
Samuli Suominen (RETIRED)
2008-12-13 17:50:15 UTC
x86 stable or not, it needs new postgres stable.. dev-zero, deptree is broken -- can >=dev-db/postgresql-base-8.3 be stabilized? (In reply to comment #3) > dev-zero, deptree is broken -- can >=dev-db/postgresql-base-8.3 be stabilized? > nerdboy, or backport ffmpeg fix to current stable. otherwise archteams will have to revert back to ~arch with this package, or package.use.mask ffmpeg etc. which way is preferred? I'd rather shoot for stablizing on the newer interfaces; is that do-able? (In reply to comment #5) > I'd rather shoot for stablizing on the newer interfaces; is that do-able? > No response from dev-zero, so I'm afraid x86 will have to revert all of it's stable keywords soon.. One package pulling old ffmpeg, another new ffmpeg isn't just acceptable = broken deptree. I thought there was a push for other packages depending on ffmpeg to update to the new header layout... Is there some timetable we can shoot for? (In reply to comment #7) > I thought there was a push for other packages depending on ffmpeg to update to > the new header layout... Is there some timetable we can shoot for? > Yesterday. !!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
media-video/ffmpeg:0
('ebuild', '/', 'media-video/ffmpeg-0.4.9_p20070616-r3', 'merge') pulled in by
<media-video/ffmpeg-0.4.9_p20070616-r20 required by ('ebuild', '/', 'sci-geosciences/grass-6.2.1', 'merge')
(and 1 more)
('ebuild', '/', 'media-video/ffmpeg-0.4.9_p20081014', 'merge') pulled in by
>=media-video/ffmpeg-0.4.9_p20081014 required by ('ebuild', '/', 'media-plugins/gst-plugins-ffmpeg-0.10.5', 'merge')
>=media-video/ffmpeg-0.4.9_p20080326 required by ('ebuild', '/', 'app-cdr/k3b-1.0.5-r3', 'merge')
(and 1 more)
stable sci-geo/grass is the only incompatible package we have in tree
Please advise on postgresql-base. grass-6.3.0 is fine on sparc, but without postgresql-base, we can't mark it stable, and reverting all versions of grass to ~sparc doesn't make any sense. I guess we'll have to hang loose for a bit on postgres... I thought Samuli was going to file a stable bug on pg 8.3 and link it to this one... Grass 6.2.1 is updated for ffmpeg, btw... (In reply to comment #12) > Grass 6.2.1 is updated for ffmpeg, btw... > Samuli, I have confirmed that grass-6.2.1 compiles against ffmpeg-0.4.9_p20081014. Since postgresql-base isn't ready to go, I'm not seeing an urgency here. So, I am going to remove all the arches for now. 19 Dec 2008; Steve Arnold <nerdboy@gentoo.org> +files/grass-6.2.1-gcc43.patch, grass-6.2.1.ebuild: Backported ffmpeg fixup and use flag cleanup (see bug #250850). Also added ggc 4.3 include patch. Still need postgres 8.3 pushed to stable before Grass 6.3 can go stable. Maintainers, feel free to add us back when everything is sorted out. Thanks. I was waiting for an advise from postgres maintainers, but without response. I won't be needing this in stable anymore, please open a new bug when you get postgres sorted out. Thanks. Can we pleeeeeease get some stable action on pg 8.3? The stable grass (6.2.1) is now broken due to compiler updates, and upstream already has several 6.4.0 rc releases out. Many of us would like to stablize Grass 6.3.0 but we can't without some pg luv. And no, I don't have time to do any extra work, since I already volunteered to work on some new sci-packages. And I have exams to grade... (In reply to comment #15) > Can we pleeeeeease get some stable action on pg 8.3? The stable grass (6.2.1) > is now broken due to compiler updates, and upstream already has several 6.4.0 > rc releases out. Many of us would like to stablize Grass 6.3.0 but we can't > without some pg luv. And no, I don't have time to do any extra work, since I > already volunteered to work on some new sci-packages. And I have exams to > grade... > 12:44 <@dev-zero> ssuominen: I'm not opening a bug, but you can 12:44 <@graaff> dev-zero: for fcgi the proper term is "maintain" (with the quotes). Feel free to improve it where you see fit. 12:44 <@graaff> Or ping me and I'll have a look at it. 12:44 <@dev-zero> graaff: ok, thanks 12:44 <@ssuominen> dev-zero, psychoschlumpf: i'll open the bug if I can get my hands on a sensible list that needs to go stable 12:45 <@ssuominen> dev-zero: would everything the virtuals pull in be sufficient? 12:45 <@dev-zero> ssuominen: no 12:45 <@ssuominen> see.. 12:45 <+psychoschlumpf> ssuominen: no 12:45 <@dev-zero> you need postgresql-{docs,base,server} 12:47 <@ssuominen> and eselect-postgressql? 12:47 <@ssuominen> *and eselect-postgresql? 12:47 <@ssuominen> plus virtuals 12:48 <@ssuominen> plus libpq 12:48 <@ssuominen> possible libpqxx? 12:48 <@ssuominen> it's pretty huge list, might end up breaking tree 12:48 <+psychoschlumpf> libpqxx is something completely different 12:49 <+psychoschlumpf> 3rd party maintained C++ library 12:49 <@ssuominen> ok So it seems we can open a bug for new postgres to be stable, but I'm still a bit unsure of the list. Did you get anything firm on which packages you need? (In reply to comment #17) > Did you get anything firm on which packages you need? > I don't need anything; don't use grass and it's not a issue for me anymore. But, only thing I managed to get out was the irclog pasted previously. Bug 285475 should do? x86 stable ppc stable sparc stable Stable on amd64 All arches done |
