Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1200692 > unrolled thread

Bug#1071149: socklog: diff for NMU version 2.1.0+repack-5.1

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1071149: socklog: diff for NMU version 2.1.0+repack-5.1 Chris Hofstaedtler <zeha@debian.org> - 2024-06-12 21:20 +0200
    Bug#1071149: socklog: diff for NMU version 2.1.0+repack-5.1 Mathieu Mirmont <mat@parad0x.org> - 2024-06-18 09:50 +0200
      Bug#1071149: socklog: diff for NMU version 2.1.0+repack-5.1 Chris Hofstaedtler <zeha@debian.org> - 2024-06-18 10:20 +0200
        Bug#1071149: socklog: diff for NMU version 2.1.0+repack-5.1 Lorenzo <plorenzo@disroot.org> - 2024-06-19 02:20 +0200

#1200692 — Bug#1071149: socklog: diff for NMU version 2.1.0+repack-5.1

[Multipart message — attachments visible in raw view] — view raw

Control: tags 1071149 + pending


Dear maintainer,

I've prepared an NMU for socklog (versioned as 2.1.0+repack-5.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

I've replaced the execute_after_dh_installinit: target with a B-D on
dh-sequence-installsysusers, which seems to be the canonical way of
doing the same thing.

Regards.

[toc] | [next] | [standalone]

#1201400

[Multipart message — attachments visible in raw view] — view raw

Hi Chris,

Sorry for being slow to respond, I'm quite busy at the moment. Would
you mind removing this NMI for the time being so I can think about
what would be best? I don't suppose there is much urgency here.

As Lorenzo noted, this package is really only meaningful in a runit
based system. I understand that the intention is to standardise within
Debian, but I also want to consider the consequences for downstream
distros.

Thanks.

Mathieu.


On Wed, Jun 12, 2024 at 09:14:24PM +0200, Chris Hofstaedtler wrote:
> Control: tags 1071149 + pending
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for socklog (versioned as 2.1.0+repack-5.1) and
> uploaded it to DELAYED/10. Please feel free to tell me if I
> should delay it longer.
> 
> I've replaced the execute_after_dh_installinit: target with a B-D on
> dh-sequence-installsysusers, which seems to be the canonical way of
> doing the same thing.
> 
> Regards.
> 

