Re: Upgrade Notifications for Kubuntu and Ubuntu Studio

[Harald Sitter]

https://invent.kde.org/system/distro-release-notifier may help

On Thu, Sep 8, 2022 at 3:09 AM Erich Eickmeyer  wrote:
>
> Hi all,
>
>
> In Kubuntu and Ubuntu Studio, we rely on Discover and the Discover Notifier 
> to run our GUI-based package updates. I don't care if you personally use apt 
> periodically from the terminal, a case can be made that we expect our users 
> to use Discover to do their updates.
>
>
> Unfortunately, Discover is very, very flawed. It uses packagekit as its 
> backend and its upgrader is designed to do one thing: upgrade packages. By 
> comparison, the Ubuntu Update Manager will give the user the option to remove 
> unused packages, unused kernels. and even notify of new Ubuntu releases, 
> which is something that Discover cannot do since it's built to be as 
> distribution-agnostic as possible.
>
>
> The lack of notification of new releases means when Release Upgrades are 
> enabled, Kubuntu and Ubuntu Studio users are not notified whether their 
> systems are set to upgrade to regular releases or LTS releases. This is 
> especially problematic for users that simply don't know any better. We simply 
> take for granted that we upgrade our systems, but new users don't necessarily 
> know that they have to do that, and they don't necessarily pay attention to 
> release announcements. We can't take that for granted that they automatically 
> know that or are paying attention; it's not basic knowledge.
>
>
> I have been seeing, with high levels of frequency, users showing-up in the 
> #kubuntu chat with EOL systems, and users showing up running 20.04 not 
> understanding why they aren't getting a notification to upgrade to 22.04. We 
> need to do better from a development standpoint and not let this happen. 
> Users need to be notified from their systems, not externally.
>
>
> Years ago, update-manager-qt was a thing, and I'm sure update-notifier-qt was 
> as well. I decided to experiment with both. Unfortunately, I ran into a few 
> issues, namely that neither exists anymore. Beyond that, using the GTK 
> equivalents, I ran into a couple of other issues:
>
>
> update-notifier doesn't even show in the system tray when there are updates 
> on my system, even after a reboot or a relog. Only if I force it by executing 
> it does it show, but it doesn't go away after running update-manager.
> update-manager runs well, but it pops-up a kdialog while running (see 
> attached screenshot). Perhaps a bug/relic from old days, but definitely 
> something that needs to be resolved.
>
>
> Honestly, if these things can be resolved and the Qt equivalents can be 
> resurrected, then it would be a huge boon to the users. Not only would they 
> have a more robust upgrade management system, but they would also have the 
> benefit of a Release Upgrade notifier when those times come.
>
>
> Of course, if someone has a better solution and would rather re-invent the 
> wheel, then sure, but I don't think re-inventing the wheel is ever a good 
> solution and would rather see collaboration and cooperation first, as is the 
> Ubuntu spirit.
>
>
> I added ubuntu-devel@ to this discussion since the packages in question are 
> in "main" and would require the help of some core devs to get some work done.
>
>
> Thanks for hearing me out,
>
> Erich
>
>
> --
>
> Erich Eickmeyer
>
> Project Leader - Ubuntu Studio
>
> Member - Ubuntu Community Council
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kubuntu-driver-manager maintainership

[Harald Sitter]

Hola

anyone want to maintain the driver manager kcm? I don't really have
time, so if nobody steps up I'd move it to unmaintained upstream.

https://invent.kde.org/system/kubuntu-driver-kcm

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

muon maintenance

[Harald Sitter]

It's me again

https://invent.kde.org/system/muon/-/merge_requests/2

:((

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

muon again

[Harald Sitter]

Yo

A while ago I've asked what to do with muon bugs and people said they'd
want to do some bug triage but it's been like 3 months since my original
mail and I've checked - nobody has done any triage.

So once again I'm here lamenting. Either we find someone who has time to
do active maintenance of muon and qapt or we should mark them as
unmaintained. Letting it rot away is neither fair to the users nor the
KDE community.

Anyone going to take this up?

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: muon bug reports

[Harald Sitter]

On 30.09.20 19:52, Mitch Golden wrote:
> Who would be the one to create it? I gather that muon will not be killed
> at the moment, but I'd like to know if anything is happening.

Anyone can! For example *you* can ;)

The obvious options are

- a list on launchpad: which I believe simply needs a group created and
a list setup in the group settings
- a kde mailing list: probably more topically relevant, needs a sysadmin
ticket filed at https://phabricator.kde.org/maniphest/task/edit/form/2/
asking to create muon-b...@kde.org or some such name

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: muon bug reports

[Harald Sitter]

Not that I know of.

On Wed, Sep 30, 2020 at 1:43 PM Mitch Golden  wrote:
>
> Has a list been created? I would like to join.
>
>- Mitch Golden
>
> On 9/25/20 9:53 AM, Mitch Golden wrote:
> > On 9/25/20 9:52 AM, Harald Sitter wrote:
> >> On 08.08.20 16:50, Nate Graham wrote:
> >>> On 8/8/20 8:48 AM, Harald Sitter wrote:
> >>>> On Sat, Aug 8, 2020 at 3:14 AM Mitch Golden 
> >>>> wrote:
> >>>>>
> >>>>> Is there something broken about muon that would require it to be
> >>>>> sunset?
> >>>>
> >>>> We don't know because nobody triages bugs, let alone works on them,
> >>>> hence my original question where bug mails should go ;)
> >>>
> >>> I suppose we should set up a new mailing list and encourage people who
> >>> care to subscribe to it.
> >>
> >> Anybody going to do this? Otherwise I'll go ahead with marking it
> >> unmaintained.
> >
> > I will join the list if someone sets it up and take a crack at triaging
> > the bugs.
> >
> >- Mitch Golden

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: muon bug reports

[Harald Sitter]

On 08.08.20 16:50, Nate Graham wrote:
> On 8/8/20 8:48 AM, Harald Sitter wrote:
>> On Sat, Aug 8, 2020 at 3:14 AM Mitch Golden 
>> wrote:
>>>
>>> Is there something broken about muon that would require it to be sunset?
>>
>> We don't know because nobody triages bugs, let alone works on them,
>> hence my original question where bug mails should go ;)
> 
> I suppose we should set up a new mailing list and encourage people who
> care to subscribe to it.

Anybody going to do this? Otherwise I'll go ahead with marking it
unmaintained.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: muon bug reports

[Harald Sitter]

On Sat, Aug 8, 2020 at 3:14 AM Mitch Golden  wrote:
>
> Is there something broken about muon that would require it to be sunset?

We don't know because nobody triages bugs, let alone works on them,
hence my original question where bug mails should go ;)

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: muon bug reports

[Harald Sitter]

I honestly don't know, Carlo did do some changes, also in the
underlying libqapt. I haven't used muon in at least half a decade, but
from what I recall it definitely was complete. Of course at the same
time it's a massively feature rich app so there's bound to be problems
and that's what those bugs are by the looks of it. Specifically half
look like weird problems elsewhere that simply happen to manifest in
muon, a quarter are legit issues in weird scenarios and the other
quarter are wishlist items. The more concerning bit is libqapt WRT
maintenance. libapt-pkg does change ABI every once in a while and if
informed porting to the new API doesn't happen then that's bound to
bit rot through uninformed hodgepodge porting eventually.

That being said, if nobody wants to maintain muon I'm fine with sunsetting it.
Equally I'm fine with sunsetting libqapt but as I recall some of the
l10n support tech depends on it (via libkubuntu).

On Fri, Aug 7, 2020 at 3:29 PM Nate Graham  wrote:
>
> Is Muon itself still developed at all? From what I can see it has had
> only one substantive commit [1] in the last two years. The rest are
> translations, appdata changes, etc. The bug tracker has tons of bugs [2]
> so it's not as if it's a mature and finished app without the need for
> much development.
>
> Nate
>
> [1]
> https://invent.kde.org/system/muon/-/commit/8453986756bfad695e318c9c147ec55c0b666d06
> [2]
> https://bugs.kde.org/buglist.cgi?component=muon&list_id=1777549&product=muon&resolution=---
>
>
>
> On 8/7/20 4:25 AM, Harald Sitter wrote:
> > elo
> >
> > muon bugs on bugs.kde.org get default assigned to
> > echidna...@kubuntu.org but I'm sure he's not done any development in
> > years so I would rather change it to something else. any preferences?
> > a mailing list ideally.
> >
> > HS
> >

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

muon bug reports

[Harald Sitter]

elo

muon bugs on bugs.kde.org get default assigned to
echidna...@kubuntu.org but I'm sure he's not done any development in
years so I would rather change it to something else. any preferences?
a mailing list ideally.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

profiling startup

[Harald Sitter]

I see there was some discussion over startup times on IRC.

If you want to profile startup you'll want to use systemd-bootchart
[1] it tracks resources usage during boot, which is valuable
information in finding out why it may be slow (outside slowness in
software).

For debugging the actual session-start you can have a look at [2]
which will tell you how to profile a plasma session on x or wayland.

[1] http://manpages.ubuntu.com/manpages/bionic/man1/systemd-bootchart.1.html
[2] http://blog.davidedmundson.co.uk/blog/plasma-startup/

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

xdg-desktop-portals & kubuntu

[Harald Sitter]

Hola

I thought I should point out that the Ubuntu Desktop team is looking
into SRUing a new xdg-desktop-portals and gnome frontend to the
supported LTSes. It probably would be a good idea for Kubuntu to also
SRU the frontend for Plasma systems. Desktop portals are a central
part of integrating confined bundles (e.g. snap, flatpak) into the
host system, without them the user experience suffers tremendously.

Also see: https://forum.snapcraft.io/t/kde-integration-xdg-desktop-portal/8880

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

libdebconf-kde 1.0.3

[Harald Sitter]

New maintenance release for libdebconf-kde, a Debian configuration
system UI frontend library.

https://download.kde.org/stable/libdebconf-kde/1.0.3/src/libdebconf-kde-1.0.3.tar.xz.mirrorlist
https://download.kde.org/stable/libdebconf-kde/1.0.3/src/libdebconf-kde-1.0.3.tar.xz.sig.mirrorlist

* Translations update
* Fixed a crash on signal QUIT (sent by packagekit to quit the helper)

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Fwd: Discover in Neon LTS

[Harald Sitter]

FYI, given the bug duplicates, this also affects Kubuntu 16.04


-- Forwarded message --
From: Aleix Pol 
Date: Fri, Nov 17, 2017 at 9:11 PM
Subject: Discover in Neon LTS
To: Discussion of the KDE Neon project 
Cc: Nate Graham 


Hi,
There's few issues that are bugging our users there [1], mainly this one:
https://bugs.kde.org/show_bug.cgi?id=383413

Would it be possible to include the last patch I did on Plasma/5.8 in
case it fixes the issue? It's revolving the same code and it kind of
makes sense. Alternatively we could have a 5.8.8.1 release if you
prefer.

I've been running the LTS on vbox and didn't manage to reproduce the issue.

Aleix

[1]
https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&list_id=1476239&product=Discover&query_format=advanced&version=5.8.0&version=5.8.2&version=5.8.3&version=5.8.4&version=5.8.5&version=5.8.6&version=5.8.7&version=5.8.8

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

deleting all kubuntu branches on debian repos

[Harald Sitter]

Servus!

I've just noticed that we still have a gazillion kubuntu_* branches in
the repos on git.debian.org, seeing as they aren't used anymore I
wonder if there are any objections to mass deleting the lot of them?
They serve no purpose other than confuse people.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Snapping KDE

[Harald Sitter]

On Tue, Jul 11, 2017 at 4:11 PM, Aleix Pol  wrote:
> FWIW, Harald put together this Plasma snap, maybe someone would be
> interested in looking into its viability?
> https://github.com/apachelogger/plasma-snap

FTR: Reading material for the interested.

High-level overview and some musing on confinement
https://apachelog.wordpress.com/2017/02/21/plasma-in-a-snap/

Roadblocking relocatability musing
https://mail.kde.org/pipermail/plasma-devel/2017-February/066782.html

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Welcoming Rik Mills as Kubuntu Developer

[Harald Sitter]

With all present devs voting in favor, Rik got voted into the circle
of Kubuntu Developers. He's done lots of awesome stuff in the past and
we are looking forward to seeing him put these new found powers to
good use.

Congratulations and welcome!

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Kubuntu Developer Application for Rik Mills (doodle poll included)

[Harald Sitter]

We should have quorum with yofel, shadeslayer and me in attendance.
Any other dev who may have time may of course chime in.

Also, as Rohan needs to be out by 20UTC I'd appreciate it if everyone
is there at 19UTC sharp.

On Sun, Feb 5, 2017 at 7:03 PM, Rik Mills  wrote:
> Thank you all.
>
> Poll is now closed and I have made a provisional choice of a meeting
> start time of between 19:00 & 20:00 UTC on Thurs 9th February.
>
> Again, if this is not convenient or possible for some kubuntu-devs, then
> perhaps we can still come to some accommodation.
>
> Regards
>
> Rik
>
> On 04/02/17 20:11, Rik Mills wrote:
>> Sadly at the moment I do not have enough existing developers responding
>> to the poll to make the application meeting possible.
>>
>> However, in the spirit of optimism..
>>
>> At the moment, Thursday 9th Feb @ 19:00 UTC is my preferred choice, but
>> there is a little flexibility on the time and day there should that
>> prove difficult.
>>
>> Please let me know if this is an issue.
>>
>> I shall most likely close the poll tomorrow evening.
>>
>> Thanks
>>
>> Rik
>>
>> On 31/01/17 19:46, Rik Mills wrote:
>>> A polite reminder about this to all devs.
>>>
>>> Pardon this. I am aware many of you are very busy.
>>>
>>> Thanks.
>>>
>>> Rik
>>>
>>> On 23/01/17 10:25, Rik Mills wrote:
 Hi,

 As encouraged by the team and council, please find below a doodle poll
 for proposed developer application meeting times.

 http://doodle.com/poll/a3qe3nbtgxsxth2r

 My developer application wiki page can be found here:

 https://wiki.ubuntu.com/RikMills/KubuntuDeveloperApplication

 That page is still a work in progress, but any comments and constructive
 criticism on that OR the application as a whole, added to the comments
 section if you are able, is very welcome. If the wiki will not cooperate
 for you, or you just wish to, you can email me, or chat in IRC/Telegram
 etc with any comments you have.

 Best regards

 Rik

>>>
>>
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Change in policy for Kubuntu Members

[Harald Sitter]

Members having access to all venues of contribution was not a result
of legacy, it was a conscious decision made at the time we introduced
source code version control. We found that we trust all members to act
in the best interest of the project and work towards the same goal.

It is truly a sad day that members of Kubuntu cannot be trusted
anymore. I always looked with fondness at the fact that membership
actually meant something more than been-around-long-enough.

:(

On Thu, Jan 12, 2017 at 12:16 AM, Valorie Zimmerman
 wrote:
> In the early days of Kubuntu, all the Kubuntu Members were packagers
> and developers. Since the community has grown, we now have some
> Kubuntu Members who are not packagers, developers or coders. Yet one
> of the privileges of Kubuntu Membership has long been the right to
> commit changes to our packaging and packages.
>
> The Kubuntu Council, after extensive discussion which you can read in
> the archives of our list on our Launchpad page [1], has updated our
> Kubuntu Policies [2] and Launchpad.
>
> Since packagers and developers are already members of the teams which
> have the permissions to commit, change or upload as needed, this
> should have no effect on Kubuntu Members, but it will improve the
> security of our code and packages on LP.
>
> Valorie, for the Kubuntu Council
>
> 1. https://launchpad.net/~kubuntu-council
> 2. https://community.kde.org/Kubuntu/Policies
>
> --
> http://about.me/valoriez
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

broken logo artwork thing

[Harald Sitter]

knome on IRC pointed the following out to me

> https://community.kde.org/Kubuntu/Artwork is borked, the logo download link 
> is pointing nowhere :P

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

what to do with repos

[Harald Sitter]

whilest doing git repo house cleaning in preparation for KDE moving
repos into phabricator I stumbled upon some stuff that runs under my
name but probably should be moved to launchpad now that its git
feature is being used for kubuntu stuff. please have a look at the
repos and tell me what to do with them

https://cgit.kde.org/clones/kde-runtime/sitter/kubuntu.git/
clone of kde-runtime with continues rebase branches of l10n patch. I
am guessing this can go with kde-runtime being no more

https://cgit.kde.org/scratch/sitter/kubuntu-docs.git/
was used to generate docbook from wiki

https://cgit.kde.org/scratch/sitter/kubuntu-rake.git/
I think this is being used to pull translations into the various
software kubuntu has in kde (whoopsie-kcm, kubuntu-debug-installer
etc.)

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Welcome Clive Johnston as Kubuntu Dev

[Harald Sitter]

After a marathon grilling I am happy to say that we can welcome Clive
as new member to the Kubuntu Dev team. He's been very active and
dedicated to Kubuntu and we are glad to accept him into the ranks of
elite Kubuntu developers.

Congratulations and welcome!

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Review Request 128520: fix incorrect markup usage

[Harald Sitter]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/128520/
---

(Updated July 25, 2016, 1:54 p.m.)


Status
--

This change has been marked as submitted.


Review request for Kubuntu, LibQApt and Aleix Pol Gonzalez.


Changes
---

Submitted with commit d109c90d9deb6ff7f2e18f1244801da098916d4f by Harald Sitter 
to branch master.


Repository: libqapt


Description
---

since kf5 kuit markup needs to be run through xi18n* rather than i18n*

(this really should have a build-time check in ki18n... fixing this crap
 after it was found at runtime is fairly stupid)


Diffs
-

  utils/qapt-batch/qaptbatch.cpp aa0f8ce01ea1f208fbf1d3b0c8fbc6ced4fc26b4 
  utils/qapt-gst-helper/PluginHelper.cpp 
45630ef258467a8804ce02af73c9a22bf3374cf8 

Diff: https://git.reviewboard.kde.org/r/128520/diff/


Testing
---

can't be bothered


Thanks,

Harald Sitter

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Review Request 128520: fix incorrect markup usage

[Harald Sitter]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/128520/
---

Review request for Kubuntu, LibQApt and Aleix Pol Gonzalez.


Repository: libqapt


Description
---

since kf5 kuit markup needs to be run through xi18n* rather than i18n*

(this really should have a build-time check in ki18n... fixing this crap
 after it was found at runtime is fairly stupid)


Diffs
-

  utils/qapt-batch/qaptbatch.cpp aa0f8ce01ea1f208fbf1d3b0c8fbc6ced4fc26b4 
  utils/qapt-gst-helper/PluginHelper.cpp 
45630ef258467a8804ce02af73c9a22bf3374cf8 

Diff: https://git.reviewboard.kde.org/r/128520/diff/


Testing
---

can't be bothered


Thanks,

Harald Sitter

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

wire.kubuntu.org still needed?

[Harald Sitter]

 valorie: can someone decide, if http://wire.kubuntu.org/
is still needed with the new kubuntu webpage "News" section?

cheers
HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: qtchooser / qdbusviewer (ksnapshot / spectacle)

[Harald Sitter]

On Wed, May 25, 2016 at 11:43 AM, Xen  wrote:
> Valorie Zimmerman schreef op 25-05-2016 4:09:
>
>> Hello Xen, have you filed bugs against Spectacle in bugs.kde.org? The
>> developer does not (presumably) read this list. Ksnapshot was not only
>> unmaintained, but was rapidly bit-rotting, and also would completely
>> cease to function in the post-Wayland world, so the Spectacle devel
>> took what he could of the old code, and started anew with the rest of
>> the application.
>>
>> It is new, so bug reports are welcomed. It is fine to do the
>> workaround of making ksnapshot work for now, but that will not work
>> forever. Therefore, it will help all of us if you make the effort to
>> file bug reports and make Spectacle better.
>
>
> Filing bug reports does not make a program better, you know that?

They actually do.

> It only tells you what is wrong about a product. That does not improve
> anything.

It does. Everyone would then know that something is wrong with a
product because the bug report told them so.

> Most of these things are things you can discover in 2 hours if you try. That
> means the developer should already be fully aware of it and shouldn't need
> other people to tell him so.

That is an assumption on your part. I personally did a comprehensive
number of tests over a 2 day period and I observed none of your
complaints.

> He apparently sought to improve things that already worked well, and made
> things worse. Who am I then to say that he should do things differently?

KSnapshot does not work on Wayland as Valorie already pointed out.

> It seems rushed, like most thing are. Spectacle has better command line
> options than KSnapshot, and more fit for an actual screenshotting
> application. However using DBus makes it harder for users, not easier. You
> can use the DBusViewer to view most or all of the options available, but
> only if the application is already started, and most of them are useless to
> a user. It is a developer tool, but now prominently features on a user
> dialog screen for just adjusting a command or changing the command that is
> started on a shortcut. DBus is not something you should expect users to use,
> it is not a user interface. This makes it incomprensible and even impossible
> to even change the default. Now you end up with a non-configurable system
> for most users.

"Most users" is far fetched. "Most users" hit the printscreen key or
start it via the menu and then save the screenshot, and that's the
entire extent of their interaction with a screenshot tool.

> The issue with KDEs configurion was not lack of DBus, it was lack of an
> ability to efficiently select applications, requiring you to type a full
> path, even though you can only use applications (normally) that are already
> in the PATH. So what was needed was a better way to select in-PATH
> applications, but now we have DBus instead which makes it even worse instead
> of better. KSnapshot was controllable by DBus, just not started that way.
> But for a user, command line options are enough.
>
> Moreoever those are meant as a user interface instead of as a developer
> interface
>
> So currently we see four changes:
> - better command line options
> - worse way to start it (DBus)
> - worse user interface
> - some failing functionality on the one hand, and added background
> functionality on the other hand.
>
> I mean no one needs me to see this, the question is whether they recognise
> it or not.
>
> I don't want to end up being the next guy to file a bug report and then
> being ignored.
>
> Moreoever the last bug report I filed spammed me incessantly. I had to take
> myself off its CC list because there were meaningless updates emailed to me
> daily. Now that was a very popular bug, you might say. But it just took me
> another 15 minutes to log back into the system after having forgotten my
> password or username.
>
> Requiring users to create accounts specifically for you is just not done.
> That is putting up barriers to entry, email suggestions or bugs should be
> free, not behind a walled garden.
>
> And moreover, I do not like BugZilla at all even if it is KDE's variant
> (there are much better systems).
>
> So no, I prefer to talk directly to developers. Sorry.

And Valorie informed you that the Kubuntu developer list is not the
correct venue to talk to the spectacle developer as he is not on here.
You can list as many defects as you want, sending them to this mailing
list will definitely not get them fixed, bug reports just might.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Fwd: CIs: stricter versioning control

[Harald Sitter]

since the mail apparently got eaten by the moderation queue...


-- Forwarded message --
From: Harald Sitter 
Date: Tue, Feb 16, 2016 at 10:37 AM
Subject: CIs: stricter versioning control
To:


Since the debian version epoch keeps getting messed up every once in a
while in the CI branches I have now rolled out tech to prevent debian
epoch bumps (basically bumping the super overriding version of
packaging).

Our jobs now record the versions they built in a file called
'last_version', this file is read on subsequent runs and it is made
sure that the epoch version of the new build is not different from the
last one (no increments nor decrements allowed).

If the epoch is found to be different this will result in an unhandled
exception in the log looking a bit like this:

> Error: test_increment_fail(CI::VersionEnforcerTest): 
> CI::VersionEnforcer::UnauthorizedChangeError:  -> 1

-->
The only way to get an epoch version change is to have someone
manually remove the last_version file from the job workspace!
<--

Usually only a jenkins admin will be able to do that. When in doubt, ask me.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

CIs: stricter versioning control

[Harald Sitter]

Since the debian version epoch keeps getting messed up every once in a
while in the CI branches I have now rolled out tech to prevent debian
epoch bumps (basically bumping the super overriding version of
packaging).

Our jobs now record the versions they built in a file called
'last_version', this file is read on subsequent runs and it is made
sure that the epoch version of the new build is not different from the
last one (no increments nor decrements allowed).

If the epoch is found to be different this will result in an unhandled
exception in the log looking a bit like this:

> Error: test_increment_fail(CI::VersionEnforcerTest): 
> CI::VersionEnforcer::UnauthorizedChangeError:  -> 1

-->
The only way to get an epoch version change is to have someone
manually remove the last_version file from the job workspace!
<--

Usually only a jenkins admin will be able to do that. When in doubt, ask me.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Review Request 126382: disable ptrace

[Harald Sitter]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126382/
---

(Updated Dec. 17, 2015, 10:15 a.m.)


Status
--

This change has been marked as submitted.


Review request for Kubuntu, Martin Gräßlin and Jonathan Riddell.


Changes
---

Submitted with commit f9263411fff21ad7edc5d5766b3053d96acb5110 by Harald Sitter 
to branch master.


Repository: kdesudo


Description
---

disable ptrace


Diffs
-

  kdesudo/main.cpp a289f96fa043918c366950684984e054fef96bcb 
  kdesudo/config.h.cmake PRE-CREATION 
  kdesudo/CMakeLists.txt a1a8f11ce737d17f838bc9193d4a8ef469fdf046 
  CMakeLists.txt 43649b8f60442dce3d4961bba375d2cda5fbec1b 

Diff: https://git.reviewboard.kde.org/r/126382/diff/


Testing
---


Thanks,

Harald Sitter

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Review Request 126382: disable ptrace

[Harald Sitter]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126382/
---

(Updated Dec. 16, 2015, 9:59 a.m.)


Review request for Kubuntu, Martin Gräßlin and Jonathan Riddell.


Changes
---

include config.h


Repository: kdesudo


Description
---

disable ptrace


Diffs (updated)
-

  kdesudo/main.cpp a289f96fa043918c366950684984e054fef96bcb 
  kdesudo/config.h.cmake PRE-CREATION 
  kdesudo/CMakeLists.txt a1a8f11ce737d17f838bc9193d4a8ef469fdf046 
  CMakeLists.txt 43649b8f60442dce3d4961bba375d2cda5fbec1b 

Diff: https://git.reviewboard.kde.org/r/126382/diff/


Testing
---


Thanks,

Harald Sitter

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Review Request 126341: app notifier is crashing right now. build a test around it

[Harald Sitter]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126341/
---

(Updated Dec. 14, 2015, 11:21 a.m.)


Status
--

This change has been marked as submitted.


Review request for Kubuntu, Muon Package Management Suite and Aleix Pol 
Gonzalez.


Changes
---

Submitted with commit 86b6b88dd04d68bc92942c9460335e3efb171fc7 by Harald Sitter 
to branch Plasma/5.5.


Repository: discover


Description
---

prevent notifier from crashing when process was not initialized yet


Diffs
-

  libdiscover/backends/ApplicationBackend/ApplicationNotifier.cpp 
7611d046b5761b75f9535415b9b8903fef7ed49b 
  libdiscover/backends/ApplicationBackend/CMakeLists.txt 
e2bb7fbeecde6983aa48b6bdb79a6c6fd41c83e3 
  libdiscover/backends/ApplicationBackend/tests/CMakeLists.txt 
274adf3a1f82ee8cd2f0f1bd6392d005b09195c6 
  libdiscover/backends/ApplicationBackend/tests/NotifierTest.h PRE-CREATION 
  libdiscover/backends/ApplicationBackend/tests/NotifierTest.cpp PRE-CREATION 

Diff: https://git.reviewboard.kde.org/r/126341/diff/


Testing
---

ran test without fix -> exception fail
ran test with fix -> pass


Thanks,

Harald Sitter

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Review Request 126341: app notifier is crashing right now. build a test around it

[Harald Sitter]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126341/
---

Review request for Kubuntu, Muon Package Management Suite and Aleix Pol 
Gonzalez.


Repository: discover


Description
---

prevent notifier from crashing when process was not initialized yet


Diffs
-

  libdiscover/backends/ApplicationBackend/ApplicationNotifier.cpp 
7611d046b5761b75f9535415b9b8903fef7ed49b 
  libdiscover/backends/ApplicationBackend/CMakeLists.txt 
e2bb7fbeecde6983aa48b6bdb79a6c6fd41c83e3 
  libdiscover/backends/ApplicationBackend/tests/CMakeLists.txt 
274adf3a1f82ee8cd2f0f1bd6392d005b09195c6 
  libdiscover/backends/ApplicationBackend/tests/NotifierTest.h PRE-CREATION 
  libdiscover/backends/ApplicationBackend/tests/NotifierTest.cpp PRE-CREATION 

Diff: https://git.reviewboard.kde.org/r/126341/diff/


Testing
---

ran test without fix -> exception fail
ran test with fix -> pass


Thanks,

Harald Sitter

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Strange symbols issue.

[Harald Sitter]

they are all guarded by #if NM_CHECK_VERSION(1, 0, 6)

our symbols file was removed by
http://anonscm.debian.org/cgit/pkg-kde/frameworks/networkmanager-qt.git/commit/?h=kubuntu_vivid_backports&id=c11436042cdfc160518336f298a785ed14bdaefd

debian's was introdcued in
http://anonscm.debian.org/cgit/pkg-kde/frameworks/networkmanager-qt.git/commit/?h=kubuntu_unstable&id=c0087fb71a218c4c7585ab8c344352adb8a7fe15

debian is a at 1.0.8
https://packages.qa.debian.org/n/network-manager.html

ubuntu is not
https://launchpad.net/ubuntu/+source/network-manager

what you are seeing is a symbol mismatch because debian unstable is
ahead of xenial

On Thu, Dec 3, 2015 at 2:30 AM, Scarlett Clark
 wrote:
> networkmanager-qt has symbols failure. Upon batchpatch completion it wants
> me to remove a pile of symbols.
> Looking for patches and reading them 
> --
> | Processing libkf5networkmanagerqt6 package |
> --
> Patching symbol file 'debian/libkf5networkmanagerqt6.symbols' with supplied
> patches ...
> * patch 'libkf5networkmanagerqt6_5.16.0+git20151202.2238+16.04-0_amd64 (---
> debian/libkf5networkmanagerqt6.symbols)' for amd64 ... OK.
> Confirmed arches: alpha, arm64, armel, armhf, hppa, i386, mips, mips64el,
> mipsel, powerpc, ppc64, ppc64el, s390x, x32
> Generating symbol file template  (this might take a while)
> pkgkde-symbolshelper: warning: there are LOST symbols (including optional):
>  SONAME: libKF5NetworkManagerQt.so.6
>   #MISSING: 5.16.0# _ZN14NetworkManager11AccessPoint15lastSeenChangedEi@Base
> 5.14.0
>   #MISSING: 5.16.0#
> _ZN14NetworkManager6Device14meteredChangedENS0_13MeteredStatusE@Base 5.14.0
>   #MISSING: 5.16.0# _ZN14NetworkManager7meteredEv@Base 5.14.0
>   #MISSING: 5.16.0#
> _ZN14NetworkManager8Notifier14meteredChangedENS_6Device13MeteredStatusE@Base
> 5.14.0
>   #MISSING: 5.16.0# _ZNK14NetworkManager11AccessPoint8lastSeenEv@Base 5.14.0
>   #MISSING: 5.16.0# _ZNK14NetworkManager6Device7meteredEv@Base 5.14.0
> scarlett@scarlett-lappy:~/Work/xenial-frameworks/networkmanager-qt$ c++filt
> _ZN14NetworkManager11AccessPoint15lastSeenChangedEi
> NetworkManager::AccessPoint::lastSeenChanged(int)
> scarlett@scarlett-lappy:~/Work/xenial-frameworks/networkmanager-qt$ c++filt
> _ZN14NetworkManager6Device14meteredChangedENS0_13MeteredStatusE
> NetworkManager::Device::meteredChanged(NetworkManager::Device::MeteredStatus)
>
> Upon looking up these symbols they all where created in this RR:
> https://git.reviewboard.kde.org/r/124998/diff/1-2/
>
> Looking through all commits since, I see no where that these were removed.
> Could someone please educate me and tell me why they would suddenly vanish
> from our build. My gut feeling tells me that removing these would end badly.
> Thank you,
> Scarlett
>
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

