Latest update - 2018.05.26 - missing key on CentOS

Enrico Tagliavini enrico.tagliavini at
Thu Jun 14 13:46:28 CEST 2018

Hello Christoph,

     if I may throw in a suggestion, without sounding like a troll or
an hater, but rather trying to be constructive: maybe this is a good
time to review the internal priorities. I understand there is one
person only maintaining the infrastructure and I fully understand he
can be busy. Blocking updates of all users for multiple weeks should
be a very high priority task, I know there is a workaround but it
involved disabling the only check guaranteeing the source of the
package. Possibly this person needs some help if he cannot flush his
queue enough to reach the point where he can take care of this task.

Again: this is just not to flame or troll, I support Kolab, and I
appreciate the work from everybody working on it and I want it to be
as successful as possible, that's also why I want such issue not to
happen or to be addressed timely.

Thank you.
Kind regards.


On 9 June 2018 at 18:18, Skale, Franz <i.bin at> wrote:
> Hi,
> thanks for clearing things up.
> Anyhow, the Task doesn't mention the lists file which are already in place.
> To get it working you have to remove the lists file before updating again:
> 1.)
> change the /etc/apt/sources.list.d/kolab to:
> deb  [ trusted=no ]
> ./
> deb-src [ trusted=no ]
> ./
> 2.)
> rm
> /var/lib/apt/lists/obs.kolabsys.com_repositories_Kolab\:_16_Debian%5f8.0_._*
> 3.)
> apt-get update
> 4.)
> apt-get upgrade
> Rgds.
> Franz
> Am 2018-06-09 17:44, schrieb Christoph Erhardt:
>> Hi,
>> see for a workaround.
>> Unfortunately, there's nothing I can do myself because the signing-key
>> stuff
>> requires SSH access to the OBS server, which I don't have. The one guy
>> who's
>> keeping all of the infrastructure together knows about the problem, but I
>> think he's extremely busy at the moment.
>> Best regards,
>> Christoph
>> On Saturday, 9 June 2018 14:13:43 CEST Skale, Franz wrote:
>>> I really don't know what the problem is on supplying a valid gpg key.
>>> Right now, i sync the package sources and rebuild them by my own.
>>> Using reprepo for debian and a valid gpg key of course.
>>> It's astoundingthat there's no response from the core developers/package
>>> managers.
>>> Rgds.
>>> Franz
>> _______________________________________________
>> users mailing list
>> users at
> _______________________________________________
> users mailing list
> users at

More information about the users mailing list