FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 08-30-2011, 11:43 AM
Stephen Gallagher
 
Default Proventester karma needed for libtalloc-2.0.6-1.fc15

https://admin.fedoraproject.org/updates/libtalloc-2.0.6-1.fc15

This CRITPATH package has been in update-testing for 20 days without any
karma. The same package went to stable in F16 a week ago with karma
automatism.

If you use Samba, SSSD, openchange, certmonger, evolution-mapi or
notmuch, please verify that these programs are not experiencing
unexpected behaviors. Libtalloc is the memory allocator used for each of
these applications, so bugs in libtalloc would result in highly-visible
new bugs in the consumers.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 08-30-2011, 05:31 PM
Peter Robinson
 
Default Proventester karma needed for libtalloc-2.0.6-1.fc15

On Tue, Aug 30, 2011 at 12:43 PM, Stephen Gallagher <sgallagh@redhat.com> wrote:
> https://admin.fedoraproject.org/updates/libtalloc-2.0.6-1.fc15
>
> This CRITPATH package has been in update-testing for 20 days without any
> karma. The same package went to stable in F16 a week ago with karma
> automatism.
>
> If you use Samba, SSSD, openchange, certmonger, evolution-mapi or
> notmuch, please verify that these programs are not experiencing
> unexpected behaviors. Libtalloc is the memory allocator used for each of
> these applications, so bugs in libtalloc would result in highly-visible
> new bugs in the consumers.

It seems it has issues with samba4 updates, and hence is causing
issues with openchange/evolution-mapi.

[peter@localhost ~]$ sudo yum upgrade *talloc*
Loaded plugins: refresh-packagekit
Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
---> Package libtalloc.x86_64 0:2.0.5-8.fc15 will be updated
---> Package libtalloc.x86_64 0:2.0.6-1.fc16 will be an update
---> Package libtalloc-devel.x86_64 0:2.0.5-8.fc15 will be updated
---> Package libtalloc-devel.x86_64 0:2.0.6-1.fc16 will be an update
---> Package pytalloc.x86_64 0:2.0.5-8.fc15 will be updated
--> Processing Dependency:
libpytalloc-util.so.2(PYTALLOC_UTIL_2.0.5)(64bit) for package:
samba4-libs-4.0.0-34.alpha15GITa6a722b.fc16.1.x86_64
---> Package pytalloc.x86_64 0:2.0.6-1.fc16 will be an update
--> Running transaction check
---> Package samba4-libs.x86_64 0:4.0.0-34.alpha15GITa6a722b.fc16.1
will be updated
--> Processing Dependency: libsamba-util-common.so()(64bit) for
package: openchange-0.10.9-4.fc16.x86_64
--> Processing Dependency:
libsamba-util-common.so(SAMBA_4.0.0ALPHA15_UNKNOWN)(64bit) for
package: openchange-0.10.9-4.fc16.x86_64
---> Package samba4-libs.x86_64 0:4.0.0-36.alpha16.fc16.1 will be an update
--> Processing Dependency: libpyldb-util.so.1()(64bit) for package:
samba4-libs-4.0.0-36.alpha16.fc16.1.x86_64
--> Running transaction check
---> Package pyldb.x86_64 0:1.1.0-1.fc16 will be installed
--> Processing Dependency: python-tdb = 1.2.9 for package:
pyldb-1.1.0-1.fc16.x86_64
---> Package samba4-libs.x86_64 0:4.0.0-34.alpha15GITa6a722b.fc16.1
will be updated
--> Processing Dependency: libsamba-util-common.so()(64bit) for
package: openchange-0.10.9-4.fc16.x86_64
--> Processing Dependency:
libsamba-util-common.so(SAMBA_4.0.0ALPHA15_UNKNOWN)(64bit) for
package: openchange-0.10.9-4.fc16.x86_64
--> Running transaction check
---> Package python-tdb.x86_64 0:1.2.9-10.fc16 will be installed
---> Package samba4-libs.x86_64 0:4.0.0-34.alpha15GITa6a722b.fc16.1
will be updated
--> Processing Dependency: libsamba-util-common.so()(64bit) for
package: openchange-0.10.9-4.fc16.x86_64
--> Processing Dependency:
libsamba-util-common.so(SAMBA_4.0.0ALPHA15_UNKNOWN)(64bit) for
package: openchange-0.10.9-4.fc16.x86_64
--> Finished Dependency Resolution
Error: Package: openchange-0.10.9-4.fc16.x86_64 (@rawhide/15)
Requires: libsamba-util-common.so()(64bit)
Removing:
samba4-libs-4.0.0-34.alpha15GITa6a722b.fc16.1.x86_64 (@rawhide)
libsamba-util-common.so()(64bit)
Updated By: samba4-libs-4.0.0-36.alpha16.fc16.1.x86_64
(updates-testing)
Not found
Error: Package: openchange-0.10.9-4.fc16.x86_64 (@rawhide/15)
Requires: libsamba-util-common.so(SAMBA_4.0.0ALPHA15_UNKNOWN)(64bit)
Removing:
samba4-libs-4.0.0-34.alpha15GITa6a722b.fc16.1.x86_64 (@rawhide)
libsamba-util-common.so(SAMBA_4.0.0ALPHA15_UNKNOWN)(64bit)
Updated By: samba4-libs-4.0.0-36.alpha16.fc16.1.x86_64
(updates-testing)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 08-30-2011, 05:51 PM
Stephen Gallagher
 