muon 5.5.0

[Harald Sitter]

New standalone muon package manager release.

http://download.kde.org/stable/muon/5.5.0/muon-5.5.0.tar.xz.mirrorlist

* discover, updater and notifier were split. muon only contains the
package manager now
* build dependencies have been reduced accordingly

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Each toolchain with their file

[Harald Sitter]

On Fri, Oct 30, 2015 at 7:49 PM, Maximiliano Curia  wrote:
> ¡Hola Aleix!
>
> El 2015-10-30 a las 18:26 +0100, Aleix Pol escribió:
>>
>> On Thu, Oct 29, 2015 at 1:36 PM, Aleix Pol  wrote:
>>>
>>> On Thu, Oct 29, 2015 at 12:39 PM, Maximiliano Curia 
>>> wrote:

 I would like to hear some feedback about this approach anyway.

 The plan would be to tag the packages that contain only dev tools (that
 produce an arch independant output) as Multi-Arch: foreign packages, the
 tools can be installed anywhere, but the cmake files that contain full path
 of the tools would need to be installed in a non arch dependant path.

 Happy hacking,
>>>
>>>
>>> I don't really see why you want to change that. The KF5_HOST_TOOLING
>>> variable needs to find the file anyway, so we're not going to be able to
>>> skip the look-up specification anyway.
>
>
>> Ping?
>
>
> I was waiting to see if somebody else had an opinion about this.
>
> Setting the KF5_HOST_TOOLING should work even if the package is Multi-Arch:
> same, you'll end up with a bin-dev installed for each arch, but that
> shouldn't be an issue. So that is another valid option.

FTR:

I think the primary motivation is to have cmake decide (or coerced)
into which host tooling is appropriate rather than have the packaging
coerce cmake (if the paths weren't arch specific cmake would have no
option but to use what is present). Former allows for more "smarts" to
be applied to allow controlled cross-compiling and moves the decision
what is compatible out of the packaging and into cmake.

At any rate, the ideal end result is to have frameworks install
everything related to development to architectured directories. So the
-devs ultimately become MA:same and can contain the build time tools
needed for their arch. At runtime cmake can then decide which of the
available tools to pick depending on the architecture it is building
on (or what the cmake toolchain file tells it to use).

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Kubuntu CI Show & Tell @ Ubuntu Online Summit

[Harald Sitter]

Aloha

It was suggested that I do a show and tell on Kubuntu CI. So I got one
scheduled for Thursday Nov 5 (a week from today).

I'd like to invite everyone to attend. In particular if you are
interested in how our CI works or the concept and motivation behind
continuous packaging.

More info and registration for UOS:
http://summit.ubuntu.com/uos-1511/meeting/22603/kubuntus-continuous-integration-and-packaging/

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kde test fail in 16.04

[Harald Sitter]

 sitter, Riddell: several KDE tests now fail with "FAIL stderr:
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++
but not for C"; e. g. kio, plasma-workspace, kcoreaddons
 these could be quiesced with "allow-stderr", but presumably
this should be fixed more properly?

Would be good if someone could take a look. If you have question I am
sure pitti can help.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Add Muon-Discover to the favorites menu

[Harald Sitter]

On Mon, Oct 19, 2015 at 9:42 AM, Michael Devendra Lutynski
 wrote:
> I realize this thread is old, but Muon Discover used to be located in the
> Kickoff menu in the "Computer" tab. Now I see it's gone in the move to KF5
> and Plasma 2.
>
> Am I the only one to think that Muon Discover should be back under the
> Computer tab? Along with "Run command" and "System Settings"? The favorites
> is a good place, I agree, yet a reliable, easy-to-describe location is
> valuable too.
>
> I give support to non-technical Kubuntu users and to be able to say, "look
> under the Computer tab for 'software center'" makes my job a lot easier :)

Suggest to visual design group please
https://forum.kde.org/viewforum.php?f=285&sid=7063c086be0be39359bd1786c0e9e8c4

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

CI merge marker checks

[Harald Sitter]

It has happened more than once that git threw a merge conflict and in
a hurry someone didn't resolve the conflict properly but simply git
add a conflicting file. This leaves lingering merge markers (>>
<<) in the file and potentially goes unnoticed for a long time as
some files are not actually parsed at build time and thus the merge
markers do not cause a build failure.

