Bug#1020681: ITP: dde-store -- DDE Store for Deepin Desktop Environment

[Arun Kumar Pariyar]

Package: wnpp
Severity: wishlist
Owner: Arun Kumar Pariyar 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: dde-store
  Version : 1.2.3
  Upstream Author : dekzi 
* URL : https://github.com/dekzi/dde-store
* License : GPL-3
  Programming Lang: C++, Qt
  Description : DDE Store for Deepin Desktop Environment

DDE Store is an app store for DDE built with Deepin Tool Kit (DTK).
This app store is designed for use with the Deepin Desktop
Environment and, is built with AppStream and PackageKit.


OpenPGP_0x4B542AF704F74516.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020706: ITP: golang-github-gonvenience-text -- convenience functions for strings

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: ChangZhuo Chen (陳昌倬) 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: golang-github-gonvenience-text
  Version : 1.0.7
  Upstream Author : Matthias Diester
* URL : 
https://salsa.debian.org/go-team/packages/golang-github-gonvenience-text
* License : Expat
  Programming Lang: Golang
  Description : convenience functions for strings

 This package will be maintained under Debian Go Packaging Team.
 This is dependencies of dyff (https://bugs.debian.org/1013751).

-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Secure Boot dbx Configuration Update

[John Darrah]

Hello,

I'm tracking testing and with my most recent update I started getting
the nag to update the Secure Boot dbx. When I click the graphical
'update' button it appears to update something, but the update button
remains as if nothing changed.

I normally update my system by logging out of the graphical session and
using a virtual console with the command line. Checking from the
command line, there doesn't seem to be any requirement to update
anything, so I'm a little confused.

I'm posting here because I don't know if this is a bug or what facility
I would even file a bug report against.

Any comment or clue on this would be helpful.

Thanks.

-- john

Bug#1020716: ITP: tryton-modules-* -- Collection of 56 base modules for the Tryton application platform

[Mathias Behrle]

X-Debbugs-CC: debian-devel@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Debian Tryton Maintainers 


I am merging 56 ITPs into this one to avoid spamming d-devel with 56
single mails. All those modules are base modules published by the Tryton
project. With the packaging of those missing modules we are closing the gap
between what is available in Tryton and Debian.

As all of the following templates were created automatically, all descriptions
etc. will of course be some more reviewed.



From: Mathias Behrle 
To: Debian Bug Tracking System 
Subject: ITP: tryton-modules-purchase-secondary-unit -- Tryton application 
platform - purchase secondary unit module

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-devel@lists.debian.org
Owner: Debian Tryton Maintainers 

* Package name: tryton-modules-purchase-secondary-unit
  Version : 6.0.0
  Upstream Author : Tryton project (www.tryton.org)
* URL : https://downloads.tryton.org/6.0
* License : GPL-3+
  Programming Lang: Python
  Description : Tryton application platform - purchase secondary unit module

 Tryton is a high-level general purpose application platform. It is the base
 of a complete business solution as well as a comprehensive health and hospital
 information system (GNUHealth).
 .
 The purchase secondary unit module adds a secondary unit of measure on purchase
 lines.
 The secondary quantity and unit price are kept synchronized with the quantity
 and unit price.
 The secondary unit is defined on the product supplier or on the product with
 its factor against the purchase unit.


This package is another base module published by the Tryton project.From: 
Mathias Behrle 
To: Debian Bug Tracking System 
Subject: ITP: tryton-modules-production-outsourcing -- Tryton application 
platform - production outsourcing module

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-devel@lists.debian.org
Owner: Debian Tryton Maintainers 

* Package name: tryton-modules-production-outsourcing
  Version : 6.0.0
  Upstream Author : Tryton project (www.tryton.org)
* URL : https://downloads.tryton.org/6.0
* License : GPL-3+
  Programming Lang: Python
  Description : Tryton application platform - production outsourcing module

 Tryton is a high-level general purpose application platform. It is the base
 of a complete business solution as well as a comprehensive health and hospital
 information system (GNUHealth).
 .
 The production outsourcing module allows to outsource production order per
 routing. When such outsourced production is set to waiting, a purchase order is
 created and its cost is added to the production.
 .
 To define an outsourced production, the routing must have a *Supplier*, a
 *Service* and its *Quantity* defined. Those values will be used to create the
 purchase order. The bought quantity is computed by multiplying the *Quantity*
 by the factor between the bill of material and the production quantity.


This package is another base module published by the Tryton project.From: 
Mathias Behrle 
To: Debian Bug Tracking System 
Subject: ITP: tryton-modules-sale-gift-card -- Tryton application platform - 
sale gift card module

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-devel@lists.debian.org
Owner: Debian Tryton Maintainers 

* Package name: tryton-modules-sale-gift-card
  Version : 6.0.4
  Upstream Author : Tryton project (www.tryton.org)
* URL : https://downloads.tryton.org/6.0
* License : GPL-3+
  Programming Lang: Python
  Description : Tryton application platform - sale gift card module

 Tryton is a high-level general purpose application platform. It is the base
 of a complete business solution as well as a comprehensive health and hospital
 information system (GNUHealth).
 .
 The *Sale Gift Card Module* manages the selling and redeeming of gift cards.
 .


This package is another base module published by the Tryton project.From: 
Mathias Behrle 
To: Debian Bug Tracking System 
Subject: ITP: tryton-modules-marketing -- Tryton application platform - 
marketing module

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-devel@lists.debian.org
Owner: Debian Tryton Maintainers 

* Package name: tryton-modules-marketing
  Version : 6.0.0
  Upstream Author : Tryton project (www.tryton.org)
* URL : https://downloads.tryton.org/6.0
* License : GPL-3+
  Programming Lang: Python
  Description : Tryton application platform - marketing module

 Tryton is a high-level general purpose application platform. It is the base
 of a complete business solution as well as a comprehensive health and hospital
 information system (GNUHealth).
 .
 The marketing module defines the fundamentals for marketing modules.


This package is another base module published by the Tryton project.From: 
Mathias Behrle 
To: Debian Bug Tracking System 
Subject: ITP: tryton-modules-account-statement-aeb43 -- Tryton appl

Re: Transition proposal: pkg-config to pkgconf

[Tollef Fog Heen]

]] "Andrej Shadura" 

