Hi!
...
> That setup sounds nice! What is your workflow to import a new upstream
> release?
>
> I see the watch file still points to the tarball:
>
> https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/watch
>
> Would it be possible to extend the debian/watch syntax t
Package: wnpp
Severity: wishlist
Owner: Philipp Kern
* Package name: yubikey-touch-detector
Version : 1.11.0-1
Upstream Author : Maxim Baz
* URL : https://github.com/maximbaz/yubikey-touch-detector
* License : ISC
Programming Lang: Go
Description : tool
Package: wnpp
Severity: wishlist
Owner: Philipp Kern
* Package name: golang-github-vtolstov-go-ioctl
Version : 0.0~git20151206.6be9cce-1
Upstream Author : Vasiliy Tolstov
* URL : https://github.com/vtolstov/go-ioctl
* License : MIT
Programming Lang: Go
Desc
On Sun Oct 6, 2024 at 4:45 PM BST, Andreas Metzler wrote:
> If you do not rename signify(src) to signify-mail(src) the bts might mix
> up bugs against signify(bin) from signify-openbsd(src) with bugs against
> the source package signify.
Do we know in which direction the problem might occur? signi
On 2024-10-06 17:45:46 +0200 (+0200), Andreas Metzler wrote:
[...]
> If you do not rename signify(src) to signify-mail(src) the bts might mix
> up bugs against signify(bin) from signify-openbsd(src) with bugs against
> the source package signify.
>
> Renaming signify-openbsd(src) to signify(src) w
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: bedstead
Version : 002.008
Upstream Contact: Ben Harris
* URL : https://bjh21.me.uk
* License : CC0-1.0; parts effectively out of copyright due to age
Programming Lan
On Sun, 2024-10-06 at 17:45 +0200, Andreas Metzler wrote:
> On 2024-10-06 Simon Josefsson wrote:
> [...]
> > I agree in principle, but I wonder if going through the effort of
> > introducing a new source package 'signify-mail' and removing the current
> > 'signify' will give us anything beyond doi
On Sun, 2024-10-06 at 09:45 +0200, Simon Josefsson wrote:
[...]
> I agree in principle, but I wonder if going through the effort of
> introducing a new source package 'signify-mail' and removing the current
> 'signify' will give us anything beyond doing the QA package upload to
> rename the binary
On 2024-10-06 Simon Josefsson wrote:
[...]
> I agree in principle, but I wonder if going through the effort of
> introducing a new source package 'signify-mail' and removing the current
> 'signify' will give us anything beyond doing the QA package upload to
> rename the binary package.
> The only
Marco d'Itri writes:
> On Oct 05, Simon Josefsson wrote:
>
>> I would like that 'apt install signify' install OpenBSD's signify (from
>> the Debian 'signify-openbsd' package) and not the 2003 mail-related
>> signify perl script from the Debian 'signify' source package.
> Agreed: the current sign
On Sun, 06 Oct 2024 at 10:02:56 +0200, Simon Josefsson wrote:
> Otto Kekäläinen writes:
> > git-buildpackage supports dual import from both upstream git and
> > tarball to maximize supply chain auditability.
>
> That setup sounds nice! What is your workflow to import a new upstream
> release?
T
Otto Kekäläinen writes:
>> No objections to have this kind of capability, but I still strongly
>> believe that importing tar archives is highly suboptimal and directly
>> branching off the upstream git repository is an highly superior workflow
>> and should be used as much as possible.
>>
>> This
Hi.
This turned out to be a non-issue. vzlogger creates a system user. So
this only affects the projects backport to buster.
Thanks for the answers, they helped me understanding this.
Joachim
Ben Hutchings writes:
> On Sat, 2024-10-05 at 20:15 +0200, Simon Josefsson wrote:
>> Ben Hutchings writes:
>>
>> > On Sat, 2024-10-05 at 12:31 +0200, Simon Josefsson wrote:
>> > [...]
>> > > This will rename the binary package to 'signify-mail', as suggested in
>> > > the first bug report above
14 matches
Mail list logo
