Bug#1083120: Viagee permanently disabled

Package: viagee Severity: grave Justification: renders package unusable thanks The Viagee package interfaces with the GMail API. Starting two years ago, access to that API required successfully completing a verification process. Recently, the Verified status has been revoked, and the author (me) d

Bug#1041447: comitup: fails to install, remove, distupgrade, and install again

On Tue, Jul 18, 2023 at 10:39 PM Andreas Beckmann wrote: > > Package: comitup > Version: 1.38-1.1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to install > (in 'bullseye'), remove (but not purge),

Bug#1037612: control

Control: tags -1 upstream Control: forwarded -1 https://github.com/cryfs/cryfs/issues/458

Bug#1019208: Fwd: ITP: viagee -- support for Gmail as the preferred email application in GNOME

Package: wnpp Severity: wishlist Owner: David Steele * Package name: viagee Version : 3.0-1 Upstream Author : David Steele * URL : https://github.com/davesteele/viagee/tree/debian * License : GPL Programming Lang: Python Description : support for Gmail

Bug#1014684: FTBFS with fmtlib 9.0.0

Control: forwarded -1 https://github.com/cryfs/cryfs/issues/432

Bug#1014684: FTBFS with fmtlib 9.0.0

Control: -1 forwarded https://github.com/cryfs/cryfs/issues/432 Thanks On Sun, Jul 10, 2022 at 5:33 AM Shengjing Zhu wrote: > I have uploaded fmtlib 9.0.0 to experimental. During rebuild the reverse > dependencies, your package FTBFS. >

Bug#1003496: Relinquish

Control: noowner -1 I no longer intend to package this software.

Bug#802260: gnome-gmail: Installation experience on KDE

Control: severity -1 wishlist thanks

Bug#976402: Proposed official virtual packages - todo and todo.txt

Update. No todo, and suggest the following for todo.txt text: command-line task management utility compatible with todo.txt CLI ( http://todotxt.org) On Tue, Dec 8, 2020 at 2:57 PM Dave Steele wrote: > Please update the Authoritative List of Virtual Package Names to > include &quo

Bug#976402: Bug#976902: topydo: provides /usr/bin/todo with incompatible interface compared to devtodo

I see two complaints about the "todo" virtual package: 1) it encompasses applications that may not have sufficiently identical interfaces, and/or 2) it uses Conflicts as a transition mechanism. Resolving (2) exceeds my threshold. I'll drop the todo package. That leaves todo.txt, implemented b

Bug#976402: Bug#976902: topydo: provides /usr/bin/todo with incompatible interface compared to devtodo

On Wed, Dec 9, 2020 at 12:40 PM Bill Allombert wrote: > On Wed, Dec 09, 2020 at 12:00:23PM -0500, Dave Steele wrote: > > /usr/bin/todo is not registered as an alternative by devtodo, > so you cannot register it as an alternative in another package. > The conflict between devtod

Bug#976402: Bug#976902: topydo: provides /usr/bin/todo with incompatible interface compared to devtodo

On Wed, Dec 9, 2020 at 3:54 AM Ansgar wrote: > Package: topydo > Version: 0.13-5 > Severity: serious > > Example use of `todo` from devtodo: > > +--- > | Add a task, like so: > | > | $ todo -a I should really update my homepage > | > | List all open tasks: > | > | $ todo > | > | Mark a task as co

Bug#976402: Proposed official virtual packages - todo and todo.txt