> Most importantly, I need a green light from the current pkg-config
> maintainer (Tollef) to proceed with the plan.

My interest in pkg-config has waned over the years (and so has the hours
put into maintenance of it), so if you want to bring it forward, go
ahead.

Cheers,
-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Re: Secure Boot dbx Configuration Update

[Ansgar]

On Sun, 2022-09-25 at 11:17 -0700, John Darrah wrote:
> I'm tracking testing and with my most recent update I started getting
> the nag to update the Secure Boot dbx. When I click the graphical
> 'update' button it appears to update something, but the update button
> remains as if nothing changed.

Some firmware updates, including DBX updates, are distributed via a
different service than apt: fwupd.  The fwupdmgr program provides a
command-line interface; the most helpful commands are probably
"fwupdmgr get-updates" (get list of updates, i.e., equivalent to "apt
update"), "fwupdmgr update" (install updates) and "fwupdmgr get-
history" (history of installed firmware updates).

The system logs might also show what the graphical update tries to
install or why it might fail.

> I'm posting here because I don't know if this is a bug or what
> facility I would even file a bug report against.

If the graphical interface (which one?) doesn't manage to successfully
install the update or still offers the update even though it was
installed, then that is probably a bug.

Ansgar

Bug email is not getting to me

[Steven Robbins]

Hi,

When I first started with Debian many many years ago, I would routinely see 
email for bug reports submitted against packages I maintain, and responses to 
said bugs.  Nowadays I get essentially none of that.  The only way I see such 
responses is by perusing bugs via the web interface -- which I do infrequently 
so messages languish.

I may have missed when something changed over the years.  Is there something I 
must do to get bugs.debian.org to reliably send me email?

I just noticed today that this applies even to responses that apparently 
directly CC my debian address; e.g. https://bugs.debian.org/cgi-bin/
bugreport.cgi?bug=1020397;msg=10

I literally searched my mail logs for the Message-ID in question and it is not 
reported.  So it appears to have been hung up somewhere.  How can I debug 
this?

I have sent a test email to my debian address and it came through.  So I think 
email is normally being delivered.  Just not from bug reports.

Thanks,
-Steve

P.S.  This has been happening for months if not years.  It's just that I 
haven't been motivated to ask the question until now.

P.P.S.  I don't subscribe to any debian lists, so it is appreciated to 
directly cc me in replies.



signature.asc
Description: This is a digitally signed message part.

Re: Bug email is not getting to me

[Andrea Pappacoda]

Il giorno dom 25 set 2022 alle 15:42:40 -05:00:00, Steven Robbins 
 ha scritto:
When I first started with Debian many many years ago, I would 
routinely see
email for bug reports submitted against packages I maintain, and 
responses to

said bugs.  Nowadays I get essentially none of that.


Hi, I think that this is related to bug #754809.

Re: Bug email is not getting to me

[Geert Stappers]

On Sun, Sep 25, 2022 at 03:42:40PM -0500, Steven Robbins wrote:
> Hi,
> 
> When I first started with Debian many many years ago, I would routinely see 
> email for bug reports submitted against packages I maintain, and responses to 
> said bugs.  Nowadays I get essentially none of that.  The only way I see such 
> responses is by perusing bugs via the web interface -- which I do 
> infrequently 
> so messages languish.
> 
> I may have missed when something changed over the years.  Is there something 
> I 
> must do to get bugs.debian.org to reliably send me email?
> 
> I just noticed today that this applies even to responses that apparently 
> directly CC my debian address; e.g. https://bugs.debian.org/cgi-bin/
> bugreport.cgi?bug=1020397;msg=10
> 
> I literally searched my mail logs for the Message-ID in question and it is 
> not 
> reported.  So it appears to have been hung up somewhere.  How can I debug 
> this?
> 
> I have sent a test email to my debian address and it came through.  So I 
> think 
> email is normally being delivered.  Just not from bug reports.
> 

Who is running the incoming mail server?

 
> P.S.  This has been happening for months if not years.  It's just that I 
> haven't been motivated to ask the question until now.

So the change might be "fresh".

 
> P.P.S.  I don't subscribe to any debian lists, so it is appreciated to 
> directly cc me in replies.

You are welcome



Groeten
Geert Stappers
Runs his own mail server
-- 
Silence is hard to parse

Re: Bug email is not getting to me

[Steven Robbins]

On Sunday, September 25, 2022 3:49:37 P.M. CDT Geert Stappers wrote:
> On Sun, Sep 25, 2022 at 03:42:40PM -0500, Steven Robbins wrote:

> > I just noticed today that this applies even to responses that apparently
> > directly CC my debian address; e.g. https://bugs.debian.org/cgi-bin/
> > bugreport.cgi?bug=1020397;msg=10
> > 
> > I literally searched my mail logs for the Message-ID in question and it is
> > not reported.  So it appears to have been hung up somewhere.  How can I
> > debug this?
> > 
> > I have sent a test email to my debian address and it came through.  So I
> > think email is normally being delivered.  Just not from bug reports.
> 
> Who is running the incoming mail server?

The mail server is run by my ISP (shaw.ca).  Using fetchmail, I pick up the 
email via IMAP and send it into my local server.  So in my original message 
when I said I had checked the logs -- it was my local server logs.

To re-iterate: mail sent today to my debian address from outside debian came 
through OK.  Mail sent from bugs.debian.org apparently does not.  I think if 
there were any issue with the incoming email server (e.g. the DMARC thing that 
Andrea Pappacoda referenced) that would affect all email to me at debian, 
wouldn't it?

-Steve


signature.asc
Description: This is a digitally signed message part.

Re: Bug email is not getting to me

[Adam D. Barratt]

On Sun, 2022-09-25 at 15:42 -0500, Steven Robbins wrote:
> When I first started with Debian many many years ago, I would
> routinely see 
> email for bug reports submitted against packages I maintain, and
> responses to 
> said bugs.  Nowadays I get essentially none of that.  The only way I
> see such 
> responses is by perusing bugs via the web interface -- which I do
> infrequently 
> so messages languish.
> 
> I may have missed when something changed over the years.  Is there
> something I 
> must do to get bugs.debian.org to reliably send me email?
> 
> I just noticed today that this applies even to responses that
> apparently 
> directly CC my debian address; e.g. https://bugs.debian.org/cgi-bin/
> bugreport.cgi?bug=1020397;msg=10
> 

The copy of that mail to your debian.org address is being rejected by
your mail server (slightly harvesting-fudged by me; the original log
has valid addresses):

2022-09-25 13:52:49 1obmVB-00FbmZ-3r == steve.robbins [at] shaw.ca
R=dnslookup T=remote_smtp defer (-46) H=shw-central.mx.a.cloudfilter.net 
[15.222.199.59] DT=4s: SMTP error from remote mail server after end of data: 
421 4.2.0  sender rejected AUP#SNDR

If you want to know _why_, I suggest you talk to the mail server
operator and/or check your settings.

Regards,

Adam

Re: Bug email is not getting to me

[Russ Allbery]

Steven Robbins  writes:

> To re-iterate: mail sent today to my debian address from outside debian
> came through OK.  Mail sent from bugs.debian.org apparently does not.  I
> think if there were any issue with the incoming email server (e.g. the
> DMARC thing that Andrea Pappacoda referenced) that would affect all
> email to me at debian, wouldn't it?

No, the annoying thing about the DMARC problem is that its effect depends
on the configuration settings of the person sending the email.

If someone sends mail from a domain that says all mail from that domain
will always have good DKIM signatures, and if the signature isn't present
or doesn't validate the mail should be rejected, and that message is
forwarded through bugs.debian.org to someone whose mail server honors
DMARC settings, the mail will be rejected.  That's because the process of
modifying the message in the way that bugs.debian.org needs to do (adding
the bug number to the Subject header, for instance) usually breaks the
signature.

If you send mail from a domain that has a more relaxed (or no) DMARC
configuration, then your mail will go through fine and you'll not see the
problem.

-- 
Russ Allbery (r...@debian.org)  

Bug#1020744: ITP: cheat -- Create and view interactive cheatsheets

[Stanislas Marquis]

Package: wnpp
Severity: wishlist
Owner: Stanislas Marquis 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian...@lists.debian.org, 
s...@astrorigin.com

* Package name: cheat
  Version : 4.3.3-1
  Upstream Author : Christopher Allen Lane 
* URL : https://github.com/cheat/cheat
* License : Expat
  Programming Lang: Go
  Description : Create and view interactive cheatsheets

'cheat' allows you to create and view interactive cheatsheets on the
command-line. It was designed to help remind *nix system administrators
of options for commands that they use frequently, but not frequently
enough to remember. It can also be used as a lightweight and flexible
note-taking application.

I intend to maintain this package within the Debian Go team.

Re: Secure Boot dbx Configuration Update

[LeJacq, Jean Pierre]

On Sunday, September 25, 2022 4:03:50 PM EDT Ansgar wrote:
> On Sun, 2022-09-25 at 11:17 -0700, John Darrah wrote:
> > I'm tracking testing and with my most recent update I started getting
> > the nag to update the Secure Boot dbx. When I click the graphical
> > 'update' button it appears to update something, but the update button
> > remains as if nothing changed.
> 
> Some firmware updates, including DBX updates, are distributed via a
> different service than apt: fwupd.  The fwupdmgr program provides a
> command-line interface; the most helpful commands are probably
> "fwupdmgr get-updates" (get list of updates, i.e., equivalent to "apt
> update"), "fwupdmgr update" (install updates) and "fwupdmgr get-
> history" (history of installed firmware updates).

I follow exactly this process and get the following error. This started 
occurring about a week ago.

Upgrade available for UEFI dbx from 77 to 217
UEFI dbx and all connected devices may not be usable while updating. Continue 
with update? [Y|n]: Y
Downloading… [***]
Decompressing…   [***]
Authenticating…  [***]
Authenticating…  [***]
Updating UEFI dbx…   [***]
Verifying…   [***]
Blocked executable in the ESP, ensure grub and shim are up to date: /boot/efi/
EFI/BOOT/shimx64.efi Authenticode checksum 
[af79b14064601bc0987d4747af1e914a228c05d622ceda03b7a4f67014fee767] is present 
in dbx

I believe the error is due to the following bug reported in the upstream bug 
system.

https://github.com/fwupd/fwupd/issues/5035

This particular bug doesn't appear in the Debian bugs for the package fwupd. 
I'm also running stable which has a terribly outdated version of fwupd. I'm on 
a Lenovo Thinkpad X1. I need to investigate a bit more before filing a bug 
report.

-- 
JP


signature.asc
Description: This is a digitally signed message part.

Re: Secure Boot dbx Configuration Update

[John Darrah]

On Sun, 2022-09-25 at 13:05 -0700, Ansgar wrote:
> On Sun, 2022-09-25 at 11:17 -0700, John Darrah wrote:
> > I'm tracking testing and with my most recent update I started
> > getting
> > the nag to update the Secure Boot dbx. When I click the graphical
> > 'update' button it appears to update something, but the update
> > button
> > remains as if nothing changed.
> 
> Some firmware updates, including DBX updates, are distributed via a
> different service than apt: fwupd.  The fwupdmgr program provides a
> command-line interface; the most helpful commands are probably
> "fwupdmgr get-updates" (get list of updates, i.e., equivalent to "apt
> update"), "fwupdmgr update" (install updates) and "fwupdmgr get-
> history" (history of installed firmware updates).
> 
> The system logs might also show what the graphical update tries to
> install or why it might fail.
> 
> > I'm posting here because I don't know if this is a bug or what
> > facility I would even file a bug report against.
> 
> If the graphical interface (which one?) doesn't manage to
> successfully
> install the update or still offers the update even though it was
> installed, then that is probably a bug.
> 
> Ansgar
> 

The graphical interface is the Gnome Software facility, fyi.

Per your suggestion I looked at fwupdmgr get-history and see the
following:

Update Error: Blocked executable in the ESP, ensure grub and shim are
up to date: /boot/efi/EFI/BOOT/BOOTX64.EFI Authenticode checksum
[2ea4cb6a1f1eb1d3dce82d54fde26ded243ba3e18de7c6d211902a594fe56788] is
present in dbx

The kernel reports the secure boot is disabled, btw. I guess I'm now
wondering if it will update if I'm not using secureboot. If this is the
case, maybe it should check if secureboot is enabled before offering
the update.

Thanks

-- john

Re: Bug email is not getting to me

[Steven Robbins]

Thanks to all who responded.  I have learned a lot!

On Sunday, September 25, 2022 4:57:19 P.M. CDT Russ Allbery wrote:

> Steven Robbins  writes:
> > To re-iterate: mail sent today to my debian address from outside debian
> > came through OK.  Mail sent from bugs.debian.org apparently does not.  I
> > think if there were any issue with the incoming email server (e.g. the
> > DMARC thing that Andrea Pappacoda referenced) that would affect all
> > email to me at debian, wouldn't it?
> 
> No, the annoying thing about the DMARC problem is that its effect depends
> on the configuration settings of the person sending the email.

Oh!  OK.  So Adam Barratt found a log somewhere that confirms my ISP is 
blocking the sender.  

> If someone sends mail from a domain that says all mail from that domain
> will always have good DKIM signatures, and if the signature isn't present
> or doesn't validate the mail should be rejected, and that message is
> forwarded through bugs.debian.org to someone whose mail server honors
> DMARC settings, the mail will be rejected.  That's because the process of
> modifying the message in the way that bugs.debian.org needs to do (adding
> the bug number to the Subject header, for instance) usually breaks the
> signature.

So are you effectively confirming this is indeed the DMARC bug [1] filed in 
2014?

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754809

> If you send mail from a domain that has a more relaxed (or no) DMARC
> configuration, then your mail will go through fine and you'll not see the
> problem.

Well, OK.  But I'm  the recipient not the sender so this advice is hard to 
implement :-)

-Steve


signature.asc
Description: This is a digitally signed message part.

Re: Bug email is not getting to me

[Russ Allbery]

Steven Robbins  writes:
> On Sunday, September 25, 2022 4:57:19 P.M. CDT Russ Allbery wrote:

>> If someone sends mail from a domain that says all mail from that domain
>> will always have good DKIM signatures, and if the signature isn't
>> present or doesn't validate the mail should be rejected, and that
>> message is forwarded through bugs.debian.org to someone whose mail
>> server honors DMARC settings, the mail will be rejected.  That's
>> because the process of modifying the message in the way that
>> bugs.debian.org needs to do (adding the bug number to the Subject
>> header, for instance) usually breaks the signature.

> So are you effectively confirming this is indeed the DMARC bug [1] filed
> in 2014?

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754809

Yeah, that's my guess.  It's a very common problem.

The right solution is probably for bugs.debian.org to rewrite all incoming
mail to change the From header to a debian.org address (probably the bug
address) and add a Reply-To header pointing to the original sender.  This
is the fix that Mailman mostly uses, and it seems to work (I've had this
problem with multiple mailing lists I run and turning on this message
mangling has fixed it).  But of course someone has to find time to
implement this.

-- 
Russ Allbery (r...@debian.org)