Re: [Piuparts-devel] Bug#856845: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

On Tue, Mar 21, 2017 at 06:32:25PM +0100, Michael Biebl wrote: > They are not missing. When I was talking about dependencies I meant the > Breaks/Replaces. but those are not "depends" and I do believe they have different effects than "depends"… > Yeah, as I wrote earlier > "Forcing the upgrade

Re: [Piuparts-devel] Bug#856845: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

Am 21.03.2017 um 18:22 schrieb Holger Levsen: > On Tue, Mar 21, 2017 at 06:05:59PM +0100, Ansgar Burchardt wrote: >> What should be wrong about the dependencies? > > they are missing? They are not missing. When I was talking about dependencies I meant the Breaks/Replaces. >> Note that you ask

Re: [Piuparts-devel] Bug#856845: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

On Tue, Mar 21, 2017 at 06:05:59PM +0100, Ansgar Burchardt wrote: > What should be wrong about the dependencies? they are missing? > Note that you ask apt explicitly to break stuff (in the logs I see " > --force-yes" which is documented as potentially breaking systems; I > hope users don't use

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

On Tue, 2017-03-21 at 16:45 +, Holger Levsen wrote: > On Sun, Mar 19, 2017 at 05:31:16PM +0100, Michael Biebl wrote: > > both systemd and udev need to be upgraded in lockstep: > > > > a/ udev has Breaks/Replaces systemd (<< 224-2) > > b/ systemd has a Breaks/Replaces udev (<< 228-5) > > > >

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

On Tue, Mar 21, 2017 at 1:45 PM, Holger Levsen wrote: > Hi Michael, > > On Sun, Mar 19, 2017 at 05:31:16PM +0100, Michael Biebl wrote: >> both systemd and udev need to be upgraded in lockstep: >> >> a/ udev has Breaks/Replaces systemd (<< 224-2) >> b/ systemd has a

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

On Tue, Mar 21, 2017 at 06:05:42PM +0100, Michael Biebl wrote: > > On Sun, Mar 19, 2017 at 05:31:16PM +0100, Michael Biebl wrote: > >> both systemd and udev need to be upgraded in lockstep: > >> Forcing the upgrade of only one of the two will fail. > > if this is the case, then I think the

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

Am 21.03.2017 um 17:45 schrieb Holger Levsen: > Hi Michael, > > On Sun, Mar 19, 2017 at 05:31:16PM +0100, Michael Biebl wrote: >> both systemd and udev need to be upgraded in lockstep: >> >> a/ udev has Breaks/Replaces systemd (<< 224-2) >> b/ systemd has a Breaks/Replaces udev (<< 228-5) >> >>

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

Hi Michael, On Sun, Mar 19, 2017 at 05:31:16PM +0100, Michael Biebl wrote: > both systemd and udev need to be upgraded in lockstep: > > a/ udev has Breaks/Replaces systemd (<< 224-2) > b/ systemd has a Breaks/Replaces udev (<< 228-5) > > Forcing the upgrade of only one of the two will fail. if

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

Hi Holger Am 19.03.2017 um 12:56 schrieb Holger Levsen: > As I see it this is because we only tell apt-get to install udev from > backports but dont tell it to also upgrade systemd to that version, so this > is probably rather a bug in apt (or maybe piuparts) but not in src:systemd. > > Do you

Re: piuparts.debian.org: jessie2bpo has >400 packages in dependency-failed-testing status

Dear systemd maintainers, On Sun, Mar 05, 2017 at 01:27:22PM +0100, Holger Levsen wrote: > Package: piuparts.debian.org > > the subject says it: jessie2bpo has >400 packages in dependency-failed-testing > status, which is far too many for the stable release. We should track down the > cause for