[Bug 252001] Re: dselect: failed to create baselist pad

2011-05-24 Thread Launchpad Bug Tracker
[Expired for dpkg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dpkg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/252001 Titl

[Bug 252001] Re: dselect: failed to create baselist pad

2011-03-25 Thread Raphaƫl Hertzog
Can anyone verify if you still have the problem with a recent version like the one in maverick or natty? If yes, please switch the status back to confirmed. ** Changed in: dpkg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubun

[Bug 252001] Re: dselect: failed to create baselist pad

2009-08-17 Thread Louis-Dominique Dubeau
As of 2009-08-17, the problem is present in a fully updated Jaunty. Chris's workaround works for me. -- dselect: failed to create baselist pad https://bugs.launchpad.net/bugs/252001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ub

[Bug 252001] Re: dselect: failed to create baselist pad

2009-02-24 Thread Chris Cheney
I commented out this line: deb http://ddebs.ubuntu.com jaunty main restricted universe multiverse and the problem went away. I don't know if the ddebs repo Packages list is faulty in some way or if it just uncovered the issue. -- dselect: failed to create baselist pad https://bugs.launchpad.net

[Bug 252001] Re: dselect: failed to create baselist pad

2009-02-24 Thread Chris Cheney
I just started having this problem myself in Jaunty. I have used dselect nearly every day since mid 1998 without problem until I started seeing this issue. ** Changed in: dpkg (Ubuntu) Status: New => Confirmed -- dselect: failed to create baselist pad https://bugs.launchpad.net/bugs/25200

[Bug 252001] Re: dselect: failed to create baselist pad

2008-07-31 Thread Megatux
I have the same problem. I'm guessing it has to do with how large the package lists are today.. It appears that this bug is related to recent fixes upstream, but the patch listed below did not help and I haven't had time to pull the latest upstream and build a new package from scratch... http://w