Your message dated Sun, 2 Jun 2024 17:43:40 +0800 with message-id <CAKq8=3+trav7NiJvqT9hjCH9B2do344a61xS2ucCnZb_8oNO_g@mail.gmail.com> and subject line Re: Bug#1072258: RFS: opam/2.1.6+dfsg-1 [RC] [Team] -- package manager for OCaml has caused the Debian Bug report #1072258, regarding RFS: opam/2.1.6+dfsg-1 [RC] [Team] -- package manager for OCaml to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1072258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072258 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: RFS: opam/2.1.6+dfsg-1 [RC] [Team] -- package manager for OCaml
- From: Bo YU <tsu.yubo@gmail.com>
- Date: Fri, 31 May 2024 10:39:10 +0800
- Message-id: <20240531023910.rmrcqskekjic3q6f@debian>
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "opam": * Package name : opam Version : 2.1.6+dfsg-1 Upstream contact : [fill in name and email of upstream] * URL : https://opam.ocaml.org * License : FSFUL, Other, BSD-3, LGPL-3 with linking exception * Vcs : https://salsa.debian.org/ocaml-team/opam Section : ocaml The source builds the following binary packages: opam - package manager for OCaml opam-doc - package manager for OCaml (documentation) opam-installer - Utility handling (un)installation of Opam .install files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opam/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opam/opam_2.1.6+dfsg-1.dsc Changes since the last upload: opam (2.1.6+dfsg-1) UNRELEASED; urgency=medium . * Team upload. * Add 0003-opam-dune-3.11.patch to fix ftbfs issue. (Closes: #1054822) * Exclude these two files * New upstream version 2.1.6+dfsg * Rebase debian/patches * Add upstream metadata * Set std-ver to 4.7.0 -- Regards, -- Bo YUAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: Gianfranco Costamagna <locutusofborg@debian.org>
- Cc: "philip.wyett@kathenas.org" <philip.wyett@kathenas.org>, 1072258-done@bugs.debian.org
- Subject: Re: Bug#1072258: RFS: opam/2.1.6+dfsg-1 [RC] [Team] -- package manager for OCaml
- From: Bo YU <tsu.yubo@gmail.com>
- Date: Sun, 2 Jun 2024 17:43:40 +0800
- Message-id: <CAKq8=3+trav7NiJvqT9hjCH9B2do344a61xS2ucCnZb_8oNO_g@mail.gmail.com>
- In-reply-to: <[🔎] 1126472219.973543.1717262672127@mail.yahoo.com>
- References: <4d76f03c-a948-4bd8-92e2-8d081af78b68@debian.org> <CAKq8=3LRMiGLTMqh_9OV3-s9Xnqm7MtFYeY+OpmRUW5AkCqAhg@mail.gmail.com> <1620230364.385069.1717156789915@mail.yahoo.com> <CAKq8=3+sX8W4FssvO_iVE0HHH+bK8R3Wbn922AMZEZhMQhi2-Q@mail.gmail.com> <765096393.508334.1717166514253@mail.yahoo.com> <CAKq8=3+w077s9MZsxm9Z-p9CGCpKS-nBAB26XXb7eqJdNArEYw@mail.gmail.com> <629183388.563447.1717171538384@mail.yahoo.com> <CAKq8=3J2kW2RaDjDv2uLthj2BesR74a85Cm9BZiOX87wg-VN=w@mail.gmail.com> <789260968.580780.1717173343551@mail.yahoo.com> <726197973.589777.1717173531041@mail.yahoo.com> <[🔎] CAKq8=3+NByeLQ4=RQ-9CpRFvA9kTX42HdQ4ut6pkP8QL3rk7xg@mail.gmail.com> <20240531023910.rmrcqskekjic3q6f@debian> <[🔎] 1883079048.941255.1717256962002@mail.yahoo.com> <[🔎] CAKq8=3+acEDo+_cee_br9YBh4XQJms_79--Ng_Z_2wGSKBPaoQ@mail.gmail.com> <[🔎] 1126472219.973543.1717262672127@mail.yahoo.com>
Hi, On Sun, Jun 2, 2024 at 1:24 AM Gianfranco Costamagna <locutusofborg@debian.org> wrote: > > Hello, > > >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 > > My workflow is: > 1. git clone > 2. uscan --debug > 3. gbp import-orig --pristine-tar ../tarball.path > 4. quilt push/quilt refresh > 5. gbp build-package -S -d --git-tag > > For some reasons, the gbp import orig is doing something weird when used with uscan? > (no big deal, I don't think this is a trouble, except that I like when the tarball has the same md5sum hash as the upstream one) Thanks for uploading again. This explanation also reduces my anxiety about messing up or not the package again.:) Okay, I will fix other issues as the salsa ci hint there. Thanks all, BR, Bo > > G.
--- End Message ---