I now added tech to detect this in the QA stage of all KCI builds [1]
and raise integration errors if markers were found. If you notice a
false positive please poke me.

[1] 
http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/commit/?id=1da12af7c6acff5ac391c7da571cd599f1d31a79

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Add Muon-Discover to the favorites menu

[Harald Sitter]

http://i.imgur.com/liEEEPl.jpg

On Thu, Oct 15, 2015 at 9:11 AM, Mustafa Muhammad
 wrote:
> Hi,
> For new users, it is not that obvious how to install packages, I suggest
> adding Muon Discover to the favorites menu for the default installation.
>
> Regards
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kdepim ABI

[Harald Sitter]

http://anonscm.debian.org/cgit/pkg-kde/applications/kdepim.git/commit/?h=kubuntu_wily_archive&id=c76f2759cc10a2b19138f083da5791858cbd3e1c

it appears to me the only incompatible change is [1] which appears to
be in viewer.h which hasn't been installed in the present soversion
ever, so this is actual private ABI that was changed and doesn't
warrant soversion twiddling of any magnitude.

[1] 
https://quickgit.kde.org/?p=kdepim.git&a=commit&h=9d52b22b3652f4dc274114f41c6ea83a31477c01

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

unstable CI builds

[Harald Sitter]

FYI I switched out our log parser and didn't get done with
reimplementing the ignore rules so expect builds to turn UNSTABLE
because they have missing optional cmake deps. Simply ignore that.
I'll retry all builds next week once I have this bit of tech
reimplemented (needs some code design fiddling first unfortunately).

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

CI merge order changed again - backports back, order adjusted

[Harald Sitter]

Backports branches are back in the game. But the merge order changed somewhat.

So. The reason I originally introduced backports as it turns out was
that we consider them a 'release' branches. i.e. we release from this
branch (albeit after distro release). As such it plays into CI efforts
of that distro series (e.g. vivid).

new order is per series and works as such:
  archive -> backports
  backports | archive -> stable | unstable
  stable -> variants
  stable -> unstable
  unstable -> variants

variants are essentially branches that have things appended to the CI
name (that's incidentally why it's kubuntu_unstable_vivid and not
kubuntu_vivid_unstable :P). so stable->variant has stable_* as target.

The problem with the previous merge order was that we always
considered all 'release' branches equal. So vivid_archive, played as
much into unstable as wily_archvie did. That was thought up as the
ultimate goal being that you fix something in vivid_archive for an SRU
and it gets automerged into wily_archive and that gets automerged into
unstable and CI'd. While that might work for _archive it most
certainly doesn't for _backports. And since the _archive use also
never happened like that this was simplified and detangled [1] now.

The only way multiple series interact branch-wise is now through the
CI variant branches and these only work latest -> not-latest. So
kubuntu_unstable -> kubuntu_unstable_vivid if we wanted utopic it
would be kubuntu_unstable -> kubuntu_unstable_vivid AND
kubuntu_unstable -> kubuntu_unstable_utopic etc.etc.

not-latest branches never auto-merge into latest anymore!

https://github.com/blue-systems/pangea-tooling/commit/0541660cdc814fd5e97a909c7f717174da3f44e4

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

pause CI before mass pushing stuff & mark irrelevant changes NOCI

[Harald Sitter]

General reminder:

Use the tech to avoid transitional CI fail. Specifically pause CI when
you push lots of plunder via
http://kci.pangea.pub/job/mgmt_pause_integration/ and use NOCI in your
commit messages when you want to prevent an immediate build.

# Pause
http://kci.pangea.pub/job/mgmt_pause_integration/
This job halts all build integration while it is running. Builds, and
only builds. You still get semi-instant feedback on broken merges and
so forth. But builds are paused.

You absolutely want to do in every situation where you push more than
one or two repos and the repos might depend on one another. Jenkins
knows how to order builds so dependency chains are retained.

For example if Jenkins can build extra-cmake-modules and kio, it will
first build ECM and then KIO as latter build-depends on former. We
have tech that enforces this in Jenkins so you know that given this
situation KIO builds after ECM.
BUT, when you push KIO before ECM and bump the version requirement on
ECM Jenkins doesn't yet know that you on your harddisk have a version
bump for ECM, so it builds KIO and KIO fails because it can't find the
ECM dependency. Pausing builds means Jenkins won't build KIO, it will
however know that there is a change, it will queue a build for that
change but it won't actually do anything until after you abort the
pause job.
So what you should do: you run the pause job -> you push KIO ->
jenkins queues it for a CI build -> you push ECM and whatever else ->
jenkins queues those as well -> you abort the pause job -> jenkins now
processes the queue *in order* of the dependency tree -> ECM builds
first.

Not pausing is a sure fire way to turn half the jobs red through dep
ordering problems. Pausing has no downside, so when in doubt: pause
first! (don't forget to unpause though, that also makes me grumpy :P)

# NOCI
When you add the keyword NOCI anywhere in your commit message your
commit will not cause a build. You can use this to mark commits as not
worth building. But beware that most, even relatively minor changes
are not NOCI. A simple comment change in control could trigger a
lintian complaint. A file rename could break the build. So you only
want to do this when your change has no impact on the CI build.

So how can you tell...

Prime and possibly only example of this are commits that only change
the changelog but do not touch the *base* version.

e.g. 4:1.0-0ubuntu1
4:1.0 = base; if you change that it's decidedly not NOCI

You can literally change anything else in the changelog. Well, you
probably shouldn't break the format but even that you'd know in <=24
hours (see blow).

Archive uploads are a good example where you only flip the
distribution field from UNRELEASED to wily or vivid or whatever. There
is no impact on the base version so the CI has no way to fail from
such a change.

Initial uploads of new releases OTOH change the base version, e.g.
frameworks goes from 5.14 to 5.15. These must be CI'd.

Caveats:
- if you have more than one commit locally and push those commits, the
latest commit counts, if it is NOCI the entire commit set will not be
looked at. This includes merge commits! so be careful not to over use
this with non-atomic commits
- NOCI essentially prevents git.debian from telling jenkins about the
change. There are still other means the commits can trigger a build
though. albeit they usually involve me swinging a staff while shouting
a spell.
- Along that last bit, even NOCI commits are integrated as part of the
daily integration update build at 0 UTC. So fear not, if you happened
to accidentally push NOCI what shouldn't have been NOCI we'll still
find out eventually.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: CI merger order change - backports remove

[Harald Sitter]

Since it came up on IRC that the backport merging could make sense
with order changes and so forth I am going to revise this a bit to
potentially be useful once more.
Since I had to write up all directives to not get myself tangled up
here's notes https://goo.gl/photos/Uh71a7FvWdgva3w16 (doubt they'll be
useful to anyone but me, but for public record keeping's sake I'll
post them all the same :P)

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: CI merger order change - backports remove

[Harald Sitter]

On Fri, Oct 9, 2015 at 9:29 AM, Scarlett Clark
 wrote:
> Sorry did I do something wrong?

No, I did. I have no clue why backports were being merged forward into
CI branches or why I added that feature, and now those merges keep CI
busy when I am supposed to roll an ISO :'<

They also have the more important side ffects that debian/control
adjustments for vivid get into CI, get reverted, get into wily, get
into vivid, get revert-reverted (to restore backport condition), get
into CI...
Point being that they form a merge cycle of perpetual regression since
a backport doesnt have to have the same packaging as a build for
$latest so merging them into CI for latest and as a result eventually
into latest (i.e. wily_archive) makes no sense.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

CI merger order change - backports remove

[Harald Sitter]

I have just removed kubuntu_*_backports branches from the CI
auto-merge order. In my original introduction of it I failed to
explain why we want it and I am now rather under the impression that
we do not want it as it basically regresses wily branches to backport
conditions ever so often while not actually adding any value on top of
that.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

CI dep resolvers

[Harald Sitter]

Quick brain dump.

We are currently using pbuilder's dependency satisfiers, but they are
rather error prone for CI purposes. So at some point we might want to
replace them with custom code as this is actually pretty straight
forward:

Reimplement pbuilder satisfier using apt (default pbuilder is
aptitude) but apt can more or less do the same thing and we generally
prefer apt over aptitude in all our tooling:
- build a fake package which has the relationships of the source
represented onto a fake binary
- make sure multi-arch and general arch qualifiers are taking into
consideration correctly
- install that fake package (for apts too old to install a .deb,
install via dpkg then apt install to let apt recover from the now
broken dep tree)
- retry with x seconds of wait on failure to mitigate network fail

This should be plenty fast and plenty reliable with retrying.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: ubiquity update

[Harald Sitter]

meh... zsyncing -.-

On Thu, Oct 1, 2015 at 9:43 AM, Jonathan Riddell  wrote:
>
> yes that's in
>
> Jonathan
>
>
> On Wed, Sep 30, 2015 at 11:17:11PM +0200, Harald Sitter wrote:
>> grml. is that with the patch from yesterday?
>>
>> On Wed, Sep 30, 2015 at 5:42 PM, Jonathan Riddell  wrote:
>> > harald's ubiquity patch has left it looking all good but if you
>> > manually resize the window it does remove the text of the current
>> > step, and the german text is still a bit cut off
>> >
>> > http://embra.edinburghlinux.co.uk/~jr/tmp/ubiquity.png
>> >
>> >
>> > Jonathan
>> >
>> > --
>> > kubuntu-devel mailing list
>> > kubuntu-devel@lists.ubuntu.com
>> > Modify settings or unsubscribe at: 
>> > https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>>
>> --
>> kubuntu-devel mailing list
>> kubuntu-devel@lists.ubuntu.com
>> Modify settings or unsubscribe at: 
>> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: ubiquity update

[Harald Sitter]

grml. is that with the patch from yesterday?

On Wed, Sep 30, 2015 at 5:42 PM, Jonathan Riddell  wrote:
> harald's ubiquity patch has left it looking all good but if you
> manually resize the window it does remove the text of the current
> step, and the german text is still a bit cut off
>
> http://embra.edinburghlinux.co.uk/~jr/tmp/ubiquity.png
>
>
> Jonathan
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: kubuntu-members @ kubuntuci

[Harald Sitter]

what's "will not let me build" mean exactly?

On Wed, Sep 30, 2015 at 5:28 AM, Scarlett Clark
 wrote:
> Hmm, not fixed for me, have a few that just need rebuild, network errors etc
> and it will not let me build.
> Scarlett
>
> On Tue, Sep 29, 2015 at 3:25 AM, Jonathan Riddell  wrote:
>>
>>
>> yay that fixed it thanks
>>
>> Jonathan
>>
>>
>> On Tue, Sep 29, 2015 at 01:19:18PM +0300, Tm_T wrote:
>> > Hi,
>> >
>> > can confirm I can login and seem to have rights, works as expected then.
>> >
>> > On 29 September 2015 at 10:12, Harald Sitter  wrote:
>> >
>> > did you tick the box?
>> >
>> > http://i.imgur.com/Cx1ag09.jpg
>> >
>> > On Mon, Sep 28, 2015 at 6:39 PM, Jonathan Riddell 
>> > wrote:
>> > >
>> > > Login works good but I don't seem to have build privilages
>> > >
>> > > Jonathan
>> > >
>> > >
>> > >
>> > > On Mon, Sep 28, 2015 at 01:41:25PM +0200, Harald Sitter wrote:
>> > >> yo,
>> > >>
>> > >> As of right now every kubuntu-member on launchpad can login at
>> > >> kci.pangea.pub to trigger/cancel/tag kubuntu ci jobs. This runs
>> > >> through launchpad openid login, so upon clicking on login you
>> > will be
>> > >> redirected to launchpad for credentials and granting permissions.
>> > >> Previous manually created accounts are no longer working and
>> > everyone
>> > >> who had one will need to login via the openid procedure.
>> > >>
>> > >> IMPORTANT: you *must* check that you are member of
>> > kubuntu-members
>> > >> (this will forward your membership information to jenkins). If
>> > you do
>> > >> not do this you will not have membership permissions and login
>> > will
>> > >> give you nothing :P
>> > >>
>> > >> If you forgot to tick the box you can simply logout and in again,
>> > >> which again goes to launchpad for authentication.
>> > >>
>> > >> Hope this helps with people forgetting their login data :P
>> > >>
>> > >> HS
>> > >>
>> > >> --
>> > >> kubuntu-devel mailing list
>> > >> kubuntu-devel@lists.ubuntu.com
>> > >> Modify settings or unsubscribe at:
>> > https://lists.ubuntu.com/mailman/
>> > listinfo/kubuntu-devel
>> > >
>> > > --
>> > > kubuntu-devel mailing list
>> > > kubuntu-devel@lists.ubuntu.com
>> > > Modify settings or unsubscribe at:
>> > https://lists.ubuntu.com/mailman/
>> > listinfo/kubuntu-devel
>> >
>> > On Mon, Sep 28, 2015 at 6:39 PM, Jonathan Riddell 
>> > wrote:
>> > >
>> > > Login works good but I don't seem to have build privilages
>> > >
>> > > Jonathan
>> > >
>> > >
>> > >
>> > > On Mon, Sep 28, 2015 at 01:41:25PM +0200, Harald Sitter wrote:
>> > >> yo,
>> > >>
>> > >> As of right now every kubuntu-member on launchpad can login at
>> > >> kci.pangea.pub to trigger/cancel/tag kubuntu ci jobs. This runs
>> > >> through launchpad openid login, so upon clicking on login you
>> > will be
>> > >> redirected to launchpad for credentials and granting permissions.
>> > >> Previous manually created accounts are no longer working and
>> > everyone
>> > >> who had one will need to login via the openid procedure.
>> > >>
>> > >> IMPORTANT: you *must* check that you are member of
>> > kubuntu-members
>> > >> (this will forward your membership information to jenkins). If
>> > you do
>> > >> not do this you will not have membership permissions and login
>> > will
>> > >> give you nothing :P
>> > >>
>> > >> If you forgot to tick the box you can simply logout and in again,
>> > >> which again goes to launchpad for authentication.
>> > >>
>> > >> Hope this helps with people forgettin

Re: kubuntu-members @ kubuntuci

[Harald Sitter]

did you tick the box?

http://i.imgur.com/Cx1ag09.jpg

On Mon, Sep 28, 2015 at 6:39 PM, Jonathan Riddell  wrote:
>
> Login works good but I don't seem to have build privilages
>
> Jonathan
>
>
>
> On Mon, Sep 28, 2015 at 01:41:25PM +0200, Harald Sitter wrote:
>> yo,
>>
>> As of right now every kubuntu-member on launchpad can login at
>> kci.pangea.pub to trigger/cancel/tag kubuntu ci jobs. This runs
>> through launchpad openid login, so upon clicking on login you will be
>> redirected to launchpad for credentials and granting permissions.
>> Previous manually created accounts are no longer working and everyone
>> who had one will need to login via the openid procedure.
>>
>> IMPORTANT: you *must* check that you are member of kubuntu-members
>> (this will forward your membership information to jenkins). If you do
>> not do this you will not have membership permissions and login will
>> give you nothing :P
>>
>> If you forgot to tick the box you can simply logout and in again,
>> which again goes to launchpad for authentication.
>>
>> Hope this helps with people forgetting their login data :P
>>
>> HS
>>
>> --
>> kubuntu-devel mailing list
>> kubuntu-devel@lists.ubuntu.com
>> Modify settings or unsubscribe at: 
>> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

On Mon, Sep 28, 2015 at 6:39 PM, Jonathan Riddell  wrote:
>
> Login works good but I don't seem to have build privilages
>
> Jonathan
>
>
>
> On Mon, Sep 28, 2015 at 01:41:25PM +0200, Harald Sitter wrote:
>> yo,
>>
>> As of right now every kubuntu-member on launchpad can login at
>> kci.pangea.pub to trigger/cancel/tag kubuntu ci jobs. This runs
>> through launchpad openid login, so upon clicking on login you will be
>> redirected to launchpad for credentials and granting permissions.
>> Previous manually created accounts are no longer working and everyone
>> who had one will need to login via the openid procedure.
>>
>> IMPORTANT: you *must* check that you are member of kubuntu-members
>> (this will forward your membership information to jenkins). If you do
>> not do this you will not have membership permissions and login will
>> give you nothing :P
>>
>> If you forgot to tick the box you can simply logout and in again,
>> which again goes to launchpad for authentication.
>>
>> Hope this helps with people forgetting their login data :P
>>
>> HS
>>
>> --
>> kubuntu-devel mailing list
>> kubuntu-devel@lists.ubuntu.com
>> Modify settings or unsubscribe at: 
>> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kubuntu-members @ kubuntuci

[Harald Sitter]

yo,

As of right now every kubuntu-member on launchpad can login at
kci.pangea.pub to trigger/cancel/tag kubuntu ci jobs. This runs
through launchpad openid login, so upon clicking on login you will be
redirected to launchpad for credentials and granting permissions.
Previous manually created accounts are no longer working and everyone
who had one will need to login via the openid procedure.

IMPORTANT: you *must* check that you are member of kubuntu-members
(this will forward your membership information to jenkins). If you do
not do this you will not have membership permissions and login will
give you nothing :P

If you forgot to tick the box you can simply logout and in again,
which again goes to launchpad for authentication.

Hope this helps with people forgetting their login data :P

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Wily upgrade issues

[Harald Sitter]

On Fri, Sep 25, 2015 at 3:27 PM, Philip Muskovac  wrote:
> On Friday 25 September 2015 09:29:18 Harald Sitter wrote:
>> On Thu, Sep 24, 2015 at 11:11 PM, Philip Muskovac  wrote:
>> > 2 things that were staring in my face after I did an upgrade test:
>> >
>> > - Application links in kickoff being broken
>> > https://kyofel.de/owncloud/index.php/s/fqzTshBuNo0uDrr Ok, we talked
>> > about this while we were packaging 15.07.80, but then everyone forgot
>> > about them. As the upstream position seems to be "we don't care" and d_ed
>> > said that it would be rather complicated to find something that matches
>> > all moved files, I'll see if I can figure out how to write some kconf
>> > update scripts to at least fix the links for the core applications.
>> see kdepim. in fact kdepim has update for all apps in 15.08.1 IIRC, so
>> only dolphin and ktp need fixing (technically everything that changed
>> name between apps1504 and apps1508 needs fixing as they all could be
>> favs).
>
> Interesting, but if you take another look at my screenshot, kontact is broken
> there, so whatever they ship doesn't quite work. But thanks for the hint

.1 wasn't entirely landed for the beta I heared yesterday, so that might be why

>>
>> > - 2 volume control widgets
>> > KMix is obsolete, right? If yes we probably want to remove it from the
>> > archive and make whatever ships the new widget break it so it gets
>> > removed on upgrades. Better ideas?
>>
>> removal-on-upgrade ought to be done via lp:update-manager I think
>
> True, that would be the correct place, thanks.
>
> Philip
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Wily upgrade issues

[Harald Sitter]

On Thu, Sep 24, 2015 at 11:11 PM, Philip Muskovac  wrote:
> 2 things that were staring in my face after I did an upgrade test:
>
> - Application links in kickoff being broken 
> https://kyofel.de/owncloud/index.php/s/fqzTshBuNo0uDrr
> Ok, we talked about this while we were packaging 15.07.80, but then everyone 
> forgot about them.
> As the upstream position seems to be "we don't care" and d_ed said that it 
> would be rather complicated to find something that matches all moved files, 
> I'll see if I can figure out how to write some kconf update scripts to at 
> least fix the links for the core applications.

see kdepim. in fact kdepim has update for all apps in 15.08.1 IIRC, so
only dolphin and ktp need fixing (technically everything that changed
name between apps1504 and apps1508 needs fixing as they all could be
favs).

> - 2 volume control widgets
> KMix is obsolete, right? If yes we probably want to remove it from the 
> archive and make whatever ships the new widget break it so it gets removed on 
> upgrades.
> Better ideas?

removal-on-upgrade ought to be done via lp:update-manager I think

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

libdebconf-kde 1.0.2

[Harald Sitter]

New maintenance release for libdebconf-kde, a Debian configuration
system UI frontend library.

http://download.kde.org/stable/libdebconf-kde/1.0.2/src/libdebconf-kde-1.0.2.tar.xz.mirrorlist

* Improving translations
* Only link qtwidgets publicly, rest are private link libraries
* Fix dependency lookup to cover all used targets

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

libqapt 3.0.1

[Harald Sitter]

New maintenance release for libqapt, a Qt wrapper library for Debian's
libaptpkg.

http://download.kde.org/stable/libqapt/3.0.1/src/libqapt-3.0.1.tar.xz.mirrorlist

* Improving translations
* Improved CMake dependency lookup
* Handle multiarch annotations correctly
* Support update phasing
* Expose site property on packages
* Cancel worker transactions upon dbus timeouts
* Prevent authentication errors from being considered successful transactions
* Improve heldstate handling by changing the heuristics for detection
* Print warnings on the terminal when we were asked to do a change we can't
* Improve gstreamer compiler flag use
* Add build support for libapt 1.1 (no new features used yet)
* Force correct encoding of typenames and origins [BUG: 339710]
* Improve progress update notifications [BUG: 330245]

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

natives with translation on kde infrastructure

[Harald Sitter]

Jon recently got the majority of our native packages moved to
git.kde.org which unfortunately means that building sources from them
is a bit tricky as we need to get translations somehow.

To get that resolved I wrote tiny wrapper tech around the plasma
release script releaseme [1] to reuse it's l10n lib to get
translations into the working directory.
It depends on rake (which depends on ruby). And having the kde: alias
defined for git.

This is automatically downloaded and run [2] when doing
dpkg-buildpackage -S inside a git clone of the relevant repositories.
Do note that this however mangles the CMakeLists.txt AND drops a po
directory along with a releaseme clone into the working directory. So
before running the buildpackage you want to commit all things and
afterwards run `git clean -fd` to get a clean clone again.
In particular DO NOT commit the po directory.

(random note: the temporary garbage created by the rake target is
blacklisted from being included in the source tarball created by
dpkg-source)

[1] 
https://quickgit.kde.org/?p=scratch%2Fsitter%2Fkubuntu-rake.git&a=blob&h=2f276ebad8e1de756103ece8d4dc9ef43c73a4b3&hb=bbc23071ecd2eb402950f87c7016b6fd28791ca5&f=Rakefile
[2] 
https://quickgit.kde.org/?p=kubuntu-debug-installer.git&a=blob&h=471838f66be850b30e064fc7e4258bb070db3510&hb=e73690dd12b389a3d1ce8377a714d44d0cbf33be&f=debian%2Frules

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

return of the symbols

[Harald Sitter]

Last wednesday I re-enabled symbol tracking in kubuntu ci. This means
that symbol additions are again picked up automatically and removals
will cause a red build.
To that end all frameworks should have up-to-date symbols with their
gcc4 optionals removed after Jonathan turned everything red on Friday
and didn't fix it since (yes, this is supposed to be public shaming).

If a build turns red and the CI logs say that "it appears symbols were
removed" that means the optional symbols we had to help with the gcc5
transition are gone. As everything to do with our kf5 stuff is long
since transitioned these should be removed as they are essentially
cruft.

Also as a general reminder: symbol tracking only happens on wily.

