-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello dear engineers.
I have prepared some new packages for Debian, would you be interested?
These packages have been verified and have the confirmed tags.
1. vifm
RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093235
https
On Fri, Jan 24, 2025 at 12:01:53PM +, Arif Ali wrote:
> > >- executable-in-usr-lib
> > >- repeated-path-segment
> > >- no-manual-page
> > >
> >
>
> The key one was, if my first upload had the above 3 lintian issues, would
> DDs be willing to accept the package on the premise that I
On Fri, 24 Jan 2025 at 12:29, Andrey Rakhmatullin wrote:
> On Fri, Jan 24, 2025 at 10:00:10AM +, Arif Ali wrote:
> > Hi mentors,
> >
> > I am working on an ITP [1] for avocado, and have an interest in this
> > package for testing framework for sosreport, which is a package I am
> > maintainin
On Fri, Jan 24, 2025 at 10:00:10AM +, Arif Ali wrote:
> Hi mentors,
>
> I am working on an ITP [1] for avocado, and have an interest in this
> package for testing framework for sosreport, which is a package I am
> maintaining.
>
> However, currently it has various lintian errors, which I am w
Hi mentors,
I am working on an ITP [1] for avocado, and have an interest in this
package for testing framework for sosreport, which is a package I am
maintaining.
However, currently it has various lintian errors, which I am working
through with upstream at the moment.
We are very close, but want
On Sat, 2025-01-18 at 11:24 +, Phil Wyett wrote:
> Hi DD's and all,
>
> Below is a listing of 'confirmed' packages from Debian Mentors that required
> DD
> review and possible sponsorship. If you could spare the time for these
> packages, it would be mu
On Sat, Jan 18, 2025 at 02:07:43PM -0500, Tiago Bortoletto Vaz wrote:
> > > It is very much appreciated that you were diligent and consulted
> > > documentation (and this list) before trying to sponsor packages as a DM.
> > > Technically, it's not p
Hi Christian,
On Sat, Jan 18, 2025 at 04:55:55PM GMT, Christian Kastner wrote:
> Hi Tiago,
>
> On 2025-01-17 14:51, Tiago Bortoletto Vaz wrote:
> > It is very much appreciated that you were diligent and consulted
> > documentation (and this list) before trying to spo
Hi Tiago,
On 2025-01-17 14:51, Tiago Bortoletto Vaz wrote:
> It is very much appreciated that you were diligent and consulted
> documentation (and this list) before trying to sponsor packages as a DM.
> Technically, it's not possible. See:
>
> https://wiki.debian.
On Sat, 2025-01-18 at 12:52 +0100, Simon Josefsson wrote:
> Phil Wyett writes:
>
> > #1084884 RFS: golang-github-regclient-regclient [ITP] -- Docker and OCI
> > Registry Client (tooling)
> > RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084884
> > dget -x
> > https://mentors.debian.net/
Phil Wyett writes:
> #1084884 RFS: golang-github-regclient-regclient [ITP] -- Docker and OCI
> Registry Client (tooling)
> RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084884
> dget -x
> https://mentors.debian.net/debian/pool/main/g/golang-github-regclient-regclient/golang-github-regcl
Hi DD's and all,
Below is a listing of 'confirmed' packages from Debian Mentors that required DD
review and possible sponsorship. If you could spare the time for these
packages, it would be much appreciated.
#1078171 RFS: rsplib -- RSerPool implementation RSPLIB
RFS: https://bugs
Hi Cordell,
On Thu, Jan 16, 2025 at 03:36:15PM GMT, Cordell Bloor wrote:
> Hello,
>
> I'm a Debian Maintainer with upload permissions for various packages in the
> ROCm GPU compute stack. The Debian ROCm Team has a few Sponsored Maintainers
> contributing to our packages, bu
On Fri, Jan 17, 2025 at 07:23:51AM +0100, Geert Stappers wrote:
> > This all seems consistent with the theory that it would be inappropriate for
> > me as a Debian Maintainer to sponsor an upload from a Sponsored Maintainer,
> > even if I have permission to independently upload my own changes for t
On Thu, Jan 16, 2025 at 03:36:15PM -0700, Cordell Bloor wrote:
> Hello,
Hi there,
> I'm a Debian Maintainer with upload permissions for various packages in the
> ROCm GPU compute stack. The Debian ROCm Team has a few Sponsored Maintainers
> contributing to our packages, but i
Hello,
I'm a Debian Maintainer with upload permissions for various packages in
the ROCm GPU compute stack. The Debian ROCm Team has a few Sponsored
Maintainers contributing to our packages, but is short on Debian
Developers to review them. One of the DDs that I work with has suggested
t
Control: tags -1 -confirmed
Control: tags -1 +moreinfo
Aidan,
Preamble...
Thank you for taking the time to prepare this package and your contribution to
the Debian project.
This review is offered to help package submitters to Debian mentors inorder to
improve their packages prior to possible
On 27.11.24 04:31, Soren Stoutner wrote:
On Tuesday, November 26, 2024 3:42:39 PM MST Preuße, Hilmar wrote:
Am 19.11.2024 um 23:39 schrieb Hilmar Preuße:
Hi,
How do I have to name the additional tar balls? Putting the needed
directory into the tar balls does not seem to do the trick. Current
Hi!
On Thu, 2024-11-28 at 09:30:15 -0300, Santiago Ruano Rincón wrote:
> This is what grep does [0]:
>
> #!/bin/sh
> set -e
>
> export DEB_BUILD_PROFILES="nocheck nodoc" DEB_BUILD_OPTIONS="nocheck
> nodoc"
>
> dpkg-source --before-build `pwd`
Nit: I'd probably use «$(pwd)» her
Hi!
[ Perhaps you already managed to solve this, but just in case. :) ]
On Thu, 2024-11-28 at 12:43:05 +0100, Santiago Vila wrote:
> Many GNU packages have built-in tests that test the just-built programs.
>
> Is there a general procedure/trick/idiom to modify them so that they t
Hi Santiago,
Am Thu, Nov 28, 2024 at 09:30:15AM -0300 schrieb Santiago Ruano Rincón:
> > Many GNU packages have built-in tests that test the just-built programs.
This reminds me to my attempt to write some autopkgtest for tar. I've
created an according bug report[1] (in CC) but I d
On Thu, 28 Nov 2024 12:43:05 +0100
Santiago Vila wrote:
> Dear mentors:
>
> Many GNU packages have built-in tests that test the just-built
> programs.
>
> Is there a general procedure/trick/idiom to modify them so that
> they test the installed version instead? (so that
Hey tocayo,
El 28/11/24 a las 12:43, Santiago Vila escribió:
> Dear mentors:
>
> Many GNU packages have built-in tests that test the just-built programs.
>
> Is there a general procedure/trick/idiom to modify them so that they test
> the installed version instead? (so that
Dear mentors:
Many GNU packages have built-in tests that test the just-built programs.
Is there a general procedure/trick/idiom to modify them so that they test
the installed version instead? (so that they can be reused with minimal
changes).
(I'd like to do this for several packages wi
On Tuesday, November 26, 2024 3:42:39 PM MST Preuße, Hilmar wrote:
> Am 19.11.2024 um 23:39 schrieb Hilmar Preuße:
>
> Hi,
>
>
> > How do I have to name the additional tar balls? Putting the needed
> > directory into the tar balls does not seem to do the trick. Currently my
> > only idea is to
Am 19.11.2024 um 23:39 schrieb Hilmar Preuße:
Hi,
How do I have to name the additional tar balls? Putting the needed
directory into the tar balls does not seem to do the trick. Currently my
only idea is to merge the two tar balls into one and name it
asyorig-acextlibs.tar.xz .
Hopefully
Hi Hilmar,
On 2024-11-24 00:48, Preuße, Hilmar wrote:
Am 21.11.2024 um 08:32 schrieb Andrius Merkys:
I can confirm this from my practical experience. Nevertheless you
should be able to make your build work by symlinking a component to
the needed subdirectory.
That seems to be a good ideas, w
Am 21.11.2024 um 08:32 schrieb Andrius Merkys:
On 2024-11-20 22:16, Soren Stoutner wrote:
Hello Andrius,
I don’t think MUT (Multiple Upstream Tarballs) has any provisions
for unpacking them to `acextlibs/ vectorgraphics/LspCpp`.
I can confirm this from my practical experience. Nevertheless
Hi,
On 2024-11-20 22:16, Soren Stoutner wrote:
On Tuesday, November 19, 2024 3:39:06 PM MST Hilmar Preuße wrote:
I hope this is an easy question: the new version of asymptote downloads
additional tar balls (two) during configure, which are unpackaged and
used during build. Page [1] describes ho
On Tuesday, November 19, 2024 3:39:06 PM MST Hilmar Preuße wrote:
> Hello,
>
> I hope this is an easy question: the new version of asymptote downloads
> additional tar balls (two) during configure, which are unpackaged and
> used during build. Page [1] describes how to add additional tar balls.
s to merge the two tar balls into one and name it
asyorig-acextlibs.tar.xz .
Better ideas?
Thanks,
Hilmar
[1]
https://raphaelhertzog.com/2010/09/07/how-to-use-multiple-upstream-tarballs-in-debian-source-packages/
--
Testmail
OpenPGP_signature.asc
Description: OpenPGP digital signature
Hi,
Just for awareness: Debian already has Debcraft, which builds Debian
packages in an isolated Docker environment. It supports both Docker
and Podman, and it also has a bunch of other automation to help do
quick rebuilds of packages after modifications, and compare how the
end result changed
Dear all DDs,
Below is a package list of the currently "confirmed", as being in good order
packages that are awaiting a DD review and possible upload to Debian. If DDs
could spare the time to pick up a package or two and finish off the package
mentor process it would be greatly a
improve their packages prior to
possible sponsorship into Debian. There is no obligation on behalf of the
submitter to make any alterations based upon information provided in the
review.
Review...
1. Build:
* pbuilder [1]: Good
* sbuild [2]: Good
2. Lintian [3]: Good
3. Licenses [4]: Good
4
ll DDs,
It has been suggested that I need to supply a list of the current "confirmed"
packages requiring a sponsor that need a DD to review and possibly upload to
Debian when ready. Below is that list.
#1072910 RFS: lsp-treemacs/0.5-1 -- treemacs integration for Emacs LSP
RFS: https://bugs
Dear all DDs,
Below is the link to the page of currently "confirmed" as being in good order
packages that are awaiting a DD review and possible upload to Debian. If DDs
could spare the time to pick up a package or two and finish off the package
mentor process it would be greatly a
cs-buttercup
> > >>>Version : 1.36-1
> > >>>Upstream contact : Jorgen Schaefer
> > >>> * URL : https://github.com/jorgenschaefer/emacs-buttercup/
> > >>> * License : GPL-3+, GFDL-1.2+ or CC-BY-SA-3
haefer
> >>> * URL : https://github.com/jorgenschaefer/emacs-buttercup/
> >>> * License : GPL-3+, GFDL-1.2+ or CC-BY-SA-3.0
> >>> * Vcs :
> >>> https://salsa.debian.org/emacsen-team/emacs-buttercup
> >>>S
1.36-1
>Upstream contact : Jorgen Schaefer
> * URL : https://github.com/jorgenschaefer/emacs-buttercup/
> * License : GPL-3+, GFDL-1.2+ or CC-BY-SA-3.0
> * Vcs : https://salsa.debian.org/emacsen-team/emacs-buttercup
>Section : lisp
Control: tags -1 +confirmed
Xyue,
Preamble...
Thank you for taking the time to prepare this package and your contribution
to the Debian project.
The review below is for assistance. This review is offered to help package
submitters to Debian mentors inorder to improve their packages prior to
Control: tags -1 +confirmed
Xiyue,
Preamble...
Thank you for taking the time to prepare this package and your contribution
to the Debian project.
The review below is for assistance. This review is offered to help package
submitters to Debian mentors inorder to improve their packages prior to
Dear all DDs,
Below is the link to the page of currently "confirmed" being in good order
packages that are awaiting a DD review and possible upload. If DDs could
spare the time to pick up a package or two and finish off the package mentor
process it would be greatly appreciat
On Thu, Aug 01, 2024 at 08:18:04AM +0300, Tommi Höynälänmaa wrote:
> Hello
>
> Packages theme-d and theme-d-intr are to be autoremoved from testing on
> August 30. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074756. I
> think that this bug is a bug in guile and not i
Hello
Packages theme-d and theme-d-intr are to be autoremoved from testing on
August 30. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074756. I think that
this bug is a bug in guile and not in theme-d and I have filed bug
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=72407 for
Evening all Debian Developers,
Below is a curated list of packages in Debian Mentors[1] that are felt to be
ready for review and possible sponsorship into Debian.
rumur - https://mentors.debian.net/package/rumur/
RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071427
c-evo-dh - https
Control: tags -1 + moreinfo
Aidan,
Preamble...
Thank you for taking the time to create this package and your contribution to
the Debian project.
The below review is for assistance. It is offered to help submitters of
packages to Debian mentors improve their packages prior to possible
On Tue, Jun 11, 2024 at 07:09:15PM +, David James wrote:
> These examples were exactly what I needed, thank you both. One more
> thing: When running a package builder such as dpkg, does dh run once
> for each item in DEB_BUILD_PROFILES?
Are you really asking about DEB_BUILD_PROFILES? Because I
uild in two dirs, like
> https://tracker.debian.org/media/packages/c/curl/rules-8.8.0-1
>
> --
> WBR, wRAR
These examples were exactly what I needed, thank you both. One more
thing: When running a package builder such as dpkg, does dh run once
for each item in DEB_BUILD_PROFILES?
Regards,
David James
On Mon, Jun 10, 2024 at 12:58:01PM +0200, Lorenzo wrote:
> > If I wish to create two binary packages with different
> > configurations from a single source package (e.g. to support
> > different ISA levels), what's the best way to implement this?
>
> I'm not su
Hi,
On Sat, 08 Jun 2024 15:54:16 +
David James wrote:
> Dear Mentors,
>
> If I wish to create two binary packages with different
> configurations from a single source package (e.g. to support
> different ISA levels), what's the best way to implement this?
I'm n
Dear Mentors,
If I wish to create two binary packages with different
configurations from a single source package (e.g. to support
different ISA levels), what's the best way to implement this?
If I have package-name-feature-1, package-name-feature-2 and
package-name-data in d/control, how
* License : LGPL-2.0+
* Vcs : https://github.com/aidan-gallagher/debpic.git
The source builds the following binary packages:
debpic
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/debpic/
<ht
Jeremy Sowden writes:
> On 2024-04-12, at 19:50:58 +0800, Sean Whitton wrote:
>> On Fri 12 Apr 2024 at 12:44pm +01, Jeremy Sowden wrote:
>> > On 2024-04-12, at 17:53:15 +0800, Sean Whitton wrote:
>> > > Do you have your 1.34 upload of buttercup in git, please?
>> >
>> > Yup, it's all on Salsa.
>>
On 2024-04-12, at 19:50:58 +0800, Sean Whitton wrote:
> On Fri 12 Apr 2024 at 12:44pm +01, Jeremy Sowden wrote:
> > On 2024-04-12, at 17:53:15 +0800, Sean Whitton wrote:
> > > Do you have your 1.34 upload of buttercup in git, please?
> >
> > Yup, it's all on Salsa.
>
> Er. I got confused, then, d
Hello,
On Fri 12 Apr 2024 at 12:44pm +01, Jeremy Sowden wrote:
> On 2024-04-12, at 17:53:15 +0800, Sean Whitton wrote:
>> Do you have your 1.34 upload of buttercup in git, please?
>
> Yup, it's all on Salsa.
Er. I got confused, then, didn't I? Should this RFS be closed?
--
Sean Whitton
sig
On 2024-04-12, at 17:53:15 +0800, Sean Whitton wrote:
> Do you have your 1.34 upload of buttercup in git, please?
Yup, it's all on Salsa.
J.
> Xiyue, you need to merge in the 1.34 upload, either something from
> Jeremy, or we can fall back to merging from dgit/sid. This has
> happened a few tim
Hello Jeremy,
Do you have your 1.34 upload of buttercup in git, please?
Xiyue, you need to merge in the 1.34 upload, either something from
Jeremy, or we can fall back to merging from dgit/sid. This has happened
a few times now -- please check whether you're missing uploads before
starting to wor
efer/emacs-buttercup/
* License : GFDL-1.2+ or CC-BY-SA-3.0, GPL-3+
* Vcs : https://salsa.debian.org/emacsen-team/emacs-buttercup
Section : lisp
The source builds the following binary packages:
elpa-buttercup - behaviour-driven testing for Emacs Lisp packages
On Sat, Mar 30, 2024 at 03:32:53PM -0400, Qianqian Fang wrote:
> info: Hint: make sure the version in debian/changelog matches the unpacked
> source tree
You should do this.
> for pybj, ci tasks finished ok, but the test-crossbuild-arm64 job failed
>
> https://salsa.debian.org/science-team/pybj/-
hi everyone,
in 2020, I learned how to package debian packages and created two python
packages
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964993
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964994
over the last few years, the upstream git repos of both projects had
been updated
Your message dated Tue, 19 Mar 2024 22:16:05 +
with message-id <20240319221605.GC31740@celephais.dreamlands>
and subject line Uploaded
has caused the Debian Bug report #1067028,
regarding RFS: emacs-buttercup/1.34-1 [Team] -- behaviour-driven testing for
Emacs Lisp packages
to be mar
Section : lisp
>
> The source builds the following binary packages:
>
> elpa-buttercup - behaviour-driven testing for Emacs Lisp packages
>
> To access further information about this package, please visit the following
> URL:
>
> https://mentors.debian.net/packa
Hi Soren,
thanks for moving the projects.
> Gesendet: Montag, 18. März 2024 um 17:12 Uhr
> Von: "Soren Stoutner"
> An: debian-mentors@lists.debian.org
> Cc: "Sven Wick"
> Betreff: Re: Moving my packages to the debian namespace on salsa?
>
> Sven,
&
ndered that myself for some time.
> Actually since my package [2]ssh-tools was moved into the debian namespace a
> while ago.
>
> I have no issue if my [3]other packages are moved there as well
> if that is considered best practice.
>
> What do I have to do for moving my
Hi,
I was reading the discussion [1]"Question about the debian group on Salsa"
because I wondered that myself for some time.
Actually since my package [2]ssh-tools was moved into the debian namespace a
while ago.
I have no issue if my [3]other packages are moved there as well
github.com/jorgenschaefer/emacs-buttercup/
* License : GFDL-1.2+ or CC-BY-SA-3.0, GPL-3+
* Vcs : https://salsa.debian.org/emacsen-team/emacs-buttercup
Section : lisp
The source builds the following binary packages:
elpa-buttercup - behaviour-driven testing for
dency, nor packages furtuer down the tree.
I hope that answers your question?
Wookey
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83
FM, Debian-ylläpitäjä / M.S
sorts of dependency, nor packages furtuer down the tree.
I hope that answers your question?
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
Hello
If the dependency graph of a binary package in the unstable distribution
is changed (e.g. because of the 64-bit time_t transition) shall the
binary package be rebuilt in the distribution?
- Tommi
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan
Hi Dale, is there any progress on this?
Can I download preliminary prebuilt packages? I was able to find out
how to get/build a package from your repository link.
Installing the Restic REST server manually is kind of annoying, this
really would be worth a Debian package.
Thanks in advance
Hi!
On Fri, 2024-01-19 at 14:13:07 +, Aidan wrote:
> On Fri, 19 Jan 2024, 00:08 Guillem Jover, wrote:
> > …regardless of whether this is or not the last blocking issue, I'd
> > still very much appreciate if you could rename the project and tool
> > upstream. :)
> I shall rename the tool to r
> if that isn't at least discussed with dpkg maintainers (I at least see
> > > no mention of it on the list) and given that this is something that
> > > "just" works with Docker.
>
> Just by chance I had seen the mail on the mentors list, but thanks for
>
quot;just" works with Docker.
Just by chance I had seen the mail on the mentors list, but thanks for
the heads-up, because I tend to look there very sporadically!
My reaction was pretty similar TBH. There's enough confusion with
things like dpkg-reconfigure and dpkg-preconfigure and other pa
On Thu, Jan 18, 2024 at 6:30 PM David Kalnischkies
wrote:
> Hi,
>
> On Thu, Jan 18, 2024 at 02:35:40PM +, Aidan wrote:
> > I am looking for a sponsor for my package "dpkg-buildenv":
>
> Similar to my recent "veto" of apt-verify in #1059267, which was
> subsequently ignored and pushed into the
ability to run the Jenkins workload within a container is the reason I
started the work.
> I'm the current maintainer of sbuild. You found the wiki page and you saw
> that
> there already exist 10 different implementations of utilities that build
> Debian
> packages insid
and you saw that
there already exist 10 different implementations of utilities that build Debian
packages inside a docker container. You still decided to add an eleventh
implementation so I guess my plea here will not amount to much but anyways here
goes my sales pitch:
If you want your code
Hi,
On Thu, Jan 18, 2024 at 02:35:40PM +, Aidan wrote:
> I am looking for a sponsor for my package "dpkg-buildenv":
Similar to my recent "veto" of apt-verify in #1059267, which was
subsequently ignored and pushed into the archive anyhow, I would
like to call into question the naming of the pa
I see you added this tool to the list of similar tools on the wiki so you
at least know about that list. So how is your tool better than other tools
on that list, or at least than the ones packaged in Debian?
Please also note that if you followed the procedure outlined at
https://mentors.debian.ne
.com/aidan-gallagher/dpkg-buildenv
* License : LGPL-2.0+
* Vcs : https://github.com/aidan-gallagher/dpkg-buildenv.git
Section : misc
The source builds the following binary packages:
dpkg-buildenv - Builds debian packages in a docker container.
To access further i
Hi,
> No. The MIT block and references should be gone (unless some files use a
> different version of the MIT license).
Perfect. Thank you.
Regards,
David James
Hi,
>If I wanted to package software licensed under MIT, and the version given
>upstream matches the Expat license word-for-word, does the above sentence mean
>I should replace all references to the MIT license with Expat?
Yes.
> Should my copyright file look like this?
No. The MIT block and
Dear Mentors,
According to
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/, the link at
the top of generated copyright files, "There are [many versions of the MIT
license](https://en.wikipedia.org/wiki/MIT_License#Various_versions). Please
use Expat instead, when it matches.
I just want to ensure that my packages are binNMU safe.
- Tommi
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83
FM, Debian-ylläpitäjä / M.Sc., Debian
On Thu, Nov 02, 2023 at 07:54:16AM +0200, Tommi Höynälänmaa wrote:
> WWW page https://wiki.debian.org/binNMU doesn't mention the case arch:all
> package depending another arch:all package when it discussed making packages
> binNMU safe. How is this case handled?
arch: all packages ar
WWW page https://wiki.debian.org/binNMU doesn't mention the case
arch:all package depending another arch:all package when it discussed
making packages binNMU safe. How is this case handled?
- Tommi Höynälänmaa
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E
arch=amd64
> https://buildd.debian.org/status/logs.php?pkg=highway&arch=i386
>
> # aptitude install libhwy1:amd64 libhwy1:i386
> libhwy1:i386 is already installed at the requested version (1.0.4-1)
> libhwy1:i386 is already installed at the requested version (1.0.4-1)
> The foll
is already installed at the requested version (1.0.4-1)
libhwy1:i386 is already installed at the requested version (1.0.4-1)
The following NEW packages will be installed:
libhwy1{b}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/538 kB of archives. After unpacki
ll -y libhwy1:i386
% apt-cache policy libhwy1:i386
libhwy1:i386:
Installed: 1.0.4-1
Candidate: 1.0.4-1
Version table:
*** 1.0.4-1 500
500 http://deb.debian.org/debian sid/main i386 Packages
100 /var/lib/dpkg/status
On 8/29/23 09:45, Mathieu Malaterre wrote:
Could someone please review what I did wrong for src:highway. For some
reason I cannot install libhwy1:amd64 + libhwy1:i386 on my system:
FTBFS on several architectures:
https://buildd.debian.org/status/package.php?p=highway
Kind Regards,
Bas
--
://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
Gives:
% sudo apt install libhwy1:i386
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
libhwy1
The following NEW packages will be installed
and it
can be hard to understand Debian upstream version numbers.
https://wiki.debian.org/Packaging/SourcePackage
https://www.debian.org/doc/debian-policy/ch-source.html
Please note that many Debian packages are not child branches of upstream
git history. Instead they import tarballs of git
> One of the 8 build-in-Docker tools listed on
> https://wiki.debian.org/SystemBuildTools#Package_build_tools is even
> called whalebuilder. It's also in Debian since 2016.
Wow, thanks. How did I miss that page on the wiki LoL. And not even
original with the naming. I did indeed waste my time a li
On Fri, Jun 02, 2023 at 12:56:03PM +0200, Rock Storm wrote:
> I've been working on a small program to locally build packages in
> containers. Sort of an alternative to `pbuilder`. Because I find
> managing containers easier than managing base.tgz. In case anyone finds
> it use
Hi all,
I've been working on a small program to locally build packages in
containers. Sort of an alternative to `pbuilder`. Because I find
managing containers easier than managing base.tgz. In case anyone finds
it useful as well, full info in the README:
https://github.com/rocksto
hi debian-perl,
after years of inactivity i got some new packages going and also
had a look at old perl packages which are still "maintained" by
me. Some of them have seen various nmu's already, so it makes
sense to move them to the debian-perl group.
Here are the RFS for tho
Hi Mechtilde,
>
> Where do you have the sources?
>
I just uploaded the sources on salsa.debian.org/ralex/odr-audioenc
I believe that the git repository is now setup (branches and tags) the
way it is supposed to be as per our previous conversation.
Please, note that I did not push the package
Hello Robin,
Where do you have the sources?
You can only upload source packages into the Debian repositorium.
And I think you need a sponsor to upload it
Regards
Mechtilde
Am 22.03.23 um 16:40 schrieb Robin ALEXANDER:
debian/bullseye would be the name of the branch in my git repository
and
debian/bullseye would be the name of the branch in my git repository
and it would target the bullseye-backports distribution
Le mercredi 22 mars 2023 à 16:11 +0100, Andrey Rakhmatullin a écrit :
> On Wed, Mar 22, 2023 at 02:42:28PM +0100, Robin Alexander wrote:
>
>
> > * debian/bullseye: debi
On Wed, Mar 22, 2023 at 02:42:28PM +0100, Robin Alexander wrote:
> Hi Mechtilde and Andrey,
>
> Got it for the official debian repository. In a nutshell:
> - Push to mentors once the freeze is released (ie, after bookworm is
> released)
> - Once package in unstable/testing, push a backport to st
Hi Mechtilde and Andrey,
Got it for the official debian repository. In a nutshell:
- Push to mentors once the freeze is released (ie, after bookworm is
released)
- Once package in unstable/testing, push a backport to stable and
oldstable
Got it as well for the number of versions:
- Keep 1
1 - 100 of 4439 matches
Mail list logo
