Bug#1072258: RFS: opam/2.1.6+dfsg-1 [RC] [Team] -- package manager for OCaml
On Sat, Jun 1, 2024 at 11:51 PM Gianfranco Costamagna
<locutusofborg@debian.org> wrote:
>
> Hello, I did upload the package, but for some reasons
>
> uscan --debug --force-download
> creates a different tarball with respect to the one on pristine-tar branch
>
> I used the upstream one, please check and explain your import workflow, because I can't understand why your name is on the files:
> ls -l opam_2.1.6.orig.tar.gz*
> -rw-rw-r-- 1 locutus locutus 836482 giu 1 17:42 opam_2.1.6.orig.tar.gz.upstream
> -rw-rw-r-- 1 locutus locutus 837526 giu 1 17:42 opam_2.1.6.orig.tar.gz.pristine-tar
>
> e.g.
> diffoscope opam_2.1.6.orig.tar.gz.upstream opam_2.1.6.orig.tar.gz.pristine-tar |grep README
> │ │ --rw-rw-r-- 0 root (0) root (0) 10200 2024-05-16 10:28:46.000000 opam-2.1.6/README.md
> │ │ +-rw-rw-r-- 0 vimer (1000) vimer (1000) 10200 2024-05-16 10:28:46.000000 opam-2.1.6/README.md
>
hmm, what is wrong with me? My import workflow is below:
1. git clone xx.git(I forked this one)
2. gbp pq import
3. gbp import-orig --pristine-tar --uscan
4. gbp pq rebase
5. gbp pq export
6. commit to master then push
>
>
> (all the files have different UID/GID)
>
> will upload the upstream tarball, feel free to address the remaining bits in a subsequent upload!
Okay, sorry for the trouble again. But today I learn many!
BR,
Bo
>
> G.
>
>
>
> Il sabato 1 giugno 2024 alle ore 16:48:27 CEST, Bo YU <tsu.yubo@gmail.com> ha scritto:
>
>
>
>
>
> Hi,
>
> On Sat, Jun 1, 2024 at 12:38 AM Gianfranco Costamagna
> <locutusofborg@debian.org> wrote:
> >
> > Merged the two commits
> > https://salsa.debian.org/ocaml-team/opam/-/merge_requests/10
> >
>
> \o/. Thanks.
> > let me know once you have something that passes pipelines then!
>
> Yeah, now I am trying to address another regression on reprotest:
> https://salsa.debian.org/ocaml-team/opam/-/jobs/5795589
>
> BR,
> Bo
>
> >
> > G.
> >
> >
> >
> >
> >
> >
> > Il venerdì 31 maggio 2024 alle ore 18:35:43 CEST, Gianfranco Costamagna <locutusofborg@debian.org> ha scritto:
> >
> >
> >
> >
> >
> > Adding it to debian/clean makes the build go to the end
> > now failing autopkgtests and similar.
> >
> > I would merge, feel free to continue from there, and please let me know when to upload.
> >
> >
> >
> >
> >
> >
> > Il venerdì 31 maggio 2024 alle ore 18:15:29 CEST, Bo YU <tsu.yubo@gmail.com> ha scritto:
> >
> >
> >
> >
> >
> > On Sat, Jun 1, 2024 at 12:05 AM Gianfranco Costamagna
> > <locutusofborg@debian.org> wrote:
> > >
> > > pipeline failed again :/
> > >
> >
> > No worried. Only it passes the extract-source phrase. The pipeline was
> > failed also in the past.
> >
> > BR,
> > Bo
> >
> > >
> > >
> > >
> > >
> > >
> > > Il venerdì 31 maggio 2024 alle ore 16:57:24 CEST, Bo YU <tsu.yubo@gmail.com> ha scritto:
> > >
> > >
> > >
> > >
> > >
> > > On Fri, May 31, 2024 at 10:41 PM Gianfranco Costamagna
> > > <locutusofborg@debian.org> wrote:
> > > >
> > > > Hello, I downloaded both
> > > > https://github.com/ocaml/opam/releases/download/2.1.6/opam-full-2.1.6.tar.gz
> > > > and
> > > > https://github.com/ocaml/opam/archive/refs/tags/2.1.6.tar.gz
> > > >
> > > > ls -l 1/opam-full-2.1.6/appveyor_build.cmd 2/opam-2.1.6/appveyor_build.cmd
> > > > -rw-r--r-- 1 locutus locutus 10160 mag 16 14:02 1/opam-full-2.1.6/appveyor_build.cmd
> > > > -rw-rw-r-- 1 locutus locutus 10160 mag 16 12:28 2/opam-2.1.6/appveyor_build.cmd
> > > >
> > > > So,
> > > >
> > > > to me looks like we can commit on master the bits changes, and then import the new version without dfsg and forget about this issue?
> > > >
> > > > https://salsa.debian.org/ocaml-team/opam/-/merge_requests/10
> > > >
> > > > Looks working for me, if you are ok, I can do, otherwise feel free to cherry-pick from my branch!
> > >
> > > Okay, this looks good to me. Please commit on master first and then I
> > > will do a team upload with a new upstream release.
> > > Thanks.
> > >
> > > BR,
> > > Bo
> > >
> > > >
> > > > G.
> > >
> >
> >
>
Reply to: