Hi, I have an issue whereby I can't do a sudo dnf upgrade to upgrade the versions of Mysql from Oracle's Mysql repository because one of the other repositories has a package upgrade that won't be applied because it has a dependency on a gdm version that as yet doesn't exist, and, dnf appears to not have support for yum's --skip-broken parameter. Does dnf have support for this functionality so that sudo dnf upgrade will upgrade the packages I want to and ignore the packages with dependency issues?
regards, Steve
Hi
On Sat, Jun 28, 2014 at 11:39 PM, Stephen Morris wrote:
Hi, I have an issue whereby I can't do a sudo dnf upgrade to upgrade the versions of Mysql from Oracle's Mysql repository because one of the other repositories has a package upgrade that won't be applied because it has a dependency on a gdm version that as yet doesn't exist, and, dnf appears to not have support for yum's --skip-broken parameter. Does dnf have support for this functionality so that sudo dnf upgrade will upgrade the packages I want to and ignore the packages with dependency issues?
https://akozumpl.github.io/dnf/cli_vs_yum.html#no-skip-broken
Rahul
On 06/30/2014 11:00 AM, Rahul Sundaram wrote:
Hi
On Sat, Jun 28, 2014 at 11:39 PM, Stephen Morris wrote:
Hi, I have an issue whereby I can't do a sudo dnf upgrade to upgrade the versions of Mysql from Oracle's Mysql repository because one of the other repositories has a package upgrade that won't be applied because it has a dependency on a gdm version that as yet doesn't exist, and, dnf appears to not have support for yum's --skip-broken parameter. Does dnf have support for this functionality so that sudo dnf upgrade will upgrade the packages I want to and ignore the packages with dependency issues?https://akozumpl.github.io/dnf/cli_vs_yum.html#no-skip-broken
Rahul
Hi Rahul, Thankyou for the link, do you know how up to date that information is? It says that dnf update and dnf upgrade do the same thing, but there is no update parameter on dnf, and, it also says that dnf upgrade has the --skip-broken functionality built in by default, but it was a dnf upgrade that highlighted that dnf doesn't have that functionality. Now that I have installed the MySQL packages I wanted (via yum --skip-broken upgrade) I have run dnf upgrade again and this time it has not produced the issue with gdm2setup (yum upgrade still does report the issue), why is dnf not working the same today as it did yesterday?
regards, Steve
Hi
On Mon, Jun 30, 2014 at 5:38 PM, Stephen Morris wrote:
Hi Rahul, Thankyou for the link, do you know how up to date that information is? It says that dnf update and dnf upgrade do the same thing, but there is no update parameter on dnf, and, it also says that dnf upgrade has the --skip-broken functionality built in by default, but it was a dnf upgrade that highlighted that dnf doesn't have that functionality.
It should be up2date. If you notice any differences that are undocumented or documented incorrectly, that should be reported as a bug. Also note that there are other differences including --best and the way the cache metadata is expired which might explain some of what you are seeing.
Rahul
On Mon, Jun 30, 2014 at 10:04:16PM -0400, Rahul Sundaram wrote:
Hi On Mon, Jun 30, 2014 at 5:38 PM, Stephen Morris wrote:
Hi Rahul,    Thankyou for the link, do you know how up to date that information is? It says that  dnf update  and   dnf upgrade  do the same thing, but there is no   update  parameter on dnf, and, it also says that  dnf upgrade  has the  --skip-broken functionality built in by default, but it was a  dnf upgrade  that highlighted that dnf doesn't have that functionality.
It should be up2date. If you notice any differences that are undocumented or documented incorrectly, that should be reported as a bug. Also note that there are other differences including --best and the way the cache metadata is expired which might explain some of what you are seeing. Rahul
Changing topic: what email clients are you guys using? I dunno if you can see it in the quoted stuff above, but on my Centos-6 system with Mutt, I see all those capital A letters with a tilde floating above it.
My system's default charset is UTF-8.
Does anyone know why I'd be seeing that? I see a LOT of them in recent months and wonder what has changed.
thanks!
On Tue, 1 Jul 2014 09:01:50 -0400 Fred Smith fredex@fcshome.stoneham.ma.us wrote:
   Thankyou for the link, do you know how up to date that information is? It says that  dnf update  and   dnf upgrade  do the same thing, but there is no   update  the  --skip-broken functionality built in by default, but it was a  dnf upgrade  that highlighted that dnf doesn't have that
