Hi.
So, you closed the bug report, with a remark (if I understood correctly)
that I should know better.
A link to where the info lies would have been more helpful.
Anyway, I found some of it:
Automatic build of lilypond_2.6.3-9 on athlon by sbuild/amd64 1.170.5
Build started at 20051026-0334
Gilles [EMAIL PROTECTED] writes:
So, you closed the bug report, with a remark (if I understood correctly)
that I should know better.
Yes, that's correct. Users of Debian unstable are expected to
understand that packages are often not installable as soon as they hit
the archive, most
Hi.
So, you closed the bug report, with a remark (if I understood correctly)
that I should know better.
Yes, that's correct. Users of Debian unstable are expected to
understand that packages are often not installable as soon as they hit
the archive, most frequently because of just
Gilles [EMAIL PROTECTED] writes:
Well, I did think of this possibility, that's why I didn't raise the issue
before several days. As I imagined that the build would be attempted every
day, and although the subversion was modified during these last days, I
couldn't understand why the mismatch
4 matches
Mail list logo
