Re: pbuilder-satisfydepends-classic profile parsing problem: slashes and spaces
Mattia, thanks for the answer, I will file a bug -- Carry a towel http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/ On Thu, Oct 22, 2020 at 4:39 PM Mattia Rizzolo wrote: > > Hi! > > On Wed, Oct 21, 2020 at 10:06:02PM +0300, Alexei Fedotov wrote: > > I'm running pbuilder-0.230.4~bpo9+1/pbuilder-satisfydepends-classic > > for the debian/control which contains > > > > Build-Depends: live-build (<= 1:20170213), ... > > > > I get the following log > > > > +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > > coreutils, findutils, ' > > +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > > coreutils, findutils' > > +++ echo 'live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, > > coreutils, findutils' > > ++ for INSTALLPKGMULTI in $(get_build_deps | split_deps) > > +++ echo 'live-build/(<=/1:20170213)' > > +++ tr / ' ' > > ++ echo ' -> Considering build-dep live-build (<= 1:20170213)' > > -> Considering build-dep live-build (<= 1:20170213) > > ++ SATISFIED=no > > +++ split_alternates 'live-build/(<=/1:20170213)' > > +++ echo 'live-build/(<=/1:20170213)' > > +++ sed 's/ *| */\n/g' > > ++ for INSTALLPKG in $(split_alternates "$INSTALLPKGMULTI") > > +++ get_pkg_name 'live-build/(<=/1:20170213)' > > +++ echo 'live-build/(<=/1:20170213)' > > +++ sed 's#^/*##; s#[[/(<].*##' > > ++ CURRENTREALPKGNAME=live-build > > ++ echo 'live-build/(<=/1:20170213)' > > ++ grep -q '\[' > > ++ echo 'live-build/(<=/1:20170213)' > > ++ grep -q '<' > > I reckon here is the problem ↑ > The code thinks that anything that contains a '<' is a build profile. > That's probably because it's considered rare for a Build-Depends to have > a << or a <= relation. > From that assumption on it probably just fails over itself. > > > What is the proper list to discuss the issue? How should it be addressed? > > Please file a bug against pbuilder, but don't expect it to be solved > quickly. > > In fact, nowadays I generally recommend people use the -apt resolver, > which tends to work better in most cases, besides being faster. > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > More about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
pbuilder-satisfydepends-classic profile parsing problem: slashes and spaces
Hello, Mattia, folks, I'm running pbuilder-0.230.4~bpo9+1/pbuilder-satisfydepends-classic for the debian/control which contains Build-Depends: live-build (<= 1:20170213), ... I get the following log +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, coreutils, findutils, ' +++ output='live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, coreutils, findutils' +++ echo 'live-build (<= 1:20170213), sed, gawk, rsync, wget, patch, coreutils, findutils' ++ for INSTALLPKGMULTI in $(get_build_deps | split_deps) +++ echo 'live-build/(<=/1:20170213)' +++ tr / ' ' ++ echo ' -> Considering build-dep live-build (<= 1:20170213)' -> Considering build-dep live-build (<= 1:20170213) ++ SATISFIED=no +++ split_alternates 'live-build/(<=/1:20170213)' +++ echo 'live-build/(<=/1:20170213)' +++ sed 's/ *| */\n/g' ++ for INSTALLPKG in $(split_alternates "$INSTALLPKGMULTI") +++ get_pkg_name 'live-build/(<=/1:20170213)' +++ echo 'live-build/(<=/1:20170213)' +++ sed 's#^/*##; s#[[/(<].*##' ++ CURRENTREALPKGNAME=live-build ++ echo 'live-build/(<=/1:20170213)' ++ grep -q '\[' ++ echo 'live-build/(<=/1:20170213)' ++ grep -q '<' ++ checkbuilddep_restrictiondeps 'live-build/(<=/1:20170213)' 'nocheck astrace' ++ local 'INSTALLPKG=live-build/(<=/1:20170213)' ++ local 'PROFILES=nocheck astrace' +++ echo 'echo "$INSTALLPKG" | sed -e 's/[^<]*<\(.*\)>.*/\1/' -e 'y|/| |' -e 's/>\s\+.*/\1/' -e 'y|/| |' -e 's/>\s\+http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/
debian release structure: Sources file
Hi, it seems I found a reason for my reprepro error. aptmethod error receiving '.../dists/experimental/main/source/Sources' The file main/source/Sources is absent in the repostory yet listed in Release index file $ grep 'main/source/Sources$' /srv/mirrors/debian-updating/dists/experimental/Release b4315530709168d45dff31cc5bdff3ec 3068757 main/source/Sources 7cfc7ee6071f0d6b0aa067b3c2455249bf63a092aecb256a25bdccc751b1899b 3068757 main/source/Sources Is it expected for Release? How do you work around this? -- Carry a towel http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/
Re: [sbuild] how to create chroot environment
I've installed schroot from http://deb.debian.org/debian and it worked. Thanks again for your help. -- Carry a towel http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/ On Mon, Apr 15, 2019 at 2:30 PM Alexei Fedotov wrote: > > Georgi, thanks! > it seems schroot package is somehow missed in my repository, I will > look into it. > > -- > Carry a towel > http://dataved.ru/ > +7 916 562 8095 > > [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ > [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings > [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/ > > On Mon, Apr 15, 2019 at 2:23 PM Georgi Naplatanov wrote: > > > > On 4/15/19 2:02 PM, Alexei Fedotov wrote: > > > Hello, > > > I've installed sbuild ver 0.73.0-4 and tried creating chroot environment > > > > > > I used the following command and get an error. > > > > > > devops@devops:~/git/docker.io$ sudo sbuild-createchroot > > > --include=eatmydata,ccache,gnupg unstable > > > /srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian > > > open3: exec of schroot -l --all-source-chroots failed: No such file or > > > directory at /usr/sbin/sbuild-createchroot line 217. > > > > > > It seems "schroot" chommand is called, and it is nowhere to be found. > > > > "schroot" is a Debian package and you can install it easily. > > > > > How could I create the chroot env? > > > > There are other ways (debootstrap for example) but if you want to use > > "sbuild" then "schroot" is the preferred way I think. > > > > Kind regards > > Georgi > >
Re: [sbuild] how to create chroot environment
Georgi, thanks! it seems schroot package is somehow missed in my repository, I will look into it. -- Carry a towel http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/ On Mon, Apr 15, 2019 at 2:23 PM Georgi Naplatanov wrote: > > On 4/15/19 2:02 PM, Alexei Fedotov wrote: > > Hello, > > I've installed sbuild ver 0.73.0-4 and tried creating chroot environment > > > > I used the following command and get an error. > > > > devops@devops:~/git/docker.io$ sudo sbuild-createchroot > > --include=eatmydata,ccache,gnupg unstable > > /srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian > > open3: exec of schroot -l --all-source-chroots failed: No such file or > > directory at /usr/sbin/sbuild-createchroot line 217. > > > > It seems "schroot" chommand is called, and it is nowhere to be found. > > "schroot" is a Debian package and you can install it easily. > > > How could I create the chroot env? > > There are other ways (debootstrap for example) but if you want to use > "sbuild" then "schroot" is the preferred way I think. > > Kind regards > Georgi >
[sbuild] how to create chroot environment
Hello, I've installed sbuild ver 0.73.0-4 and tried creating chroot environment I used the following command and get an error. devops@devops:~/git/docker.io$ sudo sbuild-createchroot --include=eatmydata,ccache,gnupg unstable /srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian open3: exec of schroot -l --all-source-chroots failed: No such file or directory at /usr/sbin/sbuild-createchroot line 217. It seems "schroot" chommand is called, and it is nowhere to be found. How could I create the chroot env? -- Carry a towel http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/