Please update the Authoritative List of Virtual Package Names to include "todo" and "todo.txt". Discussion of the change is documented in [#976402]. [#976402]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976402 Suggested content: # Miscellaneous virtualPackages: - name: todo descr

Bug#976111: topydo 0.13-3 upload seems to hang ci.debian.net workers while testing todo.txt-base

On Mon, Nov 30, 2020 at 2:51 PM Paul Gevers wrote: > > Happens. Glad you're able to point us at the problem so quickly. I have > blocklisted todo.txt-base already yesterday, so the infrastructure is > somewhat protected now. I'll lift the block once you close this bug. > > Could you lift the bloc

Bug#976072: Upcoming fix

Preparing to unpack topydo_0.13-5_all.deb ... Unpacking topydo (0.13-5) over (0.13-2) ... Setting up topydo (0.13-5) ... update-alternatives: using /usr/bin/topydo to provide /usr/bin/todo.txt (todo.txt) in auto mode update-alternatives: using /usr/bin/topydo to provide /usr/bin/todo (todo) in auto

Bug#532150: Bug#865792: reportbug: Allow an arbitrary MUA to be configured (patch)

On Mon, Jun 22, 2020 at 9:27 AM Paul Wise wrote: > > On Mon, 2020-06-22 at 12:31 +0200, Nis Martensen wrote: > > > The current MUA support in reportbug has two main limitations: > > Just importing the MUA handling from reportbug-ng would solve most of > these, including the gmail case. Preferably

Bug#954169: sirikali: Encrypted containers can not be opened

severity 954169 normal tags 954169 = moreinfo unreproducible thanks I cannot reproduce this either. I usually do not use gocryptfs, but installed it to test. I also do not use dash, but that is not likely to be the source of the problem.

Bug#954171: sirikali: Containers can not be created

severity 954171 normal tags 954171 = moreinfo unreproducible thanks I am unable to reproduce the described behavior.

Bug#935154: goopg depends on cruft package

You may want to file this upstream. https://github.com/LeoIannacone/goopg/issues On Tue, Aug 20, 2019 at 5:39 AM peter green wrote: > > Package: goopg > Version: 0.3.1-9 > Severity: serious > > goopg depends on the python-oauth2client binary package which is no longer > built by the python-oaut

Bug#865792:

> I like your patch, but it doesn't apply anymore (apologies it took so > long to review) - would you please re-base it against the current > master? thanks! My apologies as well. I missed this message. I've rebased the patch. I haven't looked closely at the code recently, but the merge was clean

Bug#929075: golang-github-jacobsa-crypto: Salsa CI failure

Package: golang-github-jacobsa-crypto Severity: minor thanks The golang-github-jacobsa-crypto package is currently failing the Salsa CI test [1]. This happens because uscan on Salsa is returning a different derived latest (git) version tag than the one on my build system [2]. This appears to be du

Bug#927985: gnome-gmail sometimes deletes message body

Package: gnome-gmail Severity: normal thanks There is a bug in gnome-gmail that causes message bodies to be absent when the capitalized "BODY" tag is used in the mailto query string. This has caused "Send Link" messages from browsers to have no links in the resulting messages.

Bug#916702: Merge request

Upstream upgrade available as a merge request. https://salsa.debian.org/debian/python-freezegun/merge_requests

Bug#918144: Goopg API Error

Package: goopg Severity: serious thanks Goopg Gmail API calls are failing, returning a 400 code. e.g, 2019-01-03 14:43:12,509:INFO:Gmail:getting message #msg-a:r-505788724173301 2019-01-03 14:43:12,587:ERROR:CommandHandler:https://www.googleapis.com/gmail/v1/users/me/messages/%23msg-a%3Ar-505

Bug#862876: Obsolete watch file for libcrypto++

On Tue, Jun 27, 2017 at 4:43 PM, László Böszörményi (GCS) wrote: > Hi David, > > On Thu, May 18, 2017 at 3:34 AM, David Steele wrote: >> This is a problem for me, because the cryfs package has less functionality >> when >> compiled against 5.6.4, relative to 5.6.3 or 5.6.5. > Can you give me s

Bug#840750: RFS: picocoin/0.1-2.gbp43047g

Sorry for the delay. Concerning your latest upload, 0.1-2+nmu1: - The yellow flags on the mentors page should be cleared - This is not an NMU (non-maintainer upload). Look at the help message associated with the lintian issue. - the home page and Vcs links are commented out in control

Bug#855889: gnome-gmail: /usr/bin/gnome-gmail uses any available python

On Wed, Feb 22, 2017 at 4:56 PM, Jan Schulz wrote: > Package: gnome-gmail > Version: 2.3.1-1 > Severity: normal > ... > > It would be nice if /usr/bin/gnome-gmail could use the full path of the system > python interpreter /usr/bin/python or as it simply does > `/usr/share/gnome-gmail/gnomegmail.py

Bug#843126: gpg2 bug encountered

The bug I encountered appears to be #46, which is still open: https://github.com/freight-team/freight/issues/46 -- "Le mieux est l'ennemi du bien" - Voltaire

Bug#850100: Authentication broken when using Mozilla

Package: gnome-gmail Version: 2.3-3 Severity: important The browser 'new window' behavior is broken for Mozilla (Firefox/Iceweasel). This has the effect of breaking the authentication process when that browser is the default http application, rendering the package unusable.

Bug#847476: Go language build dependency

Package: golang-github-hanwen-go-fuse-dev Version: 0.0~git20150627.0.324ea17-1 Replacing the golang-go build dependency with golang-any would improve cross-architecture support, by allowing the use of gccgo on architectures that do not support the native toolchain. In particular, this affects the

Bug#847368: Watch file version handling

Source: golang-github-jacobsa-crypto Version: 0.0~git2016.0.293ce0c-1-2 Severity: normal thanks Note to self, for the next source release: 1) The repacked source tar version should include 'dfsg' see https://wiki.debian.org/BenFinney/software/repack This will involved watch options: dve

Bug#843886: goopg: fails to sign and send email

On Fri, Nov 11, 2016 at 3:04 AM, Arturo Borrero Gonzalez wrote: > 2016-11-10 14:05:58,766:DEBUG:gnupg:gpg: gpg-agent is not available in > this session This is the problem. The agent is installed as a dependency, but not sufficiently configured, See the README for guidance. https://github.com/Le

Bug#843886: goopg: fails to sign and send email

On Thu, Nov 10, 2016 at 8:15 AM, Arturo Borrero Gonzalez wrote: > ... > > Then, in Gmail, if I create a new email a push 'Sign and Send', a yellow > message box appears in the gmail window with: > > Your message was not sent. Please retry. > > Any hint? > Can you verify that /etc/opt/chrome/nati

Bug#799227: Block 799227 by 800163

block 799227 by 800163 thanks -- "Le mieux est l'ennemi du bien" - Voltaire

Bug#805926: GNOME GMail broken on Jessie

On Tue, Nov 24, 2015 at 9:25 PM, Dave Steele wrote: > See 806176 > Removal request at 814860 and 806176. -- "Le mieux est l'ennemi du bien" - Voltaire

Bug#814860: RM: gnome-gmail/stable -- ROM; Broken package

On Tue, Feb 16, 2016 at 12:39 AM, Adam D. Barratt wrote: > Removals from {,old*}stable are handled by the Release Team; > reassigning. The Developer Reference section 5.9.2 and reportbug should be updated to reflect that. -- "Le mieux est l'ennemi du bien" - Voltaire

Bug#814860: RM: gnome-gmail/stable -- ROM; Broken package

On Tue, Feb 16, 2016 at 12:39 AM, Adam D. Barratt wrote: > > On Mon, 2016-02-15 at 21:21 -0500, David Steele wrote: >> >> The [gnome-gmail] package has been broken for some time, due to the >> deprecation of it's old authentication mechanism ([#805926]). The proposed >> patch fixing the package ha

Bug#806176: jessie-pu: package gnome-gmail/1.8.3-1

On Fri, Jan 1, 2016 at 11:10 PM, Dave Steele wrote: > On Fri, Jan 1, 2016 at 12:28 PM, Julien Cristau wrote: >> >> On Tue, Nov 24, 2015 at 20:52:56 -0500, Dave Steele wrote: >> >> >> > A diff of the changes is a bit problematic. An interactive compare

Bug#806176: jessie-pu: package gnome-gmail/1.8.3-1

On Fri, Jan 1, 2016 at 12:28 PM, Julien Cristau wrote: > On Tue, Nov 24, 2015 at 20:52:56 -0500, Dave Steele wrote: > > > > A diff of the changes is a bit problematic. An interactive compare is > > available at > > > > > https://github.com/davesteele/gnome-gm

Bug#800163: jessie-pu: package cloudprint/0.11-5

Control: tag -1 -moreinfo On Fri, Jan 1, 2016 at 12:04 PM, Julien Cristau wrote: > > Control: tag -1 moreinfo > > > So I have a few questions: > - what's the point of the new cps-auth script? It was added to provide a UI for authentication in the systemd environment. I kept it here to provide

Bug#806176: jessie-pu: package gnome-gmail/1.8.3-1

On Sun, Nov 29, 2015, 4:23 PM Adam D. Barratt wrote: > On Tue, 2015-11-24 at 20:52 -0500, Dave Steele wrote: > > Per 805926, gnome-gmail is broken on Jessie due to a lack of support > > for OAuth2, and a reliance on GNOME 2 for configuration data. I went > > through the e

Bug#805926: GNOME GMail broken on Jessie

See 806176

Bug#806176: jessie-pu: package gnome-gmail/1.8.3-1

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu thanks Per 805926, gnome-gmail is broken on Jessie due to a lack of support for OAuth2, and a reliance on GNOME 2 for configuration data. I went through the exercise of crafting a m

Bug#805926: GNOME GMail broken on Jessie

Package: gnome-gmail Version: 1.8.3-1 Severity: grave The gnome-gmail package is broken in Jessie for a couple of reasons.First, IMAP authentication, which used for file attachments, now requires OAuth2 authentication. OAuth2 support was first added in 1.9-1. Second, access to configuration setti

Bug#800163: jessie-pu: package cloudprint/0.11-5

Control: tags -1 - moreinfo On Mon, Sep 28, 2015 at 10:03 PM, David Steele wrote: > > Updated debdiff attached (deleted file detail again removed): > > Changes > > - Version fixed > - systemd implementation reverted to init script > - fixed self reference in cps-auth(1) > - use {Python:D

Bug#802260: gnome-gmail: Installation experience on KDE

On Tue, Oct 20, 2015 at 2:49 PM, Mario Blättermann wrote: > Hi Dave, > > 2015-10-20 15:24 GMT+02:00 Dave Steele : >> >> >> GNOME Gmail was developed for GNOME. It's behavior with KDE is >> currently undefined. Getting it to work with KDE is 'wishlis

Bug#802260: gnome-gmail: Some dependencies missing

Control: -1 severity normal Control: -1 retitle Installation experience on KDE On Sun, Oct 18, 2015 at 4:10 PM, Mario Blättermann wrote: > Package: gnome-gmail > Version: 1.9.3-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > after installing gnome-gmail in

Bug#799227: cloudprint: Uses obsolete "ClientLogin" protocol

See #800163 for the Jessie update submission.

Bug#800163: jessie-pu: package cloudprint/0.11-5

On Tue, Sep 29, 2015 at 12:45 AM, Adam D. Barratt wrote: > On Mon, 2015-09-28 at 22:03 -0400, David Steele wrote: >> Updated debdiff attached (deleted file detail again removed): > > someone's uploaded a version to stable that looks like it was > intended for unstable: ... > I'm going to mark that

Bug#800163: jessie-pu: package cloudprint/0.11-5

On Sun, Sep 27, 2015 at 2:42 PM, Adam D. Barratt wrote: > > On Sun, 2015-09-27 at 14:21 -0400, Dave Steele wrote: > > On Sun, Sep 27, 2015 at 12:24 PM, Adam D. Barratt > > I don't have a strong reason for making the systemd change. I can > > revert it, if it is

Bug#800163: jessie-pu: package cloudprint/0.11-5

On Sun, Sep 27, 2015 at 12:24 PM, Adam D. Barratt wrote: > > +cloudprint (0.13-1+deb8u3) UNRELEASED; urgency=medium > > Where did you get that version number from? (specifically the "u3" bit.) >From my attempt to understand updates versioning. It is a Jessie updates candidate, which is modified

Bug#800082: cloudprint-service: Why was the init script removed?

On Sun, Sep 27, 2015 at 11:34 AM, Graham Knap wrote: > Why was the init script removed? > Was it broken and no longer feasible to maintain? > It broke for me, and was getting in the way of OAuth2 work. > As for my second question, you seem to have implied that the answer is > "You can't". Plea

Bug#800163: jessie-pu: package cloudprint/0.11-5

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Google has removed support for SASL authentication for Cloud Print services, and is now requiring OAuth2 authentication. This breaks the version of cloudprint which is in Jessie, ma

Bug#800082: cloudprint-service: Why was the init script removed?

> > Why was the init script removed? How can I use this package with sysvinit? > > Debian stable/jessie supports systemd. Command to interact are e.g. 'systemctl {start|stop|status} cloudprintd'. There is problem with running the latest versions of cloudprint on Jessie, which is unrelated to OAuth

Bug#799227: cloudprint: Uses obsolete "ClientLogin" protocol

WIP at https://github.com/davesteele/cloudprint-service/tree/updates-jessie On Wed, Sep 16, 2015 at 9:44 PM, Vagrant Cascadian wrote: > Package: cloudprint > Version: 0.11-5 > Severity: grave > Control: fixed -1 0.13-1 > > $ cloudprint > Google username: ghkjadhsg > Password: > Traceback (most r

Bug#797505: cloudprint: Should not ship .pyc files

Nevermind. I see what's going on in your logs. The spelling thing is still valid, though :-) On Mon, Aug 31, 2015 at 10:23 AM, Dave Steele wrote: > Hi Chris, > > On Mon, Aug 31, 2015 at 3:58 AM, Chris Lamb wrote: > >> >> While working on the "reproducible b

Bug#792055: Cloudprint crashes after an hour of idle time

Package: cloudprint Version: 0.12-3 Severity: important thanks The service crashes after an hour of idle processing, with the queue check. Service is crashing after an hour. Jul 9 22:42:49 debian-testing cloudprintd[8392]: Updated Printer MFCJ5910DW Jul 9 22:42:50 debian-testing cloudp

Bug#787102: Cloudprint authentication stopped working

Package: cloudprint Version: 0.11-6 Severity: Serious The authentication mechanism used by cloudprint is no longer supported by Google. It will need to be upgraded to OAuth2 before the service is again functional. This upgrade is in process. -- "Le mieux est l'ennemi du bien" - Voltaire --

Bug#637871: This bug can be closed since it's no longer valid.

Agreed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#786371: Traceback if no access token found

Package: gnome-gmail Severity: serious Version:1.9-2 On the first run of gnome-gmail, the software will fail because no oauth token is found in the keyring. Once the first authentication is established, no further problems will be found - a Catch 22. -- "Le mieux est l'ennemi du bien" - Voltaire

Bug#785767: gnome-gmail rampant OAuth2 failures

Package: gnome-gmail Version: 1.9-2 Severity: serious Upon further testing, OAuth2 started throwing off many errors, making the package unusable. This bug is being entered to stop the migration of the current version to testing. -- "Le mieux est l'ennemi du bien" - Voltaire -- To UNSUBSCRIBE

Bug#695188: Multiple "Bug#" references in subject

Control: tag -1 newcomer thanks The git source code repository is referenced from the wiki page [1]. The problem appears to be in the Perl 'process' script. There are a number of places where the bug number and $newsubject are concatenated to make a new subject, without checking to see if the bug

Bug#715083: Broken library symlink detected in libgrok-dev

On Mon, Feb 23, 2015 at 8:54 AM, Vincent Bernat wrote: > ❦ 6 juillet 2013 05:01 GMT, David Steele : > > > This is being filed as Serious because it represents a violation > > of Policy > > Why was the severity downgraded then? > https://lists.debian.org/debian-devel/2013/07/threads.html#0

Bug#764974: [Piuparts-devel] Bug#764974: ejabberd fails testing at install time

> On Donnerstag, 2. Oktober 2014, Philipp Huebner wrote: > > I noticed that ejabberd fails piuparts testing because it can't be > > installed. The relevant line from the log is: > > > > sed: can't read /usr/share/doc/ejabberd/examples/ejabberd.yml.example: > > No such file or directory > > You did

Bug#706190: Rework packaging to remove deprecated python-support

>From Ben Finney > Can you give more information on what exactly is happening and why > this bug is “important” severity? It appeared as a broken package (method not found), but was caused by a module name collision. I renamed and re-prioritized in April 2013. Now it just contains a patch to upg

Bug#756845: [DRE-maint] Bug#756845: Independent verification of jekyll failure

That works. I'm able to create a blog site now. Thanks. On Wed, Aug 27, 2014 at 10:22 PM, Cédric Boutillier wrote: > Hi Dave, > > On Mon, Aug 25, 2014 at 01:06:58PM -0700, Dave Steele wrote: >> I am also see this, with a fresh install on jessie. > >> $ jeky

Bug#756845: More information on Jekyll startup bug

tags 756845 -moreinfo thanks Here's moreinfo. caveat - I don't know Ruby or Jekyll. Running on up-to-date Jessie. The error appears to be a subclass request, in jekyll/converters/sass.rb, of Scss, which isn't defined. The Scss class is defined in sass.rb, in the same directory. BTW, Ruby doesn'

Bug#756845: Independent verification of jekyll failure

I am also see this, with a fresh install on jessie. $ jekyll --version /usr/lib/ruby/vendor_ruby/jekyll/converters/sass.rb:6:in `': uninitialized constant Jekyll::Converters::Scss (NameError) from /usr/lib/ruby/vendor_ruby/jekyll/converters/sass.rb:5:in `' from /usr/lib/ruby/vendor_ruby/jekyll/con

Bug#746621: DDPO: Integrate Piuparts (w/ patches)

On Thu, May 1, 2014 at 10:04 PM, David Steele wrote: > Package: qa.debian.org ... > Piuparts has a new summary file format, visible at > https://piuparts.debian.org/summary.json. > > The attached patches use that data to integrate piuparts into the DDPO > report, to the right of the lintian result

Bug#746724: p.d.o spelling errors

On Fri, May 2, 2014 at 5:24 PM, Cyril Brulebois wrote: > Both licensed and licenced are correct. 'licenced' is unambiguously wrong in American English. Google.co.uk top links state it is incorrect for the Queen's English as well: http://www.grammar-monster.com/easily_confused/licence_license.htm

Bug#746722: [Piuparts-devel] Bug#746722: Bug#746722: Spurious log directory creation in piuparts-report

On Fri, May 2, 2014 at 5:21 PM, Holger Levsen wrote: > do you still propose this patch or something else? I would propose the patch, and eventual rework of packagesdb. -- "Le mieux est l'ennemi du bien" - Voltaire -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#746724: p.d.o spelling errors

Package: piuparts-master Severity: minor thanks The words "licensed" and "ditto" are spelled incorrectly in the footer of all of the web pages created by piuparts-report. -- "Le mieux est l'ennemi du bien" - Voltaire -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#746722: Spurious log directory creation in piuparts-report

-01 16:44, Dave Steele wrote: >> On Sat, Mar 1, 2014 at 1:52 AM, Andreas Beckmann wrote: >>> On 2014-02-28 22:57, Dave Steele wrote: >>>> 3057fb6 piuparts-report.py: Establish PackagesDB prefix >>> >>> NACK. Or why is this needed for sources_db? Thi

Bug#746723: Support 'file://' access for piuparts-master report output

Package: piuparts-master Severity: wishlist thanks It would be nice to be able to review the HTML output of piuparts-report without having to install and configure a web server. Access via file:/// URLs would be viable if the reports were reworked to use relative links throughout. This would also

Bug#746721: piuparts-master/slave cron file syntax wrong

Package: piuparts-master Severity: serious thanks Cron files, installed in /etc/cron.d, are not in the right format. The required 'user' field is omitted. Because of this issue, slaves are not started at boot, and no normal recovery or retest actions are taken. Reports are not automatically gener

Bug#746718: piuparts_slave_* scripts not on PATH (1)

Package: piuparts-slave thanks I'm going to take an opportunity here to log a number of annoyances that I ran into with my recent re-introduction to the packaged version of the piuparts service. It's been long enough for me that this amounts to a set of somewhat fresh eyes on the subject. Logged a

Bug#746711: [Piuparts-devel] Bug#746711: piupartslib choking on arch Depends

Control: retitle -1 dependencyparser should not crash on questionable Depends Control: severity -1 normal On Fri, May 2, 2014 at 3:17 PM, Jakub Wilk wrote: > The package in question (google-mock) doesn't use ${python:Depends}. It has > "python:all" hardcoded in debian/control. > > The ":all" qual

Bug#746711: piupartslib choking on arch Depends

Package: piuparts-common Severity: important thanks I was checking to see if there was a problem with 'https' in summary.json, and ran into this. It's coughing on the syntax of an architecture-specific dependency. That's odd, since ${python:Depends} has resolved to an arch-specific reference in

Bug#740386: [Piuparts-devel] Bug#740386: Bug#740386: Summary.json web-host

On Wed, Apr 30, 2014 at 5:29 PM, Holger Levsen wrote: > On Mittwoch, 30. April 2014, Dave Steele wrote: >> 974d80b piuparts-report.py: De-indent global summary func > > unneeded (and/or rather unwanted atm...) No functional changes, so OK. >> 4e75ffb piuparts-report.py: Re

Bug#740386: [Piuparts-devel] Summary.json web-host

On Wed, Apr 30, 2014 at 11:19 AM, Holger Levsen wrote: > On Mittwoch, 30. April 2014, Dave Steele wrote: >> I'll submit a fix tonight, to define and use a web-host. > > cool. Please hurry up, else it might not be included in 0.58! Not that it > matters much, but anyway

Bug#740386: [Piuparts-commits] [piuparts] 06/06: piuparts-report.py: Default summary dist support

On Wed, Apr 30, 2014 at 6:24 AM, Holger Levsen wrote: > holger pushed a commit to branch develop > in repository piuparts. > > commit b8096c51c66e7c97bf5aaed8014684522ffc8239 > Author: David Steele > Date: Sun Mar 9 21:34:13 2014 -0400 > diff --git a/piuparts-report.py b/piuparts-report.py >

Bug#745392: gnome-tweak-tool: enabling 'Icons on Desktop' greys out the background

>From Andreas Glaeser >I wondered for some time, why the desktop-background is grey with my >user-profile and the >normally set background is shown with a new user-profile. Now I found that >this is because >of the option 'Icons on Desktop' in the tweak-tool under 'Desktop'. I'd love to hear a

Bug#740386: [Piuparts-devel] Five-holger - Support automated summary.json reporting-section definitions

On Wed, Mar 19, 2014 at 6:36 AM, Holger Levsen wrote: > > 9a92575 test_pkgsummary.py: Initial pkgsummary tests > > includes a typo: ittp instead of http Not a typo. That's an argument validation test. > please dont disable that/those time sensitive test/s. > > good thing not to create a summary

Bug#740386: Five-holger - Support automated summary.json reporting-section definitions

On Mon, Mar 10, 2014 at 12:27 AM, Dave Steele wrote: > On Sun, Mar 2, 2014 at 9:57 PM, Holger Levsen wrote: >> >> I don't like this patch as it hardcodes info which is also in the distro-info >> packages. Plus: why is it untested? >> > >> On Sonntag, 2.

Bug#695188: Multiple "Bug#" references in subject

I'd like to second the notion that this is a real bug, and that it should be addressed - e.g. http://lists.alioth.debian.org/pipermail/piuparts-devel/2014-March/thread.html#5197 I agree with #27 that the solution could be to check for the presence of a "Bug#" in the subject before adding one. I

Bug#740386: Five-holger - Support automated summary.json reporting-section definitions

On Sun, Mar 2, 2014 at 9:57 PM, Holger Levsen wrote: > > On Sonntag, 2. März 2014, Dave Steele wrote: >> 5892fca piuparts.conf.pejacevic: Add reporting-sections > > I don't like this patch as it hardcodes info which is also in the distro-info > packages. Plus: why is

Bug#740386: [Piuparts-devel] Bug#740386: Bug#740386: Bug#740386: More robust piuparts results reporting format

On Sun, Mar 2, 2014 at 9:57 PM, Holger Levsen wrote: > control: tags -1 + pending > > + ...The names > + "unstable", "testing", "stable", "oldstable", and "experimental" > + have special meaning. > > yet this text lacks an explaination what the special meaning is. can you > explain and add that pl

Bug#740386: [Piuparts-devel] Bug#740386: More robust piuparts results reporting format

Another tack. I've removed the PackagesDB prefix commit. There is no linkage between the logdir traceback issue and summary-json. summary-json (11) 247ac53 piuparts-report: Minor rework of main loop 54d116c README_server.txt: Add reporting-section 94e8539 pkgsummary.py: Initial checkin for pkg su

Bug#740386: [Piuparts-devel] Bug#740386: More robust piuparts results reporting format

On Sat, Mar 1, 2014 at 4:16 PM, Andreas Beckmann wrote: > On 2014-03-01 16:44, Dave Steele wrote: >> On Sat, Mar 1, 2014 at 1:52 AM, Andreas Beckmann wrote: >>> On 2014-02-28 22:57, Dave Steele wrote: >>>> 3057fb6 piuparts-report.py: Establish PackagesDB prefi

Bug#740386: More robust piuparts results reporting format

On Sat, Mar 1, 2014 at 1:52 AM, Andreas Beckmann wrote: > On 2014-02-28 22:57, Dave Steele wrote: >> 3057fb6 piuparts-report.py: Establish PackagesDB prefix > > NACK. Or why is this needed for sources_db? This doesn't have logfiles. > Because PackagesDB always cares about

Bug#740386: More robust piuparts results reporting format

Package: piuparts-master Version: 0.57 Severity: wishlist Tags: patch User: debian...@lists.debian.org thanks Create a new JSON summary on the piuparts-master web site for exporting richer information about piuparts test results. The content is targeted for piuparts integration into DDPO. summary

Bug#625278: Prioritization of broken symlink issues

On Fri, Feb 21, 2014 at 12:34 PM, Agustin Martin wrote: > On Mon, Feb 17, 2014 at 12:29:49PM -0500, Dave Steele wrote: > > 1) How does lintian know to issue this warning? Does it download > > piuparts results? > > I am afraid that by manual interaction. Both work differently,

