Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8478 > unrolled thread
| Started by | Brian May <brian@linuxpenguins.xyz> |
|---|---|
| First post | 2016-05-01 12:30 +0200 |
| Last post | 2016-05-02 05:40 +0200 |
| Articles | 7 — 5 participants |
Back to article view | Back to linux.debian.maint.python
pep8 build depends on jessie Brian May <brian@linuxpenguins.xyz> - 2016-05-01 12:30 +0200
Re: pep8 build depends on jessie Piotr Ożarowski <piotr@debian.org> - 2016-05-01 14:00 +0200
Re: pep8 build depends on jessie Sebastian Ramacher <sramacher@debian.org> - 2016-05-01 14:10 +0200
Re: pep8 build depends on jessie Paul Wise <pabs@debian.org> - 2016-05-01 14:50 +0200
Re: pep8 build depends on jessie Brian May <bam@debian.org> - 2016-05-02 01:10 +0200
Re: pep8 build depends on jessie Paul Wise <pabs@debian.org> - 2016-05-02 05:20 +0200
Re: pep8 build depends on jessie Brian May <bam@debian.org> - 2016-05-02 05:40 +0200
| From | Brian May <brian@linuxpenguins.xyz> |
|---|---|
| Date | 2016-05-01 12:30 +0200 |
| Subject | pep8 build depends on jessie |
| Message-ID | <rtWNs-7Y5-9@gated-at.bofh.it> |
Hello, If I try to build a package on Jessie using sbuild that has "python-pep8 | pep8" in the build depends, it gives me the following error: --- cut --- Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-shortuuid-dummy : Depends: python-pep8 but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use --- cut --- Why isn't it falling back to installing pep8 when python-pep8 is not available? Isn't this the expected behaviour? Or have I got something wrong? Regards -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
[toc] | [next] | [standalone]
| From | Piotr Ożarowski <piotr@debian.org> |
|---|---|
| Date | 2016-05-01 14:00 +0200 |
| Message-ID | <rtYcy-yg-5@gated-at.bofh.it> |
| In reply to | #8478 |
[Brian May, 2016-05-01] > If I try to build a package on Jessie using sbuild that has > "python-pep8 | pep8" in the build depends, it gives me the [...] > Why isn't it falling back to installing pep8 when python-pep8 is not > available? Isn't this the expected behaviour? Or have I got something > wrong? buildds (or sbuild) ignore alternative dependencies and it's on purpose (reproducible builds, etc.) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[toc] | [prev] | [next] | [standalone]
| From | Sebastian Ramacher <sramacher@debian.org> |
|---|---|
| Date | 2016-05-01 14:10 +0200 |
| Message-ID | <rtYmd-UR-9@gated-at.bofh.it> |
| In reply to | #8478 |
[Multipart message — attachments visible in raw view] — view raw
On 2016-05-01 20:21:26, Brian May wrote: > Hello, > > If I try to build a package on Jessie using sbuild that has > "python-pep8 | pep8" in the build depends, it gives me the > following error: > > --- cut --- > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-shortuuid-dummy : Depends: python-pep8 but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. > E: Package installation failed > Not removing build depends: cloned chroot in use > --- cut --- > > Why isn't it falling back to installing pep8 when python-pep8 is not > available? Isn't this the expected behaviour? Or have I got something > wrong? That's expected behavior. sbuild only considers the first alternative. Regards -- Sebastian Ramacher
[toc] | [prev] | [next] | [standalone]
| From | Paul Wise <pabs@debian.org> |
|---|---|
| Date | 2016-05-01 14:50 +0200 |
| Message-ID | <rtYYV-1cd-7@gated-at.bofh.it> |
| In reply to | #8478 |
On Sun, May 1, 2016 at 6:21 PM, Brian May wrote: > "python-pep8 | pep8" in the build depends Why is pep8 in a Build-Depends? It doesn't seem like something that should be used at build time, only at upstream development time. -- bye, pabs https://wiki.debian.org/PaulWise
[toc] | [prev] | [next] | [standalone]
| From | Brian May <bam@debian.org> |
|---|---|
| Date | 2016-05-02 01:10 +0200 |
| Message-ID | <ru8EV-12R-1@gated-at.bofh.it> |
| In reply to | #8482 |
Paul Wise <pabs@debian.org> writes: > On Sun, May 1, 2016 at 6:21 PM, Brian May wrote: > >> "python-pep8 | pep8" in the build depends > > Why is pep8 in a Build-Depends? It doesn't seem like something that > should be used at build time, only at upstream development time. The idea was to allow it to build unchanged on Jessie, which doesn't have python-pep8. However looks like I will have to have "python-pep8" and any backports will need to have this modified. -- Brian May <bam@debian.org>
[toc] | [prev] | [next] | [standalone]
| From | Paul Wise <pabs@debian.org> |
|---|---|
| Date | 2016-05-02 05:20 +0200 |
| Message-ID | <rucyR-44T-1@gated-at.bofh.it> |
| In reply to | #8483 |
On Mon, May 2, 2016 at 7:06 AM, Brian May wrote: > The idea was to allow it to build unchanged on Jessie, which doesn't > have python-pep8. I guess my question wasn't clear enough. I was asking why pep8/python-pep8 are used at build time at all. They are tools for checking style, there is no reason to use them at build time at all. -- bye, pabs https://wiki.debian.org/PaulWise
[toc] | [prev] | [next] | [standalone]
| From | Brian May <bam@debian.org> |
|---|---|
| Date | 2016-05-02 05:40 +0200 |
| Message-ID | <rucSd-4fR-1@gated-at.bofh.it> |
| In reply to | #8484 |
Paul Wise <pabs@debian.org> writes: > I guess my question wasn't clear enough. I was asking why > pep8/python-pep8 are used at build time at all. They are tools for > checking style, there is no reason to use them at build time at all. Good question. However not my package, I am simply doing a NMU on a RC bug for a package another package I tried to fix requires. At quick glance it looks like the upstream tests incooporate flake8 tests. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818060 -- Brian May <bam@debian.org>
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web