Mail Archives: geda-user/2016/12/30/18:51:38
--001a114435b8bdfe990544e8dc08
Content-Type: text/plain; charset=UTF-8
Bert, you beat me to the punch! I have a draft email open right now that
mentions some of these things.
I think that most of the commits in my 4.0.0 branch should probably be in
master as well.
The MinMaskGap failure is the result of a non-zero diff between the golden
file and the pcb output file. The non-zero part is because the version
strings that pcb writes at the beginning of the file are different. The
test isn't really failing. If you update the version string in the golden
file to match the new version, then the test will pass.
I tried to create a 4.0.0 branch in the git root, but was not able to.
Maybe I don't have the requisite permissions?
I've been able to successfully do a make distcheck with each of the hids
(gtk, lesstif, and batch) on my Mac. I was just working on doing the same
on a Slackware VM and a Debian VM, but am running into some other problems
there.
--Chad
On Fri, Dec 30, 2016 at 5:27 PM, Bert Timmerman (bert DOT timmerman AT xs4all DOT nl)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
>
>> Is the reason people want to skip to version 4 just because of that fork
>> that claimed version 3.x? If so, we could still use the 2.x.x series before
>> having to worry about the naming collision, and then skip to 4.0.0. Or is
>> it that we want to tell prospective users that ours is better by having a
>> higher version number?
>>
>> DJ-
>> I agree that there haven't been any changes that would break backward
>> compatibility, but sometimes you just have to make a clean break, like when
>> the kernel went to 3.0.0.
>>
>> Bert-
>> Thanks, I can be a little OCD sometimes, and I do like things to be neat
>> and clean! Particularly when it comes to plans.
>>
>> I sort of assumed that we would either have the code sprint earlier, or
>> not have one this month since the last Sunday of the month (tomorrow) is
>> Christmas day and I imagine that a lot of people will be observing that
>> holiday.
>>
>> I'll run through the release procedure that Dan pointed out sometime in
>> the next couple of days and let folks know how things go. I think there are
>> at least a couple of compile warnings on my Mac that will need to be fixed.
>>
>> Cheers, and have a good holiday to all those who are celebrating.
>> --Chad
>>
>>
>>
>>
>> On Sat, Dec 24, 2016 at 3:01 PM, Girvin Herr (
>> girvin_herr+gherr_lists AT fastmail DOT com <mailto:girvin_herr%2Bgherr_li
>> sts AT fastmail DOT com>) [via geda-user AT delorie DOT com <mailto:
>> geda-user AT delorie DOT com>] <geda-user AT delorie DOT com <mailto:
>> geda-user AT delorie DOT com>> wrote:
>>
>>
>>
>> On 12/24/2016 04:50 AM, M. J. Everitt (m DOT j DOT everitt AT iee DOT org
>> <mailto:m DOT j DOT everitt AT iee DOT org>) [via geda-user AT delorie DOT com
>>
>> <mailto:geda-user AT delorie DOT com>] wrote:
>>
>>> As a prospective proxy maintainer for Gentoo, please let me know
>>> when you roll a tarball, and I'll run through the Gentoo
>>> packaging process, and do some preliminary build/run-testing and
>>> feed back.
>>>
>>> If wanted, I can do the same for a Slackware Linux package. I am
>> currently running Slackware 14.1 (k3.10.103), but I have a copy of
>> the latest 14.2 and plan to install it early next year. The only
>> change I can see is that the package architecture went from i486
>> in 14.1 to i586 in 14.2, but that is trivial. Of course, the
>> dependencies have changed.
>>
>> Another option would be to contact the SlackBuilds.org pcb package
>> maintainer, Felix Pfeifer: pfeifer [dot] felix [at] googlemail
>> [dot] com
>> He might be willing to do this task and put the resulting packages
>> on SlackBuilds.
>>
>> geda-gaf on SlackBuilds.org seems to be maintained by a different
>> maintainer, Stephen Van Berg: stephen_van_berg at earlicker dot com
>>
>> I would second a more consistent version numbering system, as
>>> this makes version-tracking easier for packagers too, so pcb v4
>>> would indeed be a good choice if settled upon!
>>>
>> Consistency, yes. But the form doesn't matter for Slackware
>> packaging. x.y.z is just as fine as yyyymmdd. The only caveat is
>> that dashes may not be used in the version string. I usually
>> change them to underscores or remove them entirely if in yyyy-mm-dd.
>>
>> Girvin Herr
>>
>>
>>> Good luck, thanks, and keep us posted on the list :)
>>>
>>> Michael.
>>>
>>> On 24/12/16 12:23, Peter Clifton (petercjclifton AT googlemail DOT com
>>> <mailto:petercjclifton AT googlemail DOT com>) [via
>>> geda-user AT delorie DOT com <mailto:geda-user AT delorie DOT com>] wrote:
>>>
>>>> Nice to hear work is going on with mainline pcb as well...
>>>>
>>>> One thing prior to release. We ought to git rm the debian
>>>> directory that added to the repository.
>>>>
>>>> This matches preferred distro policy, and makes life easier for
>>>> the official packagers (so they can use our sources directly
>>>> without having to repackage them to remove the debian dir.
>>>>
>>>> I checked this with our debian packagers some while back to
>>>> confirm, but never got around to making the delete.
>>>>
>>>> Peter
>>>>
>>>>
>>
>> Hi Chad,
>
> I see you are busy with the 4.0.0. test drive in your "home/cparker/4.0.0"
> branch.
>
> AFAICT some of those commits should be in master, others should go in a
> "pcb-4.0.0" release branch once you have finished testing.
>
> One other thing is that I found is that "make check" fails on the
> MinMaskGap test ... in a pristine Ubuntu 12.04 (precise) environment, see
> https://travis-ci.org/bert/pcb/builds and https://bugs.launchpad.net/pcb
> /+bug/1653280.
>
> I think we need to squash this bug before we can ship 4.0.0 ("make check"
> failing can be seen as "bad form").
>
> I will keep you informed about any findings in the bug report.
>
> Kind regards,
>
> Bert Timmerman.
>
--001a114435b8bdfe990544e8dc08
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Bert, you beat me to the punch! I have a draft email =
open right now that mentions some of these things.<br><br></div><div>I thin=
k that most of the commits in my 4.0.0 branch should probably be in master =
as well.<br></div><div><br></div><div>The MinMaskGap failure is the result =
of a non-zero diff between the golden file and the pcb output file. The non=
-zero part is because the version strings that pcb writes at the beginning =
of the file are different. The test isn't really failing. If you update=
the version string in the golden file to match the new version, then the t=
est will pass.<br><br></div><div>I tried to create a 4.0.0 branch in the gi=
t root, but was not able to. Maybe I don't have the requisite permissio=
ns?<br><br></div><div>I've been able to successfully do a make distchec=
k with each of the hids (gtk, lesstif, and batch) on my Mac. I was just wor=
king on doing the same on a Slackware VM and a Debian VM, but am running in=
to some other problems there.<br><br></div><div>--Chad<br></div><div><br></=
div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri,=
Dec 30, 2016 at 5:27 PM, Bert Timmerman (<a href=3D"mailto:bert.timmerman@=
xs4all.nl">bert DOT timmerman AT xs4all DOT nl</a>) [via <a href=3D"mailto:geda-user AT d=
elorie.com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr"><<a href=3D"mai=
lto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>><=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">Chad Parke=
r (<a href=3D"mailto:parker DOT charles AT gmail DOT com" target=3D"_blank">parker.cha=
rles AT gmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D=
"_blank">geda-user AT delorie DOT com</a>] wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
Is the reason people want to skip to version 4 just because of that fork th=
at claimed version 3.x? If so, we could still use the 2.x.x series before h=
aving to worry about the naming collision, and then skip to 4.0.0. Or is it=
that we want to tell prospective users that ours is better by having a hig=
her version number?<br>
<br>
DJ-<br>
I agree that there haven't been any changes that would break backward c=
ompatibility, but sometimes you just have to make a clean break, like when =
the kernel went to 3.0.0.<br>
<br>
Bert-<br>
Thanks, I can be a little OCD sometimes, and I do like things to be neat an=
d clean! Particularly when it comes to plans.<br>
<br>
I sort of assumed that we would either have the code sprint earlier, or not=
have one this month since the last Sunday of the month (tomorrow) is Chris=
tmas day and I imagine that a lot of people will be observing that holiday.=
<br>
<br>
I'll run through the release procedure that Dan pointed out sometime in=
the next couple of days and let folks know how things go. I think there ar=
e at least a couple of compile warnings on my Mac that will need to be fixe=
d.<br>
<br>
Cheers, and have a good holiday to all those who are celebrating.<br>
--Chad<br>
<br>
<br>
<br>
<br></span><span class=3D"">
On Sat, Dec 24, 2016 at 3:01 PM, Girvin Herr (<a href=3D"mailto:girvin_herr=
%2Bgherr_lists AT fastmail DOT com" target=3D"_blank">girvin_herr+gherr_lists AT fast=
m<wbr>ail.com</a> <mailto:<a href=3D"mailto:girvin_herr%252Bgherr_lists@=
fastmail.com" target=3D"_blank">girvin_herr%2Bgherr_li<wbr>sts AT fastmail DOT com=
</a>>) [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">g=
eda-user AT delorie DOT com</a> <mailto:<a href=3D"mailto:geda-user AT delorie DOT com=
" target=3D"_blank">geda-user AT delorie DOT com</a>><wbr>] <<a href=3D"mail=
to:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a> <m=
ailto:<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user@=
delorie.com</a>><wbr>> wrote:<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 On 12/24/2016 04:50 AM, M. J. Everitt (<a href=3D"mailto:m.j.=
everitt AT iee DOT org" target=3D"_blank">m DOT j DOT everitt AT iee DOT org</a><br></span>
=C2=A0 =C2=A0 <mailto:<a href=3D"mailto:m DOT j DOT everitt AT iee DOT org" target=3D"_=
blank">m DOT j DOT everitt AT iee DOT org</a>>) [via <a href=3D"mailto:geda-user AT delori=
e.com" target=3D"_blank">geda-user AT delorie DOT com</a><div><div class=3D"h5"><b=
r>
=C2=A0 =C2=A0 <mailto:<a href=3D"mailto:geda-user AT delorie DOT com" target=3D=
"_blank">geda-user AT delorie DOT com</a>><wbr>] wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 As a prospective proxy maintainer for Gentoo, please let me k=
now<br>
=C2=A0 =C2=A0 when you roll a tarball, and I'll run through the Gentoo<=
br>
=C2=A0 =C2=A0 packaging process, and do some preliminary build/run-testing =
and<br>
=C2=A0 =C2=A0 feed back.<br>
<br>
</blockquote>
=C2=A0 =C2=A0 If wanted, I can do the same for a Slackware Linux package.=
=C2=A0 I am<br>
=C2=A0 =C2=A0 currently running Slackware 14.1 (k3.10.103), but I have a co=
py of<br>
=C2=A0 =C2=A0 the latest 14.2 and plan to install it early next year.=C2=A0=
The only<br>
=C2=A0 =C2=A0 change I can see is that the package architecture went from i=
486<br>
=C2=A0 =C2=A0 in 14.1 to i586 in 14.2, but that is trivial.=C2=A0 Of course=
, the<br>
=C2=A0 =C2=A0 dependencies have changed.<br>
<br>
=C2=A0 =C2=A0 Another option would be to contact the SlackBuilds.org pcb pa=
ckage<br>
=C2=A0 =C2=A0 maintainer, Felix Pfeifer:=C2=A0 pfeifer [dot] felix [at] goo=
glemail<br>
=C2=A0 =C2=A0 [dot] com<br>
=C2=A0 =C2=A0 He might be willing to do this task and put the resulting pac=
kages<br>
=C2=A0 =C2=A0 on SlackBuilds.<br>
<br>
=C2=A0 =C2=A0 geda-gaf on SlackBuilds.org seems to be maintained by a diffe=
rent<br>
=C2=A0 =C2=A0 maintainer, Stephen Van Berg:=C2=A0 stephen_van_berg at earli=
cker dot com<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 I would second a more consistent version numbering system, as=
<br>
=C2=A0 =C2=A0 this makes version-tracking easier for packagers too, so pcb =
v4<br>
=C2=A0 =C2=A0 would indeed be a good choice if settled upon!<br>
</blockquote>
=C2=A0 =C2=A0 Consistency, yes.=C2=A0 But the form doesn't matter for S=
lackware<br>
=C2=A0 =C2=A0 packaging.=C2=A0 x.y.z is just as fine as yyyymmdd.=C2=A0 The=
only caveat is<br>
=C2=A0 =C2=A0 that dashes may not be used in the version string.=C2=A0 I us=
ually<br>
=C2=A0 =C2=A0 change them to underscores or remove them entirely if in yyyy=
-mm-dd.<br>
<br>
=C2=A0 =C2=A0 Girvin Herr<br>
<br>
</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5">
<br>
=C2=A0 =C2=A0 Good luck, thanks, and keep us posted on the list :)<br>
<br>
=C2=A0 =C2=A0 Michael.<br>
<br>
=C2=A0 =C2=A0 On 24/12/16 12:23, Peter Clifton (<a href=3D"mailto:petercjcl=
ifton AT googlemail DOT com" target=3D"_blank">petercjclifton AT googlemail DOT com</a><b=
r></div></div>
=C2=A0 =C2=A0 <mailto:<a href=3D"mailto:petercjclifton AT googlemail DOT com" t=
arget=3D"_blank">petercjclifton AT googlem<wbr>ail.com</a>>) [via<span clas=
s=3D""><br>
=C2=A0 =C2=A0 <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">ge=
da-user AT delorie DOT com</a> <mailto:<a href=3D"mailto:geda-user AT delorie DOT com"=
target=3D"_blank">geda-user AT delorie DOT com</a>><wbr>] wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 Nice to hear work is going on with mainline pcb as well...<br=
>
<br>
=C2=A0 =C2=A0 One thing prior to release. We ought to git rm the debian<br>
=C2=A0 =C2=A0 directory that added to the repository.<br>
<br>
=C2=A0 =C2=A0 This matches preferred distro policy, and makes life easier f=
or<br>
=C2=A0 =C2=A0 the official packagers (so they can use our sources directly<=
br>
=C2=A0 =C2=A0 without having to repackage them to remove the debian dir.<br=
>
<br>
=C2=A0 =C2=A0 I checked this with our debian packagers some while back to<b=
r>
=C2=A0 =C2=A0 confirm, but never got around to making the delete.<br>
<br>
=C2=A0 =C2=A0 Peter<br>
<br>
</blockquote></span></blockquote>
<br>
<br>
</blockquote>
Hi Chad,<br>
<br>
I see you are busy with the 4.0.0. test drive in your "home/cparker/4.=
0.0" branch.<br>
<br>
AFAICT some of those commits should be in master, others should go in a &qu=
ot;pcb-4.0.0" release branch once you have finished testing.<br>
<br>
One other thing is that I found is that "make check" fails on the=
MinMaskGap test ... in a pristine Ubuntu 12.04 (precise) environment, see =
<a href=3D"https://travis-ci.org/bert/pcb/builds" rel=3D"noreferrer" target=
=3D"_blank">https://travis-ci.org/bert/pcb<wbr>/builds</a> and <a href=3D"h=
ttps://bugs.launchpad.net/pcb/+bug/1653280" rel=3D"noreferrer" target=3D"_b=
lank">https://bugs.launchpad.net/pcb<wbr>/+bug/1653280</a>.<br>
<br>
I think we need to squash this bug before we can ship 4.0.0 ("make che=
ck" failing can be seen as "bad form").<br>
<br>
I will keep you informed about any findings in the bug report.<br>
<br>
Kind regards,<br>
<br>
Bert Timmerman.<br>
</blockquote></div><br></div>
--001a114435b8bdfe990544e8dc08--
- Raw text -