Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1111080 > unrolled thread

Bug#937085: [Pkg-mozext-maintainers] Bug#937085: mozilla-devscripts: Python2 removal in sid/bullseye

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#937085: [Pkg-mozext-maintainers] Bug#937085: mozilla-devscripts: Python2 removal in sid/bullseye Håvard F. Aasen <havard.f.aasen@pfft.no> - 2022-07-27 10:50 +0200
    Bug#937085: [Pkg-mozext-maintainers] Bug#937085: mozilla-devscripts: Python2 removal in sid/bullseye Paul Gevers <elbrus@debian.org> - 2022-08-01 21:40 +0200

#1111080 — Bug#937085: [Pkg-mozext-maintainers] Bug#937085: mozilla-devscripts: Python2 removal in sid/bullseye

Hi,

On Thu, 03 Sep 2020 00:23:42 +0200 Benjamin Drung <bdrung@debian.org> wrote:
> Hi Jann,
> 
> Am Montag, den 31.08.2020, 22:58 +0200 schrieb Jann Haber:
> > Hi all,
> > 
> > I just updated the MR on Salsa for redland-bindings, it now
> > successfully creates a python3-librdf package instead of the python-
> > librdf package. This change still needs to be tested, however it
> > looks good, since the build process runs without obvious errors. The
> > upload to unstable I assume needs to be done together with mozilla-
> > devscripts, once it is also converted to python3.
> 
> Thanks for working on it.
> 
> > Benjamin, you have done some work on mozilla-devscripts and got stuck
> > since redland-bindings were python2 only.
> 
> I checked if I had code locally and found two commits (one work in
> progress) for the Python 3 migration. I pushed both into the "python3"
> branch on GitLab:
> https://salsa.debian.org/webext-team/webext-devscripts/-/commits/python3
> 
> Feel free to pick that up and finish it.
> 
I have continued working on the redland-bindings package, cleaned it up a
bit, and enabled the Python 3 testsuite. I created an MR [1]. I believe 
redland-bindings is ready to be uploaded to NEW/unstable.

> > Can you provide any insight on how to test the new package properly?
> > What would be the next steps for mozilla-devscripts?
> 
> Next steps would be: Finish the Python 3 migration of mozilla-
> devscripts from the "python3" branch. Check that the package builds
> (IIRC it runs some Python code checker on build).

Is this part done, so it's ready to begin testing?
> 
> To test that the Python 3 migration did not break anything, I would
> take a bunch of webext package (that build depend on mozilla-
> devscripts) and rebuild them (once with the current package and once
> with the Python 3 port). Then use diffoscope to compare the content of
> the two builds to be identical (same generated dependencies, same
> paths, etc). That should give us confidence to not break anything.

Did I look in the wrong place? when doing:
$ apt-cache rdepends mozilla-devscripts
Reverse Depends:
  devscripts

Which is only in the suggests section.

> 
> -- 
> Benjamin Drung
> Debian & Ubuntu Developer
> 
> 
> 


Regards,
Håvard

[1] https://salsa.debian.org/debian/redland-bindings/-/merge_requests/2

[toc] | [next] | [standalone]

#1111696

[Multipart message — attachments visible in raw view] — view raw

Hi Håvard, all,

On Wed, 27 Jul 2022 10:37:25 +0200 =?UTF-8?Q?H=c3=a5vard_F=2e_Aasen?= 
<havard.f.aasen@pfft.no> wrote:
> I have continued working on the redland-bindings package, cleaned it up a
> bit, and enabled the Python 3 testsuite. I created an MR [1]. I believe 
> redland-bindings is ready to be uploaded to NEW/unstable.

I just uploaded it to NEW/experimental. Which means that once accepted 
we can iron out mozilla-devscripts there too.

> > To test that the Python 3 migration did not break anything, I would
> > take a bunch of webext package (that build depend on mozilla-
> > devscripts) and rebuild them (once with the current package and once
> > with the Python 3 port). Then use diffoscope to compare the content of
> > the two builds to be identical (same generated dependencies, same
> > paths, etc). That should give us confidence to not break anything.
> 
> Did I look in the wrong place? when doing:
> $ apt-cache rdepends mozilla-devscripts
> Reverse Depends:
>   devscripts
> 
> Which is only in the suggests section.

You need the reverse *build* depends.

paul@mulciber ~ $ reverse-depends -b mozilla-devscripts
Reverse-Testsuite-Triggers
* devscripts

Reverse-Build-Depends
* autofill-forms
* devscripts
* dispmua
* mozilla-noscript
* tinyjsd
* tree-style-tab
* umatrix

Paul

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web