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#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

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

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

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

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

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 <dste...@gmail.com> wrote: > See 806176 > Removal request at 814860 and 806176. -- "Le mieux est l'ennemi du bien" - Voltaire

Bug#805926: GNOME GMail broken on Jessie

See 806176

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

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, > >

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

See #800163 for the Jessie update submission.

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 >

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#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#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

Bug#715112: Broken library symlink detected in libsamba-util-dev

On Sat, Jul 6, 2013 at 2:03 AM, Steve Langasek vor...@debian.org wrote: Control: severity 715110 normal Control: severity 715122 normal On Sat, Jul 06, 2013 at 05:01:15AM +, David Steele wrote: Package: libsamba-util-dev Version: 4.0.0~beta2+dfsg1-3.2 Severity: serious User:

Bug#715104: Re: [pcp] Bug#715104: Broken library symlink detected in libpcp-trace2-dev

On Sat, Jul 6, 2013 at 2:22 AM, Ken McDonell k...@internode.on.net wrote: Apologies David, thunderbird decided that a reply to list should not include you ... but this was principally for you. I'm replying to the bug. Original Message Subject: Re: [pcp] Bug#715104: Broken

Bug#715112: Broken library symlink detected in libsamba-util-dev

On Sat, Jul 6, 2013 at 5:48 AM, Julien Cristau jcris...@debian.org wrote: On Sat, Jul 6, 2013 at 04:10:16 -0400, Dave Steele wrote: I guess the next step is a clearer statement of consensus on what to do next. My position - I believe that the bug submittal, and the current severity

Bug#712384: Apache configuration broken in sid

Package: piuparts-master Version: 0.53 Severity: grave thanks Recent versions of apache2 break the piuparts-master web configuration. It looks like this is caused by all 2.44 versions of apache2. See the link below for instruction. I also had to add a Require line. It appears that a .conf

Bug#712384: Feedback

Lintian feedback W: piuparts-master: apache2-reverse-dependency-uses-obsolete-directory etc/apache2/conf.d/piuparts.apache W: piuparts-master: non-standard-apache2-configuration-name piuparts.apache != piuparts-master.conf W: piuparts-master: