On 2023-01-26, at 20:42:16 +0100, Romain Francoise wrote:
> Now finally uploaded! (And it didn't go through NEW.)
Cool. :)
J.
signature.asc
Description: PGP signature
Now finally uploaded! (And it didn't go through NEW.)
--
Romain Francoise
https://people.debian.org/~rfrancoise/
On Sun, Jan 22, 2023 at 02:08:41PM +, Jeremy Sowden wrote:
> Agreed. Not sure what the thinking was (those changes were initially
> made in April, '21). I think we can then remove the shorewall.postinst
> and shorewall6.postinst scripts completely.
Ok, I will do that in the next few days.
On 2023-01-21, at 20:00:05 +0100, Romain Francoise wrote:
> I noticed while testing that you removed the '--no-start' argument to
> dh_installinit calls in the unified package, and that's not right, as
> README.Debian documents.
>
> The situation is even a bit more complex:
>
> *
On Sat, Jan 21, 2023 at 10:47:12AM -0500, Roberto C. Sánchez wrote:
> Whenever a source package produces a new binary package, whether that
> package exists in the archive already or not, it will land in NEW.
Ah, makes sense. Thanks.
Experimental it is, then. :-)
I noticed while testing that you removed the '--no-start' argument to
dh_installinit calls in the unified package, and that's not right, as
README.Debian documents.
The situation is even a bit more complex:
* shorewall.postinst and shorewall6.postinst source the config file in
/etc/default
On Sat, Jan 21, 2023 at 09:58:13AM +0100, Romain Francoise wrote:
> On Fri, Jan 20, 2023 at 11:59:44AM +, Jeremy Sowden wrote:
> > The Developer's Reference, § 5.6.1, expresses the preference that when
> > new binary packages are added to a source package, it should be
> > uploaded to
On 2023-01-21, at 10:00:33 +0100, Romain Francoise wrote:
> On Fri, Jan 20, 2023 at 05:18:19PM -0500, Roberto C. Sánchez wrote:
> > I think that the bug is actually assigned to the shorewall-doc binary
> > package, not the shorewall-doc source package. Assuming that the
> > shorewall source
On 2023-01-21, at 09:58:13 +0100, Romain Francoise wrote:
> On Fri, Jan 20, 2023 at 11:59:44AM +, Jeremy Sowden wrote:
> > The Developer's Reference, § 5.6.1, expresses the preference that
> > when new binary packages are added to a source package, it should be
> > uploaded to experimental, so
On Fri, Jan 20, 2023 at 05:18:19PM -0500, Roberto C. Sánchez wrote:
> I think that the bug is actually assigned to the shorewall-doc binary
> package, not the shorewall-doc source package. Assuming that the
> shorewall source package will start to emit a shorewall-doc binary
> package, I think
On Fri, Jan 20, 2023 at 11:59:44AM +, Jeremy Sowden wrote:
> The Developer's Reference, § 5.6.1, expresses the preference that when
> new binary packages are added to a source package, it should be
> uploaded to experimental, so I've updated the version and distribution
> in the change-log
On Fri, Jan 20, 2023 at 09:46:35PM +, Jeremy Sowden wrote:
> On 2023-01-19, at 22:56:39 +0100, Romain Francoise wrote:
> > On Thu, Jan 19, 2023 at 7:01 PM Jeremy Sowden wrote:
> > > I've pushed all the work to my repo on Salsa:
> > >
> > > https://salsa.debian.org/azazel/shorewall
> > >
> >
On 2023-01-19, at 22:56:39 +0100, Romain Francoise wrote:
> On Thu, Jan 19, 2023 at 7:01 PM Jeremy Sowden wrote:
> > I've pushed all the work to my repo on Salsa:
> >
> > https://salsa.debian.org/azazel/shorewall
> >
> > Do you want to review it before I push to the shorewall-team repo?
>
> It
On 2023-01-19, at 22:56:39 +0100, Romain Francoise wrote:
> On Thu, Jan 19, 2023 at 7:01 PM Jeremy Sowden wrote:
> > I've pushed all the work to my repo on Salsa:
> >
> > https://salsa.debian.org/azazel/shorewall
> >
> > Do you want to review it before I push to the shorewall-team repo?
>
> It
Hi Jeremy,
On Thu, Jan 19, 2023 at 7:01 PM Jeremy Sowden wrote:
> I've pushed all the work to my repo on Salsa:
>
> https://salsa.debian.org/azazel/shorewall
>
> Do you want to review it before I push to the shorewall-team repo?
It all looks pretty good to me! In fact, it's a radical
On 2023-01-15, at 22:03:46 +0100, Romain Francoise wrote:
> On Sun, Jan 15, 2023 at 10:38:43AM +, Jeremy Sowden wrote:
> > I've managed to coax gbp into importing 5.2.8 into one upstream
> > branch with each upstream tar-ball as a subdirectory.
> >
> > I'm currently working on merging the
Hi,
Replying to the latest messages in the thread in one go...
On Sun, Jan 08, 2023 at 02:35:17PM +, Jeremy Sowden wrote:
> I've created a Shorewall team on tracker.d.o and added you both to it.
Thanks!
On Mon, Jan 09, 2023 at 08:51:54AM -0500, Roberto C. Sánchez wrote:
> For a bit of
On 2023-01-09, at 08:51:54 -0500, Roberto C. Sánchez wrote:
> On Sat, Jan 07, 2023 at 12:48:08PM +0100, Romain Francoise wrote:
> > On Tue, Jan 3, 2023 at 11:54 PM Jeremy Sowden wrote:
> > > I've imported my fork of Roberto's SF repo to Salsa:
> > >
> > >
On Sat, Jan 07, 2023 at 12:48:08PM +0100, Romain Francoise wrote:
> On Tue, Jan 3, 2023 at 11:54 PM Jeremy Sowden wrote:
> > I've imported my fork of Roberto's SF repo to Salsa:
> >
> > https://salsa.debian.org/azazel/shorewall
> >
> > I haven't touched it in 18 months, so I'll give it a polish
On Mon, Jan 02, 2023 at 06:08:57PM +0100, Romain Francoise wrote:
> Hi,
>
> [Cc'ing Roberto directly to make sure he's aware of this discussion.]
>
Thanks for that. I'm not sure I would have seen it otherwise.
> I'm also a Shorewall[6] user and while the state of the package isn't
> really
On 2023-01-08, at 14:35:17 +, Jeremy Sowden wrote:
> On 2023-01-07, at 12:48:08 +0100, Romain Francoise wrote:
> > On Tue, Jan 3, 2023 at 11:54 PM Jeremy Sowden wrote:
> > > I've imported my fork of Roberto's SF repo to Salsa:
> > >
> > > https://salsa.debian.org/azazel/shorewall
> > >
> >
On 2023-01-07, at 12:48:08 +0100, Romain Francoise wrote:
> On Tue, Jan 3, 2023 at 11:54 PM Jeremy Sowden wrote:
> > I've imported my fork of Roberto's SF repo to Salsa:
> >
> > https://salsa.debian.org/azazel/shorewall
> >
> > I haven't touched it in 18 months, so I'll give it a polish when I
On Tue, Jan 3, 2023 at 11:54 PM Jeremy Sowden wrote:
> I've imported my fork of Roberto's SF repo to Salsa:
>
> https://salsa.debian.org/azazel/shorewall
>
> I haven't touched it in 18 months, so I'll give it a polish when I have
> some time, and perhaps we can use it as a starting point.
On 2023-01-03, at 22:06:03 +, Jeremy Sowden wrote:
> On 2023-01-02, at 18:08:57 +0100, Romain Francoise wrote:
> > [Cc'ing Roberto directly to make sure he's aware of this
> > discussion.]
> >
> > I'm also a Shorewall[6] user and while the state of the package
> > isn't really alarming right
On 2023-01-02, at 18:08:57 +0100, Romain Francoise wrote:
> [Cc'ing Roberto directly to make sure he's aware of this discussion.]
>
> I'm also a Shorewall[6] user and while the state of the package isn't
> really alarming right now, I need it to be properly maintained going
> forward.
>
> We
Hi,
[Cc'ing Roberto directly to make sure he's aware of this discussion.]
I'm also a Shorewall[6] user and while the state of the package isn't
really alarming right now, I need it to be properly maintained going
forward.
We could set up a pkg-shorewall team on Salsa and co-maintain the
Another ping. Offer still stands.
J.
signature.asc
Description: PGP signature
On 2021-04-02, at 11:51:20 +0100, Jeremy Sowden wrote:
> I'd be happy to help. I've been a Shorewall user for many years, and
> I've recently been lending a hand to the Netfilter Packaging Team.
Ping! :)
Haven't had a response. Offer of help still stands.
J.
signature.asc
Description: PGP
On 2021-04-02, at 11:51:20 +0100, Jeremy Sowden wrote:
> I'd be happy to help. I've been a Shorewall user for many years, and
> I've recently been lending a hand to the Netfilter Packaging Team.
I've forked your SF repo and committed changes to package 5.2.8:
I'd be happy to help. I've been a Shorewall user for many years, and
I've recently been lending a hand to the Netfilter Packaging Team.
J.
signature.asc
Description: PGP signature
30 matches
Mail list logo