Also on a general note: I doubt I will get vivid to green again (read:
can't be bothered to) so I would recommend using unstable/stable
directly instead of daily or weekly since the latter two are
incredibly outdated what with not having had passing promotion for
months now.

Also: a lot of pieces of the kdepim stack had their ABI broken in git
master but upstream has yet to greenlight my sobumps. Until the
sobumps are in the pim builds will be broken.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

new pim stack (transition finally went through)

[Harald Sitter]

Heya

to make sure everyone knows a thing or two about our new mad pim stack
let me quickly outline things involved. Actually, let me outline it
quickly but it will still be a very long mail. sorz.

Firstly kdepim4 is gone from the archive as it can not be co-installed
with the new pim stack and the two stacks do not share data but
akonadi uses the same directories, so things could weirdly implode if
we were to allow mixing runtimes in any capacity.

# kde-sc 4 compatibility

## akonadi1 - locked at version 1.13
A compatibility source providing the library package
libakonadiprotocolinternals1 (along with libakonadi-dev) which is used
by kde4pimlibs to use akonadi.
Akonadi1 has an intentionally defunct runtime. It does not build any
runtime parts (i.e. akonadi-server) as these would conflict with the
new Akonadi which unfortunately enough has a different wire format
(i.e. the old akonadi lib cannot use the new runtime). This has the
unfortunate downside that software that expects a working
akonadi-server will not function correctly with our stack. While
unfortunate this isn't something we can do anything about. And worse
yet, due to how applications linked *all* kdepimlibs we do not know
which directly depend on akonadi technology as all of them link
against akonadi bu that doesn't mean they use it.

## kde4pimlibs - locked at version 4.14.10
A compability source providing the entire set of previous packages
from kdepimlibs. These libraries (except libakonadi-kde4) are expected
to work as before. The data they work on is not shared with the kf5
counter parts though so much like kwallet4 they are essentially a dead
end.

# new akonadi

New akonadi source is creating a new akonadi-server which is pretty
much featuring the same runtime lineup as we had previously (i.e.
forcefully wants mysql but can have other backends added because
akonadi does not allow auto-migration of backends so mysql must not be
lost ever).
This is the one and only akonadi-server we have now. It is compatible
with all new libs but not with the old ones. Also this will eventually
(nobody knows when) get replaced by an entirely new better designed
implementation of akonadi, nothing to worry about for now though.

# new libraries

- kdepimlibs

kdepimlibs is vastly reduced from what it was in kde4 as most things
were split out.

- akonadi-calendar
- akonadi-search
- kalarmcal
- kblog
- kcalcore
- kcalutils
- kcontacts
- kholidays
- kidentitymanagement
- syndication
- ktnef
- kpimtextedit
- kontactinterface
- kmime
- kmbox
- kmailtransport

Most of these were split from kdepimlibs

All of these new libraries should be packaged in accordance with
multiarch standards. They are mostly tiny one-library packages making
them vastly more manageable.

# new runtime

## kdepim-runtime
Not co-installable port of 4.x version of runtime assets. Along with
akonadi-server this forms the concerning runtime part of the
transition. In 4.x kdepimlibs would force kdepim-runtime into all
applications that linked against any one kdepimlibs library meaning we
simply do not know what actually might have required kdepim-runtime,
so it is possible that 4.x-using applications might have problems
after this transition since they can no longer find the assets they
require from kdepim-runtime.

## kdepim
Pretty much a straight port from the 4.x version with soversions
bumped. The applications knode and kjots are gone, along with the
mobile applications UIs.

# Future

- There are still a bunch of improvements to be made to kdepim*
  - kdepimlibs restructuring bin/akonadi* for better MA support
  - put akonadi2xml and knut resource into dev-tools package as they
are mostly useless
  - kdepim-runtime needs bdep on libkolab & libkolabxml
  - kdepim needs bdep on libkolab & libkolabxml
- Applications 15.12 will need at least a partial library transition
as libraries already broke ABI again
- akonadi will eventually get changed for a completely new code base
which likely will need a full transition again, although I hope the
kdepim team works out a soft-migration for that as to not break every
application that appears until then.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

ffmpeg transition

[Harald Sitter]

wily is moving from libav back to libffmpeg. library-wise we seem to
be sorted, but there are also runtime utils to be considered here.

to transit them libav-tools dependency/recommends/suggests needs
changing to ffmpeg and the runtime tool that is being called probably
needs to be changed to ffmpeg as well

rdeps:
- soundkonverter
- kphotoalbum
- kdenlive

I also seem to recall amarok and k3b using some runtime tools from
libav so perhaps have a look at those as well.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Review Request 125003: Use kdesu instead of pkexec

[Harald Sitter]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125003/#review84655
---

Ship it!


Ship It!

- Harald Sitter


On Aug. 31, 2015, 2:46 p.m., Aleix Pol Gonzalez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125003/
> ---
> 
> (Updated Aug. 31, 2015, 2:46 p.m.)
> 
> 
> Review request for Kubuntu, Muon Package Management Suite and Harald Sitter.
> 
> 
> Bugs: 351311
> http://bugs.kde.org/show_bug.cgi?id=351311
> 
> 
> Repository: muon
> 
> 
> Description
> ---
> 
> pkexec doesn't cut it on GUI applications, kdesu seems to work.
> 
> On kubuntu it should be using sudo instead of su.
> 
> 
> Diffs
> -
> 
>   README.PACKAGERS 28f1519 
>   libmuon/backends/ApplicationBackend/ApplicationNotifier.cpp bb56c35 
>   libmuon/backends/ApplicationBackend/CMakeLists.txt 4785e1f 
>   libmuonapt/CMakeLists.txt 1c8bae9 
>   libmuonapt/QAptActions.cpp 7b82f67 
> 
> Diff: https://git.reviewboard.kde.org/r/125003/diff/
> 
> 
> Testing
> ---
> 
> Builds, coudln't test further.
> 
> 
> Thanks,
> 
> Aleix Pol Gonzalez
> 
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Review Request 125003: Use kdesu instead of pkexec

[Harald Sitter]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125003/#review84652
---


With kdesu you need to either separate the actual calls with "--", or -c 
followed by a completely built argument string

e.g.
/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu -- /usr/bin/software-properties-kde 
--attach 23068678 --dont-update
OR
/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu -c 
"/usr/bin/software-properties-kde --attach 23068678 --dont-update"

any other argument list will result in kdesu parsing --attach and --dont-update 
as kdesu arguments.

Also argument spearation for --attach is broken.

I Opened issues for all of that


libmuonapt/QAptActions.cpp (line 392)
<https://git.reviewboard.kde.org/r/125003/#comment58585>

needs -- or -c for argument list



libmuonapt/QAptActions.cpp (line 395)
<https://git.reviewboard.kde.org/r/125003/#comment58584>

should be "--attach" << winid
i.e. winid as additional argument not concated onto --attach

currently this comes out as 

23529 execve("/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu", 
["/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu", 
"/usr/bin/software-properties-kde", "--attach23068678", "--dont-update"], [/* 
112 vars */] 



libmuonapt/QAptActions.cpp (line 506)
<https://git.reviewboard.kde.org/r/125003/#comment58586>

needs -- or -c for argument list


- Harald Sitter


On Aug. 31, 2015, 2:17 p.m., Aleix Pol Gonzalez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125003/
> -------
> 
> (Updated Aug. 31, 2015, 2:17 p.m.)
> 
> 
> Review request for Kubuntu, Muon Package Management Suite and Harald Sitter.
> 
> 
> Bugs: 351311
> http://bugs.kde.org/show_bug.cgi?id=351311
> 
> 
> Repository: muon
> 
> 
> Description
> ---
> 
> pkexec doesn't cut it on GUI applications, kdesu seems to work.
> 
> On kubuntu it should be using sudo instead of su.
> 
> 
> Diffs
> -
> 
>   README.PACKAGERS 28f1519 
>   libmuon/backends/ApplicationBackend/ApplicationNotifier.cpp bb56c35 
>   libmuon/backends/ApplicationBackend/CMakeLists.txt 4785e1f 
>   libmuonapt/CMakeLists.txt 1c8bae9 
>   libmuonapt/QAptActions.cpp 7b82f67 
> 
> Diff: https://git.reviewboard.kde.org/r/125003/diff/
> 
> 
> Testing
> ---
> 
> Builds, coudln't test further.
> 
> 
> Thanks,
> 
> Aleix Pol Gonzalez
> 
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: marble autotpkgtest regressions

[Harald Sitter]

   Uploading marble_15.08.0-0ubuntu4.dsc: done.

should fix the tests
there are some porting problems though... looking into those now

On Fri, Aug 28, 2015 at 7:49 AM, Harald Sitter  wrote:
> holding up transition out of proposed:
>
> http://autopkgtest.ubuntu.com/packages/m/marble/wily/amd64/
> http://autopkgtest.ubuntu.com/packages/m/marble/wily/i386/

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kdepimlibs transition

[Harald Sitter]

As it turns out the kdepim crew didn't assess transition implications
sufficiently rendering us in a state where there's a whole bunch of
third party apps that use kdepimlibs.

Since those apps are still using kde4libs we need a compatibility
kdepimlibs that is not coming from upstream :(

Consequently there now is a proposed kde4pimlibs [1]. It would be
great if someone could review and upload and get an archive admin to
let the stuff through NEW.

To go along with this and to facilitate pim transitioning out of the
proposed pocket there also is a notes page on the transition heap [2].
For the most part we are stuck on unblocking kdepimlibs (kf5) which
should be entirely possible once kde4pimlibs is in proposed (along
with rebuilds of 3 rdeps).

In theory with kde4pimlibs and rebuild-needing-rdeps in proposed the
entire stack should then be able to transition. If not beating on the
remaining issues until the stack transits is the goal here.

There are however further adjustments to be made later. Firstly
kde4pimlibs probably needs to stop injecting kdepim-runtime rdeps (how
ever it does that to begin with) and then all rdeps need rebuilding to
get rid of runtime. Effectively the compatibility recommended by
upstream is to have link compat but runtime compat will be extremely
limited to not existent. Nothing to be done about this now
unfortunately.

kdepimlibs and kde4pimlibs should be entirely co-installable if
problems should get encountered please raise them upstream directly as
this needs addressing asap.

[1] 
http://anonscm.debian.org/cgit/pkg-kde/krap/kde4pimlibs.git/log/?h=kubuntu_wily_archive
[2] https://notes.kde.org/p/kubuntu-kdepim-15.08-transition

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

marble autotpkgtest regressions

[Harald Sitter]

holding up transition out of proposed:

http://autopkgtest.ubuntu.com/packages/m/marble/wily/amd64/
http://autopkgtest.ubuntu.com/packages/m/marble/wily/i386/

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

bluedevil CI

[Harald Sitter]

random FYI: bluedevil is now being CI'd on wily again (disabled for
vivid because no bluez5)

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kdecoration v5 transition someone plz get rdeps rebuilt

[Harald Sitter]

as it turns out we somehow cheated our away around a gcc5 transition
for kdecoration. I have now merged the debian change and uploaded this
bugger:

https://launchpad.net/ubuntu/+source/kdecoration/4:5.3.95-0ubuntu2

I am too stupid to get rebuilds of the rdeps using the new version
though. I'd appreciate it if someone could have a look. The packages
are accepted but for some reason they still aren't built against...
It might be that we have to wait for
https://launchpad.net/ubuntu/+source/kwin/4:5.3.95-0ubuntu5 as I think
kwin is an rdep of oxygen and breeze.

rdeps:
- kwin
- oxygen
- breeze

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kubuntu ci patches series ignore

[Harald Sitter]

as you hopefully all know kubuntu ci checks if a patch is actually
listed in series. this now also has an override mechanic [1] since we
need it for kdepim

debian/patches/ignore

exactly the same format as the series itself. all patches listed in
ignore are not being complained about

more information
https://community.kde.org/Kubuntu/CI/PatchesSeriesIgnore

[1] 
http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/commit/?id=ec7b353ca1890a5cc22951b27070b7d178156cf0

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

pam-kwallet5 adoption

[Harald Sitter]

salut

wily is getting pam-kwallet5 enabled (alongside pam-kwallet4 as seen
previously) currently stuff is waiting a bit in proposed but
eventually the following stuff will change with the intended end
result that users get their wallet unlocked by default. this will
apply moving forward for all new users and all existing users as long
as:

a) their main wallet is called kdewallet (can be checked via
kwalletmanager and changed through export&import)
b) the wallet's password is equal to the account password (also
changable via kwalletmanager)

Since systems are presently running kwalletd and kwalletd5 for legacy
kwallet4 apps and kwallet5 apps respectively both pams are used by
default and this is going to stay this way until kwalletd(4) is
retired from the archive as otherwise we cannot guarantee that the
user doesn't encounter a kwallet4 using application.

## changes

sddm (both in pam config):
https://launchpad.net/ubuntu/+source/sddm/0.11.0-0ubuntu11

lightdm pending (both in pam configs):
https://code.launchpad.net/~apachelogger/lightdm/lightdm-pam-kwallet5/+merge/268899

seed (recommends both):
http://bazaar.launchpad.net/~kubuntu-dev/ubuntu-seeds/kubuntu.wily/revision/1320

kwallet-kf5 (additional patch to prevent bad UX from migration wizard;
upstream 5.14):
https://launchpad.net/ubuntu/+source/kwallet-kf5/5.13.0-0ubuntu2

