Watchdog init info
Oliver Grawert wrote: > is there a reason that you use the old obsolete watchdog package > instead of using systemd's watchdog feature ? One of our packages uses watchdog package as a dependency. And this package is installed on multitude of servers with Ubuntu 12.04 and 14.04. Actually, we are trying to move to Ubuntu 16.04 with the least efforts just installing our packages on it. Regards, Artem Konvalyuk -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: git workflows for general Ubuntu development
On Mon, Nov 14, 2016 at 04:58:44PM -0800, Nish Aravamudan wrote: > 2) dgit does not fully meet our needs at this time. It's going to be > something Robie covers in more detail in the UOS session, but hopefully > he'll be able to respond here, as well. I think there's the follow-up question here of "why not improve dgit to meet our needs?". That was certainly always what I envisioned happening when I was sketching out preparatory work for this on the Launchpad side; I'd already done some initial preparation to get it working for us; and there are some problems (perhaps not fatal, but not necessarily trivial) associated with having more than one potential importer, not to mention the duplicated effort. -- Colin Watson [cjwat...@ubuntu.com] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: git workflows for general Ubuntu development
On 15.11.2016 [09:57:56 +1300], Michael Hudson-Doyle wrote: > On 15 November 2016 at 01:51, Robie Basak wrote: > > > On the server team, we've been working on a process that uses git to do > > our "Ubuntu merges". As a consequence, we now have a mechanism that can > > import package histories into git on Launchpad. We think that this work > > opens up a bunch of new possibilities, such as for drive-by contributors > > submitting merge proposals entirely through git. > > > > This is pretty exciting! Do you think your work will fulfil the goals of > the UDD project or is there still some stuff that's out of scope? Is there a list of those goals? I have never used UDD and wasn't contributing to Ubuntu when it was in-use. > > We'll be talking about our work tomorrow, as part of the Ubuntu Online > > Summit. The session page is at > > http://summit.ubuntu.com/uos-1611/meeting/22710/git-based-merge-workflow/ > > and is currently scheduled for 2016-11-15 18:00 UTC. Times may change, > > so be sure to check the schedule tomorrow. > > > > I originally wrote about this in August 2014 > > (https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038418.html). > > We've come on a long way since then. Our automated git imports preserve > > histories. Where relevant, Ubuntu packages are correctly parented from > > their Debian origins. We hope to start running this live soon, which > > will import package uploads into our git trees as they happen rather > > than on-demand. Once this is live, anyone will be able to easily clone > > from the "current" Ubuntu packaging git trees, which we think is useful > > in itself. > > > > If you're interested, we'd love your feedback. What are your use cases? > > What sort of workflows would you like to see? You can see some further > > notes of ours as they form in the pad on the session page linked above. > > What have we missed? > > > > The two questions I have (which are touched on but not afaics really > answered in the notes are) 1) how does this work if I already maintain the > packaging for some package in git? 2) what about dgit? 1) No impact to you -- we currently don't have plans to 'import the world' (meaning all source packages). If the importer were to run against that source package, though, it would simply import the source package(s) according to Launchpad's publishing history in Debiand and Ubuntu. What is most interesting, perhaps, is that you can push 'upload/' tags to the repository the importer uses (presuming permissions) and the importer will recognize that tag, compare it to the corresponding upload in Launchpad (source package comparison) and if they match, it will use the upload-tag as the imported-commit, and parent it into the history. So if you have broken-out changes (and this is true for merges too) in your git tree, you can use the upload/ tags to reflect that. There is no presumption of common ancestry, so the resulting history (if you have a separate repository right now), might look a little strange, but it should work :) It's a bit hand-wavy written out like that, so feel free to ping me on IRC (nacc) and I'll try and help clarify. 2) dgit does not fully meet our needs at this time. It's going to be something Robie covers in more detail in the UOS session, but hopefully he'll be able to respond here, as well. Thanks, Nish -- Nishanth Aravamudan Ubuntu Server Canonical Ltd -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: git workflows for general Ubuntu development
On 15 November 2016 at 01:51, Robie Basak wrote: > On the server team, we've been working on a process that uses git to do > our "Ubuntu merges". As a consequence, we now have a mechanism that can > import package histories into git on Launchpad. We think that this work > opens up a bunch of new possibilities, such as for drive-by contributors > submitting merge proposals entirely through git. > This is pretty exciting! Do you think your work will fulfil the goals of the UDD project or is there still some stuff that's out of scope? > We'll be talking about our work tomorrow, as part of the Ubuntu Online > Summit. The session page is at > http://summit.ubuntu.com/uos-1611/meeting/22710/git-based-merge-workflow/ > and is currently scheduled for 2016-11-15 18:00 UTC. Times may change, > so be sure to check the schedule tomorrow. > > I originally wrote about this in August 2014 > (https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038418.html). > We've come on a long way since then. Our automated git imports preserve > histories. Where relevant, Ubuntu packages are correctly parented from > their Debian origins. We hope to start running this live soon, which > will import package uploads into our git trees as they happen rather > than on-demand. Once this is live, anyone will be able to easily clone > from the "current" Ubuntu packaging git trees, which we think is useful > in itself. > > If you're interested, we'd love your feedback. What are your use cases? > What sort of workflows would you like to see? You can see some further > notes of ours as they form in the pad on the session page linked above. > What have we missed? > The two questions I have (which are touched on but not afaics really answered in the notes are) 1) how does this work if I already maintain the packaging for some package in git? 2) what about dgit? > Note that developer time, as always, is limited. We've developed what we > have so far to speed up our own work. Our use cases are probably quite > different from non-core contributors. Possibly enabling the drive-by > contribution use case is a happy consequence. Volunteers able to work on > additional things are welcome to join us. However I am specifically > looking for things we can tweak without much effort that will help > others. I regret that we don't have the time to take on a big project > that doesn't benefit our own use cases. So please understand that if you > make a proposal that involves significant developer work, it is unlikely > to happen unless you also find developers to volunteer their time to > work on it. > > At the UOS session we'll be able to discuss this in real-time on Google > Hangouts and concurrently on IRC. But our time in the session is limited > to one hour, so replying to this thread to first distill any > conversation would be helpful if possible. Cheers, mwh -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Watchdog init info
Hello! I have Ubuntu 16.04 server and need to install watchdog package (5.14-3ubuntu0.16.04.1) and some other packages. But there is some kind of loop detected with insserv: insserv: warning: script '' missing LSB tags and overrides insserv: There is a loop between service watchdog and if stopped insserv: loop involving service at depth 2 insserv: loop involving service watchdog at depth 1 insserv: Stopping depends on watchdog and therefore on system facility `$all' which can not be true! insserv: exiting now without changing boot order! Is it correct to put '$all' facility into 'Required-Stop' field? It seems to break insserv launch when there are init-scripts without LSB information. In https://wiki.debian.org/LSBInitScripts/ it is stated that '$all' only works for start ordering, not stop ordering. Init info of watchdog: ### BEGIN INIT INFO # Provides: watchdog # Short-Description: Start software watchdog daemon # Required-Start:$all # Required-Stop: $all # Should-Start: # Should-Stop: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 ### END INIT INFO If 'Required-Stop' is empty insserv works fine. Has anyone experienced similar problem? Of cource I can use insserv overrides but maybe it is better to fix watchdog package (if there is something to fix). Regargs, Artem Konvalyuk -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Gnash
On Mon, 2016-11-14 at 17:07 +0100, Nils Kassube wrote: > Due to the path above, I think the culprit isn't apt but synaptic. It > should probably use a path outside the /root directory. I was thinking about "user '_apt'", not "apt", but you a right, the path /root/ is an issue. Not for synaptic and other app's settings, but for temporary files that are related to _"apt"_/"user '_apt'". Regards, Ralf -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Watchdog init info
hi, On Mo, 2016-11-14 at 18:28 +0300, Артём Конвалюк wrote: > Hello! > > I have Ubuntu 16.04 server and need to install watchdog package > (5.14-3ubuntu0.16.04.1) and some other packages. > is there a reason that you use the old obsolete watchdog package instead of using systemd's watchdog feature ? ciao oli signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Gnash
Ralf Mardorf wrote: > On Mon, 14 Nov 2016 16:06:33 +0100, Oliver Grawert wrote: > >On So, 2016-11-13 at 16:24 +0100, Till Uhlmann wrote: > >> "W: Can't drop privileges for downloading as file > >> '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. ^^^ > since the operation anyway is done by root, anyway, there seems to be > an issue with _apt, that could be fixed. Perhaps just owner:group of > the file permissions need to be fixed. Due to the path above, I think the culprit isn't apt but synaptic. It should probably use a path outside the /root directory. Nils -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Watchdog init info
Hello! I have Ubuntu 16.04 server and need to install watchdog package (5.14-3ubuntu0.16.04.1) and some other packages. But there is some kind of loop detected with insserv: insserv: warning: script '' missing LSB tags and overrides insserv: There is a loop between service watchdog and if stopped insserv: loop involving service at depth 2 insserv: loop involving service watchdog at depth 1 insserv: Stopping depends on watchdog and therefore on system facility `$all' which can not be true! insserv: exiting now without changing boot order! Is it correct to put '$all' facility into 'Required-Stop' field? It seems to break insserv launch when there are init-scripts without LSB information. In https://wiki.debian.org/LSBInitScripts/ it is stated that '$all' only works for start ordering, not stop ordering. Init info of watchdog: ### BEGIN INIT INFO # Provides: watchdog # Short-Description: Start software watchdog daemon # Required-Start:$all # Required-Stop: $all # Should-Start: # Should-Stop: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 ### END INIT INFO If 'Required-Stop' is empty insserv works fine. Has anyone experienced similar problem? Of cource I can use insserv overrides but maybe it is better to fix watchdog package (if there is something to fix). Regargs, Artem Konvalyuk -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Gnash
On 2016-11-14 16:06, Oliver Grawert wrote: hi, On So, 2016-11-13 at 16:24 +0100, Till Uhlmann wrote: "W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Keine Berechtigung) are you aware the "W:" in the front means this is just a warning ? it does not have any effect on the operation itself ... Related bug, I think: https://launchpad.net/bugs/1570141 The Debian developer doesn't seem eager to fix it: https://bugs.debian.org/813786 -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Gnash
On Mon, 14 Nov 2016 16:06:33 +0100, Oliver Grawert wrote: >hi, >On So, 2016-11-13 at 16:24 +0100, Till Uhlmann wrote: >> >> "W: Can't drop privileges for downloading as file >> '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - >> pkgAcquire::Run (13: Keine Berechtigung) >> > >are you aware the "W:" in the front means this is just a warning ? it >does not have any effect on the operation itself ... Good point :) since the operation anyway is done by root, anyway, there seems to be an issue with _apt, that could be fixed. Perhaps just owner:group of the file permissions need to be fixed. Regards, Ralf -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Gnash
hi, On So, 2016-11-13 at 16:24 +0100, Till Uhlmann wrote: > > "W: Can't drop privileges for downloading as file > '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - > pkgAcquire::Run (13: Keine Berechtigung) > are you aware the "W:" in the front means this is just a warning ? it does not have any effect on the operation itself ... ciao oli signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
git workflows for general Ubuntu development
On the server team, we've been working on a process that uses git to do our "Ubuntu merges". As a consequence, we now have a mechanism that can import package histories into git on Launchpad. We think that this work opens up a bunch of new possibilities, such as for drive-by contributors submitting merge proposals entirely through git. We'll be talking about our work tomorrow, as part of the Ubuntu Online Summit. The session page is at http://summit.ubuntu.com/uos-1611/meeting/22710/git-based-merge-workflow/ and is currently scheduled for 2016-11-15 18:00 UTC. Times may change, so be sure to check the schedule tomorrow. I originally wrote about this in August 2014 (https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038418.html). We've come on a long way since then. Our automated git imports preserve histories. Where relevant, Ubuntu packages are correctly parented from their Debian origins. We hope to start running this live soon, which will import package uploads into our git trees as they happen rather than on-demand. Once this is live, anyone will be able to easily clone from the "current" Ubuntu packaging git trees, which we think is useful in itself. If you're interested, we'd love your feedback. What are your use cases? What sort of workflows would you like to see? You can see some further notes of ours as they form in the pad on the session page linked above. What have we missed? Note that developer time, as always, is limited. We've developed what we have so far to speed up our own work. Our use cases are probably quite different from non-core contributors. Possibly enabling the drive-by contribution use case is a happy consequence. Volunteers able to work on additional things are welcome to join us. However I am specifically looking for things we can tweak without much effort that will help others. I regret that we don't have the time to take on a big project that doesn't benefit our own use cases. So please understand that if you make a proposal that involves significant developer work, it is unlikely to happen unless you also find developers to volunteer their time to work on it. At the UOS session we'll be able to discuss this in real-time on Google Hangouts and concurrently on IRC. But our time in the session is limited to one hour, so replying to this thread to first distill any conversation would be helpful if possible. Robie Basak Ubuntu Server Team signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Gnash
On Mon, 14 Nov 2016 07:42:22 +, Colin Law wrote:
>On 14 Nov 2016 7:22 a.m., "Till Uhlmann" wrote:
>>
>> I'm unable to unistall gnash from my system. Ubuntu 16.04 Mate.
>> "W: Can't drop privileges for downloading as file
>> '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. -
>> pkgAcquire::Run (13: Keine Berechtigung)"
(13: Permission denied)
Please always run
LANG=C
e.g.
LANG=C apt purge gnash
or
sudo LANG=C synaptic
and always mention what release and flavour you are using, e.g. run
lsb_release -rc
and if required inform us if this is e.g. lubuntu, ubuntu-mate or
another flavour.
Also consider to sent such a request to the users mailing list.
>> is the information i got by
>> trying uninstall gnash-common/gnash may i need only a valid apt-key
>> for reinstall gnash correct bevore uninstalling again
>
>How exactly are you trying to install it?
I can't confirm this bug, but seemingly some people suffer from this:
https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1543280 [1]
Please post the output of
getent passwd _apt
here it looks like this
[root@moonstudio ~]# getent passwd _apt
_apt:x:113:65534::/nonexistent:/bin/false
You can run this as user, I run as root, because I run it in a
container, without booting (systemd-nspawn -qD /mnt/moonstudio).
Regards,
Ralf
[1]
Running
cat /etc/passwd | grep apt
is disgusting, this should read
grep apt /etc/passwd
or
getent passwd _apt
even when first using
cat /etc/passwd
we could then type
^cat^grep apt
and enter, to replace "cat" with "grep apt"
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
