On Mon, 2009-02-02 at 09:33 +0100, Uwe Kubosch wrote:
On Mon, 2009-02-02 at 07:11 +0100, Jeroen van Meeuwen wrote:
I've taken over the ruby package, which basically is the first
core-component piece of software on my relatively small list of packages.
Attached is a patch that was in ruby-1.8.6, and that I rebased to
ruby-1.8.7. Since it's a really simple patch, I wonder why it's not
upstream.
Please do not move the Ruby 1.8 package to 1.8.7. The consensus in the
Ruby community is that 1.8.7 introduces unnecessary incompatibilities
without really adding value. 1.8.7 is meant as a transitional package
to Ruby 1.9, but the majority of Ruby users will want to keep using Ruby
1.8.6 until they switch directly to Ruby 1.9.1. You should focus on
maintaining Ruby 1.8.6 and Ruby 1.9.1 in parallel. Ruby 1.8.7 should be
passed over unless there is a very clear demand from Fedora users to
introduce it.
...
I had something witty-yet-acerbic to respond with, but I think my
presence alone in this thread may be enough :P
Geh...
http://kanarip.livejournal.com/9911.html
Kind regards,
Jeroen van Meeuwen
-kanarip
--
Fedora-packaging mailing list
Fedora-packaging@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-packaging
02-03-2009, 04:14 PM
Jeroen van Meeuwen
Stupid question
Jeffrey Ollie wrote:
On Mon, Feb 2, 2009 at 12:11 AM, Jeroen van Meeuwen <kanarip@kanarip.com> wrote:
I've taken over the ruby package, which basically is the first
core-component piece of software on my relatively small list of packages.
Attached is a patch that was in ruby-1.8.6, and that I rebased to
ruby-1.8.7. Since it's a really simple patch, I wonder why it's not
upstream.
I'm not sure what this fixes, in that ruby will build without the patch as
well. I've searched through the logs to see if there's some kind of warning
related to socket.c, but there is none from what I can tell.
I'd love to learn what this patch does and then try and get upstream to
accept it (so that I have less work to do). Can someone on this list help me
with this?
For a while back in February of '08 was some breakage in glibc where
NI_MAXHOST wasn't defined anymore (at least not under the usual
circumstances that Fedora programs are/were compiled), thus breaking
the build of many different packages, Ruby included. From the looks
of that patch the Ruby developers anticipated NI_MAXHOST being
undefined, but flubbed the fixup. Certainly seems like the patch
should be upstream to me...
Thanks!
It turns out it is upstream already, just not in 1.8.7-p72. I feel
confident to ship the patch now ;-)
Kind regards,
Jeroen van Meeuwen
-kanarip
--
Fedora-packaging mailing list
Fedora-packaging@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-packaging
05-13-2010, 06:37 AM
steef
stupid question
hi list,
how do i get rid of the message of a new (of course much valued)
maintainer Christian about MTA'S and cron when updating squeeze on the
commandline before using startx? apt-get upgrade hangs on this message
and i do not know the protocol to go on in this situation (if there is
any). so i cannot upgrade.
thank you in advance!
steef
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
how do i get rid of the message of a new (of course much valued)
maintainer Christian about MTA'S and cron when updating squeeze on the
commandline before using startx? apt-get upgrade hangs on this message
and i do not know the protocol to go on in this situation (if there is
any). so i cannot upgrade.
thank you in advance!
steef
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
how do i get rid of the message of a new (of course much valued)
maintainer Christian about MTA'S and cron when updating squeeze on the
commandline before using startx? apt-get upgrade hangs on this message
and i do not know the protocol to go on in this situation (if there is
any). so i cannot upgrade.
thank you in advance!
Is it a changelog message? If it's a dialog, just dismiss it. If X is
running, use the mouse. If not, the keyboard.
Tell us more. When and where does the message appear?
MAA
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
On Thu,13.May.10, 08:37:31, steef wrote:
>
> hi list,
>
> how do i get rid of the message of a new (of course much valued)
> maintainer Christian about MTA'S and cron when updating squeeze on
> the commandline before using startx? apt-get upgrade hangs on this
> message and i do not know the protocol to go on in this situation
> (if there is any). so i cannot upgrade.
Sorry steef, but I have no idea what you are talking about. Can you
please post the message? Might be a good idea to prepend
LANG=C
to your command to get it in English.
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
05-13-2010, 10:20 AM
godo
stupid question
On 05/13/2010 08:37 AM, steef wrote:
hi list,
how do i get rid of the message of a new (of course much valued)
maintainer Christian about MTA'S and cron when updating squeeze on the
commandline before using startx? apt-get upgrade hangs on this message
and i do not know the protocol to go on in this situation (if there is
any). so i cannot upgrade.
thank you in advance!
steef
Hi,
I'm think by pressing "Q".
--
Bye,
Goran Dobosevic
Hrvatski: www.dobosevic.com
English: www.dobosevic.com/en/
Registered Linux User #503414
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
how do i get rid of the message of a new (of course much valued)
maintainer Christian about MTA'S and cron when updating squeeze on the
commandline before using startx? apt-get upgrade hangs on this message
and i do not know the protocol to go on in this situation (if there is
any). so i cannot upgrade.
thank you in advance!
steef
Hi,
I'm think by pressing "Q".
thank you all for your answers. i should have known after all those
years that 'q' = quit was the solution. sorry for my noise. mea culpa,
mea maxima culpa,
steef
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Stupid question
