I am just wondering why there is two packages one named "kicad" and another labelled "eeschema" thats installs together when updating from the ppa.

What is the purpose of distributing eeschema in a separate package ?




Le 13/03/2014 00:45, Fabrizio Tappero a écrit :
Guys,
I did not mean to sound harsh, my apologies if I was.
I am all for PPAs and for Jean-Samuel work, I was just hoping to point
out that users might get a little frustrated if builds do not work.

cheers
Fabrizio


On Wed, Mar 12, 2014 at 7:41 PM, Jean-Samuel Reynaud
<js.reyn...@gmail.com> wrote:
Anyway, I had remove faulty package and every packages are come back now...




2014-03-12 19:34 GMT+01:00 Adam Wolf <adamw...@feelslikeburning.com>:

Personally, I'm glad the PPA is around.  My upstream debianization is
taking longer than expected--surprise surprise.

I can see how Fabrizio could look at a page of broken builds and assume
the whole PPA is broken, but it certainly looks like a transient error to
me.  Good news coming on that front from Wayne and Layne soon!

Thanks Jean-Samuel!

Adam Wolf
Wayne and Layne, LLC


On Wed, Mar 12, 2014 at 1:30 PM, Jean-Samuel Reynaud
<js.reyn...@gmail.com> wrote:
Yes you are true, there is a broken compilation (on rev 4742). So package
was unable to be build... I'm trying to re-enable 4741 until fix.

@All this PPA was dedicated to a daily build of source. So sources can be
broken and then package can become broken...


Regards,
Jean-Samuel


2014-03-12 17:54 GMT+01:00 Maciej Sumiński <maciej.sumin...@cern.ch>:

On 03/12/2014 05:54 PM, Dick Hollenbeck wrote:
On 03/12/2014 10:50 AM, Fabrizio Tappero wrote:
I am looking at this ppa repo and I see that it fails on all builds
and that there is a
size limit error too.

Kaspar, I know that having a KiCad PPA link on the official webpage is
something that we
all want but, in my opinion it is important to link things that we are
sure will work. I
tihnk stability is important and KiCad users want that.

Is it the case to maybe undo this link?


Fabrizio, that is a bit harsh and premature.  First you should have a
conversation with
Jean-Samuel about it.  Give him a chance to correct any problems
quickly.

Actually, it is caused by one of bugs that Jean-Pierre has pointed out.
There is already a fix in lp:~cern-kicad/kicad/fixes, waiting for review.

Regards,
Orson


_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Reply via email to