control: tag -1 - moreinfo
On Mon, Mar 30, 2015 at 12:58 AM, Cyril Brulebois wrote:
> Thanks for trying, but no, that's not sufficient. I really would
> like having a real use case where the bug gets reproduced without
> “cheating” (for the lack of a better wording), so that we can actually
> chec
Control: tag -1 moreinfo
Michael Gilbert (2015-03-29):
> I couldn't get netcfg to trigger rdnssd installation with my set up,
> so here is what I did to mimic the process:
>
> boot from jessie RC2
> nothing special up through pkgsel
> before pkgsel, manually install rdnssd 1.0.1-2 from sid
> pro
control: tag -1 - moreinfo
On Wed, Feb 25, 2015 at 11:23 PM, Cyril Brulebois wrote:
> It would be nice to compare what happens when one installs gnome/jessie
> vs. gnome/sid. I really wouldn't want this conflict to trigger having
> rdnssd installed and network-manager/gnome not…
Everything seems
On Sun, Mar 1, 2015 at 12:32 AM, Michael Gilbert wrote:
>> It would be nice to compare what happens when one installs gnome/jessie
>> vs. gnome/sid. I really wouldn't want this conflict to trigger having
>> rdnssd installed and network-manager/gnome not…
>
> After a successful jessie gnome install
> It would be nice to compare what happens when one installs gnome/jessie
> vs. gnome/sid. I really wouldn't want this conflict to trigger having
> rdnssd installed and network-manager/gnome not…
After a successful jessie gnome install over ipv6
$ dpkg -l | grep rdnssd
$ dpkg -l | grep network-ma
Holger Levsen (2015-02-26):
> Hi,
>
> On Donnerstag, 26. Februar 2015, Cyril Brulebois wrote:
> > It would be nice to compare what happens when one installs gnome/jessie
> > vs. gnome/sid. I really wouldn't want this conflict to trigger having
> > rdnssd installed and network-manager/gnome not…
>
Hi,
On Donnerstag, 26. Februar 2015, Cyril Brulebois wrote:
> It would be nice to compare what happens when one installs gnome/jessie
> vs. gnome/sid. I really wouldn't want this conflict to trigger having
> rdnssd installed and network-manager/gnome not…
https://jenkins.debian.net/view/chroot-in
Control: tag -1 moreinfo
Michael Gilbert (2015-02-15):
> package: release.debian.org
> user: release.debian@packages.debian.org
> usertags: unblock
> severity: normal
> x-debbugs-cc: debian-b...@lists.debian.org
>
> Please consider unblocking ndisc6. I did a QA upload to fix bug #740998.
>
Tags: + d-i
Le 2015-02-19 06:30, Michael Gilbert a écrit :
On Tue, Feb 17, 2015 at 10:03 AM, Mehdi Dogguy wrote:
Wouldn't that break the installer? ... since netcfg is installing
rdnssd
and network-manager is being installed by default.
I don't see why it would. Yes, rdnssd-udeb is used by
On Tue, Feb 17, 2015 at 10:03 AM, Mehdi Dogguy wrote:
> Wouldn't that break the installer? ... since netcfg is installing rdnssd
> and network-manager is being installed by default.
I don't see why it would. Yes, rdnssd-udeb is used by netcfg in the
d-i environment but network-manager is not pre
On Sun, Feb 15, 2015 at 04:10:07PM -0500, Michael Gilbert
wrote:
> +ndisc6 (1.0.1-2) unstable; urgency=medium
>
> +
> + * QA upload.
> + * Set maintainer to the Debian QA Group (see #71300
package: release.debian.org
user: release.debian@packages.debian.org
usertags: unblock
severity: normal
x-debbugs-cc: debian-b...@lists.debian.org
Please consider unblocking ndisc6. I did a QA upload to fix bug #740998.
The kfreebsd builds are missing because of #764692, which sounds
unlikel
12 matches
Mail list logo
