kio-gdrive_20.12.2-1_source.changes ACCEPTED into unstable

2021-02-11 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 Feb 2021 16:52:41 -0500 Source: kio-gdrive Architecture: source Version: 20.12.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Nicholas D Steeves Changes:

Processing of kio-gdrive_20.12.2-1_source.changes

2021-02-11 Thread Debian FTP Masters
kio-gdrive_20.12.2-1_source.changes uploaded successfully to localhost along with the files: kio-gdrive_20.12.2-1.dsc kio-gdrive_20.12.2.orig.tar.xz kio-gdrive_20.12.2-1.debian.tar.xz kio-gdrive_20.12.2-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host

Bug#910347: Not reproducible for me

2021-02-11 Thread Aurélien COUDERC
Hi ghost, I used to have similar issues but I don’t remember seeing it recently so it may well be resolved. I’m using scaling 1,25 so not exactly the same as you but I did experience the issue and it did disappear for me on bullseye. Did you try running bullseye by any chance ? I’ll monitor

[bts-link] source package konsole

2021-02-11 Thread debian-bts-link
# # bts-link upstream status pull for source package konsole # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #910347 (http://bugs.debian.org/910347)

qconf_2.5-1~bpo10+1_amd64.changes ACCEPTED into buster-backports, buster-backports

2021-02-11 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Feb 2021 00:46:18 +0300 Source: qconf Binary: qconf Architecture: source amd64 Version: 2.5-1~bpo10+1 Distribution: buster-backports Urgency: medium Maintainer: Debian Qt extras Maintainers Changed-By: Boris

Processed: Re: Closing as per reporter request

2021-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 981679 Bug #981679 {Done: Aurélien COUDERC } [kdevelop] kdevelop: Clang plugin breaks when clang package bumps version Bug reopened Ignoring request to alter fixed versions of bug #981679 to the same values previously set > thanks

Bug#981679: Closing as per reporter request

2021-02-11 Thread Pino Toscano
reopen 981679 thanks Hi, In data giovedì 11 febbraio 2021 10:18:14 CET, Aurélien COUDERC ha scritto: > control: fixed -1 4:5.6.2-4 > > Thanks for the follow up. > Closing as per your request. > > What I read from upstream git log is that the commit you mention is on master > and the fix was

Bug#981679: marked as done (kdevelop: Clang plugin breaks when clang package bumps version)

2021-02-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Feb 2021 10:18:14 +0100 with message-id <5291564.lL144ORZWD@grummly> and subject line Closing as per reporter request has caused the Debian Bug report #981679, regarding kdevelop: Clang plugin breaks when clang package bumps version to be marked as done. This means that

Bug#982221: k3b: please stop using cdrkit

2021-02-11 Thread Thomas Schmitt
Hi, i am the developer of libburnia, including cdrskin and xorriso. Feel free to ask for advise about how to use their features to achieve what K3B needs. I have to warn, though, that UDF is not supported by libisofs. Besides the fact that some smaller operating systems cannot deal with files of

Bug#981679: Close Bug: KDevelop 5.6.2 now recognizes Debian specific clang --version output

2021-02-11 Thread Justin
This bug can be closed. No longer an issue with KDevelop 5.6.2. Fixed in KDevelop git commit fa83c76b133a52c8ce0e7af0aa8c060fadaa8536 Background: Debian and Ubuntu (and others?) have unique clang --version output. KDevelop tries a few different ways to determine the clang include directory.