On Tue, Jan 20, 2009 at 01:04, Bastien ROUCARIES
wrote:
> On Mon, Jan 19, 2009 at 10:50 AM, Bastien ROUCARIES
> wrote:
>>ll need I suppose cooperation from BTS itself but in a second
>> time. We need only two user tags by foreign distrib:
>> bts-link-foreign-xref-$distrib set to the foregin bugzi
On Mon, Jan 19, 2009 at 09:46, Stefano Zacchiroli wrote:
> On Mon, Jan 19, 2009 at 09:17:06AM +0100, Raphael Hertzog wrote:
>> Before you decide to push out errors to maintainers via PTS (as I've seen
>> mentionned), you should really improve the tool so that the only remaining
>> errors are reall
Hello Raphael,
On Mon, Jan 19, 2009 at 09:17, Raphael Hertzog wrote:
> On Sat, 17 Jan 2009, Sandro Tosi wrote:
>> In recent bts-link runs, we noticed some errors. The log is available
>> at [2]: please take the time to give it a look, search for your
>> packages and check the situation. There are
On Sun, Jan 18, 2009 at 19:54, Bastien ROUCARIES
wrote:
> On Sat, Jan 17, 2009 at 8:36 PM, Sandro Tosi wrote:
>> Hello,
>
>> If you feel something is missing, should be fixed or enhanced, let
>> us[4] know; of course, patches are welcome ;) (git repo at [5]).
>
> I really useful stuff will be to
On Sun, Jan 18, 2009 at 11:20, Frank Küster wrote:
> "Paul Wise" wrote:
>> Debian TeX Maintainers
>>texlive-bin
>
> One was a typo in the upstream address. The other one,
Thanks for fixing this.
> E: pkg=texlive-bin, bug=351672, msg=Does not deals dupes:
> [http://sourceforge.net/tracker/
On Sun, Jan 18, 2009 at 10:12, Emilio Pozuelo Monfort wrote:
>> E: pkg=update-manager, bug=415376, msg=Parse error:
> [https://bugs.launchpad.net/update-manager/+bug/95168/] No product specified
> but
> bug affects multiple products
>
> That looks wrong to me. The error says "No product specified
On Sun, Jan 18, 2009 at 03:21, Raphael Geissert
wrote:
> Hi,
>
> Sandro Tosi wrote:
> [...}
>> In recent bts-link runs, we noticed some errors. The log is available
>> at [2]: please take the time to give it a look, search for your
>> packages and check the situation. There are errors in that log
On Mon, Jan 19, 2009 at 10:50 AM, Bastien ROUCARIES
wrote:
>ll need I suppose cooperation from BTS itself but in a second
> time. We need only two user tags by foreign distrib:
> bts-link-foreign-xref-$distrib set to the foregin bugzilla entry
> bts-link-foreign-status-$distrib magically set by b
On Mon, Jan 19, 2009 at 10:46 AM, Olivier Berger
wrote:
> Le lundi 19 janvier 2009 à 07:12 +0100, Christian Perrier a écrit :
>> Quoting Bastien ROUCARIES (roucaries.bast...@gmail.com):
>> >
>> > I really useful stuff will be to use user tag in order to crossref
>> > another distrib bugzilla. For
On Mon, Jan 19, 2009 at 10:36 AM, Olivier Berger
wrote:
> Hi.
>
> Le dimanche 18 janvier 2009 à 19:54 +0100, Bastien ROUCARIES a écrit :
>> On Sat, Jan 17, 2009 at 8:36 PM, Sandro Tosi wrote:
>> > Hello,
>>
>> > If you feel something is missing, should be fixed or enhanced, let
>> > us[4] know; o
On Mon, Jan 19, 2009 at 10:40:13AM +0100, Olivier Berger wrote:
> Did you mean "The bts-link is polluted", above ?
No, I did mean the PTS.
I've no idea whether that is true also for bts-link :)
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.juss
On Mon, 2009-01-19 at 10:46 +0100, Olivier Berger wrote:
> There would be some need for inter-distro work here, maybe... any ideas
> on where to discuss that much welcome ;)
distributi...@lists.freedesktop.org would be a good place to start.
http://lists.freedesktop.org/mailman/listinfo/distribut
On Mon, Jan 19, 2009 at 7:46 PM, Stefano Zacchiroli wrote:
> BTW, when that is done, please submit a wishlist bugreport on the PTS
> requesting integration, *together* with a description of the parsing
> rules of the error output of bts-link OR maybe a switch to a format
> which can be parsed out
On Mon, Jan 19, 2009 at 7:12 AM, Christian Perrier wrote:
> Quoting Bastien ROUCARIES (roucaries.bast...@gmail.com):
>> On Sat, Jan 17, 2009 at 8:36 PM, Sandro Tosi wrote:
>> > Hello,
>>
>> > If you feel something is missing, should be fixed or enhanced, let
>> > us[4] know; of course, patches ar
Hi.
Le dimanche 18 janvier 2009 à 19:54 +0100, Bastien ROUCARIES a écrit :
> On Sat, Jan 17, 2009 at 8:36 PM, Sandro Tosi wrote:
> > Hello,
>
> > If you feel something is missing, should be fixed or enhanced, let
> > us[4] know; of course, patches are welcome ;) (git repo at [5]).
>
> I really
Le lundi 19 janvier 2009 à 07:12 +0100, Christian Perrier a écrit :
> Quoting Bastien ROUCARIES (roucaries.bast...@gmail.com):
> >
> > I really useful stuff will be to use user tag in order to crossref
> > another distrib bugzilla. For instance some bug are fixed on redhat
> > like #506180 but not
Le lundi 19 janvier 2009 à 09:46 +0100, Stefano Zacchiroli a écrit :
> The PTS is being polluted by tons of micro-parsers for the output of
> the tools it monitor, a convergence at least on the surface syntaxes
> would be nice to ease future maintenance.
>
Did you mean "The bts-link is polluted"
On Mon, Jan 19, 2009 at 09:17:06AM +0100, Raphael Hertzog wrote:
> Before you decide to push out errors to maintainers via PTS (as I've seen
> mentionned), you should really improve the tool so that the only remaining
> errors are really user errors.
BTW, when that is done, please submit a wishlis
On Sat, 17 Jan 2009, Sandro Tosi wrote:
> In recent bts-link runs, we noticed some errors. The log is available
> at [2]: please take the time to give it a look, search for your
> packages and check the situation. There are errors in that log that
> might be ok, but others can refer to broken links
Quoting Bastien ROUCARIES (roucaries.bast...@gmail.com):
> On Sat, Jan 17, 2009 at 8:36 PM, Sandro Tosi wrote:
> > Hello,
>
> > If you feel something is missing, should be fixed or enhanced, let
> > us[4] know; of course, patches are welcome ;) (git repo at [5]).
>
> I really useful stuff will b
Ben Finney wrote:
[...]
>
> Since the problem is not with the package itself, but with an external
> service, I think this would be better in DEHS.
>
DEHS-provided information is displayed in the PTS as well, as it is up to the
package maintainer(s) or collaborators to "fix" it (either on the De
On Sat, Jan 17, 2009 at 8:36 PM, Sandro Tosi wrote:
> Hello,
> If you feel something is missing, should be fixed or enhanced, let
> us[4] know; of course, patches are welcome ;) (git repo at [5]).
I really useful stuff will be to use user tag in order to crossref
another distrib bugzilla. For in
"Paul Wise" wrote:
> Debian TeX Maintainers
>texlive-bin
One was a typo in the upstream address. The other one,
E: pkg=texlive-bin, bug=351672, msg=Does not deals dupes:
[http://sourceforge.net/tracker/index.php?func=detail&aid=1425283&group_id=23164&atid=377580]
I do not understand. T
Twas brillig at 10:12:26 18.01.2009 UTC+01 when po...@ubuntu.com did gyre and
gimble:
>>mercurial
EPM> Looks like they're not using Trac anymore...
Yes, moved to roundup.
--
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
Paul Wise wrote:
> On Sun, Jan 18, 2009 at 6:36 AM, Sandro Tosi wrote:
>
>> In recent bts-link runs, we noticed some errors. The log is available
>> at [2]: please take the time to give it a look, search for your
>> packages and check the situation. There are errors in that log that
>> might be o
Raphael Geissert writes:
> What about generating a nice report page and making the PTS warn
> when bts-link had troubles handling forwarded bugs of a given
> package.
Good idea.
Since the problem is not with the package itself, but with an external
service, I think this would be better in DEHS.
Hi,
Sandro Tosi wrote:
[...}
> In recent bts-link runs, we noticed some errors. The log is available
> at [2]: please take the time to give it a look, search for your
> packages and check the situation. There are errors in that log that
> might be ok, but others can refer to broken links, no more
On Sun, Jan 18, 2009 at 6:36 AM, Sandro Tosi wrote:
> In recent bts-link runs, we noticed some errors. The log is available
> at [2]: please take the time to give it a look, search for your
> packages and check the situation. There are errors in that log that
> might be ok, but others can refer t
Hello,
as you might have seen (if you use the forwarded BTS feature) we have
a tool, called bts-link[1], that help us track upstream bugs
situation, tagging Debian bugs accordingly.
In recent bts-link runs, we noticed some errors. The log is available
at [2]: please take the time to give it a look
29 matches
Mail list logo
