I have a dilemma.
I need to orphan a package that's specific to the ARM architecture,
because my Netwinder broke down (We had some severe power spikes about
a month ago, which killed it). I no longer have an ARM build machine.
The Debian Developer's Reference says to change the maintainer to
"D
I have a dilemma.
I need to orphan a package that's specific to the ARM architecture,
because my Netwinder broke down (We had some severe power spikes about
a month ago, which killed it). I no longer have an ARM build machine.
The Debian Developer's Reference says to change the maintainer to
"
Good Folk,
About four months ago, I created meself a brand spanking new GnuPG
key, to supplement/replace my old PGP key in the Debian Keyring. I
dutifully signed the new key with my old one, and sumbitted it to
[EMAIL PROTECTED]
Four months, three tries, and twelve other signatures later (I
att
Good Folk,
About four months ago, I created meself a brand spanking new GnuPG
key, to supplement/replace my old PGP key in the Debian Keyring. I
dutifully signed the new key with my old one, and sumbitted it to
[EMAIL PROTECTED]
Four months, three tries, and twelve other signatures later (I
at
> "LaMont" == LaMont Jones <[EMAIL PROTECTED]> writes:
LaMont> I have a package (Postfix) that wants to behave
LaMont> differently if NIS is installed (more to the point, if
LaMont> there is an NIS alias map). Since I've managed to remain
LaMont> almost completely clueless on
> "Mike" == Mike Goldman <[EMAIL PROTECTED]> writes:
Mike> I have a package (oo2c, an optimizing Oberon-2 compiler)
Mike> which is presently released for i386. A bug-report was
Mike> filed against it, that it did not build on Alpha [...]
Mike> Assuming that I can manage to cr
Two questions, both related to an upload of 'libcompface' for ARM.
- I have built some packages for the ARM architecture, and usually
they are installed the day after I have uploaded them to master.
One particular package has not been installed after 2-3 days.
(libcompface).
I re-d
7 matches
Mail list logo