Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2017-02-18 Thread Manuel A. Fernandez Montecelo
Control: tags -1 + pending Hi, 2016-10-20 02:51 Axel Beckert: Control: tag -1 + confirmed Hi Michael, Michael Biebl wrote: >> Is this not happening for you? > > Seems not, no. But then again, I'm using aptitude most of the time and > apt only in a few percent of all cases. It's safe to

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Axel Beckert
Control: tag -1 + confirmed Hi Michael, Michael Biebl wrote: > >> Is this not happening for you? > > > > Seems not, no. But then again, I'm using aptitude most of the time and > > apt only in a few percent of all cases. > > It's safe to assume that you have a /var/lib/aptitude/pkgstates. > Can

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Michael Biebl
Am 20.10.2016 um 02:21 schrieb Axel Beckert: > According to your description, I'd expect tons of differences. > >> The first time /var/lib/aptitude/pkgstates is created, it inherits the >> autobit state from the apt db, but after that, any changes apt makes are >> no longer applied to aptitude.

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Axel Beckert
Hi, Michael Biebl wrote: > > I somehow doubt that. As I see it, this either this broke only very > > recently (after the 0.8.3 upload) or it's only happening under some > > circumstances. > > Just curious, can you reproduce the issue with the steps I outlined? Haven't tried it yet admittedly.

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Michael Biebl
Am 20.10.2016 um 01:42 schrieb Axel Beckert: > Hi, > > Michael Biebl wrote: >> Afaics, once /var/lib/aptitude/pkgstates exists, which it will after any >> non-trivial use of aptitude, the sync between apt and aptitude is >> completely broken. > > I somehow doubt that. As I see it, this either

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Michael Biebl
Am 20.10.2016 um 02:12 schrieb Michael Biebl: > Am 20.10.2016 um 01:42 schrieb Axel Beckert: >> Hi, >> >> Michael Biebl wrote: >>> Afaics, once /var/lib/aptitude/pkgstates exists, which it will after any >>> non-trivial use of aptitude, the sync between apt and aptitude is >>> completely broken.

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Axel Beckert
Hi, Michael Biebl wrote: > Afaics, once /var/lib/aptitude/pkgstates exists, which it will after any > non-trivial use of aptitude, the sync between apt and aptitude is > completely broken. I somehow doubt that. As I see it, this either this broke only very recently (after the 0.8.3 upload) or

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Michael Biebl
Am 20.10.2016 um 01:03 schrieb Axel Beckert: > Hi Michael, > > Michael Biebl wrote: >> Am 20.10.2016 um 00:44 schrieb Michael Biebl: >>> So, the complete steps to reproduce the issue: >>> - create a fresh chroot via debootstrap >>> - start aptitude in interactive mode, select a random,

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Axel Beckert
Hi Michael, Michael Biebl wrote: > Am 20.10.2016 um 00:44 schrieb Michael Biebl: > > So, the complete steps to reproduce the issue: > > - create a fresh chroot via debootstrap > > - start aptitude in interactive mode, select a random, non-related > > package, say netbase, mark it as

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Michael Biebl
Am 20.10.2016 um 00:44 schrieb Michael Biebl: > So, the complete steps to reproduce the issue: > - create a fresh chroot via debootstrap > - start aptitude in interactive mode, select a random, non-related > package, say netbase, mark it as auto-installed via "M" At this point, you should have

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Michael Biebl
Am 20.10.2016 um 00:23 schrieb Axel Beckert: > I have a slight suspicion that aptitude and apt might refer to > different architectures of gobject-introspection in this case (in > which both might be correct, just not displaying the expected or > multiple packages). I don't think this is the

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Michael Biebl
Am 20.10.2016 um 00:23 schrieb Axel Beckert: > Hi Michael, > > Michael Biebl wrote earlier: >> Architecture: amd64 (x86_64) >> Foreign Architectures: i386 > > Michael Biebl wrote: >> As an example, after installing the example deb I attached earlier, it >> pulls in dependencies like

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Axel Beckert
Hi Michael, Michael Biebl wrote earlier: > Architecture: amd64 (x86_64) > Foreign Architectures: i386 Michael Biebl wrote: > As an example, after installing the example deb I attached earlier, it > pulls in dependencies like gobject-introspection. > > $ apt-mark showauto | grep

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Michael Biebl
Hi Am 19.10.2016 um 23:48 schrieb Axel Beckert: > Michael Biebl wrote: >> So if I install via apt, the auto state is not properly set for >> aptitude. I have no idea how apt and aptitude interact and if the >> autobit is something which is supposed to be shared between both? > > It is. > >> Do

Bug#841347: [Aptitude-devel] Bug#841347: packages are not marked as auto "i A" in aptitude

2016-10-19 Thread Axel Beckert
Hi Michael, Michael Biebl wrote: > So if I install via apt, the auto state is not properly set for > aptitude. I have no idea how apt and aptitude interact and if the > autobit is something which is supposed to be shared between both? It is. > Do they access the same database Nowadays they do.