On 13/01/18 18:22, Pino Toscano wrote:
> Dear release team,
>
> On domenica 31 dicembre 2017 14:24:20 CET Pino Toscano wrote:
>> On domenica 31 dicembre 2017 14:03:56 CET Sandro Knauß wrote:
>>> Hey,
>>>
>>> I added the release team list, cause they may help explaining interpret the
>>> britney o
Dear release team,
On domenica 31 dicembre 2017 14:24:20 CET Pino Toscano wrote:
> On domenica 31 dicembre 2017 14:03:56 CET Sandro Knauß wrote:
> > Hey,
> >
> > I added the release team list, cause they may help explaining interpret the
> > britney output.
> > And help to find the right buttons
Hey,
> > my thought was to use experimental to prepare 17.12 and also use a debian/
> > experimental branch in git to not interfere or do you need experimental to
> > prepare something too?
>
> I'm still doing changes (see my other email), so I'd really prefer to
> not deal with pending changes m
On domenica 31 dicembre 2017 14:12:19 CET Sandro Knauß wrote:
> Hey,
>
> > I'd kindly ask you to hold that until:
> > a) KDEPIM 17.08.3 migrates to testing
> > b) I sort out the coinstallation issues with kdepim4
>
> my thought was to use experimental to prepare 17.12 and also use a debian/
> exp
On domenica 31 dicembre 2017 14:03:56 CET Sandro Knauß wrote:
> Hey,
>
> I added the release team list, cause they may help explaining interpret the
> britney output.
> And help to find the right buttons to push, to get kdepim migrating to
> testing.
>
> > > I tried to understand, why kdepim ha
Hey,
> I'd kindly ask you to hold that until:
> a) KDEPIM 17.08.3 migrates to testing
> b) I sort out the coinstallation issues with kdepim4
my thought was to use experimental to prepare 17.12 and also use a debian/
experimental branch in git to not interfere or do you need experimental to
prepa
Hey,
I added the release team list, cause they may help explaining interpret the
britney output.
And help to find the right buttons to push, to get kdepim migrating to testing.
> > I tried to understand, why kdepim hasn't moved to testing, but I don't
> > understand the britney output completely
On sabato 30 dicembre 2017 19:49:13 CET Sandro Knauß wrote:
> Hey,
>
> I tried to understand, why kdepim hasn't moved to testing, but I don't
> understand the britney output completely.
I don't either, but let's see.
> For me it looks that we missed the removals for armhf. Only armhf have
> conf
Hey,
I tried to understand, why kdepim hasn't moved to testing, but I don't
understand the britney output completely.
For me it looks that we missed the removals for armhf. Only armhf have
conflicting packages like:
trying: kdepim-addons
skipped: kdepim-addon
Hey,
> Yes, so far there are no blocking issues on our side, so I'd wait for
> the stack to migrate, and then we can do eventually more uploads.
> Of course, feel free to add your changes to git in the meanwhile
> (pushing them, heh).
That's why I didn't want to dig into it, because I wanted to a
On 27 December 2017 at 11:20, Pino Toscano wrote:
> In data mercoledì 27 dicembre 2017 15:04:50 CET, Sandro Knauß ha scritto:
>> now we got some issues for the new kdepim 17.08 stack. What is the best way
>> to
>> go on? fix them "as fast as possible" or better wait till it migrates to
>> testing
In data mercoledì 27 dicembre 2017 15:04:50 CET, Sandro Knauß ha scritto:
> now we got some issues for the new kdepim 17.08 stack. What is the best way
> to
> go on? fix them "as fast as possible" or better wait till it migrates to
> testing? I'm thinking, if it may break the tessting migration,
Hey,
now we got some issues for the new kdepim 17.08 stack. What is the best way to
go on? fix them "as fast as possible" or better wait till it migrates to
testing? I'm thinking, if it may break the tessting migration, if we upload
here a new kdepim-runtime here a new whatsoever...
#885111 kd
Hey,
now most of kdepim 17.08.3 was successfully built now.
But now I triggered a bug of dak and now part of kdepim will need to through
NEW again.
If you have any good ideas or anything how we can fix that form out side...
Otherwise
kdepim will be broken in sid till ftp-masters have the time t
Hey,
> > * comaptlevel to 10 (11 is not suitable for ubuntu at the moment and me
> > personally see no big gain in bumping to 11 for kdepim)
>
> We still use compat 9 everywhere -- the changes from v9 to v10 do not
> look like affecting our packages, at least for the majority of them,
> but we w
In data martedì 19 dicembre 2017 17:02:37 CET, Sandro Knauß ha scritto:
> I now finished the most work for kdepim 17.08.3 for unstable and pushed
> everything:
Great, let's see.
> * I build everything in tiers to make sure, that the deps are uptodate
> * updated symbols
> * Bumped Standards-Vers
Hey Pino,
I now finished the most work for kdepim 17.08.3 for unstable and pushed
everything:
* I build everything in tiers to make sure, that the deps are uptodate
* updated symbols
* Bumped Standards-Version to 4.2.1
* comaptlevel to 10 (11 is not suitable for ubuntu at the moment and me
perso
17 matches
Mail list logo
