First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 232277
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Net-Mail Packages <net-mail@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: BobCaTT <bugs@menfin.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 232277 depends on: Show dependency tree
Bug 232277 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-07-18 23:30 0000
Hi,

imapsync refuse to start and even display help with version of
dev-perl/Mail-IMAPClient version 3.xx
Even the latest version 1.255 failed.


Reproducible: Always

Steps to Reproduce:
1. install/upgrade Mail-IMAPClient to version 3
2. install imapsync
3. run imapsync 

Actual Results:  
stromboli ~# imapsync 
Subroutine Authuser redefined at /usr/bin/imapsync line 2564.
imapsync needs perl lib Mail::IMAPClient release 2.2.9 exactly, future imapsync
release may suppoort 3.0.x, but sorry not now. See file BUG_IMAPClient_3.xx
# Looks like your test died before it could output anything.

Expected Results:  
help should be displayed

------- Comment #1 From Joe Peterson 2008-07-18 23:37:01 0000 -------
Note that a revbump of the imapsync-1.255 ebuild changing one line will fix
this:

24c24
<       >=dev-perl/Mail-IMAPClient-2.1.4"
---
>       =dev-perl/Mail-IMAPClient-2.2.9"

------- Comment #2 From Carsten Lohrke 2008-07-18 23:44:01 0000 -------
Raúl: Why did you mark the Mail-IMAPClient version stable? There's no
stabilization bug, I don't see that we had a second pair of eyes looking, if
stabilization is fine.

------- Comment #3 From Carsten Lohrke 2008-07-18 23:45:05 0000 -------
(In reply to comment #1)
> Note that a revbump of the imapsync-1.255 ebuild changing one line will fix
> this:

No, it doesn't. It's stable tree breakage.

------- Comment #4 From Joe Peterson 2008-07-18 23:47:49 0000 -------
Even if the newer Mail-IMAPClient were *not* marked stable, this would break
those who use the unstable Mail-IMAPClient.  imapsync *mandates* a specific
version, so the ebuild needs to specify that version exactly.

------- Comment #5 From Raúl Porcel 2008-07-19 09:33:12 0000 -------
Reverted to ~arch.

------- Comment #6 From Tobias Scherbaum 2008-07-19 09:39:17 0000 -------
(In reply to comment #3)
> (In reply to comment #1)
> > Note that a revbump of the imapsync-1.255 ebuild changing one line will fix
> > this:
> 
> No, it doesn't. It's stable tree breakage.
> 

revbumped to -r1 with a fixed dep on "=dev-perl/Mail-IMAPClient-2.2.9".

As for the stable b0rkage we would need x86 to mark imapsync-1.255-r1 stable,
cc'ing x86 therefore. 1.255 has been in portage for less than the usual month,
do what you think is appropriate here. Thanks!

------- Comment #7 From Raúl Porcel 2008-07-19 09:48:34 0000 -------
(In reply to comment #6)
> (In reply to comment #3)
> > (In reply to comment #1)
> > > Note that a revbump of the imapsync-1.255 ebuild changing one line will fix
> > > this:
> > 
> > No, it doesn't. It's stable tree breakage.
> > 
> 
> revbumped to -r1 with a fixed dep on "=dev-perl/Mail-IMAPClient-2.2.9".
> 
> As for the stable b0rkage we would need x86 to mark imapsync-1.255-r1 stable,
> cc'ing x86 therefore. 1.255 has been in portage for less than the usual month,
> do what you think is appropriate here. Thanks!
> 

Its not stable anymore :P No need to do anything here for x86

------- Comment #8 From Tobias Scherbaum 2008-07-19 09:52:52 0000 -------
(In reply to comment #7)
> Its not stable anymore :P No need to do anything here for x86

Any objections to close this one then? 

------- Comment #9 From Raúl Porcel 2008-07-19 09:54:22 0000 -------
Nope

First Last Prev Next    No search results available      Search page      Enter new bug