As I said in the past, I agree with the long list of unfixed bugs is the TDE's great unresolved matter. But I completely disagree in the qualifiers to Kftpgrabber and Kasablanca as antiquities: are I have tried many ftp clients and Kftpgrabber and Kasablanca are the only ones I get to connect via SFTP to my web host (and it is a popular web hosting company in my region).

Thanks

---

De: Darrell Anderson darrella@hushmail.com Para: trinity-devel@lists.pearsoncomputing.net Enviado: Martes 18 de febrero de 2014 19:48 Asunto: Re: [trinity-devel] R: [trinity-devel] TDE kftpgrabber and kasablanca FTP clients - connect, but no file list ever retrieved

...

I tried KFtpgrappeb on a debian mirror, but after establishing a connection, it "stops" on the "fetching file lise". There is definitely something wrong somewhere.

I am going to be frank here and will sound harsh and mean. We are eager to add older kde3 apps to the repo but part of me thinks we do this with a bean-counter mindset --- to impress people how many apps we have. From my own usage and observation I find many of those older apps useless fluff.

We spend zero time on quality control and testing. Browse the bug tracker --- filled with paper cut issues. Or, to be blunt, what I call "chicken shit" issues. The bug reports all just sit there with no attention.

David, file Yet Another Bug Report. I don't know what else to do.

Darrell

---

To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

On 02/18/2014 12:48 PM, Darrell Anderson wrote:

...

I tried KFtpgrappeb on a debian mirror, but after establishing a connection, it "stops" on the "fetching file lise". There is definitely something wrong somewhere.

I am going to be frank here and will sound harsh and mean. We are eager to add older kde3 apps to the repo but part of me thinks we do this with a bean-counter mindset --- to impress people how many apps we have. From my own usage and observation I find many of those older apps useless fluff.

We spend zero time on quality control and testing. Browse the bug tracker --- filled with paper cut issues. Or, to be blunt, what I call "chicken shit" issues. The bug reports all just sit there with no attention.

David, file Yet Another Bug Report. I don't know what else to do.

Darrell

I understand your frustration Darrell, and no you are not being mean. You are apparently taking the information I am posting in a way other than it is intended to be received. I am not complaining saying "look this is broken, TDE is bad or not ready", quite the contrary. I am testing all of the applications and passing on the information so that you, I, Michele, Salvek, Francios, Tim, whoever is packaging for a distribution will know what applications are working and which are broken .. and .. to give everyone the ability to confirm my findings.

I am packaging for potentially hundreds of users. I do NOT want to include packages in my offerings that are broken or do not work. That will reflect badly on TDE.

Like I said in my last post regarding this topic, I don't want/expect you to do anything about it other than know "Rankin testing app X, Y and Z and reported breakage."

I also test these apps because I do not know what you or anyone else considers to be "apps that should work in TDE and will reflect poorly on TDE if included broken" If any of these apps are apps that fall into that category, then I've provided that information through testing so that appropriate action can be taken or priorities set -- period. Nothing more, nothing less.

I do not use any of these apps, but since they are part of the tree, I feel obligated to know whether they (1) build, and (2) work, so that when R14 is released and I get a question about package Y, I can at least give an educated response regarding the same.

The only critical/blocking issue I know of for Arch is the systemd user session tracking issue that leaves hundreds of open sftp/file/http processes open. That in itself doesn't mean TDE is unusable in pure-systemd, because something limits/closes stale processes after a given period of time ultimately limiting the impact. But since that doesn't effect non pure-systemd distros, if it can't be fixed for R14, so be it, I'll just wait until it can be fixed to release packages for Arch.

Other than that, I think R14 is ready to freeze for RC1. These little packages can be targeted for fixing in 14.0.1 and be part of what gives meaning to the '1'. Except for those broken packages, you, or anyone else considers critical to 14.0.0, consider this information for fixing in .1 :)