Bug#1056321: elogind conflicts with same version libelogind

2023-11-23 Thread Low Salt Popcorn
Wouldn't it be better, or at least more elegant, to turn libelogind0 into a dummy transitional package that pulls in libsystemd0? Here's the result of trying to install elogind using the apt front end. $ sudo apt install -t testing elogind Reading package lists... Building dependency tree... Read

Bug#338457: samba: segfault after upgrade

2005-12-06 Thread Popcorn
On 12/6/05, Steve Langasek <[EMAIL PROTECTED]> wrote: clone 338457 -1unmerge -1submitter -1 Popcorn <[EMAIL PROTECTED]>retitle -1 samba: segfault after upgradereassign -1 samba 3.0.20b-2+b1thanks Unfortunately, the backtraces made with samba-dbg installed point to a stackcorruption pro

Bug#338457: samba: segfault after upgrade

2005-12-01 Thread Popcorn
t;[EMAIL PROTECTED]> wrote: Quoting Popcorn ([EMAIL PROTECTED]):> So tell me more about this samba-dbg package. And after I install it, what do I> need to do anything with it in order to give you a backtrace that can be used? Nothing special.> How do I know that a backtrace is usable?  

Bug#338457: samba: segfault after upgrade

2005-11-30 Thread Popcorn
this information any where else.  I have been able to reproduce this error, or one similar to it, and I am pretty sure I can continue to reproduce it. Thanks  LanceOn 11/29/05, Steve Langasek <[EMAIL PROTECTED]> wrote: On Tue, Nov 29, 2005 at 12:48:52AM +0100, Popcorn wrote:> I was unabl

Bug#338457: samba: segfault after upgrade

2005-11-28 Thread Popcorn
wrote:> Quoting Popcorn ([EMAIL PROTECTED]):> > yes, yes I do think its a bit scarce.  I seem to have "missused" the reportbug > > tool.  Is this a bit better? As you may have guessed this is my first bug> > report.  I hope it is more helpful this time.  if you need any ot

Bug#338457: samba: segfault after upgrade

2005-11-27 Thread Popcorn
I will try to reproduce this tomorrow.  On 11/27/05, Christian Perrier <[EMAIL PROTECTED]> wrote: Quoting Popcorn ([EMAIL PROTECTED]):> yes, yes I do think its a bit scarce.  I seem to have "missused" the reportbug > tool.  Is this a bit better? As you may have guessed this i