Bug#1050824: Removed package(s) from unstable
Version: 0.0~git20170218.0.4afe952-8+rm Dear submitter, as the package golang-github-facebookgo-grace has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050824 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1050824: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: golang-github-facebookgo-grace | 0.0~git20170218.0.4afe952-8 | source golang-github-facebookgo-grace-dev | 0.0~git20170218.0.4afe952-8 | all --- Reason --- RoQA; dead upstream; orphaned; gitea leaf library -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1050824 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1050823: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: golang-github-cupcake-rdb | 0.0~git20161107.0.43ba341-12 | source golang-github-cupcake-rdb-dev | 0.0~git20161107.0.43ba341-12 | all --- Reason --- RoQA; dead upstream; orphaned; gitea leaf package -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1050823 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1050823: Removed package(s) from unstable
Version: 0.0~git20161107.0.43ba341-12+rm Dear submitter, as the package golang-github-cupcake-rdb has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050823 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1050816: Removed package(s) from unstable
Version: 2.3.4.2-17+rm Dear submitter, as the package mmorph has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050816 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1050816: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: mmorph | 2.3.4.2-17 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; orphaned; dead upstream; low popcon; RC-buggy -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1050816 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1050811: Removed package(s) from unstable
Version: 0.93-10+rm Dear submitter, as the package clif has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050811 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1050811: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: clif |0.93-10 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, riscv64, s390x --- Reason --- RoQA; orphaned; dead upstream; low popcon; RC-buggy (non-free) -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1050811 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#970957: marked as done (mmorph: autopkgtest must be marked superficial)
Your message dated Fri, 01 Sep 2023 15:20:15 + with message-id and subject line Bug#1050816: Removed package(s) from unstable has caused the Debian Bug report #970957, regarding mmorph: autopkgtest must be marked superficial to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 970957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mmorph Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in mmorph is running a trivial command that does not provide significant test coverage: -Test-Command: mmorph -h -Test-Command: mmorph -v Executing that command is considered to be a trivial test, which does not provide significant coverage for a package as a whole. But these tests are a useful way to detect regressions in dependencies and prevent them from breaking your package. However, it is important that we are realistic about the level of test coverage provided by these commands: most regressions cannot be detected in this way. So it is not appropriate for packages with only superficial tests to have the reduced migration time to migrate from unstable to testing as that means less opportunity for testing by users compared to the package with no tests. To support this, the keyword "Restrictions: superficial" has been defined [1]. Packages where all tests are marked with this keyword are not considered for the reduced migration age from unstable to testing, and will not be allowed to migrate automatically in later stages of the freeze [2]. Its always better to have more extensive testing than having superficial testing, which again is better than having no test. Please consider i) Adding a non-trivial test, and/or ii) Mark the trivial test with "Restrictions: superficial", similar to [3] or [4]. The Release Team has listed this issue in the list of Release Critical Issues for bullseye [5] and has mentioned that the test must be marked superficial if it is not testing one of its own installed binary packages in some way. As a result, the severity of this bug report might be increased to serious in future. [1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions [2] https://release.debian.org/bullseye/freeze_policy.html [3] https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468 [4] https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3 [5] https://release.debian.org/bullseye/rc_policy.txt -- Regards Sudip --- End Message --- --- Begin Message --- Version: 2.3.4.2-17+rm Dear submitter, as the package mmorph has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050816 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#747014: marked as done (Duplicate (but inconsistent) struct declaration)
Your message dated Fri, 01 Sep 2023 15:19:47 +
with message-id
and subject line Bug#1050811: Removed package(s) from unstable
has caused the Debian Bug report #747014,
regarding Duplicate (but inconsistent) struct declaration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
747014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clif
Version: 0.93-9
Severity: wishlist
Usertags: goto-cc
During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder)
the build failed with the following error. Please note that we use our research
compiler tool-chain (using tools from the cbmc package), which permits extended
reporting on type inconsistencies at link time.
[...]
gcc c-parser.o c-lex.o keyword.o rs-parser.o rs-lex.o tables.o help.o global.o
store_cont.o virtual_machine.o clif.o getc_unix.o comp_maint.o allocx.o
printf_unix.o input.o memmove.o symbols.o remote_call.o ch-parser.o ch-lex.o
channel_maint.o s-conv.o dbg-out.o pso.o sig-svr4.o -lelf -lm -lX11 -o clif
error: conflicting function declarations "in_word_set"
old definition in module c-lex file ls.l line 481
struct el_mc * (char *, unsigned int)
new definition in module keyword file keyword.c line 59
struct el_mc * (char *str, unsigned int len)
reason for conflict at nil.tok in types listed below (struct/struct):
names of component 1 differ (tok/kval)
struct el_mc {
char * name;
signed int tok;
}
struct el_mc {
char * name;
signed int kval;
}
As the C standard requires matching field names for all struct members, one of
the declarations should be fixed to match the other - or just use a shared
header file.
Best,
Michael
pgpHZnHKRpods.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.93-10+rm
Dear submitter,
as the package clif has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1050811
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#967990: marked as done (mmorph: Removal of sys_nerr and sys_errlist)
Your message dated Fri, 01 Sep 2023 15:20:15 + with message-id and subject line Bug#1050816: Removed package(s) from unstable has caused the Debian Bug report #967990, regarding mmorph: Removal of sys_nerr and sys_errlist to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mmorph Version: 2.3.4.2-17 Severity: important Hello, Version 2.32 of glibc will not ship the sys_nerr and sys_errlist symbols any more. This package is using them, so will start FTBFS when we upload version 2.32 of glibc. Samuel --- End Message --- --- Begin Message --- Version: 2.3.4.2-17+rm Dear submitter, as the package mmorph has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050816 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#597103: marked as done (mmorph: fails at 64 bit platforms with "üé" sequence)
Your message dated Fri, 01 Sep 2023 15:20:15 + with message-id and subject line Bug#1050816: Removed package(s) from unstable has caused the Debian Bug report #597103, regarding mmorph: fails at 64 bit platforms with "üé" sequence to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 597103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mmorph Version: 2.3.4.2-12 Severity: important *** Please type your report below this line *** I have a sample grammar wich works fine in mmorph at 32 bit Debian Lenny and fails at 64 bit one. I get the following error: program bug: lexical left context does not match when mmorph reach a word which contains "üé" sequence. I run mmorph this way: mmorph -n -m sample_grammar.mmorph -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES.iso88591, LC_CTYPE=es_ES.iso88591 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages mmorph depends on: ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ii libdb4.64.6.21-11Berkeley v4.6 Database Libraries [ mmorph recommends no packages. mmorph suggests no packages. -- no debconf information -- Fco. Mario Barcala Rodríguez http://www.xente.mundo-r.com/barcala --- End Message --- --- Begin Message --- Version: 2.3.4.2-17+rm Dear submitter, as the package mmorph has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050816 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1016457: marked as done (clif: non-DFSG source code in clif)
Your message dated Fri, 01 Sep 2023 15:19:47 + with message-id and subject line Bug#1050811: Removed package(s) from unstable has caused the Debian Bug report #1016457, regarding clif: non-DFSG source code in clif to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: clif Version: 0.90.2-1 Severity: serious Tags: upstream Justification: Policy 2.2.1 X-Debbugs-Cc: eribe...@debian.org The file ch-lex.c doesn't have a license on its header. However, starting at line 927, I noticed the following text: -- /* Copyright (c) 1989 AT */ /*All Rights Reserved */ /* THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT */ /* The copyright notice above does not evidence any*/ /* actual or intended publication of such source code. */ #pragma ident "@(#)ncform 6.8 95/02/11 SMI" -- It's clear to me that part of the file includes a non-free source code. Eriberto --- End Message --- --- Begin Message --- Version: 0.93-10+rm Dear submitter, as the package clif has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050811 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
powerdebug_0.7.0-2013.08-4_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Sep 2023 16:04:46 +0200 Source: powerdebug Architecture: source Version: 0.7.0-2013.08-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Changes: powerdebug (0.7.0-2013.08-4) unstable; urgency=medium . * QA upload. . [ Vagrant Cascadian ] * debian/rules: Pass default CFLAGS from dpkg-buildflags to make. Checksums-Sha1: 75682e750faed281f9336e9dd6f0dacef853ef7e 1728 powerdebug_0.7.0-2013.08-4.dsc 1952b78e440dfbd10d955d17799e3442f6b351b6 6764 powerdebug_0.7.0-2013.08-4.debian.tar.xz 453e331902acce3396a9499d5b032c1420fc8503 5553 powerdebug_0.7.0-2013.08-4_source.buildinfo Checksums-Sha256: 23d0ddd6c8df616b9f87e16816a5d8975b7447269a7da75b289ac04cfae389d6 1728 powerdebug_0.7.0-2013.08-4.dsc 73588356de42b6b821b89b298ba298a8f23780457cf2ca0c6bcdfceaa8bbab28 6764 powerdebug_0.7.0-2013.08-4.debian.tar.xz f11d24fbfff4f5b84d428acea48764227ce123a73c73cfea77081c16bb167d4f 5553 powerdebug_0.7.0-2013.08-4_source.buildinfo Files: 62a0141162eef22ae168b9d1c7820194 1728 utils optional powerdebug_0.7.0-2013.08-4.dsc 3659290f866ce31a30153863be46c801 6764 utils optional powerdebug_0.7.0-2013.08-4.debian.tar.xz d9aa3be6507ea0d8951bdc1dda1b8f5f 5553 utils optional powerdebug_0.7.0-2013.08-4_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTx76YQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFMFnC/9IdKinxhTNR1nE6p2+Sw3Q9L5tvd68THft VIBdCCRuOlH/O9+nyYx8iIMsICFxWlyrXBqPUtoO25A7nCIIn4h0hnmehebN4mck Uc6or9AG2vxeMFcKXCrKH39jHPWd4PLd4GBIN+bxsAxdt9WZI5SKMjsnESFMxR7x F5Hk33HqJau58T5Zi3tSuhrZZKkRVCkEonFTderi0lYHf48Ii9zlWGuPBX6JGXv9 dIuZs+elC8a8zwn+E1k1ASjTUTJIJC5tXg6SHGDPb8v0a9lZX8qktOJG4rRWoMiD rJloPBz0HMnx677bXziRaXaT8mWBsJYevGUYNI2e97YGs41kiOXkOS1gB1auvJrs UxjuQcSZKEpQoghWfvO7Le8gGdrjnvnidAyrm2l9JrRRq4rqe7pcjE0nLcdEL6Nr 4n0fb8kfQh+H9Kyj6v7WPj3sm+ZFYjPkH87tsq1OTZwTGQ4gs03pUOR7lSFMwrdW KqrcX1B76A2rejFkZAbxEt0H4Yvk5mw= =UESD -END PGP SIGNATURE-
Processing of powerdebug_0.7.0-2013.08-4_source.changes
powerdebug_0.7.0-2013.08-4_source.changes uploaded successfully to localhost along with the files: powerdebug_0.7.0-2013.08-4.dsc powerdebug_0.7.0-2013.08-4.debian.tar.xz powerdebug_0.7.0-2013.08-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
kmfl-keyboards-mywin_2.3.3-2_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Sep 2023 15:21:30 +0200 Source: kmfl-keyboards-mywin Architecture: source Version: 2.3.3-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Changes: kmfl-keyboards-mywin (2.3.3-2) unstable; urgency=medium . * QA upload. * add Martin Hosken to debian/copyright, found in myWin.kmn. * improve description based on text found in myWin.kmn. * Migrate repository from alioth to salsa. * Replace Priority: extra. Checksums-Sha1: e7e1252a704d6a70f0c4285195e369f51e0d73c1 1828 kmfl-keyboards-mywin_2.3.3-2.dsc 9ce60b2b45d8e38e877904ba4c5cfddfa3b48f7b 2608 kmfl-keyboards-mywin_2.3.3-2.debian.tar.xz 2eec9f65ff318b33f0f7ef05abd60fb04944baf9 5458 kmfl-keyboards-mywin_2.3.3-2_source.buildinfo Checksums-Sha256: bd0ad410bca3302efb226ee8a14742af3bf1eced2775d205be55932e32c2485f 1828 kmfl-keyboards-mywin_2.3.3-2.dsc ea84c999ca19a3d98692a3ece1d077c11e7bb4745aabe26247eca68db0c3dee0 2608 kmfl-keyboards-mywin_2.3.3-2.debian.tar.xz 8324a95274defd84c5f59a87c1daa8c946feddfd089a0adfcaceed27e2a8b7bd 5458 kmfl-keyboards-mywin_2.3.3-2_source.buildinfo Files: 4554964ee35aa8daa0736fcf4fe765dd 1828 utils optional kmfl-keyboards-mywin_2.3.3-2.dsc 5762ac635f11b4de316629c69b4fa1e1 2608 utils optional kmfl-keyboards-mywin_2.3.3-2.debian.tar.xz 87c403d757cc29bc85b065eb9f81bb2e 5458 utils optional kmfl-keyboards-mywin_2.3.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTx6s4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFK/GC/4jb3hxWET6DSa9E3Q8193Ca1nl0v5bpgxd 3NiE8iJAeERdayK3RNiG+/NBX25mTqN+oWzTzMMETekidYvDJNJdY0jBVN9G/Awe ba0RpxZTEY9WDWVvbgJ7VNzXz7NCXo9cC653dkOVSSwjdJ1vE1WzHTcYQuJdNeLb Y+XnuuYx9d1XNQm1maFB9hdVaQtjJ9mh0QvqubHdmSf8+oFxKkmQFRg2WKQZiFh9 6MHKEG7Lz4+0meRv9Ig67xz3bbbejfZUIeg1vhi04tnbvL495UcO7DbHj+oG2gdk eDspX5qKwQNiTu69tTIVDcXyhXx5epsRB2u0kO4ZhzFfycQQ5ODYLZ7MWq926aZu IqUzzOs4/m0HQFcqRBvHQNMu+a59cvqj3/eXSs0WkCZKhIf2k6GPnAXIgt075YL3 EUo8XIFxPHrEx62k051i5Mu2zRi92MQvA2fol54NF4ujRMhT1DmaYhOoxXmSpfLr IKBNU6EZxaapSjpHkJVTCHRH3kcO3Nc= =t4Zu -END PGP SIGNATURE-
Processing of kmfl-keyboards-mywin_2.3.3-2_source.changes
kmfl-keyboards-mywin_2.3.3-2_source.changes uploaded successfully to localhost along with the files: kmfl-keyboards-mywin_2.3.3-2.dsc kmfl-keyboards-mywin_2.3.3-2.debian.tar.xz kmfl-keyboards-mywin_2.3.3-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
mmh_0.4-6_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Sep 2023 14:50:17 +0200 Source: mmh Architecture: source Version: 0.4-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Closes: 1046192 Changes: mmh (0.4-6) unstable; urgency=medium . * QA upload * Recover original stamp-h.in (Closes: #1046192) Checksums-Sha1: 32631660e0dcffb2b70888c8249875242dc4 1897 mmh_0.4-6.dsc 788bca38dabbf1953c306b8d08b8c028bee3c00b 13584 mmh_0.4-6.debian.tar.xz 521cbeae1fc23e9db7aded22dbb5d22691732b83 5537 mmh_0.4-6_source.buildinfo Checksums-Sha256: b5ceaf02fbb3e3c2d74fb79d7e1253da54c2bb361d1a66458f5276a9c6a240f4 1897 mmh_0.4-6.dsc 30d19d91030f178dad5cb253e148b9f40d280f0fbf9c123eeeb2ee5a5c397637 13584 mmh_0.4-6.debian.tar.xz b5c2470bb8cb6e6275988279c6c713227ab566c42514bff4050a95e523d3addf 5537 mmh_0.4-6_source.buildinfo Files: 5fae171acc434343e17a4a635949b016 1897 mail optional mmh_0.4-6.dsc a8fa8deb4422f7c89bdf813598dcf464 13584 mail optional mmh_0.4-6.debian.tar.xz 0e186dd6ebd2a86c6f7ab043150c2a5f 5537 mail optional mmh_0.4-6_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTx3m0QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFIGVDADVZDMEsDoZ6OOF7KSpZ+NCJYxFTj3xcbPi KcgKc9Ek39RZYAp7ur/Ib+xt737X3DPXYIEMN9FP0oOkLMAmicDnjfEGgqk3YNWM sz0dZoXmzM0pJ+bcPY1OWXVJdtpf/Lfatx81XUvhlaJoY0b59bt+oHbM/YmlDnGf SiuT+KRqK0/1AyS3emtzQQ0o4g9l5zrQO88za8nqxZgzaAF19KUhiN36sjK/uxwW rAUGtfRkX06gdbzQQcjDTN6fW18CssCgHMPv5/U8rwK/uezjIogP2IfeHfTwsaB9 Qm0UohU60VJQJzOwNoSreFiEv2bv7PazFFlK/rudA68ldRpkyOWiAe2q5uF8ZWB1 d6BSOaLlbvaZy82GEHtgtnxA9gcuOn+RUeJ/CD2nX/kt2S7KWuUZsiywT8tcFfjY MdrPrJ/h+wSjq4f5Lt285omMO7PQ+BWRHA0gDFon7ftDAh11zQ/wyKGbL4g4ZWIs GCMbJxQ7NBXCMaehiPO0NhgXBO3IaSg= =Xx50 -END PGP SIGNATURE-
Bug#1046192: marked as done (mmh: Fails to build source after successful build)
Your message dated Fri, 01 Sep 2023 13:10:03 + with message-id and subject line Bug#1046192: fixed in mmh 0.4-6 has caused the Debian Bug report #1046192, regarding mmh: Fails to build source after successful build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1046192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mmh Version: 0.4-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --- > > dpkg-buildpackage: info: source package mmh > dpkg-buildpackage: info: source version 0.4-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Adrian Bunk > dpkg-source --before-build . > debian/rules clean > dh clean --with autoreconf,bash-completion --no-parallel >dh_auto_clean -O--no-parallel > make -j1 distclean > make[1]: Entering directory '/<>' > for subdir in h config sbr uip etc man; do \ > target=`echo distclean-recursive | sed 's/-recursive//'`; \ > (cd $subdir && make CC='gcc' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' > DEFS='-DHAVE_CONFIG_H -D_GNU_SOURCE' CFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fcommon' LDFLAGS='-Wl,-z,relro -Wl,-z,now ' LIBS='' > prefix='/usr' exec_prefix='/usr' bindir='/usr/bin/mh' etcdir='/etc/mmh' > libdir='/usr/lib/mmh' mandir='/usr/share/man' mailspool='/var/mail' > sendmailpath='/usr/sbin/sendmail' $target) || exit 1; \ > done > make[2]: Entering directory '/<>/h' > rm -f *~ > rm -f Makefile > make[2]: Leaving directory '/<>/h' > make[2]: Entering directory '/<>/config' > rm -f *.o *~ > rm -f Makefile > make[2]: Leaving directory '/<>/config' > make[2]: Entering directory '/<>/sbr' > rm -f *.o *~ > rm -f libmh.a sigmsg.h > rm -f Makefile dtimep.c > make[2]: Leaving directory '/<>/sbr' > make[2]: Entering directory '/<>/uip' > rm -f *.o *~ > rm -f ali anno burst comp dist flist folder forw mmh mark mhbuild mhl mhsign > mhpgp mhlist mhmail mhparam mhpath mhstore new packf pick print-mimetype > prompter rcvdist rcvpack rcvstore refile repl rmf rmm send sendfiles show > slocal sortm spost whatnow whatnow2 whom ap dp fmtdump mhtest mmhwrap inc > rm -f Makefile > make[2]: Leaving directory '/<>/uip' > make[2]: Entering directory '/<>/etc' > rm -f *~ > rm -f Makefile > make[2]: Leaving directory '/<>/etc' > make[2]: Entering directory '/<>/man' > rm -f *~ > rm -f ali.1mh anno.1mh burst.1mh comp.1mh dist.1mh flist.1mh flists.1mh > folder.1mh folders.1mh forw.1mh inc.1mh mark.1mh mhbuild.1mh mhl.1mh > mhlist.1mh mhsign.1mh mhpgp.1mh mmh.1mh mmhwrap.1mh mhmail.1mh mhparam.1mh > mhpath.1mh mhstore.1mh new.1mh fnext.1mh fprev.1mh unseen.1mh next.1mh > packf.1mh pick.1mh prev.1mh prompter.1mh rcvdist.1mh rcvpack.1mh rcvstore.1mh > refile.1mh repl.1mh rmf.1mh rmm.1mh scan.1mh send.1mh sendfiles.1mh show.1mh > slocal.1mh sortm.1mh whatnow.1mh whom.1mh whatnow2.1mh mh-alias.5mh > mh-format.5mh mh-mail.5mh mh-profile.5mh mmh-intro.7mh mh-chart.7mh > mh-draft.7mh mh-sequence.7mh spost.8mh ap.8mh dp.8mh fmtdump.8mh > rm -f man.sed mh-chart.man7 > rm -f titles[0-9].temp > rm -f Makefile > make[2]: Leaving directory '/<>/man' > rm -f *~ > rm -rf autom4te.cache > rm -f Makefile config.h config.status config.log config.cache stamp-h > distname ChangeLog > make[1]: Leaving directory '/<>' >dh_autoreconf_clean -O--no-parallel >dh_clean -O--no-parallel > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: verifying ./mmh_0.4.orig.tar.gz.asc > dpkg-source: info: building mmh using existing ./mmh_0.4.orig.tar.gz > dpkg-source: info: building mmh using
Processing of mmh_0.4-6_source.changes
mmh_0.4-6_source.changes uploaded successfully to localhost along with the files: mmh_0.4-6.dsc mmh_0.4-6.debian.tar.xz mmh_0.4-6_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
lua-coxpcall_1.17.0-3_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Sep 2023 14:33:34 +0200 Source: lua-coxpcall Architecture: source Version: 1.17.0-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Changes: lua-coxpcall (1.17.0-3) unstable; urgency=medium . * QA upload * Drop lua5.2.dh-lua.conf Checksums-Sha1: 2387314e2e2b845e129bcc90bccec3ceeadfe81f 1749 lua-coxpcall_1.17.0-3.dsc fe494401495d83f0a667d1d8b9c0576884ce3eb6 3156 lua-coxpcall_1.17.0-3.debian.tar.xz ec3cd0d725fda66bc1f3b989c53fbb92593985db 6005 lua-coxpcall_1.17.0-3_source.buildinfo Checksums-Sha256: ac22ed69a46d60c2cd792eea4384062f6793cc27fda23e828f71639115370f46 1749 lua-coxpcall_1.17.0-3.dsc a9f1ad864c3d57570751e788b096908a9cd477b86249b0539e74ba464a7e2f24 3156 lua-coxpcall_1.17.0-3.debian.tar.xz 15d6eb451846e10940f81408276a1a0d13d13d55ffbc490c36de65d7d3b43a6f 6005 lua-coxpcall_1.17.0-3_source.buildinfo Files: b51fa3219154b50fc60621eadd8722a7 1749 interpreters optional lua-coxpcall_1.17.0-3.dsc 8617cc364cfedbb2f6c39a08bd489500 3156 interpreters optional lua-coxpcall_1.17.0-3.debian.tar.xz ed987f894c24e595d41da1a406a37aca 6005 interpreters optional lua-coxpcall_1.17.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTx2moQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFKBCDACWxeancXvJL4tQReS6KTP0CwhAQy35BQqD 0Im2KnpEVyHTkAWR/OLu+vdoo0kXmJ0kLJ/jqKi6a75/4a2AqwqzHfj7bM4HeBV4 lEAvOM8eEx8onVYPfOKX/6hdbCoDAstOiQAITfbXnMTHWqOmdBocFPI/KlEsslIu p/xM5KyYluC3zLM86ZEjbob2VVNpRtSZA3C2aTmAy56lG5kSlT5JfWjk5vjFfsgt 9t/D6EaU+uNBuPdzjgLS/psgwLNrfbAJmPzGO57xIMtY5Yd4XxVd4ciCIpJHX3zc cfsywraG3kJSfKweJq+LZP5fa6eHnRyb3a5lxhvJaQ4t1XzGYo28FIJeeCs5EGnF 6wb6Fz1GpiYkrkrw81SACtuaDN1lz4b+vmg6jouuYCt8ipQ7pagK33CQLQAA8LNZ aXiqAzPWr9r3Ya3tphBzO8ernu03vGFTz3EjV1CTulc+iNyqBrPdPvxy+Kgc5D7c sG094WwZsBrHgiNOj2m+jJMkQYYXGV8= =y1zj -END PGP SIGNATURE-
Processing of lua-coxpcall_1.17.0-3_source.changes
lua-coxpcall_1.17.0-3_source.changes uploaded successfully to localhost along with the files: lua-coxpcall_1.17.0-3.dsc lua-coxpcall_1.17.0-3.debian.tar.xz lua-coxpcall_1.17.0-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
apt-listchanges_3.26_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Sep 2023 14:22:56 +0200 Source: apt-listchanges Architecture: source Version: 3.26 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian Germann Changes: apt-listchanges (3.26) unstable; urgency=medium . * QA upload. * Remove constraints unnecessary since buster * Revert "Change maintainer to myself" (keep orphaned) . [ Akbarkhon Variskhanov ] * doc: Fix "and than" to "and then" Checksums-Sha1: c27f1c02df7e8f8428b667b5096171621b457997 1548 apt-listchanges_3.26.dsc b2850434006086a121d47a640761b708846dea22 143356 apt-listchanges_3.26.tar.xz 3e58ad98edd2824cca95792320453255f079a138 5949 apt-listchanges_3.26_source.buildinfo Checksums-Sha256: 4679e4cc023d751f1ccbc7a052810049c670f9b829a8f97ccbaebb1afb1ebee2 1548 apt-listchanges_3.26.dsc 1a0c6a7a396c9174167aca064c9c9067384a0ae48712c452bc6e5eeb941074f2 143356 apt-listchanges_3.26.tar.xz 71095bc5369491bee2e24abff788cc4f08baa5496a2c7a0a02925b6d4163dd52 5949 apt-listchanges_3.26_source.buildinfo Files: 95e44600d4385636eef353455ec040d5 1548 utils standard apt-listchanges_3.26.dsc 0cab3c920374e81a1bb3497d5c4e0294 143356 utils standard apt-listchanges_3.26.tar.xz ca60cc384e8b7f29eb741dbab7817c6a 5949 utils standard apt-listchanges_3.26_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTx1+IQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFB2tC/sGeQqjPBGrdUf6lcOxZCyAU5rl4fMDd1bd sWHzFJ0+W0NAdb9Qeqyfa+rxITYBNUDHOq/mOqbk9cSKiyHvahdyEmn2KZrtNzNz XamZ5iMylpLF+9MzaV5AkrYMQxTtKWLciL/OMXry6fR+jKmc9vJN5H3dZ+OzXHn+ qNVEXwCP0tBuyZkm0KVWlMdp+PAdqzX0bexkiZqAFRzC1Ld6TRMKyrV9V24TQYAp wl9uHfdyIp161dAXL21EY0hubpmMjquZL4m304FSjH2tk0ilgDxkOHhwJU9eniQf TMur9CpBDEhit4F+4/u59ScAL4nwG7f3WouLSnKwUN4FYW2JC7WPGQgwTtyTzOdw l6jyU9/9avA29D/ymHVdgHfIaBlVGC0xggAW7oWb84AvJJaHQWrSq3XmMnN/Sik6 w5tPW2ZNGbfJ5aou5Bq8zWY0cFGOQ8a0UUKgoZGVxxDCKQ+Xg21MMMtjIupRUTWc eLU9KG/Hme63emG0tPg7KGTGTPmC8EA= =EknD -END PGP SIGNATURE-
Processing of apt-listchanges_3.26_source.changes
apt-listchanges_3.26_source.changes uploaded successfully to localhost along with the files: apt-listchanges_3.26.dsc apt-listchanges_3.26.tar.xz apt-listchanges_3.26_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1051015: pekwm: please set XDG_CURRENT_DESKTOP and use it to configure xdg-desktop-portal
Package: pekwm
Version: 0.1.18-1
Severity: normal
User: xdg-desktop-por...@packages.debian.org
Usertags: portals.conf
As well as being available as a window manager to integrate into some
larger environment, Pekwm behaves like a very small desktop environment
in its own right, by providing a /usr/share/xsessions/pekwm.desktop
which can be selected on entry to a display manager such as lightdm.
If it's going to register as a desktop environment, then it should behave
like a desktop environment in other ways, such as choosing an
XDG_CURRENT_DESKTOP identifier.
xdg-desktop-portal 1.17.x introduces a new way to select which portals will
be used for which desktop environments, modelled on mimeapps.list:
- each desktop environment should provide a file like
/usr/share/xdg-desktop-portal/pekwm-portals.conf
- the filename is ${DESKTOP}-portals.conf where ${DESKTOP} is the desktop
environment's entry in $XDG_CURRENT_DESKTOP (the same as the DesktopNames
from /usr/share/{x,wayland-}sessions/*.desktop), folded to lower case
- sysadmins and users can override this via files named portals.conf or
${DESKTOP}-portals.conf in various locations like /etc/xdg-desktop-portal
and ~/.config/xdg-desktop-portal
But as far as I can tell, Pekwm doesn't set XDG_CURRENT_DESKTOP, so for
the purposes of this mechanism, it's not programmatically distinguishable
from any other desktop environment or window manager.
XDG_CURRENT_DESKTOP is also used in pre-existing freedesktop.org standards
like the OnlyShowIn/NotShowIn fields for .desktop files, and the ability to
provide a desktop-environment-specific mimeapps.list. Setting
XDG_CURRENT_DESKTOP would allow Pekwm to participate in those
specifications.
To reproduce
* Start from a basic non-GUI virtual machine (I used autopkgtest-build-qemu)
* Ensure that a user account exists
* apt install lightdm xorg pekwm
* reboot
* Log in as the user account, selecting "Pekwm" from the menu of
possible X11 sessions
* Open an xterm and run:
systemctl --user show-environment
(It's the systemd activation environment that matters here, more than
`env`, because xdg-desktop-portal will typically be run as a systemd
user service.)
Expected result
===
XDG_CURRENT_DESKTOP should be set to a colon-separated sequence of
desktop environment names, most specific first. Pekwm seems to be its
own thing rather than being based on another desktop environment, so
XDG_CURRENT_DESKTOP=Pekwm
would seem appropriate.
This would allow the Pekwm session to have its own
desktop-environment-specific mimeapps.list or portals.conf(5), for
example /usr/share/xdg-desktop-portal/pekwm-portals.conf.
Actual result
=
XDG_CURRENT_DESKTOP is unset.
This means that xdg-desktop-portal configuration can only be done via a
non-desktop-specific portals.conf, but that's not really something that a
non-opinionated distribution like Debian can usefully ship in a centralized
way, so each user of Pekwm who wants a working xdg-desktop-portal will
have to configure it themselves.
At the moment, this is mitigated by xdg-desktop-portal (>= 1.17) having
been patched to fall back to xdg-desktop-portal-gtk as a last-resort
desktop-environment-specific backend, but hard-coding that implementation
isn't really something we should be doing centrally (and the idea was
rejected upstream), so I intend to remove that patch before trixie
is released.
Suggested fix
=
Add a sequence of semicolon-separated desktop environment names to
/usr/share/xsessions/pekwm.desktop, most likely just "Pekwm":
DesktopNames=Pekwm;
(For example, icewm and windowmaker use "ICEWM" and "WindowMaker" in
their equivalent xsessions file.)
And then create a /usr/share/xdg-desktop-portal/pekwm-portals.conf
with whatever portal backends are desired for an Pekwm session,
for example perhaps this:
[preferred]
default=gtk;
Please see portals.conf(5) or its source code
https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst
for full details.
Thanks,
smcv
--
This is part of a mass bug filing:
https://lists.debian.org/debian-devel/2023/08/msg00311.html
Bug#1051012: miwm: please set XDG_CURRENT_DESKTOP and use it to configure xdg-desktop-portal
Package: miwm
Version: 1.1-8
Severity: normal
User: xdg-desktop-por...@packages.debian.org
Usertags: portals.conf
As well as being available as a window manager to integrate into some
larger environment, Miwm behaves like a very small desktop environment
in its own right, by providing a /usr/share/xsessions/miwm.desktop
which can be selected on entry to a display manager such as lightdm.
If it's going to register as a desktop environment, then it should behave
like a desktop environment in other ways, such as choosing an
XDG_CURRENT_DESKTOP identifier.
xdg-desktop-portal 1.17.x introduces a new way to select which portals will
be used for which desktop environments, modelled on mimeapps.list:
- each desktop environment should provide a file like
/usr/share/xdg-desktop-portal/miwm-portals.conf
- the filename is ${DESKTOP}-portals.conf where ${DESKTOP} is the desktop
environment's entry in $XDG_CURRENT_DESKTOP (the same as the DesktopNames
from /usr/share/{x,wayland-}sessions/*.desktop), folded to lower case
- sysadmins and users can override this via files named portals.conf or
${DESKTOP}-portals.conf in various locations like /etc/xdg-desktop-portal
and ~/.config/xdg-desktop-portal
But as far as I can tell, Miwm doesn't set XDG_CURRENT_DESKTOP, so for
the purposes of this mechanism, it's not programmatically distinguishable
from any other desktop environment or window manager.
XDG_CURRENT_DESKTOP is also used in pre-existing freedesktop.org standards
like the OnlyShowIn/NotShowIn fields for .desktop files, and the ability to
provide a desktop-environment-specific mimeapps.list. Setting
XDG_CURRENT_DESKTOP would allow Miwm to participate in those
specifications.
To reproduce
* Start from a basic non-GUI virtual machine (I used autopkgtest-build-qemu)
* Ensure that a user account exists
* apt install lightdm xorg miwm
* reboot
* Log in as the user account, selecting "Miwm" from the menu of
possible X11 sessions
* Open an xterm and run:
systemctl --user show-environment
(It's the systemd activation environment that matters here, more than
`env`, because xdg-desktop-portal will typically be run as a systemd
user service.)
Expected result
===
XDG_CURRENT_DESKTOP should be set to a colon-separated sequence of
desktop environment names, most specific first. Miwm seems to be its
own thing rather than being based on another desktop environment, so
XDG_CURRENT_DESKTOP=Miwm
would seem appropriate.
This would allow the Miwm session to have its own
desktop-environment-specific mimeapps.list or portals.conf(5), for
example /usr/share/xdg-desktop-portal/miwm-portals.conf.
Actual result
=
XDG_CURRENT_DESKTOP is unset.
This means that xdg-desktop-portal configuration can only be done via a
non-desktop-specific portals.conf, but that's not really something that a
non-opinionated distribution like Debian can usefully ship in a centralized
way, so each user of Miwm who wants a working xdg-desktop-portal will
have to configure it themselves.
At the moment, this is mitigated by xdg-desktop-portal (>= 1.17) having
been patched to fall back to xdg-desktop-portal-gtk as a last-resort
desktop-environment-specific backend, but hard-coding that implementation
isn't really something we should be doing centrally (and the idea was
rejected upstream), so I intend to remove that patch before trixie
is released.
Suggested fix
=
Add a sequence of semicolon-separated desktop environment names to
/usr/share/xsessions/miwm.desktop, most likely just "Miwm":
DesktopNames=Miwm;
(For example, icewm and windowmaker use "ICEWM" and "WindowMaker" in
their equivalent xsessions file.)
And then create a /usr/share/xdg-desktop-portal/miwm-portals.conf
with whatever portal backends are desired for an Miwm session,
for example perhaps this:
[preferred]
default=gtk;
Please see portals.conf(5) or its source code
https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst
for full details.
Thanks,
smcv
--
This is part of a mass bug filing:
https://lists.debian.org/debian-devel/2023/08/msg00311.html
Bug#1051010: lwm: please set XDG_CURRENT_DESKTOP and use it to configure xdg-desktop-portal
Package: lwm
Version: 1.2.4-1
Severity: normal
User: xdg-desktop-por...@packages.debian.org
Usertags: portals.conf
As well as being available as a window manager to integrate into some
larger environment, Lwm behaves like a very small desktop environment
in its own right, by providing a /usr/share/xsessions/lwm.desktop
which can be selected on entry to a display manager such as lightdm.
If it's going to register as a desktop environment, then it should behave
like a desktop environment in other ways, such as choosing an
XDG_CURRENT_DESKTOP identifier.
xdg-desktop-portal 1.17.x introduces a new way to select which portals will
be used for which desktop environments, modelled on mimeapps.list:
- each desktop environment should provide a file like
/usr/share/xdg-desktop-portal/lwm-portals.conf
- the filename is ${DESKTOP}-portals.conf where ${DESKTOP} is the desktop
environment's entry in $XDG_CURRENT_DESKTOP (the same as the DesktopNames
from /usr/share/{x,wayland-}sessions/*.desktop), folded to lower case
- sysadmins and users can override this via files named portals.conf or
${DESKTOP}-portals.conf in various locations like /etc/xdg-desktop-portal
and ~/.config/xdg-desktop-portal
But as far as I can tell, Lwm doesn't set XDG_CURRENT_DESKTOP, so for
the purposes of this mechanism, it's not programmatically distinguishable
from any other desktop environment or window manager.
XDG_CURRENT_DESKTOP is also used in pre-existing freedesktop.org standards
like the OnlyShowIn/NotShowIn fields for .desktop files, and the ability to
provide a desktop-environment-specific mimeapps.list. Setting
XDG_CURRENT_DESKTOP would allow Lwm to participate in those
specifications.
To reproduce
* Start from a basic non-GUI virtual machine (I used autopkgtest-build-qemu)
* Ensure that a user account exists
* apt install lightdm xorg lwm
* reboot
* Log in as the user account, selecting "Lwm" from the menu of
possible X11 sessions
* Open an xterm and run:
systemctl --user show-environment
(It's the systemd activation environment that matters here, more than
`env`, because xdg-desktop-portal will typically be run as a systemd
user service.)
Expected result
===
XDG_CURRENT_DESKTOP should be set to a colon-separated sequence of
desktop environment names, most specific first. Lwm seems to be its
own thing rather than being based on another desktop environment, so
XDG_CURRENT_DESKTOP=Lwm
would seem appropriate.
This would allow the Lwm session to have its own
desktop-environment-specific mimeapps.list or portals.conf(5), for
example /usr/share/xdg-desktop-portal/lwm-portals.conf.
Actual result
=
XDG_CURRENT_DESKTOP is unset.
This means that xdg-desktop-portal configuration can only be done via a
non-desktop-specific portals.conf, but that's not really something that a
non-opinionated distribution like Debian can usefully ship in a centralized
way, so each user of Lwm who wants a working xdg-desktop-portal will
have to configure it themselves.
At the moment, this is mitigated by xdg-desktop-portal (>= 1.17) having
been patched to fall back to xdg-desktop-portal-gtk as a last-resort
desktop-environment-specific backend, but hard-coding that implementation
isn't really something we should be doing centrally (and the idea was
rejected upstream), so I intend to remove that patch before trixie
is released.
Suggested fix
=
Add a sequence of semicolon-separated desktop environment names to
/usr/share/xsessions/lwm.desktop, most likely just "Lwm":
DesktopNames=Lwm;
(For example, icewm and windowmaker use "ICEWM" and "WindowMaker" in
their equivalent xsessions file.)
And then create a /usr/share/xdg-desktop-portal/lwm-portals.conf
with whatever portal backends are desired for an Lwm session,
for example perhaps this:
[preferred]
default=gtk;
Please see portals.conf(5) or its source code
https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst
for full details.
Thanks,
smcv
--
This is part of a mass bug filing:
https://lists.debian.org/debian-devel/2023/08/msg00311.html
Bug#1051000: ctwm: please set XDG_CURRENT_DESKTOP and use it to configure xdg-desktop-portal
Package: ctwm
Version: 4.0.3-2
Severity: normal
User: xdg-desktop-por...@packages.debian.org
Usertags: portals.conf
As well as being available as a window manager to integrate into some
larger environment, CTWM behaves like a very small desktop environment
in its own right, by providing a /usr/share/xsessions/ctwm.desktop
which can be selected on entry to a display manager such as lightdm.
If it's going to register as a desktop environment, then it should behave
like a desktop environment in other ways, such as choosing an
XDG_CURRENT_DESKTOP identifier.
xdg-desktop-portal 1.17.x introduces a new way to select which portals will
be used for which desktop environments, modelled on mimeapps.list:
- each desktop environment should provide a file like
/usr/share/xdg-desktop-portal/ctwm-portals.conf
- the filename is ${DESKTOP}-portals.conf where ${DESKTOP} is the desktop
environment's entry in $XDG_CURRENT_DESKTOP (the same as the DesktopNames
from /usr/share/{x,wayland-}sessions/*.desktop), folded to lower case
- sysadmins and users can override this via files named portals.conf or
${DESKTOP}-portals.conf in various locations like /etc/xdg-desktop-portal
and ~/.config/xdg-desktop-portal
But as far as I can tell, CTWM doesn't set XDG_CURRENT_DESKTOP, so for
the purposes of this mechanism, it's not programmatically distinguishable
from any other desktop environment or window manager.
XDG_CURRENT_DESKTOP is also used in pre-existing freedesktop.org standards
like the OnlyShowIn/NotShowIn fields for .desktop files, and the ability to
provide a desktop-environment-specific mimeapps.list. Setting
XDG_CURRENT_DESKTOP would allow CTWM to participate in those
specifications.
To reproduce
* Start from a basic non-GUI virtual machine (I used autopkgtest-build-qemu)
* Ensure that a user account exists
* apt install lightdm xorg ctwm
* reboot
* Log in as the user account, selecting "CTWM" from the menu of
possible X11 sessions
* Open an xterm and run:
systemctl --user show-environment
(It's the systemd activation environment that matters here, more than
`env`, because xdg-desktop-portal will typically be run as a systemd
user service.)
Expected result
===
XDG_CURRENT_DESKTOP should be set to a colon-separated sequence of
desktop environment names, most specific first. CTWM seems to be its
own thing rather than being based on another desktop environment, so
XDG_CURRENT_DESKTOP=CTWM
would seem appropriate.
This would allow the CTWM session to have its own
desktop-environment-specific mimeapps.list or portals.conf(5), for
example /usr/share/xdg-desktop-portal/ctwm-portals.conf.
Actual result
=
XDG_CURRENT_DESKTOP is unset.
This means that xdg-desktop-portal configuration can only be done via a
non-desktop-specific portals.conf, but that's not really something that a
non-opinionated distribution like Debian can usefully ship in a centralized
way, so each user of CTWM who wants a working xdg-desktop-portal will
have to configure it themselves.
At the moment, this is mitigated by xdg-desktop-portal (>= 1.17) having
been patched to fall back to xdg-desktop-portal-gtk as a last-resort
desktop-environment-specific backend, but hard-coding that implementation
isn't really something we should be doing centrally (and the idea was
rejected upstream), so I intend to remove that patch before trixie
is released.
Suggested fix
=
Add a sequence of semicolon-separated desktop environment names to
/usr/share/xsessions/ctwm.desktop, most likely just "CTWM":
DesktopNames=CTWM;
(For example, icewm and windowmaker use "ICEWM" and "WindowMaker" in
their equivalent xsessions file.)
And then create a /usr/share/xdg-desktop-portal/ctwm-portals.conf
with whatever portal backends are desired for an CTWM session,
for example perhaps this:
[preferred]
default=gtk;
Please see portals.conf(5) or its source code
https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst
for full details.
Thanks,
smcv
--
This is part of a mass bug filing:
https://lists.debian.org/debian-devel/2023/08/msg00311.html
