Your message dated Tue, 16 Oct 2018 01:30:46 +0200 with message-id <1539646246.27420.2.camel@jasp.net> and subject line Re: Bug#889042: lintian: Do not use dot as a separator in build profile names has caused the Debian Bug report #889042, regarding lintian: Do not use dot as a separator in build profile names 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 owner@bugs.debian.org immediately.) -- 889042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889042 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: lintian: Do not use dot as a separator in build profile names
- From: Javier Serrano Polo <javier@jasp.net>
- Date: Thu, 01 Feb 2018 13:16:17 +0100
- Message-id: <1517487377.20410.112.camel@sempati.menos4>
- Reply-to: javier--7C8FrOsBhwV6hRgYM4mLHJBYcgPTm9@jasp.net
Package: lintian Version: 2.5.72 Severity: wishlist Please switch the dot to a suitable character, such as slash, in pkg.$sourcepackage.$anything build profile names, since dot is a valid character in package names.Attachment: smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---
- To: 889042-done@bugs.debian.org
- Subject: Re: Bug#889042: lintian: Do not use dot as a separator in build profile names
- From: Javier Serrano Polo <javier@jasp.net>
- Date: Tue, 16 Oct 2018 01:30:46 +0200
- Message-id: <1539646246.27420.2.camel@jasp.net>
- Reply-to: javier--RYqcOWXjKCUG7XJMmIvJ70vaPc5WKG@jasp.net
- In-reply-to: <[🔎] 1539608460.455226.1542427944.0C84A426@webmail.messagingengine.com>
- References: <1517487377.20410.112.camel@sempati.menos4> <1517487377.20410.112.camel@sempati.menos4> <1517508583.2647902.1256245520.2D3A6E48@webmail.messagingengine.com> <2b834f9e-6fc7-fd06-1ea0-06f3bb6f2e28@thykier.net> <20180202055011.GA7655@alf.mars> <1517576062.17796.39.camel@sempati.menos4> <1517487377.20410.112.camel@sempati.menos4> <1531442634.27140.7.camel@jasp.net> <1531469862.934711.1439430072.3229EF43@webmail.messagingengine.com> <1517487377.20410.112.camel@sempati.menos4> <1531472902.27140.9.camel@jasp.net> <1531473483.949594.1439478248.1B7AFF68@webmail.messagingengine.com> <1517487377.20410.112.camel@sempati.menos4> <1539385381.25361.74.camel@jasp.net> <[🔎] 1539417174.548534.1540616352.6CD74F26@webmail.messagingengine.com> <1517487377.20410.112.camel@sempati.menos4> <1539479285.25361.90.camel@jasp.net> <[🔎] 1539608460.455226.1542427944.0C84A426@webmail.messagingengine.com>
El dl 15 de 10 de 2018 a les 14:01 +0100, Chris Lamb va escriure: > I was therefore wondering whether you also saw: > > > > if you no longer believe this is a bug please go ahead and > > > close it. > > Thanks in advance. I am still in development. -- ,''`/ : :' : Javier Serrano Polo `/ `'` javier@jasp/net `-Attachment: smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---