> diff -Nru socklog-2.1.0+repack/debian/changelog socklog-2.1.0+repack/debian/changelog
> --- socklog-2.1.0+repack/debian/changelog	2023-03-06 22:01:18.000000000 +0100
> +++ socklog-2.1.0+repack/debian/changelog	2024-06-12 21:08:18.000000000 +0200
> @@ -1,3 +1,13 @@
> +socklog (2.1.0+repack-5.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +
> +  [ Timo Röhling ]
> +  * Replace dh-sysusers with dh-sequence-installsysusers.
> +    (Closes: #1071149)
> +
> + -- Chris Hofstaedtler <zeha@debian.org>  Wed, 12 Jun 2024 21:08:18 +0200
> +
>  socklog (2.1.0+repack-5) unstable; urgency=medium
>  
>    * Various uninteresting changes
> diff -Nru socklog-2.1.0+repack/debian/control socklog-2.1.0+repack/debian/control
> --- socklog-2.1.0+repack/debian/control	2023-03-06 21:52:36.000000000 +0100
> +++ socklog-2.1.0+repack/debian/control	2024-06-12 21:08:18.000000000 +0200
> @@ -8,8 +8,9 @@
>  Standards-Version: 4.6.2
>  Homepage: http://smarden.org/socklog
>  Build-Depends: debhelper-compat (= 13),
> +               debhelper (>= 13.3),
>                 dh-runit,
> -               dh-sysuser,
> +               dh-sequence-installsysusers,
>                 doc-base
>  Rules-Requires-Root: no
>  
> diff -Nru socklog-2.1.0+repack/debian/rules socklog-2.1.0+repack/debian/rules
> --- socklog-2.1.0+repack/debian/rules	2023-03-06 21:52:36.000000000 +0100
> +++ socklog-2.1.0+repack/debian/rules	2024-06-12 21:08:18.000000000 +0200
> @@ -8,7 +8,7 @@
>  CONF_LD = src/conf-ld
>  
>  %:
> -	dh $@ --with runit,sysuser
> +	dh $@ --with runit
>  
>  override_dh_auto_clean:
>  	rm -rf compile command
> diff -Nru socklog-2.1.0+repack/debian/socklog-run.sysuser socklog-2.1.0+repack/debian/socklog-run.sysuser
> --- socklog-2.1.0+repack/debian/socklog-run.sysuser	2023-03-06 21:52:36.000000000 +0100
> +++ socklog-2.1.0+repack/debian/socklog-run.sysuser	1970-01-01 01:00:00.000000000 +0100
> @@ -1,5 +0,0 @@
> -_socklog-unix defaults
> -_socklog-klog defaults
> -_socklog-inet defaults
> -_socklog-ucspi-tcp defaults
> -_socklog-notify defaults
> diff -Nru socklog-2.1.0+repack/debian/socklog-run.sysusers socklog-2.1.0+repack/debian/socklog-run.sysusers
> --- socklog-2.1.0+repack/debian/socklog-run.sysusers	1970-01-01 01:00:00.000000000 +0100
> +++ socklog-2.1.0+repack/debian/socklog-run.sysusers	2024-06-12 21:07:15.000000000 +0200
> @@ -0,0 +1,6 @@
> +u	_socklog-unix		-	"Socklog unix user"
> +u	_socklog-klog		-	"Socklog klog user"
> +u	_socklog-inet		-	"Socklog inet user"
> +u	_socklog-ucspi-tcp	-	"Socklog ucspi-tcp user"
> +u	_socklog-notify		-	"Socklog notify user"
> +


-- 
Mathieu Mirmont <mat@parad0x.org>

[toc] | [prev] | [next] | [standalone]

#1201403

Hi Mathieu,

* Mathieu Mirmont <mat@parad0x.org> [240618 09:40]:
> Hi Chris,
> 
> Sorry for being slow to respond, I'm quite busy at the moment. Would
> you mind removing this NMI for the time being so I can think about
> what would be best?

I've rescheduled it to DELAYED/14 to provide more time.

> I don't suppose there is much urgency here.

This is one of many loose ends needing tying up for getting UsrMerge
done for trixie and having forky not being in a limbo-state again.
While individual packages could finish very late, given the overall
amount of things we have to keep track of, the remaining time until
the (estimated date of the) trixie transition freeze is not that
generous.

Please help us out and let us close as many topics as we can.

> As Lorenzo noted, this package is really only meaningful in a runit
> based system. I understand that the intention is to standardise within
> Debian, but I also want to consider the consequences for downstream
> distros.

I think in Debian we are now down to two or three source packages. I
would imagine downstream distros need to deal with this already, one
way or another.

Let me know if the 14 days are not enough.

Best,
Chris

[toc] | [prev] | [next] | [standalone]

#1201473

On Tue, 18 Jun 2024 10:13:33 +0200 Chris Hofstaedtler <zeha@debian.org>
wrote:

> This is one of many loose ends needing tying up for getting UsrMerge
> done for trixie and having forky not being in a limbo-state again.

Chris,

would you mind briefly elaborating how this is blocking the UrsMerge
transition?

Best,
Lorenzo

> While individual packages could finish very late, given the overall
> amount of things we have to keep track of, the remaining time until
> the (estimated date of the) trixie transition freeze is not that
> generous.
> 
> Please help us out and let us close as many topics as we can.
> 
> > As Lorenzo noted, this package is really only meaningful in a runit
> > based system. I understand that the intention is to standardise
> > within Debian, but I also want to consider the consequences for
> > downstream distros.
> 
> I think in Debian we are now down to two or three source packages. I
> would imagine downstream distros need to deal with this already, one
> way or another.
> 
> Let me know if the 14 days are not enough.
> 
> Best,
> Chris

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web