Claws Mail version 3.10.0
On 07/01/14 21:01, Fred Smith wrote:
On Mon, Jun 30, 2014 at 10:04:16PM -0400, Rahul Sundaram wrote:
Hi On Mon, Jun 30, 2014 at 5:38 PM, Stephen Morris wrote:
Hi Rahul,    Thankyou for the link, do you know how up to date that information is? It says that  dnf update  and   dnf upgrade  do the same thing, but there is no   update  parameter on dnf, and, it also says that  dnf upgrade  has the  --skip-broken functionality built in by default, but it was a  dnf upgrade  that highlighted that dnf doesn't have that functionality.
It should be up2date. If you notice any differences that are undocumented or documented incorrectly, that should be reported as a bug. Also note that there are other differences including --best and the way the cache metadata is expired which might explain some of what you are seeing. Rahul
Changing topic: what email clients are you guys using? I dunno if you can see it in the quoted stuff above, but on my Centos-6 system with Mutt, I see all those capital A letters with a tilde floating above it.
My system's default charset is UTF-8.
Does anyone know why I'd be seeing that? I see a LOT of them in recent months and wonder what has changed.
First off, Rahul seems to be sending messages/replies in multipart/alternative which means the same information/body is sent in text/plain and text/html. It is up to the client to decide which to present to the end user.
In your case, the text/html portion is being rendered. The actual MIME headers for that are....
Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
And the  character you're seeing is the result of =C2=A0=C2=A0=C2=A0 in the quoted printable.
I'm using T-Bird and it seems the html is being rendered correctly. So, mutt seems to have an issue with qp encoding rendering.
Allegedly, on or about 01 July 2014, Fred Smith sent:
I dunno if you can see it in the quoted stuff above, but on my Centos-6 system with Mutt, I see all those capital A letters with a tilde floating above it.
My system's default charset is UTF-8.
Does anyone know why I'd be seeing that? I see a LOT of them in recent months and wonder what has changed.
They were working properly on my system. Perhaps you've accidentally set an overriding charset in your mail client, itself?
On 07/01/2014 11:01 PM, Fred Smith wrote:
On Mon, Jun 30, 2014 at 10:04:16PM -0400, Rahul Sundaram wrote:
Hi On Mon, Jun 30, 2014 at 5:38 PM, Stephen Morris wrote: Hi Rahul,    Thankyou for the link, do you know how up to date that information is? It says that  dnf update  and   dnf upgrade  do the same thing, but there is no   update  parameter on dnf, and, it also says that  dnf upgrade  has the  --skip-broken functionality built in by default, but it was a  dnf upgrade  that highlighted that dnf doesn't have that functionality. It should be up2date. If you notice any differences that are undocumented or documented incorrectly, that should be reported as a bug. Also note that there are other differences including --best and the way the cache metadata is expired which might explain some of what you are seeing. RahulChanging topic: what email clients are you guys using? I dunno if you can see it in the quoted stuff above, but on my Centos-6 system with Mutt, I see all those capital A letters with a tilde floating above it.
My system's default charset is UTF-8.
Does anyone know why I'd be seeing that? I see a LOT of them in recent months and wonder what has changed.
thanks!
Hi Fred, I'm using Thunderbird which like Ed's is configured to send both text and html. Like Ed said there is potentially an issue at your end or Rahul's end, as further to what you are seeing when I replied to your mail Thunderbird actually generated 2 responses, which I've never seen it do before. Relative to those characters in the history, in the first line under Rahul's salutation, the first 3 extraneous characters are where I have inserted a Tab, the other instances in that text are just Spaces, so something is doing a horrible translation.
regards, Steve
On 07/02/14 05:45, Stephen Morris wrote:
I'm using Thunderbird which like Ed's is configured to send both text and html. Like Ed said there is potentially an issue at your end or Rahul's end, as further to what you are seeing when I replied to your mail Thunderbird actually generated 2 responses, which I've never seen it do before. Relative to those characters in the history, in the first line under Rahul's salutation, the first 3 extraneous characters are where I have inserted a Tab, the other instances in that text are just Spaces, so something is doing a horrible translation.
I think I need to correct your statement......
When sending to fedoraproject.org domain I have configured T-Bird to send *only* text/plain.
Now, in checking, =A0=C2 quoted printable does decode to Â. If, in T-Bird, you open Rahul's message in a new window and then change "View-->Character Encoding" from UTF-8 to ISO8859-1 the  will be shown.
So, I wonder why mutt is ignoring the charset=UTF-8. I also wonder why Rahul's client is inserting the qp string.
But, I don't think it is worth the time (certainly not in this thread) to take it further.
On 07/02/14 06:29, Ed Greshko wrote:
On 07/02/14 05:45, Stephen Morris wrote:
I'm using Thunderbird which like Ed's is configured to send both text and html. Like Ed said there is potentially an issue at your end or Rahul's end, as further to what you are seeing when I replied to your mail Thunderbird actually generated 2 responses, which I've never seen it do before. Relative to those characters in the history, in the first line under Rahul's salutation, the first 3 extraneous characters are where I have inserted a Tab, the other instances in that text are just Spaces, so something is doing a horrible translation.I think I need to correct your statement......
When sending to fedoraproject.org domain I have configured T-Bird to send *only* text/plain.
Now, in checking, =A0=C2 quoted printable does decode to Â. If, in T-Bird, you open Rahul's message in a new window and then change "View-->Character Encoding" from UTF-8 to ISO8859-1 the  will be shown.
So, I wonder why mutt is ignoring the charset=UTF-8. I also wonder why Rahul's client is inserting the qp string.
But, I don't think it is worth the time (certainly not in this thread) to take it further.
Sorry, I couldn't help myself.
=A0=C2 in QP decodes to U+00A0 NO-BREAK SPACE in UTF-8 and is a non-printable character.
On 07/02/2014 08:29 AM, Ed Greshko wrote:
On 07/02/14 05:45, Stephen Morris wrote:
I'm using Thunderbird which like Ed's is configured to send both text and html. Like Ed said there is potentially an issue at your end or Rahul's end, as further to what you are seeing when I replied to your mail Thunderbird actually generated 2 responses, which I've never seen it do before. Relative to those characters in the history, in the first line under Rahul's salutation, the first 3 extraneous characters are where I have inserted a Tab, the other instances in that text are just Spaces, so something is doing a horrible translation.I think I need to correct your statement......
When sending to fedoraproject.org domain I have configured T-Bird to send *only* text/plain.
Just for my benefit how have you configured Thunderbird to do this? I used to do this with Mandriva but I can't find where to do this in the version I am using now. The only option I can see that might be close, but it is a global option, is Options->Delivery Format which I currently have set to Auto Detect.
Now, in checking, =A0=C2 quoted printable does decode to Â. If, in T-Bird, you open Rahul's message in a new window and then change "View-->Character Encoding" from UTF-8 to ISO8859-1 the  will be shown.
I have view-->Character Encoding set to Unicode and I see those characters in Fred's Mail but not in Rahul's. I have opened Rahul's mail in a new tab and switched the encoding to Western and i shows the characters as you said, what I have also noticed is that in Fred's reply there are more of those characters than what there is in Rahul's mail. For example, in the first line under the salutation where I used a Tab, in Rahul's mail there are 2 of the characters in question, but in Fred's response there are 3, which makes it look like there are multiple factors at play.
So, I wonder why mutt is ignoring the charset=UTF-8. I also wonder why Rahul's client is inserting the qp string.
But, I don't think it is worth the time (certainly not in this thread) to take it further.
You are right, it is vastly OT for this thread.
regards, Steve
On 07/02/2014 03:22 PM, Stephen Morris issued this missive:
On 07/02/2014 08:29 AM, Ed Greshko wrote:
On 07/02/14 05:45, Stephen Morris wrote:
I'm using Thunderbird which like Ed's is configured to send bothtext and html. Like Ed said there is potentially an issue at your end or Rahul's end, as further to what you are seeing when I replied to your mail Thunderbird actually generated 2 responses, which I've never seen it do before. Relative to those characters in the history, in the first line under Rahul's salutation, the first 3 extraneous characters are where I have inserted a Tab, the other instances in that text are just Spaces, so something is doing a horrible translation.
I think I need to correct your statement......
When sending to fedoraproject.org domain I have configured T-Bird to send *only* text/plain.
Just for my benefit how have you configured Thunderbird to do this? I used to do this with Mandriva but I can't find where to do this in the version I am using now. The only option I can see that might be close, but it is a global option, is Options->Delivery Format which I currently have set to Auto Detect.
Go to "Edit->Preferences", then open the "Composition" box. Under the "General" tab, you'll see a "Send options..." box near the bottom. Click on that and you'll be presented with the HTML and Plain Text domains stuff. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - The Theory of Rapitivity: E=MC Hammer - - -- Glenn Marcus (via TopFive.com) - ----------------------------------------------------------------------
07/02/2014 06:10 PM, Rick Stevens wrote:
On 07/02/2014 03:22 PM, Stephen Morris issued this missive:
On 07/02/2014 08:29 AM, Ed Greshko wrote:
On 07/02/14 05:45, Stephen Morris wrote:
I'm using Thunderbird which like Ed's is configured to send bothtext and html. Like Ed said there is potentially an issue at your end or Rahul's end, as further to what you are seeing when I replied to your mail Thunderbird actually generated 2 responses, which I've never seen it do before. Relative to those characters in the history, in the first line under Rahul's salutation, the first 3 extraneous characters are where I have inserted a Tab, the other instances in that text are just Spaces, so something is doing a horrible translation.
I think I need to correct your statement......
When sending to fedoraproject.org domain I have configured T-Bird to send *only* text/plain.
Just for my benefit how have you configured Thunderbird to do this? I used to do this with Mandriva but I can't find where to do this in the version I am using now. The only option I can see that might be close, but it is a global option, is Options->Delivery Format which I currently have set to Auto Detect.
Go to "Edit->Preferences", then open the "Composition" box. Under the "General" tab, you'll see a "Send options..." box near the bottom. Click on that and you'll be presented with the HTML and Plain Text domains stuff.
Lost the original message so I'm replying to Rick's...
Right click in TBird's left tab on your account name then choose Settings. That will open "Account Settings" then choose "Composition & Addressing". The top box should be unchecked (Compose messages in HTML format).
Between Rick's suggestion and this you should be ready to go!
Allegedly, on or about 03 July 2014, Stephen Morris sent:
I have view-->Character Encoding set to Unicode and I see those characters in Fred's Mail but not in Rahul's. I have opened Rahul's mail in a new tab and switched the encoding to Western and i shows the characters as you said, what I have also noticed is that in Fred's reply there are more of those characters than what there is in Rahul's mail.
As a general rule, at least for reading mail, you do not set defaults to something like that. The default for mail, is us-ascii (the default being used when there is no header is present to say what the message content is written in, then the simplest us-ascii is the norm). Anything else should (probably "must") have headers declaring what it is, and the mail client will pay attention to them.
A need to pick something else to display mail arises from dealing with broken clients that send something else without saying what it is. And, in ancient computing times, various systems which used all sorts of different encoding schemes, and never bothered to declare what they use. In this day and age, there should be no client that composes a message without describing the character encoding that it used. Such a client would have been written by a really crap author.
For composing mail, your editor's default (that's a different setting), should be the same as your system's, or your mail client should be able to figure it out for themselves. Some can't, hence the need to be able to set a default, here.
When composing mail that includes portions of someone else's text (a reply with quotes), the mail client should be transcoding any different schemes, so that the whole message uses the same scheme.
On 07/03/2014 11:31 AM, Mike Wright wrote:
07/02/2014 06:10 PM, Rick Stevens wrote:
On 07/02/2014 03:22 PM, Stephen Morris issued this missive:
On 07/02/2014 08:29 AM, Ed Greshko wrote:
On 07/02/14 05:45, Stephen Morris wrote:
I'm using Thunderbird which like Ed's is configured to send bothtext and html. Like Ed said there is potentially an issue at your end or Rahul's end, as further to what you are seeing when I replied to your mail Thunderbird actually generated 2 responses, which I've never seen it do before. Relative to those characters in the history, in the first line under Rahul's salutation, the first 3 extraneous characters are where I have inserted a Tab, the other instances in that text are just Spaces, so something is doing a horrible translation.
I think I need to correct your statement......
When sending to fedoraproject.org domain I have configured T-Bird to send *only* text/plain.
Just for my benefit how have you configured Thunderbird to do this? I used to do this with Mandriva but I can't find where to do this in the version I am using now. The only option I can see that might be close, but it is a global option, is Options->Delivery Format which I currently have set to Auto Detect.
Go to "Edit->Preferences", then open the "Composition" box. Under the "General" tab, you'll see a "Send options..." box near the bottom. Click on that and you'll be presented with the HTML and Plain Text domains stuff.
Lost the original message so I'm replying to Rick's...
Right click in TBird's left tab on your account name then choose Settings. That will open "Account Settings" then choose "Composition & Addressing". The top box should be unchecked (Compose messages in HTML format).
Between Rick's suggestion and this you should be ready to go!
Thanks guys. I've followed Rick's suggestion, which was the options I was looking for but couldn't find. Removing the check box against 'Compose Messages in HTML' is something I didn't really want to do as this is a global option rather than a domain level option, plus I communicate with a number of different clients where the mail in html is the preferred option.
regards, Steve
-
Ed Greshko -
Fred Smith -
Maurizio Marini -
Mike Wright -
Rahul Sundaram -
Rick Stevens -
Stephen Morris -
Tim