Your message dated Mon, 4 Sep 2023 20:48:56 +0200 with message-id <zpymmgiohulhs...@thunder.hadrons.org> and subject line Re: Bug#1043298: Package dependenciens mishmash has caused the Debian Bug report #1043298, regarding Package dependenciens mishmash to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1043298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dpkg Version: 1.21.22 (amd64) There seem to be problem with the packages dependencies. While attempting to upgrade while having other then only default repositories included (there is no error about package duplicates), I had recivied following dependency issue: By some packages, dpkg (thru aptitude) requires that the package from with it's dependant has in the same time the version is: smaller, equal, bigger and equal, with is mutually exclusive. System: Debian (bookworm) Please fix it asap. Mcgiwerpublickey - mcgiwer@proton.me - 0xD936838D.asc
Description: application/pgp-keyssignature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---[ In general when interacting with the Debian Bug Tracking System, please reply to the bug report address, otherwise the conversation might get lost, and other people might not be able to help, or be aware of potentially similar problems. Thanks! ] Hi! On Wed, 2023-08-09 at 00:33:32 +0200, Guillem Jover wrote: > On Tue, 2023-08-08 at 18:28:57 +0000, Mcgiwer wrote: > > Package: dpkg > > Version: 1.21.22 (amd64) > > > There seem to be problem with the packages dependencies. > > If there is a problem with package dependencies, then that should > probably be assigned to the specific package involved. My point, which didn't seem clear from the reply I got privately, is that the dependency affects specific packages, and those might be the problem, but in general I'd first think this might be out-dated archive metadata (missing «aptitude update»), or missing archive areas (say missing «contrib» when enabling «non-free) or similar rather than an actual dependency issue, as those should have been detected before the release went out. > > While attempting to upgrade while having other then only default > > repositories included (there is no error about package duplicates), > > I had recivied following dependency issue: > > > > By some packages, dpkg (thru aptitude) requires that the package > > from with it's dependant has in the same time the version is: > > smaller, equal, bigger and equal, with is mutually exclusive. > > I do not recognize this message, so I'm not even sure what this report > is about, what packages are involved, or what the actual error is. Or > even whether this is really a problem in dpkg or a problem at all. Pasting the actual exact error message (even if it's localized in anything other than English) would be more helpful, and the specific package that is broken (from the aptitude TUI or CLI output). > > System: Debian (bookworm) > > > Please fix it asap. > > Hard to do anything with this with the information given, to be > honest. As is, this report is not actionable. But in, any case I still think this is not a problem with dpkg, so I'll be closing this report now. If you are still affected by this, please contact the debian-user mailing list or some of the other support channels to get help trying to pin this down. And if this ends up really being a problem in dpkg, then of course feel free to file a report or reopen this one! Thanks, Guillem
--- End Message ---