Bug#625278: Prioritization of broken symlink issues

On Mon, Feb 17, 2014 at 7:14 AM, Agustin Martin wrote: > Anyway, I think this will be fixed before we reach that point. But something > like > > stage a) lintian warning + piuparts warning > stage b) lintian error + piuparts error > > would have IMHO be a better approach, even if the time betwee

Bug#625278: Prioritization of broken symlink issues

On Sun, Feb 16, 2014 at 11:14 AM, Agustin Martin wrote: > 2014-02-15 5:47 GMT+01:00 Dave Steele : >> Hi Agustin, >> >> On the subject of TODO list priorities, note that the Piupart broken symlink >> test is likely to be elevated soon, returning an error result rathe

Bug#625278: Prioritization of broken symlink issues

On Tue, 3 May 2011, Agustin Martin wrote: >On Tue, May 03, 2011 at 05:05:09AM +0200, J G Miller wrote: >> Package: dictionaries-common >> Version: 1.10.6 >> Severity: normal >> >> The dictionaries-common package contains two dangling symbolic links >> in /usr/lib/ispell >> >> 0 lrwxrwxrwx 1 root ro

Bug#715098: Broken library symlink detected in libostyle-dev

On Mon, Oct 7, 2013 at 7:46 PM, Neil Roeth wrote: > On 07/06/2013 01:01 AM, David Steele wrote: > >> >> ... >> The log contains the following broken symlinks: >> >>/usr/lib/libostyle.so >> -> libostyle.so.1.0.0 >>/usr/lib/libospgrove.so >> -> libospgrove.so.1.0.0 >>/usr/lib/

Bug#712440: Missing recently archived bugs

On Sun, Sep 29, 2013 at 1:01 AM, Don Armstrong wrote: > On Sat, 28 Sep 2013, Dave Steele wrote: >> Should I expect to be able to use BTS to get a complete history of >> bugs for a project? > > Yes, all of them should be returned. I'm not sure why 717780 isn't bein

Bug#706904: Chinese Checkers RFS review

On Fri, Sep 20, 2013 at 1:16 PM, Michael Shuler wrote: > On 09/20/2013 10:06 AM, Dave Steele wrote: >> In any case, it sounds like the guidance on this ticket is that either >> solution is fineish. > > Not to my knowledge. A native package should only be one that is solely

Bug#706904: Chinese Checkers RFS review

On Fri, Sep 20, 2013 at 10:19 AM, Paul Tagliamonte wrote: > On Fri, Sep 20, 2013 at 10:18:18AM -0400, Dave Steele wrote: >> I'm not sure we are clear with terms here. The newbie is the upstream, >> and he has chosen to include the debian directory in his main >> repos

Bug#706904: Chinese Checkers RFS review

On Fri, Sep 20, 2013 at 9:08 AM, Paul Tagliamonte wrote: > On Fri, Sep 20, 2013 at 08:00:23AM -0400, Dave Steele wrote: >> Do you have a source for that? I was told otherwise before. > > This is what defines a Debian native package. > > Here's why it's

  1   2   3   >