Package: wnpp
Severity: wishlist
Owner: Chilledheart
X-Debbugs-Cc: debian-devel@lists.debian.org, huke...@hotmail.com
* Package name: yass
Version : 1.3.13
Upstream Contact: Chilledheart
* URL : https://github.com/Chilledheart/yass
* License : GPLv2
Programm
On 2023-08-09 22:10 +0200, Johannes Schauer Marin Rodrigues wrote:
> it has been a long time since I've analyzed this so things might've changed
> indeed since then. But what I remember is that, depending on the source
> package, running sbuild with --source would produce a different source packag
Hi,
Quoting Guillem Jover (2023-08-09 20:55:17)
> On Wed, 2023-08-09 at 19:55:41 +0200, Johannes Schauer Marin Rodrigues wrote:
> > I would only consider switching the default if at the same time, some checks
> > were done that made sure that the result is bit-by-bit identical to the
> > original.
Hi!
On Wed, 2023-08-09 at 19:55:41 +0200, Johannes Schauer Marin Rodrigues wrote:
> I would only consider switching the default if at the same time, some checks
> were done that made sure that the result is bit-by-bit identical to the
> original.
>
> The source package is the *input* to sbuild no
On August 9, 2023 5:55:41 PM UTC, Johannes Schauer Marin Rodrigues
wrote:
>Hi,
>
>Quoting Stefano Rivera (2023-08-09 14:38:56)
>> Personally, I have my sbuild configured to build a source package after the
>> build, so that I can be sure that I don't regress my own packages' clean
>> target. I
Hi,
Quoting Stefano Rivera (2023-08-09 14:38:56)
> Personally, I have my sbuild configured to build a source package after the
> build, so that I can be sure that I don't regress my own packages' clean
> target. It would be nice if this was a default feature in sbuild, for most
> packages this is
"Jakub Ružička" schreef op 9 augustus 2023 17:11:15 CEST:
>On 23-08-09 15:08, Colin Watson wrote:
>> How will this sort of thing work when a git tree isn't necessarily
>> available at binary package build time, since buildds build binary
>> packages from a source package rather than directly from
On Wed, 2023-08-09 at 18:30 +0300, Adrian Bunk wrote:
> On Wed, Aug 09, 2023 at 02:26:17PM +0800, Paul Wise wrote:
> > On Tue, 2023-08-08 at 18:32 +0300, Adrian Bunk wrote:
> >
> > > Manual opt-in for our > 11k -dev packages is a significant cost
> > > that would have to be justified by the peopl
On Tue, Aug 08, 2023 at 10:26:09AM +0200, Helmut Grohne wrote:
> As a minor data point, I also do not rely on `debian/rules clean` to
> work for reproducing the original source tree, because too many packages
> fail it.
>
> Let me point out though that moving to git-based packaging is not the
> pr
On Wed, Aug 09, 2023 at 02:26:17PM +0800, Paul Wise wrote:
> On Tue, 2023-08-08 at 18:32 +0300, Adrian Bunk wrote:
>
> > Manual opt-in for our > 11k -dev packages is a significant cost
> > that would have to be justified by the people who oppose opt-out.
>
> You could use the Janitor to do autom
On Tue, 2023-08-08 at 18:32 +0300, Adrian Bunk wrote:
> On Tue, Aug 08, 2023 at 09:19:16AM -0300, Antonio Terceiro wrote:
> > On Tue, Aug 08, 2023 at 11:35:01AM +0300, Adrian Bunk wrote:
> > > On Tue, Aug 08, 2023 at 06:46:38AM -, Sune Vuorela wrote:
> > > > On 2023-08-07, Benjamin Drung wrote
On 23-08-09 15:08, Colin Watson wrote:
> How will this sort of thing work when a git tree isn't necessarily
> available at binary package build time, since buildds build binary
> packages from a source package rather than directly from git and the
> source package doesn't usually include a git tree
On Wed, Aug 09, 2023 at 08:31:09AM +0200, Bjørn Mork wrote:
> "Theodore Ts'o" writes:
>
> > I was curious about this, since I rely on snapshots.debian.org in
> > order to create repeatable builds for a file system test appliance, so
> > I started digging a bit. Looking at the debian-bugs pseudo-
On Wed, Aug 09, 2023 at 04:16:29PM +0200, Jakub Ružička wrote:
> * Package name: python-poetry-dynamic-versioning
> Version : 0.25.0
> Upstream Contact: Matthew T. Kennerly
> * URL : https://github.com/mtkennerly/poetry-dynamic-versioning
> * License : Expat
>
Package: wnpp
Severity: wishlist
Owner: Jakub Ružička
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-poetry-dynamic-versioning
Version : 0.25.0
Upstream Contact: Matthew T. Kennerly
* URL : https://github.com/mtkennerly/poetry-dynamic-versioning
*
On 2023-08-09 10:56 +0100, Simon McVittie wrote:
> On Tue, 08 Aug 2023 at 10:26:09 +0200, Helmut Grohne wrote:
> > With this you touch another purpose of `debian/rules clean`: Removing
> > generated files. Since we currently discourage repackaging and
> > `dpkg-source -b` is vaguely happy about del
Hi Sven (2023.08.05_19:01:19_+)
> It might be worth to consider changing your workflow a bit and work with
> a git repository. It does not have to be a clone of the repository (if
> any) where the package is maintained, you can start with a fresh import,
> e.g. with "gbp import-dsc".
>
> Then
On Tue, 08 Aug 2023 at 10:26:09 +0200, Helmut Grohne wrote:
> With this you touch another purpose of `debian/rules clean`: Removing
> generated files. Since we currently discourage repackaging and
> `dpkg-source -b` is vaguely happy about deleted files, a common
> technique for dealing with generat
"Theodore Ts'o" writes:
> I was curious about this, since I rely on snapshots.debian.org in
> order to create repeatable builds for a file system test appliance, so
> I started digging a bit. Looking at the debian-bugs pseudo-package
> "snapshot.debian.org":
>
> https://bugs.debian.org/cgi-bin/p
19 matches
Mail list logo
