Hey Guus,
Guus Sliepen [2015-12-27 20:50 +0100]:
> Please check if the problem still exists with version 0.8.4. Version 0.8
> didn't correctly order itself with respect to network-online.target, but
> 0.8.4 should have fixed that.
This should be unrelated to network-online.target. networking.serv
Hello Guus,
Guus Sliepen [2015-12-27 23:11 +0100]:
> > * An udev rule which reacts to adding or removing network devices.
> >This is currently shipped as /lib/udev/rules.d/80-networking.rules
> >but I propose that ifupdown ships it as
> >/lib/udev/rules.d/80-ifupdown.rules to avoid a
On 26 December 2015 at 06:06, Michael Biebl wrote:
> Am 26.12.2015 um 08:37 schrieb martin f krafft:
>> also sprach Jörg Frings-Fürst [2015-12-26 11:48
>> +1300]:
>>> Care to elaborate why?
>>
>> Sorry, it's not terribly useful to augment the original bug report
>> that I first cloned.
>>
>> Bas
On Sun, Dec 27, 2015 at 08:58:32PM +0100, Martin Pitt wrote:
> for historical reasons the udev package has shipped the functionality
> for handling network device hotplug events. However, it's a bit weird
> to ship the coldplugging parts (/etc/init.d/networking and
> networking.service) in ifupdow
Package: ifupdown
Severity: wishlist
Version: 0.8.4
Hello,
for historical reasons the udev package has shipped the functionality
for handling network device hotplug events. However, it's a bit weird
to ship the coldplugging parts (/etc/init.d/networking and
networking.service) in ifupdown, but no
On Sun, Dec 27, 2015 at 07:58:06PM +0100, Martin Pitt wrote:
> Package: ifupdown
> Version: 0.8
>
> /etc/init.d/networking has some functionality to check if the root
> file system or swap are on a network file system, in
> check_network_file_systems() and check_network_swap(). In that case,
> th
Package: ifupdown
Version: 0.8
Hello,
/etc/init.d/networking has some functionality to check if the root
file system or swap are on a network file system, in
check_network_file_systems() and check_network_swap(). In that case,
the interfaces are not ifdown'ed during shutdown, so that these
networ
Processing control commands:
> severity -1 normal
Bug #774080 [udev] udev: /dev/dvd symlink changed while a program using it was
running
Severity set to 'normal' from 'wishlist'
> tag -1 pending
Bug #774080 [udev] udev: /dev/dvd symlink changed while a program using it was
running
Added tag(s) p
Control: severity -1 normal
Control: tag -1 pending
Vincent Danjean [2014-12-28 15:02 +0100]:
> While the extraction was running (with the bash loop), I put a CD in
> the DVD writer. To my surprise (it tooks me time to identify the root of
> the problem), the /dev/dvd symlink changed to point to
Your message dated Sun, 27 Dec 2015 13:33:32 +
with message-id
and subject line Bug#806558: Removed package(s) from experimental
has caused the Debian Bug report #799706,
regarding kdbus-dkms: not all services available
to be marked as done.
This means that you claim that the problem has been
Version: 0.20150901t074837.245fe93-2+rm
Dear submitter,
as the package kdbus-dkms has just been removed from the Debian archive
experimental we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bu
We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:
kdbus-dkms | 0.20150901t074837.245fe93-2 | source, all
--- Reason ---
ROM; abandoned upstream in current form
--
The "/usr/lib/modules-load.d/" path isn't documented because it's
changed to "/lib/modules-load.d/" by
find debian/install/deb/usr/share/man/ -type f | xargs sed -ri
's_/usr(/lib/systemd|/lib/udev|/lib/modules-load.d|/lib/modules\\-load|/lib[^/]|/lib/[^a-z])_\1_g'
in systemd's "debian/rules".
Si
13 matches
Mail list logo