kubuntu-meta needs updating to adopt the seed change, alas, it doesn't
like me so I can't.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

random things that need doing

[Harald Sitter]

holas

I am out a bit earlier today so I'll just dump a list of things that
could use some work if someone is interested:

- pam-kwallet5 needs integration into sddm and lightdm pam profiles
(simply hold on to pam-kwallet4 for what to change). I tried it with a
pam-auth-update in the kubuntu_unstable_pam-auth-update branch but
that adds pam-kwallet to deep in the profile stack making it used in
TTY, SSH and polkit sessions as well breaking things severely

- fix for https://bugs.kde.org/show_bug.cgi?id=351056 needs testing
and possibly cherrypicking into packaging until frameworks 5.14 (also
maybe inform other packagers that they might want this when using
pam-kwallet5)

- kdepim(-runtime) need libkolab and libkolabxml as build deps and
they in turn need update to new releases. not sure we should CI those.
probably not. also in debian they are maintained by the kolab team
IIRC

- oxygen (and I think also breeze) has it's configuration helper
packaged along the style which is meh and should be split into a
standalone package as the config works for style and window decoration
alike

- discover appears to have a notification spam bug again which needs
investigating (i.e. notifies of updates constantly while apt-get
update is running)

- discover also has broken software-properties support
https://bugs.kde.org/show_bug.cgi?id=351311

- CI needs greeing up, I mostly got wily stable sorted if we get wily
green ASAP that would be good so we can land apps15.08.1 and
plasma5.4.1 with green CI packaging again (vivid CI can mostly be
ignored as I can mass retry unstable builds once wily is green)

- unless Riddell did it already all applications repos need their
watch file changed to look at the right stable and *also* at the right
unstable path. best write a script to fix this

(random note: kwin CI is temporarily switched to a testing branch for
upstream, failure there can be ignored)

also feel free to put this on the trello board, ETOOLAZY :P

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

[Merge] lp:~apachelogger/kubuntu-packaging/pykde4-no-kdepimlibs into lp:~kubuntu-packagers/kubuntu-packaging/pykde4

[Harald Sitter]

Harald Sitter has proposed merging 
lp:~apachelogger/kubuntu-packaging/pykde4-no-kdepimlibs into 
lp:~kubuntu-packagers/kubuntu-packaging/pykde4.

Requested reviews:
  Scott Kitterman (kitterman)

For more details, see:
https://code.launchpad.net/~apachelogger/kubuntu-packaging/pykde4-no-kdepimlibs/+merge/268193
-- 
Your team Kubuntu Packagers is subscribed to branch 
lp:~kubuntu-packagers/kubuntu-packaging/pykde4.
=== modified file 'debian/changelog'
--- debian/changelog	2015-08-17 08:21:24 +
+++ debian/changelog	2015-08-17 08:24:43 +
@@ -1,3 +1,12 @@
+pykde4 (4:4.14.2-0ubuntu4) UNRELEASED; urgency=medium
+
+  * Build without kdepimlibs5-dev present to facilitate the kdepim frameworks
+5 transition. kdepimlibs as of KDE Applications 15.08 will be frameworks
+based and not co-installable with the old libs (due to data files).
+Disable the pimlibs in pykde4.
+
+ -- Harald Sitter   Mon, 17 Aug 2015 10:21:55 +0200
+
 pykde4 (4:4.14.2-0ubuntu3) wily; urgency=medium
 
   * Unversioned boost build dependency

=== modified file 'debian/control'
--- debian/control	2015-08-17 08:21:24 +
+++ debian/control	2015-08-17 08:24:43 +
@@ -5,7 +5,7 @@
 XSBC-Original-Maintainer: Debian Qt/KDE Maintainers 
 Build-Depends: 
  debhelper (>= 7.3), cmake, pkg-kde-tools (>= 0.12),
- kdelibs5-dev (>= 4:4.14.2), kdepimlibs5-dev (>= 4:4.14.2),
+ kdelibs5-dev (>= 4:4.14.2),
  libphonon-dev (>= 4:4.6.0really4.4.4), libsoprano-dev (>= 2.7.0),
  libqt4-dev (>= 4:4.7.1), libqt4-opengl-dev (>= 4:4.7.1), libqtwebkit-dev,
  libboost-dev,

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: [Merge request] Fix okteta FTBFS

[Harald Sitter]

On Sun, Aug 16, 2015 at 2:29 AM, Clive Johnston  wrote:
> Hi list,
>
> This is my first email so I'm not sure on the structure, please tell me know
> if I get it wrong.
>
> Please review the following links which are patches for the package okteta -
> Kubuntu KDE Applications 15.07.90 (wily)
> [kubuntu-ppa/staging-kdeapplications]

Seems they have been applied on friday already, and Philip uploaded
the package yesterday, so I suppose this is resolved.

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

symbols on new pim libraries WAS: Re: away until monday afternoon

[Harald Sitter]

On Fri, Aug 14, 2015 at 11:30 AM, Jonathan Riddell  wrote:
> I'm away until monday afternoon
>
> Please keep fixing those applications packages and keep reponsding to
> doko's pings about stuff that needs fixed for gcc transition
> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_15.07.90_wily.html

On a related note. Since there was confusion about this earlier.

All packages listed in green (the ones I handled) here:
https://notes.kde.org/p/kubuntu-apps-15.08
have either no symbols file or a stub file. So any missing symbols are
simply because the stubs were generated on GCC4 and can be safely
removed.

And finally because it came up yesterday: to conveniently strip
MISSING lines from all symbols files in a package you can use
symbolstrip from [1] and to generate a new symbols file from scratch
you can use symbolize (heavily automated thing ontop of gensymbols).

symbolstrip is simply called in the dir containing debian/.

symbolize has --help and is usually called like so (it infers package
name from the lib name):
> symbolize -v 15.07.90 -i 
> tmp/usr/lib/x86_64-linux-gnu/libKF5IdentityManagement.so.5

If someone feels less lazy then me feel free to put them in a repo somewhere.

[1] http://people.ubuntu.com/~apachelogger/tmp/symbol/

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Missing KDEPlasma-addons

[Harald Sitter]

http://packages.ubuntu.com/source/wily/kdeplasma-addons

On Fri, Aug 14, 2015 at 1:52 AM, Valorie Zimmerman
 wrote:
> I was told in #plasma that some of the widgets I've been missing are
> in kdeplasma-addons.
>
> However:
>
> [23:04]  !info kdeplasma-addons
> [23:04]  Package kdeplasma-addons does not exist in wily
> [23:04]  !info kdeplasma-addons vivid
> [23:04]  Package kdeplasma-addons does not exist in vivid
>
> Yet we have kdeplasma-addons-data and kdeplasma-addons-dbg available.
> Is this an oversight?
>
> Debian has a meta-package: 
> https://packages.debian.org/unstable/kdeplasma-addons
>
> Riddell told me to write here rather than file a bug.
>
> Valorie
>
> --
> http://about.me/valoriez
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kubuntu-repo-merge no-create switch

[Harald Sitter]

repo-merge now supports a new switch --no-create which allows us to
disable the automatic branch creation upon merging. this use case
appears when merging unstable->stable for CI as stable is not
applicable to everything (neither is unstable).
e.g. plasma repos partially have unstable but no stable or stable but
no unstable.

https://github.com/apachelogger/kubuntu-repo-merge/commit/da5f657dc4755ca41ca1b42c0a355aace393c5a5

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: new applications in pkg-kde git today

[Harald Sitter]

dolphin doesn't appear pushed

On Wed, Aug 12, 2015 at 7:51 PM, Jonathan Riddell  wrote:
> picmi - clivejo
> kross-interpeters - jriddell
> dolphin-plugins - jriddell
> baloo-widgets - jriddell
> dolphin - jriddell
>
> I've also got marble compiling away in a pbuilder here
>
> There's a bunch of kdepim bits still to do but to compile those needs
> the existing kdepim binaries and I don't know if those exist currently
> or if we need to compile them ourselves.
>
> Jonathan
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

irc notification for repos hosted on git.kde

[Harald Sitter]

since we have (all?) our actual applications on git.kde for a while, I
have now enabled IRC commit notifications going to #kubuntu-devel for
all relevant repos. should it get too spammy, which I doubt as only
muon sees regular changes, please get in touch with me so we can
figure out a solution.

repository=kubuntu-debug-installer|kubuntu-docs|kubuntu-driver-kcm|kubuntu-notification-helper|libkubuntu|libqapt|muon

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

CI branch reminder

[Harald Sitter]

Please remember that when you add or port something to qt5/kf5 you
must create a kubuntu_unstable (and kubuntu_stable where applicable)
branch or tell me about it. Otherwise we'll not CI it.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: [Merge request] Patchset for KDE Frameworks 5.13

[Harald Sitter]

all imported and uploaded to staging ppa

thanks

On Mon, Aug 10, 2015 at 9:54 AM, José Manuel Santamaría
 wrote:
> Hi,
>
> I have been working this weekend on a patchset to improve the status of KDE
> Frameworks 5.13, it's temporarily available here:
> http://gpul.grupos.udc.es/kubuntu_patches/kdeframeworks-5.13.0/
>
> Cheers.
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: [Merge request] Fix qt-gstreamer FTBFS (with and without GCC 5)

[Harald Sitter]

ahoy

On Sun, Aug 9, 2015 at 7:15 PM, José Manuel Santamaría
 wrote:
> currently qt-gstreamer is FTBFS'ing in wily for various reasons, so I have
> fixed it with this set of patches:
> http://gpul.grupos.udc.es/kubuntu_patches/misc/qt-gstreamer/

I have this staged in a branch, waiting for doko to tell me it's ok to
upload and Riddell to discuss how to handle the repo since it is a
source copy repo which we don't like :/

FWIW, I made commit 3 and 4 one commit. git rebase -i $hash is your
friend for squashing commits.

> P.S. I have sent the find_gstconfig_properly.diff to the upstream's mailing 
> list.

Can't find it :'<
Please note for future patches that we require patches to be dep3, and
(in theory anyway) to be approved by upstream or at least someone who
understands the code before it gets added.

cheers
HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: kgamma -> kgamma5

[Harald Sitter]

On Fri, Aug 7, 2015 at 5:20 PM, Jonathan Riddell  wrote:
> ssh in and mv on the server
>
> is that the wrong way to do it?

I really think in this instance it should have been a copy. They are
not the same thing anymore. There's a new source, so there should be a
new repo IMO.

At any rate. when you *move* you need to symlink the old location to
the new location as well, otherwise people are going to complain about
broken git remotes.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: [Merge request] Fix oxygen-fonts FTBFS because of failing qmake -query

[Harald Sitter]

applied. thanks.

On Thu, Aug 6, 2015 at 5:10 PM, José Manuel Santamaría
 wrote:
> Hi,
>
> oxygen-fonts is currently failing to build, so with Harald's help I have fixed
> it, the patch is temporarily available here:
> http://gpul.grupos.udc.es/kubuntu_patches/misc/oxygen-fonts/
>
> and also attached to this mail.
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: git moves

[Harald Sitter]

On Thu, Aug 6, 2015 at 12:54 AM, Maximiliano Curia
 wrote:
>> WRT kgamma, I don't see why we should have two of them.
>
> We don't need two, but we already have the kde4 version that is bigger than
> the one released in plasma5.

I vote for an epoch, so we use an epoch for something reasonable for once >.<

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

CI branch merges and random information updates

[Harald Sitter]

ahoy ahoy

random things of interest:

# apps
all applications repos that had a kubuntu_unstable branch now had
their _unstable merged into _stable. i.e. stable is now tracking the
upcoming Applications/15.08.
you *must not* merge stable into a branch from which you want to
release a 15.04 release.

# plasma
plasma 5.4 tagging is supposed to happen tomorrow. shortly after that
kubuntu_stable of all plasma repos will get kubuntu_unstable merged.
i.e. same thing: stable is going to track Plasma/5.4 soon

# deprecations
breeze-qt4 and oxygen-qt4 are now gone entirely from CI as they were
folded into the breeze and oxygen packaging respectively

# symbols reminder
please do not twiddle symbol files in release branches (.e.g
kubuntu_wily_archive). if a symbol file is not uptodate then this is
nothing more than a symptom of a deeper problem and I'd appreciate
putting the time and effort towards solving the underlying problem
rather than apply temporary fixes that confuse the CI

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

