Re: why was there no bug filed?
hi, On Thu, Dec 05, 2002 at 12:04:21AM +0100, martin f krafft wrote: also sprach Colin Watson [EMAIL PROTECTED] [2002.12.04.1353 +0100]: I'd be extremely surprised if the explanation wasn't something along the lines of we didn't get round to it or something more important came up. Humans, not automatic systems, file bugs. there is not going to be a week when i don't learn something from you, oh my sponsor, advocate, and mentor. i thought that the bugs were automatically filed. wouldn't that be rather easy to accomplish? don't think so. usually the buildd maintainers give further information about the relevant parts of the build log that might have caused the problem. or even provide solutions. I don't think AI is that clever yet ;). so long Othmar
Re: why was there no bug filed?
On Thu, Dec 05, 2002 at 12:04:21AM +0100, martin f krafft wrote: you, oh my sponsor, advocate, and mentor. i thought that the bugs were automatically filed. wouldn't that be rather easy to accomplish? It would be easy to file bugs when builds fail but it would be hard to do this constructively. For example, there are basic things like checking that the bug isn't already filed which would be hard to automate. You need to look at the build log to see why the build failed then look at the BTS to see if the bug is there already. There are also things like known architecture issues like buggy compilers or library builds that aren't really bugs in the packages themselves. -- You grabbed my hand and we fell into it, like a daydream - or a fever.
Re: why was there no bug filed?
also sprach Mark Brown [EMAIL PROTECTED] [2002.12.05.1228 +0100]: It would be easy to file bugs when builds fail but it would be hard to do this constructively. For example, there are basic things like checking that the bug isn't already filed which would be hard to automate. You need to look at the build log to see why the build failed then look at the BTS to see if the bug is there already. There are also things like known architecture issues like buggy compilers or library builds that aren't really bugs in the packages themselves. thanks for the explanation! You grabbed my hand and we fell into it, like a daydream - or a fever. we're trapped in the belly of this horrible machine, and the machine is bleeding to death. s good! -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc pgp9pRoOHVDUm.pgp Description: PGP signature
Re: why was there no bug filed?
On Wed, Dec 04, 2002 at 10:56:44AM +0100, martin f krafft wrote: speaks for itself. i didn't notice in months... http://buildd.debian.org/build.php?arch=armpkg=gradmver=1.5a-1 http://bugs.debian.org/gradm It's easier to notice these things in a timely fashion if you put 'grep-excuses your name' (or just 'grep-excuses' with GREP_EXCUSES_MAINTAINER='your name' in ~/.devscripts) in your crontab. -- Colin Watson [EMAIL PROTECTED]
Re: why was there no bug filed?
also sprach Colin Watson [EMAIL PROTECTED] [2002.12.04.1319 +0100]: It's easier to notice these things in a timely fashion if you put 'grep-excuses your name' (or just 'grep-excuses' with GREP_EXCUSES_MAINTAINER='your name' in ~/.devscripts) in your crontab. nice! still doesn't explain why the bug wasn't reported, does it? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc pgpm8xeoPaAIV.pgp Description: PGP signature
Re: why was there no bug filed?
On Wed, Dec 04, 2002 at 01:34:07PM +0100, martin f krafft wrote: also sprach Colin Watson [EMAIL PROTECTED] [2002.12.04.1319 +0100]: It's easier to notice these things in a timely fashion if you put 'grep-excuses your name' (or just 'grep-excuses' with GREP_EXCUSES_MAINTAINER='your name' in ~/.devscripts) in your crontab. nice! still doesn't explain why the bug wasn't reported, does it? I'd be extremely surprised if the explanation wasn't something along the lines of we didn't get round to it or something more important came up. Humans, not automatic systems, file bugs. -- Colin Watson [EMAIL PROTECTED]
Re: why was there no bug filed?
hi, On Wed, Dec 04, 2002 at 01:34:07PM +0100, martin f krafft wrote: also sprach Colin Watson [EMAIL PROTECTED] [2002.12.04.1319 +0100]: It's easier to notice these things in a timely fashion if you put 'grep-excuses your name' (or just 'grep-excuses' with GREP_EXCUSES_MAINTAINER='your name' in ~/.devscripts) in your crontab. nice! still doesn't explain why the bug wasn't reported, does it? simple answer (colin watson summarized it also quite well): the logfiles are handled by humans. so, take care about the status of your packages yourself or be patient :). ideally you should probably take care of them anyway. at least I look at the build logs of my newly uploaded packages. and in any case, it wouldn't harm. so long Othmar
Re: why was there no bug filed?
also sprach Colin Watson [EMAIL PROTECTED] [2002.12.04.1353 +0100]: I'd be extremely surprised if the explanation wasn't something along the lines of we didn't get round to it or something more important came up. Humans, not automatic systems, file bugs. there is not going to be a week when i don't learn something from you, oh my sponsor, advocate, and mentor. i thought that the bugs were automatically filed. wouldn't that be rather easy to accomplish? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc pgpKizQRaqi14.pgp Description: PGP signature
