Bug#790422: Parsing.Parse_error

2016-01-23 Thread Christoph Berg
Re: Mehdi Dogguy 2016-01-21 <696fb80d6c0023c5e54ecfb56e670...@dogguy.org> > Updated patch, without the changes in "applications/distcheck.ml". Hi Mehdi, thanks for your efforts. I'm afraid backporting extlib isn't trivial: dose3 -> librpm-dev (>= 4.12) already in jessie-backports -> ocamlgra

Bug#790422: Parsing.Parse_error

2016-01-21 Thread Mehdi Dogguy
On 2016-01-20 01:14, Mehdi Dogguy wrote: Hi, On 19/01/2016 23:07, Christoph Berg wrote: Long story, but that's the real-world example here. In fact I'm considering upgrading the apt.pg.o build host to stretch just because of this bugfix, and because a backport of the current dose-debcheck vers

Bug#790422: Parsing.Parse_error

2016-01-19 Thread Mehdi Dogguy
Hi, On 19/01/2016 23:07, Christoph Berg wrote: > > Long story, but that's the real-world example here. In fact I'm > considering upgrading the apt.pg.o build host to stretch just because > of this bugfix, and because a backport of the current dose-debcheck > version to jessie looks too hard. >

Bug#790422: Parsing.Parse_error

2016-01-19 Thread Christoph Berg
Re: Johannes Schauer 2015-07-01 <20150701114957.2789.95115@hoothoot> > Hi, > > Quoting Ralf Treinen (2015-06-30 19:22:43) > > On Mon, Jun 29, 2015 at 03:29:51PM +0200, Johannes Schauer wrote: > > > > > As for the second problem (the empty Packages file) I was annoyed by this > > > myself for a lo

Bug#790422: Parsing.Parse_error

2015-07-01 Thread Johannes Schauer
Hi, Quoting Ralf Treinen (2015-06-30 19:22:43) > On Mon, Jun 29, 2015 at 03:29:51PM +0200, Johannes Schauer wrote: > > > As for the second problem (the empty Packages file) I was annoyed by this > > myself for a long time and would like to get to know a use case where an > > empty input file woul

Bug#790422: Parsing.Parse_error

2015-06-30 Thread Ralf Treinen
Hi guys, On Mon, Jun 29, 2015 at 03:29:51PM +0200, Johannes Schauer wrote: > As for the second problem (the empty Packages file) I was annoyed by this > myself for a long time and would like to get to know a use case where an empty > input file would make sense. Currently I'm working around this

Bug#790422: Parsing.Parse_error

2015-06-29 Thread Johannes Schauer
Hi, Quoting Joachim Breitner (2015-06-29 15:54:29) > Am Montag, den 29.06.2015, 15:29 +0200 schrieb Johannes Schauer: > > Firstly, there are two syntax errors in your Sources file. They are > > "libghc-data-default-dev (<< = 0.6)" and "libghc-shakespeare-dev (<< > > = 2.1)". > > Observe how the v

Bug#790422: Parsing.Parse_error

2015-06-29 Thread Joachim Breitner
Control: retitle -1 Parsing.Parse_error - improve error message Control: severity -1 wishlist Hi, Am Montag, den 29.06.2015, 15:29 +0200 schrieb Johannes Schauer: > Firstly, there are two syntax errors in your Sources file. They are > "libghc-data-default-dev (<< = 0.6)" and "libghc-shakespeare-d

Bug#790422: Parsing.Parse_error

2015-06-29 Thread Johannes Schauer
Hi, Quoting Joachim Breitner (2015-06-29 14:17:45) > with the attached file and an empty Packages files , I get $ > dose-builddebcheck --latest --explain --failures --deb-native-arch=amd64 > Packages Sources The applications raised this exception : Parsing.Parse_error > > > I cannot see a mistak

Bug#790422: Parsing.Parse_error

2015-06-29 Thread Joachim Breitner
Package: dose-builddebcheck Version: 3.3-4 Severity: normal File: /usr/bin/dose-builddebcheck -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, with the attached file and an empty Packages files , I get $ dose-builddebcheck --latest --explain --failures --deb-native-arch=amd64 Packages Sources