baloo and kfilemetadata unstable now in frameworks

[Harald Sitter]

plasma/kfilemetadata -> frameworks/kfilemetadata
plasma/baloo -> frameworks/baloo

unstable branch was removed from the plasma repositories
stable branch was removed from the frameworks repositories

KCI should switch the builds accordingly whenever it decides to build them again

plasma initial upload should no longer attempt to use any of the two.
frameworks OTOH should.

unstable branch should be good to go as per integration in plasma,
soversions might be off (<5) that's not really a problem though as I
think I tracked ABI breakage from stable to unstable anyway.

I also adjusted the control vcs/homepage and watch file accordingly

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

kde applications 15.08 - kf5 ports

[Harald Sitter]

any volunteers who would want to port the packaging of new kf5 apps
due for release with apps 15.08?

if so grab a repo from git.debian.org and port away. list of minimal changes:
- redo build-depends
http://build.kde.org/userContent/dependency-metadata.tar.xz helps
with figuring out deps. do not that debhelper, cmake, pkg-kde-tools
are a minimum requirement
- in debian/rules exchange the /2/ for a /3/ in the include path at the top
- check descriptions and depends in control. cleanup and remove kde4
mentioning etc.
- push changes into kubuntu_unstable branch
- tell me

new stuff that needs porting:
- kdebugsettings
- dolphin
- baloo-widgets
- kross-interpreters
- picmi
- kio-extras (this actually needs copying from plasma and have its
unstable branch in plasma deleted)

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Fwd: Package conflict

[Harald Sitter]

expunged

On Wed, Jul 15, 2015 at 2:00 PM, Jonathan Riddell  wrote:
> also deleted oxygen-qt4 kubuntu_unstable branch now
>
> Jonathan
>
>
> On 15 July 2015 at 08:55, Harald Sitter  wrote:
>> FTR there is a handy script for that ^^
>> http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/tree/kci/expunge.rb
>>
>> going to run it shortly
>>
>> On Tue, Jul 14, 2015 at 5:42 PM, Jonathan Riddell  wrote:
>>>
>>> I'm not sure, a question for Harald that one.
>>>
>>> Thanks for testing.
>>>
>>> Jonathan
>>>
>>>
>>> On Tue, Jul 14, 2015 at 11:41:49AM -0400, Joseph Yasi wrote:
>>>> Will deleting the branch clear out the packages from
>>>> ppa:kubuntu-ci/{un,}stable or does that need manual intervention?
>>>>
>>>> On Tue, Jul 14, 2015 at 11:28 AM, Jonathan Riddell  
>>>> wrote:
>>>> >
>>>> > I've removed breeze-qt4 from wily now so only breeze will make 
>>>> > kde-style-breeze-qt4.
>>>> >
>>>> > I've also deleted the kubuntu_unstable branch from the git repository.

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Fwd: Package conflict

[Harald Sitter]

FTR there is a handy script for that ^^
http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/tree/kci/expunge.rb

going to run it shortly

On Tue, Jul 14, 2015 at 5:42 PM, Jonathan Riddell  wrote:
>
> I'm not sure, a question for Harald that one.
>
> Thanks for testing.
>
> Jonathan
>
>
> On Tue, Jul 14, 2015 at 11:41:49AM -0400, Joseph Yasi wrote:
>> Will deleting the branch clear out the packages from
>> ppa:kubuntu-ci/{un,}stable or does that need manual intervention?
>>
>> On Tue, Jul 14, 2015 at 11:28 AM, Jonathan Riddell  wrote:
>> >
>> > I've removed breeze-qt4 from wily now so only breeze will make 
>> > kde-style-breeze-qt4.
>> >
>> > I've also deleted the kubuntu_unstable branch from the git repository.

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Fwd: Package conflict

[Harald Sitter]

forwarding to development mailing list.
Jonathan I think you merged that? could it be that you forgot to
delete the kubuntu_unstable branch from the now deprecated breeze-qt4
repo?

-- Forwarded message --
From: Joseph Yasi 
Date: Mon, Jul 13, 2015 at 5:06 PM
Subject: Package conflict
To: Harald Sitter 


The breeze source package and breeze-qt4 source package are both
providing kde-style-breeze-qt4. The breeze metapackage also has a
binary:Version dependency on kde-style-breeze-qt4 which causes the
dependency tree to break whenever breeze-qt4 is updated. Is breeze-qt4
supposed to be a separate package or is this a redundancy? If so, can
the kde-style-breeze-qt4 package be dropped from breeze and the version
dependency fixed?

Thanks,
Joe

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

debian merging disabled

[Harald Sitter]

as apparently people don't give a flip about resolving merge conflicts
with debian, I am disabling automatic merging of debian's master
branch again. i.e. if you want to merge with debian you can do it by
hand moving forward.
http://i.imgur.com/JQ5G11i.jpg

when I enabled this feature I was very clear about me not wanting to
be the person to keep this crap going single handedly. lo and behold I
ended up doing it anyway because the broken merges are interfering
with my work...

#pissedoff

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

akademy registration

[Harald Sitter]

[13:05] * seaLne pokes people coming to akademy to register
https://akademy.kde.org/2015/register

kindly remember to register if you plan to attend (which you should).
best check right now in case you forgot.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: CI daily trigger change

[Harald Sitter]

starting tomorrow back to 0 UTC

On Thu, Jun 11, 2015 at 4:05 AM, Harald Sitter  wrote:
> moved to 3 UTC now. because why not.
>
> On Wed, Jun 3, 2015 at 7:44 PM, Harald Sitter  wrote:
>> aloha
>>
>> since I am currently at the US west coast I switched KCI dailies to
>> trigger at 7 UTC rather than 0 UTC so they don't build while I am
>> trying to play pin the tail on the donkey CI-style.
>>
>> HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Kubuntu Membership Application Meeting - Doodle Poll

[Harald Sitter]

#councilmemberping

it seems the doodle is missing times for
philip
rohan
scott

if you don't have time at least mark yourself unavailable please


On Sun, Jun 14, 2015 at 12:16 PM, Matthias Klumpp  wrote:
> Hello everyone :-)
> I am pursuing my Kubuntu membership[1], and one of the
> last missing steps in the application process is the IRC interview.
> In order to find a date for it, I created a Doodle poll. Doodle says
> it will be adjusted for timezones, hopefully that's true ;-)
> (otherwise, my timezone is CEST)
>  => http://doodle.com/erwzrscse5hxedkr
>
> I'm still a bit low on testimonials, but I wrote to some people
> already, and hopefully they'll find the time to write something until
> the meeting.
>
> Kind regards,
> Matthias Klumpp
>
> [1]: https://wiki.ubuntu.com/MatthiasKlumpp and
> https://wiki.ubuntu.com/MatthiasKlumpp/KubuntuMembershipApplication
>
> --
> Debian Developer | Freedesktop-Developer
> I welcome VSRE emails. See http://vsre.info/
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: [kubuntu-devel] [Merge request] [kf 5.11 for wily part 3] Patches needed to update

[Harald Sitter]

works in wily, not vivid though

On Sun, Jun 14, 2015 at 10:57 PM, José Manuel Santamaría Lema
 wrote:
> Jonathan Riddell 
>> not applied kio as the not-installed stuff doesn't like wildcards,
>
> Actually, I think it does, see the history of the kubuntu_wily_archive and
> ctrl+f "wildcads". That points you to this commit:
> http://anonscm.debian.org/cgit/pkg-kde/pkg-kde-tools.git/commit/?h=kubuntu_wily_archive&id=0b560297f7b8167758eb399f318eb98bb013df86
> which apparently is already available in wily.
>
> At least it worked on siduction's fork of pkg-kde-tools (right now based on 
> the
> experimental branch)
>
>> also not
>> applied kross as I think it's better to list the plugins explicitly.
>
> Fair enough.
>
>> The
>> reset are in kubuntu_unstable already
>
> Ok, thanks.
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

automated qml dep injection

[Harald Sitter]

since I keep getting asked the same question over and over again

here is why automated qml dep injections a la
Depends: ${qml:Depends}
is not very practical and in fact not something I pursue

1. qml module lookup rules are somewhat flexible and can be modified
at runtime such that lookup at buildtime often goes wrong
2. qml modules may be injected at runtime into the binary such that
lookup becomes entirely impossible as they are essentially modules
internal to the binary
3. qml modules are runtime deps and as such have 0 use in the build
environment and prolong the build entirely needlessly
4. the actual algorithm for finding a module is pretty complicated (in
particular also with multiarch in the picture)

probably I forgot something, but those are the major things

all of this put together makes it IMO pointless to go down the road of
autodetection. instead a re-active QA approach a la autopkgtest is
much more reasonable and is what we get through KCI these days.

HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Fwd: PSA: KDE Telepathy master now must have new plugin installed

[Harald Sitter]

-- Forwarded message --
From: Martin Klapetek 
Date: Wed, Jun 10, 2015 at 3:08 PM
Subject: PSA: KDE Telepathy master now must have new plugin installed
To: KDE Telepathy ,
kde-distro-packag...@kde.org, kdelibs 


Hello,

to all KDE Telepathy users compiling from master - with today's changes
you must install new additional Telepathy plugin in order for KDE Telepathy
to work at all. This plugin is currently located at github[1] and will hopefully
move soon somewhere upstream at freedesktop.org.

This is a runtime-only dependency and it's a must have. KDE Telepathy will not
work without it at all. I'll be adding it to kdesrc-build too. It requires
libmission-control-plugins-dev (or equivalent), libsignon-glib[-dev] and
libaccounts-glib[-dev].

For packagers, there is a find-package call in ktp-common-internals marked
as RUNTIME. There will be a release prior to KDE Applications 15.08 release,
but if you're providing nightly builds, you must include this new package,
ideally mark it as a hard dependency of ktp-common-internals.

One more note - if you're building Ubuntu's signon-ui by hand, it
tries to install
some files to /etc. These files must be present in /etc and not in any
other folder
otherwise Google authentication will not work; apparently this is a
signon-ui limitation
which I'll be looking into at some point.

[1] - https://github.com/mck182/telepathy-accounts-signon

Cheers
--
Martin Klapetek | KDE Developer

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Giving back to the KDE Community

[Harald Sitter]

On Thu, Jun 11, 2015 at 11:36 AM, Vishesh Handa  wrote:
> Harold.

s/o/a/ :'<

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: CI daily trigger change

[Harald Sitter]

moved to 3 UTC now. because why not.

On Wed, Jun 3, 2015 at 7:44 PM, Harald Sitter  wrote:
> aloha
>
> since I am currently at the US west coast I switched KCI dailies to
> trigger at 7 UTC rather than 0 UTC so they don't build while I am
> trying to play pin the tail on the donkey CI-style.
>
> HS

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Re: Kubuntu PPA tidy

[Harald Sitter]

+1

On Mon, Jun 8, 2015 at 5:58 PM, Jonathan Riddell  wrote:
> I'd like to tidy the PPAs as they're getting messy
>
> I proposed to delete:
> Kubuntu Next [obsolete]
> Kubuntu Next Backports [obsolete]
> Kubuntu Next Stage 1 (DON'T USE) [needs a better name]
> Kubuntu Next Stage 2 (DON'T USE) [needs a better name]
> Kubuntu Next Stage 0 (DON'T USE) [needs a better name]
> Kubuntu Package Staging (DON'T USE) [needs a better name]
> Kubuntu 14.10 - Bluez 5 Backports [obsolete?]
> Kubuntu 14.10 - Qt 5.4 backports [obsolete?]
>
> I propose to keep:
> Kubuntu Backports
> Kubuntu Beta Backports
> Kubuntu Experimental
> Kubuntu Updates
>
> I propose to create:
> -Kubuntu Stage Frameworks-
> -Kubuntu Stage Plasma
> -Kubuntu Stage Apps
> -Kubuntu Stage Misc
>
> these would replace the deleted stage PPAs but with nicer names.  I'd
> ask wgrant to bump them up to 10GB and make sure the old ones are
> unused before deleting them.
>
> Thoughts?
>
> Jonathan
>
> --
> kubuntu-devel mailing list
> kubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel