Hello,
I'm seeking a sponsor for a package I'm maintaining: qdu. Please refer to
bug #250280:
http://bugs.debian.org/250280
I have been working with the upstream author and have a first version of
the package uploaded to mentors.debian.net. For more information on
qdu, please see the upstream
Hello,
I'm seeking a sponsor for a package I'm maintaining: qdu. Please refer to
bug #250280:
http://bugs.debian.org/250280
I have been working with the upstream author and have a first version of
the package uploaded to mentors.debian.net. For more information on
qdu, please see the upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sunday 30 May 2004 23:06, Martin Michlmayr wrote:
> * Tobias Toedter <[EMAIL PROTECTED]> [2004-05-30 21:37]:
> > I'm not quite sure what to do now, because the stable release of
> > course still contains the package. Should I close all remainin
* Tobias Toedter <[EMAIL PROTECTED]> [2004-05-30 21:37]:
> I'm not quite sure what to do now, because the stable release of
> course still contains the package. Should I close all remaining bugs
> nevertheless, sending an explanation to the submitters? Or should I
> wait until the next stable relea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
recently, I filed a bug against ftp.d.o and asked for the removal of the
package onshore-timesheet. That program is dead upstream, the Debian
package has been orphaned and removed from testing, and it has several open
bugs (including one RC).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sunday 30 May 2004 23:06, Martin Michlmayr wrote:
> * Tobias Toedter <[EMAIL PROTECTED]> [2004-05-30 21:37]:
> > I'm not quite sure what to do now, because the stable release of
> > course still contains the package. Should I close all remainin
* Tobias Toedter <[EMAIL PROTECTED]> [2004-05-30 21:37]:
> I'm not quite sure what to do now, because the stable release of
> course still contains the package. Should I close all remaining bugs
> nevertheless, sending an explanation to the submitters? Or should I
> wait until the next stable relea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
recently, I filed a bug against ftp.d.o and asked for the removal of the
package onshore-timesheet. That program is dead upstream, the Debian
package has been orphaned and removed from testing, and it has several open
bugs (including one RC).
In een door u verzonden emailbericht is een VIRUS gevonden. Het VIRUS is door
ons verwijderd. Afhankelijk van het soort VIRUS is het mogelijk dat de
geadresseerde het bericht niet of onvolledig heeft ontvangen. Wij adviseren u
om uw
computer(s) te controleren op VIRUSSEN mbv een actuele virussc
In een door u verzonden emailbericht is een VIRUS gevonden. Het VIRUS is door
ons verwijderd. Afhankelijk van het soort VIRUS is het mogelijk dat de
geadresseerde het bericht niet of onvolledig heeft ontvangen. Wij adviseren u om uw
computer(s) te controleren op VIRUSSEN mbv een actuele virussca
Andreas Metzler <[EMAIL PROTECTED]> writes:
> On 2004-05-30 Mike Williams <[EMAIL PROTECTED]> wrote:
>> One of my packages (librmagick-ruby) recently stopped working (details left
>> intentionally vague). I believe this was due to a change in one of the
>> libraries it depends on.
>
>> In any cas
* Mike Williams [Sun, 30 May 2004 20:19:30 +1000]:
> One of my packages (librmagick-ruby) recently stopped working (details left
> intentionally vague). I believe this was due to a change in one of the
> libraries it depends on.
> In any case, rebuilding against an updated sid install got it work
On 2004-05-30 Mike Williams <[EMAIL PROTECTED]> wrote:
> One of my packages (librmagick-ruby) recently stopped working (details left
> intentionally vague). I believe this was due to a change in one of the
> libraries it depends on.
> In any case, rebuilding against an updated sid install got it
Mike Williams wrote:
One of my packages (librmagick-ruby) recently stopped working (details left
intentionally vague). I believe this was due to a change in one of the
libraries it depends on.
In any case, rebuilding against an updated sid install got it working
again, without any source change
One of my packages (librmagick-ruby) recently stopped working (details left
intentionally vague). I believe this was due to a change in one of the
libraries it depends on.
In any case, rebuilding against an updated sid install got it working
again, without any source changes required. In other w
Andreas Metzler <[EMAIL PROTECTED]> writes:
> On 2004-05-30 Mike Williams <[EMAIL PROTECTED]> wrote:
>> One of my packages (librmagick-ruby) recently stopped working (details left
>> intentionally vague). I believe this was due to a change in one of the
>> libraries it depends on.
>
>> In any cas
* Mike Williams [Sun, 30 May 2004 20:19:30 +1000]:
> One of my packages (librmagick-ruby) recently stopped working (details left
> intentionally vague). I believe this was due to a change in one of the
> libraries it depends on.
> In any case, rebuilding against an updated sid install got it work
On 2004-05-30 Mike Williams <[EMAIL PROTECTED]> wrote:
> One of my packages (librmagick-ruby) recently stopped working (details left
> intentionally vague). I believe this was due to a change in one of the
> libraries it depends on.
> In any case, rebuilding against an updated sid install got it
Mike Williams wrote:
One of my packages (librmagick-ruby) recently stopped working (details left
intentionally vague). I believe this was due to a change in one of the
libraries it depends on.
In any case, rebuilding against an updated sid install got it working
again, without any source changes r
One of my packages (librmagick-ruby) recently stopped working (details left
intentionally vague). I believe this was due to a change in one of the
libraries it depends on.
In any case, rebuilding against an updated sid install got it working
again, without any source changes required. In other w
20 matches
Mail list logo
