Bug#1009747:
Hi Reinhard. I am afraid that when `dbus-user-session` and `podman` were not installed, it probably still won't work without reboot. If I am not mistaken, some things like group membership update require if not reboot, then at least relogin. However, I can not test it, because I abandoned the idea of using `podman` with stable Debian - https://github.com/containers/podman/discussions/14134 Nevertheless, it is nice to see that somebody took care of `podman` in Debian. So thanks for reaching out. On Fri, 19 Aug 2022 at 10:30, Reinhard Tartler wrote: > > Hi Anatoli, > > Sorry to hear that you had bad surprises with the podman package, but I'm > happy to read in > https://github.com/containers/podman/issues/12983#issuecomment-1119662438 > that you managed to get the software working by rebooting. This tells me that > those warnings correctly indicated a system misconfiguration or rather an > runtime error and your dbus user session wasn't running. > > I'm going to change the podman package to add a "Recommends" relationship so > that the package gets installed by default. > > Thanks for your bugreport. > > On Sat, Apr 16, 2022 at 12:03 PM Anatoli Babenia > wrote: >> >> It appears installing `dbus-user-session` doesn't fix the problem with >> excessive messages. >> > > > -- > regards, > Reinhard -- Anatoli Babenia +1 (650) 605-3365 +375 (29) 320-4241
Bug#1009747:
It appears installing `dbus-user-session` doesn't fix the problem with excessive messages.
Bug#1009747: Missing dependency on dbus-user-session
Package: podman Version: 3.0.1+dfsg1-3+deb11u1 All `podman` commands produce a lot of warnings on default install. $ podman version WARN[] The cgroupv2 manager is set to systemd but there is no systemd user session available WARN[] For using systemd, you may need to login using an user session WARN[] Alternatively, you can enable lingering with: `loginctl enable-linger 1000` (possibly as root) WARN[] Falling back to --cgroup-manager=cgroupfs WARN[] The cgroupv2 manager is set to systemd but there is no systemd user session available WARN[] For using systemd, you may need to login using an user session WARN[] Alternatively, you can enable lingering with: `loginctl enable-linger 1000` (possibly as root) WARN[] Falling back to --cgroup-manager=cgroupfs Version: 3.0.1 API Version: 3.0.0 Go Version: go1.15.15 Built:Thu Jan 1 00:00:00 1970 OS/Arch: linux/amd64 As mentioned in `podman` tracker this is because of missing dependency on `dbus-user-session` https://github.com/containers/podman/issues/12983#issuecomment-1019581809
Bug#976246: dpkg-source: Reference detection of native vs non-native source package type
Hello. > > It would help greatly if `dpkg-source` reported native or non-native > > package type. > > > > -dpkg-source: info: using source format '1.0' > > +dpkg-source: info: using non-native source format '1.0' > > While I think something like this would be nice, unfortunately I'm afraid > this cannot be done right now, because there are still package at least > in Debian that have a mismatched version format compared to their source > format. In that case `dpkg-source` could throw a warning about ambiguity. > > It would be nice to see a reference algorithm that detects different package > > types. It would help people like me to troubleshoot issues with Debian > > packaging faster. > > It would be nice, and I've been trying to get there, but see above. I still don't see why `dpkg-source` should not produce helpful messages while there are some other packages that fail validation.
Bug#976301: closed by Debian FTP Masters (reply to Sean Whitton ) (Bug#976301: fixed in debian-policy 4.6.0.0)
My last comment is not addressed. On Wed, 18 Aug 2021 at 07:06, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the debian-policy package: > > #976301: Fix invalid `changelog` format example > > It has been closed by Debian FTP Masters > (reply to Sean Whitton ). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters < > ftpmas...@ftp-master.debian.org> (reply to Sean Whitton < > spwhit...@spwhitton.name>) by > replying to this email. > > > -- > 976301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976301 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded message -- > From: Debian FTP Masters > To: 976301-cl...@bugs.debian.org > Cc: > Bcc: > Date: Wed, 18 Aug 2021 04:03:49 + > Subject: Bug#976301: fixed in debian-policy 4.6.0.0 > Source: debian-policy > Source-Version: 4.6.0.0 > Done: Sean Whitton > > We believe that the bug you reported is fixed in the latest version of > debian-policy, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 976...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Sean Whitton (supplier of updated > debian-policy package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Tue, 17 Aug 2021 20:06:42 -0700 > Source: debian-policy > Architecture: source > Version: 4.6.0.0 > Distribution: unstable > Urgency: medium > Maintainer: Debian Policy Editors > Changed-By: Sean Whitton > Closes: 932696 944920 976301 983657 989581 > Changes: > debian-policy (4.6.0.0) unstable; urgency=medium > . >[ Sean Whitton ] >* Policy: Allow manpages to be included in the dependencies of packages > Wording: Helmut Grohne > Seconded: Russ Allbery > Seconded: Christoph Berg > Seconded: Sean Whitton > Closes: #983657 >* Policy: Support for subpaths in Vcs-Git > Wording: Russ Allbery > Seconded: Sean Whitton > Seconded: Mattia Rizzolo > Closes: #932696 >* 4.4: Fix changelog format: needs an extra space before sign-off > (Closes: #976301). > Thanks to Anatoli Babenia for reporting the problem. >* autopkgtest: Update variable name ADTTMP->AUTOPKGTEST_TMP (Closes: > #989581). > Thanks to Fabrice Bauzac-Stehly for reporting the problem. > . >[ Russ Allbery ] >* Policy: Add new encouraged keyword, make keywords consistent > Wording: Russ Allbery > Seconded: Sam Hartman > Seconded: Sean Whitton > Closes: #944920 >* Clarify that no package may install files in /usr/lib64. The previous > wording implied this restriction only applied to 64-bit packages. >* Reserve the /etc/rcn.d directories for the init-system-helpers package > rather than the sysvinit package, reflecting a change already made in > the archive. > Checksums-Sha1: > 9d4ad492c2f1368d39e8654b2dae242309f0f896 2052 debian-policy_4.6.0.0.dsc > cb9fd69c42d86abf47a47e86cb03191f3c54964b 546236 > debian-policy_4.6.0.0.tar.xz > Checksums-Sha256: > a946f1ab52de55b60822bba441fad31f793a9a8576ae1dae33720c033dba3e1b 2052 > debian-policy_4.6.0.0.dsc > 9982f5718b8104963b1010238a13a3130ffa692cc9f9268feeb70dc4ae656111 546236 > debian-policy_4.6.0.0.tar.xz > Files: > 5f4c982995def9ba579643f6ffc22ca8 2052 doc optional > debian-policy_4.6.0.0.dsc > c941bd543be3706cf56459c6e39a66bb 546236 doc optional > debian-policy_4.6.0.0.tar.xz > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmEcf8EACgkQaVt65L8G > YkD8TQ/8CPvmUWfEt7x9EKqR/d3veNFg6Es6BgLZ83zl9lY3PJE039BH37XY8NkQ > 60L8wDv49wz+O4suJekEwlM3FwSbFb3o+L2s7wRU04SPIJki9poredhqN89eSVrt > b+M5rf9PkLUsB6WdZhGtVHmt0xUrJ9Zs9b3hufgRjXOeUGZIO1sT0OiZ282eT4Um > GsDMWQoX3BpGQ9x5NiVCer4ZdTMyACmJlxQ5RpbXuf+xJYSfnjVjpkTt70sclZ+P > +wU/sizEK6pswYlfPWs2JE3nmOZh0UvMGF630t0xyMWt+ZgyJwc4Z9wNnpbYJ2gZ > IakYdNPlSGfFe310bLTiAWb7ASY
Bug#976301: Fix invalid `changelog` format example
It is hard to spot the space in front of the string, and much harder to understand that it is significant. That's why I still think that applying my patch as-is is a better choice. In committed change https://salsa.debian.org/dbnpolicy/policy/-/commit/69933a335bce539ec8e75f3b5625dc69509d9886 the test that explains blank lines goes as replacement for those blank like, but the text that explains two space pattern is an inline comment. In my patch user needs to replace every placeholder with the content that is described within.
Bug#976301: Fix invalid `changelog` format example
Guillem is right. I was trying to construct `changelog` entry manually and couldn't get it right using the doc.
Bug#976301: Fix invalid `changelog` format example
Package: debian-policy
Control: tag -1 + patch
Hello,
I am seeking seconds for the following patch:
diff --git a/policy/ch-source.rst b/policy/ch-source.rst
index edae8c1..1265c5e 100644
--- a/policy/ch-source.rst
+++ b/policy/ch-source.rst
@@ -126,7 +126,7 @@ That format is a series of entries like this:
[blank line(s), included in output of dpkg-parsechangelog]
* even more change details
[optional blank line(s), stripped]
[]{+[space]--+} maintainer name [two [-spaces]
date-]{+spaces]date+}
``package`` and ``version`` are the source package name and version
number.
Bug#976246: dpkg-source: Reference detection of native vs non-native source package type
Package: dpkg-dev
Version: 1.19.7
Severity: normal
File: /usr/bin/dpkg-source
Dear Maintainer,
It would help greatly if `dpkg-source` reported native or non-native
package type.
-dpkg-source: info: using source format '1.0'
+dpkg-source: info: using non-native source format '1.0'
There is no information about native vs non-native format in this wiki page
https://wiki.debian.org/Packaging/SourcePackage
Mentors FAQ explains it in a lot of detail, but still hard to understand.
https://wiki.debian.org/DebianMentorsFaq#What_is_the_difference_between_a_native_Debian_
package_and_a_non-native_package.3F
`dpkg-source` code does explain the logic either. Detection of source format
relies on checking command line flags, and it does not make sense to me.
my $v = Dpkg::Version->new($self->{fields}->{'Version'});
if ($sourcestyle =~ m/[kpursKPUR]/) {
error(g_('non-native package version does not contain a revision'))
if $v->is_native();
} else {
# FIXME: This will become fatal in the near future.
warning(g_('native package version may not have a revision'))
unless $v->is_native();
}
https://salsa.debian.org/dpkg-team/dpkg/-/blob/09c9e02046f18f02bf3c3c2533bc557abfdc828c/scripts/Dpkg/Source/Package/V1.pm#L355
It would be nice to see a reference algorithm that detects different package
types. It would help people like me to troubleshoot issues with Debian
packaging faster.
https://github.com/openSUSE/obs-build/issues/633
I was not aware of the differences between native and non-native
packages before. Wish I could spend less time discovering this.
Bug#975558: Add public domain to copyright types
On Tue, 24 Nov 2020 at 02:33, Craig Small wrote: > > It's not used a lot because its a bit vague. All three of us could write > some license that we think is public domain but it is worded differently. The > problem for dh-make is, which one is the "right" one? > > For GPL-2 for example, there is a canonical version of the license. SPDX > lists several licenses that have public domain in their name. SPDX Legal Team tries to handle PD with copyright law, and explains that they want to treat each public domain dedication as sepate implicit licenses https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files However, everything that is said also applies to GPL in countries where software licenses have no formal status. If we agree that public domain dedication is not a license, but a will of an author, then enforcing SPDX, which doesn't have a mechanism for copyright opt out, will filter out public domain software from package repositories. > dh-make already has a blank license and a custom license (where you feed it > the copyright file). I'm not convinced putting in a best-guess for public > domain license will be helpful.
Bug#975558: Add public domain to copyright types
Nice. I tried to use Packages Search to get a list of public domain
packages, but https://packages.debian.org/index doesn't search
licenses.
Using
https://codesearch.debian.net/search?q=public-domain+path%3Adebian%2Fcopyright=0
gives "5310 files grepped (2321 results)". Not sure if that means that
2321 out of 5310 packages contain public domain code.
>From the DFSGLicenses FAQ my use case can be solved with placing this
text into `debian/copyright`.
Copyright: Anatoli Babenia
License: public-domain
As for inclusion in `dh-make`, I think that there should be a simple
way for people to state their will for copyright opt-out for their source
code. Telling people to use different copyright laws that don't provide
opt-out mechanisms to opt-out from those laws looks wrong. WTFPL,
CC-0, Unlicense are all products of that approach that are not
guaranteed to work. Requiring authors to write explanations why they
place their code in public domain looks like a lack of trust to me. I
would state that overcomplicating such a simple thing as public domain
is not in the interests of people who chose to share their code this way.
Bug#975558: Add public domain to copyright types
Package: dh-make Version: 2.202001 I could not find any examples on how to make public domain packaged in Debian. Would be nice if `dh_make` supported it with `--copyright pd` option.
