New component-mismatches for source universe -> main

The following universe packages have new reverse dependencies in main or got seeded. They need to get a MainInclusionReport and be promoted, or the reverse dependencies in main need to be dropped: [Reverse-Depends: Rescued from graphene, gstreamer1.0-gl (MAIN)] Please see

Re: Request to reset src:mariadb-10.1 to previous known working state in Ubuntu archives

Thanks Robie for your comment. Comments to them below: 2018-03-15 15:47 GMT+02:00 Robie Basak : .. > Unfortunately, to the best of my knowledge we don't ever try to make > this kind of revert in the archive because of the knock-on effects it'll > have everywhere else. I

Re: xchat and hexchat

Hello, >I've added this to the TB agenda. I imagine it'll take quite a bit of >reading of the various references (I've added them to the agenda item) >so appreciate you may not be able to decide by tomorrow's meeting. just to give my quick maintainer point of view. 1) the security issues it

Re: Request to reset src:mariadb-10.1 to previous known working state in Ubuntu archives

2018-03-16 2:58 GMT+02:00 Robie Basak : >> Yes, once an epoch is in the wild in Debian or Ubuntu, it's irreversible. >> Others will simply need to follow suit. >> >> > If a PPA does not do this, then users will end up downgraded, with a >> > failed data migration and

Re: Request to reset src:mariadb-10.1 to previous known working state in Ubuntu archives

On Fri, Mar 16, 2018 at 12:35:42AM +, Robie Basak wrote: > On Fri, Mar 16, 2018 at 12:01:11AM +0200, Otto Kekäläinen wrote: > > > And keep the epoch forever. No thanks. Epochs happen. A lot. Here's a quick check of my installed packages: $ dpkg -l | awk '/^i/ {print $3}' | grep '.:' | wc