[Emc-developers] Bug#1045366: linuxcnc: Fails to build source after successful build

[Lucas Nussbaum]

Source: linuxcnc
Version: 2.9.0~pre1+git20230208.f1270d6ed7-1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> ---
> 
> dpkg-buildpackage: info: source package linuxcnc
> dpkg-buildpackage: info: source version 2.9.0~pre1+git20230208.f1270d6ed7-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Sebastian Kuzminsky 
> 
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean
>   rm -f debian/linuxcnc-doc-de.debhelper.log 
> debian/linuxcnc-doc-en.debhelper.log debian/linuxcnc-doc-es.debhelper.log 
> debian/linuxcnc-doc-fr.debhelper.log debian/linuxcnc-doc-zh-cn.debhelper.log 
> debian/linuxcnc-uspace-dev.debhelper.log debian/linuxcnc-uspace.debhelper.log
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> py3clean .
> if [ -r src/Makefile.inc -a -r src/config.status ]; then /usr/bin/make -C src 
> clean -s; fi
> make[2]: Entering directory '/<>/src'
> make[2]: Leaving directory '/<>/src'
> rm -f Makefile.inc
> rm -f src/config.log src/config.status
> rm -f 
> dh_clean
>   rm -f debian/debhelper-build-stamp
>   rm -rf debian/.debhelper/
>   rm -f -- debian/linuxcnc-uspace-dev.substvars 
> debian/linuxcnc-uspace.substvars debian/linuxcnc-uspace.postinst.debhelper 
> debian/linuxcnc-uspace.prerm.debhelper debian/linuxcnc-doc-de.substvars 
> debian/linuxcnc-doc-en.substvars debian/linuxcnc-doc-fr.substvars 
> debian/linuxcnc-doc-es.substvars debian/linuxcnc-doc-zh-cn.substvars 
> debian/files
>   rm -fr -- debian/linuxcnc-uspace-dev/ debian/tmp/ 
> debian/linuxcnc-uspace/ debian/linuxcnc-doc-de/ debian/linuxcnc-doc-en/ 
> debian/linuxcnc-doc-fr/ debian/linuxcnc-doc-es/ debian/linuxcnc-doc-zh-cn/
>   find .  \( \( \
>   \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
> -type f -a \
>   \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
>   \) -exec rm -f {} + \) -o \
>   \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
> \)
> make[1]: Leaving directory '/<>'
>dh_clean
>   rm -f debian/debhelper-build-stamp
>   rm -rf debian/.debhelper/
>   rm -f -- debian/linuxcnc-uspace-dev.substvars 
> debian/linuxcnc-uspace.substvars debian/linuxcnc-doc-de.substvars 
> debian/linuxcnc-doc-en.substvars debian/linuxcnc-doc-fr.substvars 
> debian/linuxcnc-doc-es.substvars debian/linuxcnc-doc-zh-cn.substvars 
> debian/files
>   rm -fr -- debian/linuxcnc-uspace-dev/ debian/tmp/ 
> debian/linuxcnc-uspace/ debian/linuxcnc-doc-de/ debian/linuxcnc-doc-en/ 
> debian/linuxcnc-doc-fr/ debian/linuxcnc-doc-es/ debian/linuxcnc-doc-zh-cn/
>   find .  \( \( \
>   \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
> -type f -a \
>   \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
>   \) -exec rm -f {} + \) -o \
>   \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
> \)
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building linuxcnc using existing 
> ./linuxcnc_2.9.0~pre1+git20230208.f1270d6ed7.orig.tar.

Re: [Emc-developers] Downloading of DOCS still an issue

[gene heskett]

On 8/13/23 13:40, Rod Webster wrote:

@marius, There is a new buildbot Seb has built http://buildbot2.highlab.com/
One solution would be to download the docs you want and install with sudo
dpkg -i
Alternatively, you could edit your sources to use them with apt. This is
described for Bookworm and 2.9 in the docs under heading #9 here.
http://linuxcnc.org/docs/2.9/html/getting-started/getting-linuxcnc.html
  If you wanted to get for say buster and master, you would need to change
the echo statement to suit. I am not sure how the linuxcnc 2.8 iso does
this, you might need to review and update files in /etc/apt/sources.list
and /etc/apt/sources.list.d/
That looks complex but doable. Printed FFR. I'll see what I can do, 
thanks a bunch Rod.  Take care and stay well.


@gene, if you want to move forward to bookworm, the process is described in
the 2.9 docs per the second link
The Raspberry pi is a bit of a problem as there is no new buildbot for it.
Today, you would be better off using 64 bit arm64 instead of armhf (on a pi
4b). Installing on bookworm is also described in the docs above. The gpio
was broken due to depreciation of the non standard method we used.  I think
Andy has fixed that recently pending a new driver that uses the correct
method. But there is no alternative but to build from source on the pi to
obtain the latest versions as the bookworm image is locked by debian
policies at an earlier version. I was hoping that the new buildbot would
build Raspberry images using a cross compiler on AMD64 hardware as per some
links I shared on Issue #2349
https://github.com/LinuxCNC/linuxcnc/issues/2349 Currently the old buildbot
uses a pi to build everything which is not desirable moving forward.

Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au


On Sun, 13 Aug 2023 at 23:05, gene heskett  wrote:


On 8/13/23 05:17, Steffen M￶ller wrote:

Hello,


Gesendet: Freitag, 11. August 2023 um 09:38 Uhr
Von: "Marius" 

There seem to be a problem with the DOCS on the server. Upgrading is not
possible if the docs are included as they just will not download at all
or take many hours if they do download.

I reported this before but it seems to be still ongoing issue.


I'm a bit puzzled by the issue you've mentioned regarding the DOCS on

the server. I thought it might be connected to the online documentation on
the web server, but it seems that part is working fine for the sections I
checked.


Could you provide more details about the problem? Is it related to a

Debian documentation package? If you have specific steps or commands to
recreate the error, please share them.


If someone else on this list can already reproduce this issue, please

step forward :)


Sorry for the delay in getting back to you. We're here to help, so the

more information you can give us, the better. With more details, I'm sure
someone with expertise will come forward to address the issue.


Many thanks!
Steffen



I don't have the expertise, but I can report results.

Because I have no interest in languages I don't speak and there is no
way to build just the English docs. I am locked out of any upgrades as
I'm running buster, I cannot even build linuxcnc on bullseye because
bullseye's python is too new. This has been reported several times on
this list.

I normally, since I'm not a for profit shop, run master from the
buildbot, as a hobbiest I can afford to bleed occasionally, but the
buster in-release file has been removed from the buildbot for armhf,
disabling my access to the buildbot's output for buster master.

So I'm back to running some scripts here that duplicate the buildbot,
including building install-able debs. But something has gone wrong and
the installed debs, which run just fine, now break apt, and the only
solution is to fix-broken, which will remove the debs my pi just spent
40 minutes building and 3 minutes installing.

I can after that, probably install bookworm and then install linuxcnc,
v2.9.0 from the bookworm repo's.

But that is not the point Steffan, because I'm not a for profit user,
I've been playing canary in the coal mine, running master for almost 20
years, reporting unseen bugs as I've encountered them, my contribution
to the stability of linuxcnc.  These guy's are good, I've only reported
a failure twice in that time frame. OTOH my test is just to see if it
runs from a shell so I don't catch everything.

So at present, I can't build the docs because my machine does not have
the resources installed to build all the languages that have been added
in the last 2 years.  I could probably install them if I had a list of
what's needed. But its also time to install bookworm. A different kettle
of fish entirely.

Lets assume I install bookworm, first on my wintel stuff. But is the
plan to lock up the buildbot now that linuxcnc is officially in debian?
IDK. If that is the case, my canary just died.

And because the buster in-release file has been deleted, synaptic nor
apt 

Re: [Emc-developers] Downloading of DOCS still an issue

[Rod Webster]

@marius, There is a new buildbot Seb has built http://buildbot2.highlab.com/
One solution would be to download the docs you want and install with sudo
dpkg -i
Alternatively, you could edit your sources to use them with apt. This is
described for Bookworm and 2.9 in the docs under heading #9 here.
http://linuxcnc.org/docs/2.9/html/getting-started/getting-linuxcnc.html
 If you wanted to get for say buster and master, you would need to change
the echo statement to suit. I am not sure how the linuxcnc 2.8 iso does
this, you might need to review and update files in /etc/apt/sources.list
and /etc/apt/sources.list.d/

@gene, if you want to move forward to bookworm, the process is described in
the 2.9 docs per the second link
The Raspberry pi is a bit of a problem as there is no new buildbot for it.
Today, you would be better off using 64 bit arm64 instead of armhf (on a pi
4b). Installing on bookworm is also described in the docs above. The gpio
was broken due to depreciation of the non standard method we used.  I think
Andy has fixed that recently pending a new driver that uses the correct
method. But there is no alternative but to build from source on the pi to
obtain the latest versions as the bookworm image is locked by debian
policies at an earlier version. I was hoping that the new buildbot would
build Raspberry images using a cross compiler on AMD64 hardware as per some
links I shared on Issue #2349
https://github.com/LinuxCNC/linuxcnc/issues/2349 Currently the old buildbot
uses a pi to build everything which is not desirable moving forward.

Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au


On Sun, 13 Aug 2023 at 23:05, gene heskett  wrote:

> On 8/13/23 05:17, Steffen M￶ller wrote:
> > Hello,
> >
> >> Gesendet: Freitag, 11. August 2023 um 09:38 Uhr
> >> Von: "Marius" 
> >>
> >> There seem to be a problem with the DOCS on the server. Upgrading is not
> >> possible if the docs are included as they just will not download at all
> >> or take many hours if they do download.
> >>
> >> I reported this before but it seems to be still ongoing issue.
> >
> > I'm a bit puzzled by the issue you've mentioned regarding the DOCS on
> the server. I thought it might be connected to the online documentation on
> the web server, but it seems that part is working fine for the sections I
> checked.
> >
> > Could you provide more details about the problem? Is it related to a
> Debian documentation package? If you have specific steps or commands to
> recreate the error, please share them.
> >
> > If someone else on this list can already reproduce this issue, please
> step forward :)
> >
> > Sorry for the delay in getting back to you. We're here to help, so the
> more information you can give us, the better. With more details, I'm sure
> someone with expertise will come forward to address the issue.
> >
> > Many thanks!
> > Steffen
> >
>
> I don't have the expertise, but I can report results.
>
> Because I have no interest in languages I don't speak and there is no
> way to build just the English docs. I am locked out of any upgrades as
> I'm running buster, I cannot even build linuxcnc on bullseye because
> bullseye's python is too new. This has been reported several times on
> this list.
>
> I normally, since I'm not a for profit shop, run master from the
> buildbot, as a hobbiest I can afford to bleed occasionally, but the
> buster in-release file has been removed from the buildbot for armhf,
> disabling my access to the buildbot's output for buster master.
>
> So I'm back to running some scripts here that duplicate the buildbot,
> including building install-able debs. But something has gone wrong and
> the installed debs, which run just fine, now break apt, and the only
> solution is to fix-broken, which will remove the debs my pi just spent
> 40 minutes building and 3 minutes installing.
>
> I can after that, probably install bookworm and then install linuxcnc,
> v2.9.0 from the bookworm repo's.
>
> But that is not the point Steffan, because I'm not a for profit user,
> I've been playing canary in the coal mine, running master for almost 20
> years, reporting unseen bugs as I've encountered them, my contribution
> to the stability of linuxcnc.  These guy's are good, I've only reported
> a failure twice in that time frame. OTOH my test is just to see if it
> runs from a shell so I don't catch everything.
>
> So at present, I can't build the docs because my machine does not have
> the resources installed to build all the languages that have been added
> in the last 2 years.  I could probably install them if I had a list of
> what's needed. But its also time to install bookworm. A different kettle
> of fish entirely.
>
> Lets assume I install bookworm, first on my wintel stuff. But is the
> plan to lock up the buildbot now that linuxcnc is officially in debian?
> IDK. If that is the case, my canary just died.
>
> And because the buster in-release file has been deleted, synaptic 

Re: [Emc-developers] Downloading of DOCS still an issue

[gene heskett]

On 8/13/23 05:17, Steffen Möller wrote:

Hello,


Gesendet: Freitag, 11. August 2023 um 09:38 Uhr
Von: "Marius" 

There seem to be a problem with the DOCS on the server. Upgrading is not
possible if the docs are included as they just will not download at all
or take many hours if they do download.

I reported this before but it seems to be still ongoing issue.


I'm a bit puzzled by the issue you've mentioned regarding the DOCS on the 
server. I thought it might be connected to the online documentation on the web 
server, but it seems that part is working fine for the sections I checked.

Could you provide more details about the problem? Is it related to a Debian 
documentation package? If you have specific steps or commands to recreate the 
error, please share them.

If someone else on this list can already reproduce this issue, please step 
forward :)

Sorry for the delay in getting back to you. We're here to help, so the more 
information you can give us, the better. With more details, I'm sure someone 
with expertise will come forward to address the issue.

Many thanks!
Steffen



I don't have the expertise, but I can report results.

Because I have no interest in languages I don't speak and there is no 
way to build just the English docs. I am locked out of any upgrades as 
I'm running buster, I cannot even build linuxcnc on bullseye because 
bullseye's python is too new. This has been reported several times on 
this list.


I normally, since I'm not a for profit shop, run master from the 
buildbot, as a hobbiest I can afford to bleed occasionally, but the 
buster in-release file has been removed from the buildbot for armhf, 
disabling my access to the buildbot's output for buster master.


So I'm back to running some scripts here that duplicate the buildbot, 
including building install-able debs. But something has gone wrong and 
the installed debs, which run just fine, now break apt, and the only 
solution is to fix-broken, which will remove the debs my pi just spent 
40 minutes building and 3 minutes installing.


I can after that, probably install bookworm and then install linuxcnc, 
v2.9.0 from the bookworm repo's.


But that is not the point Steffan, because I'm not a for profit user, 
I've been playing canary in the coal mine, running master for almost 20 
years, reporting unseen bugs as I've encountered them, my contribution 
to the stability of linuxcnc.  These guy's are good, I've only reported 
a failure twice in that time frame. OTOH my test is just to see if it 
runs from a shell so I don't catch everything.


So at present, I can't build the docs because my machine does not have 
the resources installed to build all the languages that have been added 
in the last 2 years.  I could probably install them if I had a list of 
what's needed. But its also time to install bookworm. A different kettle 
of fish entirely.


Lets assume I install bookworm, first on my wintel stuff. But is the 
plan to lock up the buildbot now that linuxcnc is officially in debian? 
IDK. If that is the case, my canary just died.


And because the buster in-release file has been deleted, synaptic nor 
apt will touch the buildbots output for armhf.


I can still do a git pull and build linuxcnc, install and run it, but 
that breaks apt, and now tha docs are locked away. So what do I do to 
restore my access to the docs?


I should also point out that my 3 wintel busters running on old Dell's 
are still getting all 4 master updates from the buildbot as of this 
morning, only the armhf build seems to be affected.


Thank you, take care & stay well, Steffan.




___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Downloading of DOCS still an issue

[Marius]

Hi Steffen

The process is very simple. I use the Synaptic Package Manager to 
install and update from http://buildbot.linuxcnc.org, dist:- buster and 
repository is master-rtpreempt.


All the files are downloaded fine but none of the doc files want to 
download. The process just hangs while waiting for the doc file and then 
after many timed-out attempts it will fail. This happens for en, de, fr 
docs. None other are selected for installation. These are the standard 
ones I think.



On 2023/08/13 11:16, Steffen Möller wrote:

Hello,


Gesendet: Freitag, 11. August 2023 um 09:38 Uhr
Von: "Marius" 

There seem to be a problem with the DOCS on the server. Upgrading is not
possible if the docs are included as they just will not download at all
or take many hours if they do download.

I reported this before but it seems to be still ongoing issue.

I'm a bit puzzled by the issue you've mentioned regarding the DOCS on the 
server. I thought it might be connected to the online documentation on the web 
server, but it seems that part is working fine for the sections I checked.

Could you provide more details about the problem? Is it related to a Debian 
documentation package? If you have specific steps or commands to recreate the 
error, please share them.

If someone else on this list can already reproduce this issue, please step 
forward :)

Sorry for the delay in getting back to you. We're here to help, so the more 
information you can give us, the better. With more details, I'm sure someone 
with expertise will come forward to address the issue.

Many thanks!
Steffen



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Downloading of DOCS still an issue

[Steffen Möller]

Hello,

> Gesendet: Freitag, 11. August 2023 um 09:38 Uhr
> Von: "Marius" 
>
> There seem to be a problem with the DOCS on the server. Upgrading is not
> possible if the docs are included as they just will not download at all
> or take many hours if they do download.
>
> I reported this before but it seems to be still ongoing issue.

I'm a bit puzzled by the issue you've mentioned regarding the DOCS on the 
server. I thought it might be connected to the online documentation on the web 
server, but it seems that part is working fine for the sections I checked.

Could you provide more details about the problem? Is it related to a Debian 
documentation package? If you have specific steps or commands to recreate the 
error, please share them.

If someone else on this list can already reproduce this issue, please step 
forward :)

Sorry for the delay in getting back to you. We're here to help, so the more 
information you can give us, the better. With more details, I'm sure someone 
with expertise will come forward to address the issue.

Many thanks!
Steffen



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers