Hi Maxime,
On Tue, Dec 21, 2021 at 07:47:47PM +0100, Maxime Lombard wrote:
>Hello,
>
>I'm an user of Debian since 10 years ago and it's only now that i decide
>to help to packaging.
>I send this email about wine and wine-development package which are not
>updated since a very
Package: wnpp
Severity: wishlist
Owner: Stephen Kitt
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: golang-github-lestrrat-go-strftime
Version : 1.0.5
Upstream Author : Daisuke Maki
* URL : https://github.com/lestrrat-go/strftime
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Stephen Kitt
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: golang-github-lestrrat-go-envload
Version : 0.0~20180221
Upstream Author : Daisuke Maki
* URL : https://github.com/lestrrat-go/envload
* License :
Hello,
2021-10-02 11:57 Graham Inggs:
Hi
We are doing a roll call for porters of all prospective release
architectures. If you are an active porter behind one of these
architectures [1] and intend to continue for the development cycle of
Debian Bookworm (est. release mid-2023), please respond
On Thursday, December 30, 2021 2:35:56 AM EST Bastian Blank wrote:
> On Wed, Dec 29, 2021 at 04:35:22PM -0500, Scott Kitterman wrote:
> > The postfix package ships a script in /etc/resolvconf/update-libc.d/ to
> > restart postfix when resolv.conf is updated. As far as I know, that
> > still works
On Thursday, December 30, 2021 2:36:45 AM EST Bastian Blank wrote:
> On Thu, Dec 30, 2021 at 01:48:49AM +, Scott Kitterman wrote:
> > It does. My question is on the other end of the problem. Once
> > resolv.conf is updated, how do I trigger an action for another package?
> > In this case it'
Scott Kitterman writes:
> I believe I can solve this problem by adding Recommends: resolvconf if that's
> the only way. I had hoped there would be some "modern" way to do it from
> within Debian's default package set.
Funny. That seems to have been the solution to this bug almost 20 years
ag
Scott Kitterman writes:
> I believe I can solve this problem by adding Recommends: resolvconf if that's
> the only way. I had hoped there would be some "modern" way to do it from
> within Debian's default package set.
I hope that wouldn't interfere with an enabled systemd-resolved,
otherwise
On Thursday, December 30, 2021 8:50:48 AM EST Bjørn Mork wrote:
> Scott Kitterman writes:
> > I believe I can solve this problem by adding Recommends: resolvconf if
> > that's the only way. I had hoped there would be some "modern" way to do
> > it from within Debian's default package set.
>
> Fu
On Thursday, December 30, 2021 9:01:07 AM EST David Bremner wrote:
> Scott Kitterman writes:
> > I believe I can solve this problem by adding Recommends: resolvconf if
> > that's the only way. I had hoped there would be some "modern" way to do
> > it from within Debian's default package set.
>
>
On Thu, Dec 30, 2021 at 08:26:07AM -0500, Scott Kitterman wrote:
> > Maybe you should stop supporting the non-standard chroot configuration?
> What do you mean by non-standard? It's true that the upstream default is now
> not in the chroot, but it's totally a configuration supported by upstream.
On 29.12.21 22:35, Scott Kitterman wrote:
The postfix package ships a script in /etc/resolvconf/update-libc.d/ to restart
postfix when resolv.conf is updated.
Why copy the file? Couldn't you bind mount it into the chroot so you
don't need to update it everytime the host /etc/resolv.conf change
On Dec 30, Scott Kitterman wrote:
> I would too. It would be nice if systemd-resolved had some mechanism to
> support this kind of functionality. If you're going to replace resolvconf,
> then you ought to actually replace it.
systemd-resolved is supposed to forward queries to the upstream res
On Thu, Dec 30, 2021 at 09:19:35PM +0100, Marco d'Itri wrote:
> systemd-resolved is supposed to forward queries to the upstream resolver
> and always be available on 127.0.0.53, so what does actually change in
> resolve.conf when using it?
Only if you are using the stub resolver. systemd-resolv
On 2021-12-26 18:08 -0600, Dirk Eddelbuettel wrote:
>
> Does anybody know where we are with respect to the WNPPs / ITPs / ... on the
> Amazon SDK for C++?
>
> I have a package that could take advantage of this if it were packaged, and I
> am sure a number of other packages are in a similar situat
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 1242 (new: 2)
Total number of packages offered up for adoption: 184 (new: 0)
Total number of packages reques
Hi Dirk,
On Mon, Dec 27, 2021 at 08:10:50AM -0600, Dirk Eddelbuettel wrote:
> My (very informal) packaging has always been in the open (but on GitHub). A
> possible first step might be to review the added files in debian/ and in a
> first pass edit out all references to 'informal' or 'unofficial'
17 matches
Mail list logo
