Control: tags -1 unreproducible thanks On Wed, Apr 09, 2025 at 03:43:27PM +0000, hyuw77yckxszm...@firemail.cc wrote: > On 2025-04-09 15:17, Marc Haber wrote: > > So you're upgrading from unstable, 2.10.0.3 to unstable, 2.11.1-1. > > Right? > > Upgraded, done. After actions described it got installed. Debian testing, > yes, did reportbug output not include that?
Unfortunately, reportbug doesn't report the version of the package being upgraded from. A full transcript of the upgrading process would have helped. > > It would be incredibly helpful to have the verbatim output of all calls. > > Dont have console output stored. You should do that in the future. It makes your bugreports easier to act on. > It clearly had no problem writing files. It wrote many of them, like: > /var/log/atop/atop_20250409 > /var/log/atop/atop_20250409_oldformat > /var/log/atop/atop_20250409_oldformat_oldformat > after few retries with apt full-upgrade. I will adapt the postinst to be a bit more robust and to not error out if it doesn't convert. Better lose today's data than aborting the upgrade. > > Can you reproduce the issue with the backed up logs? In that case, can > > you run postinst configure with bash -x so that we can see what the > > script actually tries to do? > > How do I reproduce it, when I have done installing/upgrading? As I have > repeatedly been told, debian does not support downgrades etc etc. I do find > it odd that debian testing makes it so cumbersome to simply downgrade > something, "this is how debian works" as I have been told. Debian testing is an unreleased development version that is targeted at developers who know their way around the distribution. It is generally not recommended to run Debian testing if you don't know how to debug package upgrades. In the situation in question, you would have to pull the older version of the package from snapshot.debian.org, install it (that is not supported but works in most of the cases. If it doesn't you have to clean up) and re-run the upgrade. > Deleted these backed up logs also some time before bugreport, I had them > just for my atopsar runs which I have done for now and did not need them > anymore. Or so I thought. It would have been a good idea to have a backup. I cannot reproduce the issue in my test environments. Without more input and with the data deleted, there is probably nothing to do. Noone else has reported a similar issue since the last testing migration, so without a reproducer there is nothing I can do for you. Greetings Marc
