kamoso 18.04.0-3 is marked for autoremoval from testing on 2018-12-22
It is affected by these RC bugs:
914441: kamoso: no user interface is shown: qrc:/qml/Main.qml:7 module
"org.kde.kirigami" is not installed
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 20 Dec 2018 22:40:02 +0100
Source: kdevelop-python
Binary: kdevelop-python kdevelop-python-data kdevelop-python-l10n
Architecture: source
Version: 5.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 20 Dec 2018 22:26:44 +0100
Source: okteta
Binary: libkasten3controllers3 libkasten3core3 libkasten3gui3
libkasten3okteta1controllers1abi1 libkasten3okteta1core1 libkasten3okteta1gui1
libokteta2core2 libokteta2gu
kdevelop-python_5.3.1-2_source.changes uploaded successfully to localhost
along with the files:
kdevelop-python_5.3.1-2.dsc
kdevelop-python_5.3.1-2.debian.tar.xz
kdevelop-python_5.3.1-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 20 Dec 2018 22:35:37 +0100
Source: kdevelop-php
Binary: kdevelop-php kdevelop-php-l10n
Architecture: source
Version: 5.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 20 Dec 2018 22:31:54 +0100
Source: kdevelop
Binary: kdevelop53-libs kdevelop kdevelop-data kdevelop-dev kdevelop-l10n
plasma-kdevelop kdevplatform-dev kdevplatform-l10n
Architecture: source
Version: 4:5.3.1-2
Dis
kdevelop-php_5.3.1-2_source.changes uploaded successfully to localhost
along with the files:
kdevelop-php_5.3.1-2.dsc
kdevelop-php_5.3.1-2.debian.tar.xz
kdevelop-php_5.3.1-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
On Thu, Dec 20, 2018 at 10:11:59PM +0100, Pino Toscano wrote:
> > I wonder why you can't just use the default python3 version instead of
> > doing these changes.
>
> Because it uses the Python library, and it needs to be adjusted to each
> version of it (since the internal parts of the API change)
> Since you seem to care about this, what about instead direct your
> efforts towards a successful migration of src:llvm-defaults (that
> switches the default from LLVM 6 to 7) to testing, since it is stuck
> in unstable for more than a month?
How can I do it? I am not a Debian maintainer, just an
kdevelop_5.3.1-2_source.changes uploaded successfully to localhost
along with the files:
kdevelop_5.3.1-2.dsc
kdevelop_5.3.1-2.debian.tar.xz
kdevelop_5.3.1-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
okteta_0.25.4-2_source.changes uploaded successfully to localhost
along with the files:
okteta_0.25.4-2.dsc
okteta_0.25.4-2.debian.tar.xz
okteta_0.25.4-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
In data giovedì 20 dicembre 2018 19:04:33 CET, Alexander Kernozhitsky ha
scritto:
> According to #916837, llvm-defaults-6.0 will be removed soon. But kdevelop
> still depends on one of the packages from this source. This package is
>
> libclang1-6.0
>
> It wasn't noticed by transition tracker c
Your message dated Thu, 20 Dec 2018 22:11:59 +0100
with message-id <1821624.0Fsbc4Q2io@pendragon>
and subject line Re: Bug#916819: stop using python 3.6
has caused the Debian Bug report #916819,
regarding stop using python 3.6
to be marked as done.
This means that you claim that the problem has be
Package: kdevelop
Version: 4:5.2.4-1
Severity: normal
--- Please enter the report below this line. ---
According to #916837, llvm-defaults-6.0 will be removed soon. But kdevelop
still depends on one of the packages from this source. This package is
libclang1-6.0
It wasn't noticed by transition
14 matches
Mail list logo
