Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-13 Thread Modestas Vainius
Hello, On sekmadienis 12 Gruodis 2010 23:32:39 Roger Leigh wrote: I can implement the URItoFileName function directly in Perl, or find some way to access the function directly from Perl. If you could check if we can get away without these special filenames, that would be very

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-12 Thread Roger Leigh
On Thu, Dec 09, 2010 at 12:29:12AM +0200, Modestas Vainius wrote: Hello, On ketvirtadienis 09 Gruodis 2010 00:06:52 Roger Leigh wrote: On trečiadienis 08 Gruodis 2010 22:37:56 Roger Leigh wrote: Certainly for the apt and aptitude resolvers; for the internal resolver, it's still

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-08 Thread Roger Leigh
tags 606278 + patch fixed-upstream thanks On Wed, Dec 08, 2010 at 10:28:55AM +, Roger Leigh wrote: On Wed, Dec 08, 2010 at 03:08:09AM +0200, Modestas Vainius wrote: Hello, On trečiadienis 08 Gruodis 2010 02:47:14 Modestas Vainius wrote: I guess now it wants a key. I spotted

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-08 Thread Roger Leigh
On Wed, Dec 08, 2010 at 10:28:55AM +, Roger Leigh wrote: On Wed, Dec 08, 2010 at 03:08:09AM +0200, Modestas Vainius wrote: Hello, On trečiadienis 08 Gruodis 2010 02:47:14 Modestas Vainius wrote: I guess now it wants a key. I spotted `sbuild-update --keygen` in the changelog and

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-08 Thread Modestas Vainius
Hello, On trečiadienis 08 Gruodis 2010 13:06:23 Roger Leigh wrote: Ok, the latter is because you removed a key option (that I added some time ago) from aptitude command line in 80f811184d7c7b06a6a5ec8d646b1eac015dffa2. That's: '-o',

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-08 Thread Roger Leigh
On Wed, Dec 08, 2010 at 09:19:44PM +0200, Modestas Vainius wrote: On trečiadienis 08 Gruodis 2010 13:06:23 Roger Leigh wrote: Ok, the latter is because you removed a key option (that I added some time ago) from aptitude command line in 80f811184d7c7b06a6a5ec8d646b1eac015dffa2. That's:

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-08 Thread Modestas Vainius
Hello, On trečiadienis 08 Gruodis 2010 22:37:56 Roger Leigh wrote: Certainly for the apt and aptitude resolvers; for the internal resolver, it's still useful. Is it possible to request an update of specific archive components, so that we don't need to do a complete fetch of everything?

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-08 Thread Roger Leigh
On Wed, Dec 08, 2010 at 11:48:37PM +0200, Modestas Vainius wrote: Hello, On trečiadienis 08 Gruodis 2010 22:37:56 Roger Leigh wrote: Certainly for the apt and aptitude resolvers; for the internal resolver, it's still useful. Is it possible to request an update of specific archive

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-08 Thread Modestas Vainius
Hello, On ketvirtadienis 09 Gruodis 2010 00:06:52 Roger Leigh wrote: On trečiadienis 08 Gruodis 2010 22:37:56 Roger Leigh wrote: Certainly for the apt and aptitude resolvers; for the internal resolver, it's still useful. Is it possible to request an update of specific archive

Bug#606278: [buildd-tools-devel] Bug#606278: Bug#606278: aptitude resolver is completely broken in 0.60.6

2010-12-07 Thread Roger Leigh
On Tue, Dec 07, 2010 at 11:58:13PM +, Roger Leigh wrote: On Wed, Dec 08, 2010 at 01:38:26AM +0200, Modestas Vainius wrote: aptitude resolver no longer works in 0.60.6. I suppose it has become pretty important because it's the only which supports experimental properly. See sample build