Default Proventester karma needed for libtalloc-2.0.6-1.fc15

On Tue, 2011-08-30 at 18:31 +0100, Peter Robinson wrote:
> On Tue, Aug 30, 2011 at 12:43 PM, Stephen Gallagher
> <sgallagh@redhat.com> wrote:
> > https://admin.fedoraproject.org/updates/libtalloc-2.0.6-1.fc15
> >
> > This CRITPATH package has been in update-testing for 20 days without
> any
> > karma. The same package went to stable in F16 a week ago with karma
> > automatism.
> >
> > If you use Samba, SSSD, openchange, certmonger, evolution-mapi or
> > notmuch, please verify that these programs are not experiencing
> > unexpected behaviors. Libtalloc is the memory allocator used for
> each of
> > these applications, so bugs in libtalloc would result in
> highly-visible
> > new bugs in the consumers.
>
> It seems it has issues with samba4 updates, and hence is causing
> issues with openchange/evolution-mapi.


Yeah, I realized that when I rebuild samba4 yesterday I didn't have the
new libtalloc in the buildroot. This will be fixed with
samba4-4.0.0-25.alpha11.fc15.5
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 08-30-2011, 07:20 PM
Adam Williamson
 
Default Proventester karma needed for libtalloc-2.0.6-1.fc15

On Tue, 2011-08-30 at 07:43 -0400, Stephen Gallagher wrote:
> https://admin.fedoraproject.org/updates/libtalloc-2.0.6-1.fc15
>
> This CRITPATH package has been in update-testing for 20 days without any
> karma. The same package went to stable in F16 a week ago with karma
> automatism.
>
> If you use Samba, SSSD, openchange, certmonger, evolution-mapi or
> notmuch, please verify that these programs are not experiencing
> unexpected behaviors. Libtalloc is the memory allocator used for each of
> these applications, so bugs in libtalloc would result in highly-visible
> new bugs in the consumers.

Is a simple CIFS mount exercising libtalloc? I wasn't sure about that,
so I didn't file any karma yet. I have a CIFS share from my NAS box
mounted on my F16 system and that's working fine, but I wasn't sure if
that's enough of a use case to +1 the update.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 08-30-2011, 07:41 PM
Stephen Gallagher
 
Default Proventester karma needed for libtalloc-2.0.6-1.fc15

On Tue, 2011-08-30 at 12:20 -0700, Adam Williamson wrote:
> On Tue, 2011-08-30 at 07:43 -0400, Stephen Gallagher wrote:
> > https://admin.fedoraproject.org/updates/libtalloc-2.0.6-1.fc15
> >
> > This CRITPATH package has been in update-testing for 20 days without any
> > karma. The same package went to stable in F16 a week ago with karma
> > automatism.
> >
> > If you use Samba, SSSD, openchange, certmonger, evolution-mapi or
> > notmuch, please verify that these programs are not experiencing
> > unexpected behaviors. Libtalloc is the memory allocator used for each of
> > these applications, so bugs in libtalloc would result in highly-visible
> > new bugs in the consumers.
>
> Is a simple CIFS mount exercising libtalloc? I wasn't sure about that,
> so I didn't file any karma yet. I have a CIFS share from my NAS box
> mounted on my F16 system and that's working fine, but I wasn't sure if
> that's enough of a use case to +1 the update.

Yes, everything in Samba uses talloc for memory allocation.


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 03:40 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org