Hi !
I'm running trinity desktop on Debian Jessie. As I tried to install k9copy program, apt-get complained about dependency on "mencoder"
The package "mencoder" doesn't seem to be available in jessie. Any idea how to solve it?
Here is my /etc/apt/sources.list.d/trinity.list file ----8<---- deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/de... jessie main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build-dep... jessie main ----8<----
Here is the output of apt-get install command: ----8<---- root@tuoni:~# apt-get install k9copy-trinity Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: k9copy-trinity : Depends: mencoder but it is not installable E: Unable to correct problems, you have held broken packages. ----8<----
Cheers,
Ilya Dogolazky
On Thursday 04 September 2014 01:40:14 am you wrote:
Hi !
I'm running trinity desktop on Debian Jessie. As I tried to install k9copy program, apt-get complained about dependency on "mencoder"
The package "mencoder" doesn't seem to be available in jessie. Any idea how to solve it?
Here is my /etc/apt/sources.list.d/trinity.list file ----8<---- deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-bu ilds/debian jessie main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-bu ild-dependencies/debian jessie main ----8<----
Here is the output of apt-get install command: ----8<---- root@tuoni:~# apt-get install k9copy-trinity Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: k9copy-trinity : Depends: mencoder but it is not installable E: Unable to correct problems, you have held broken packages. ----8<----
Cheers,
Ilya Dogolazky
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Looks like it is removed from Debian, The depends will have to be removed from k9copy-trinity
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732159
On Thursday 04 of September 2014 14:56:30 Greg Madden wrote:
On Thursday 04 September 2014 01:40:14 am you wrote:
Hi !
I'm running trinity desktop on Debian Jessie. As I tried to install k9copy program, apt-get complained about dependency on "mencoder"
The package "mencoder" doesn't seem to be available in jessie. Any idea how to solve it?
Here is my /etc/apt/sources.list.d/trinity.list file ----8<---- deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-bu ilds/debian jessie main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-bu ild-dependencies/debian jessie main ----8<----
Here is the output of apt-get install command: ----8<---- root@tuoni:~# apt-get install k9copy-trinity Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: k9copy-trinity : Depends: mencoder but it is not installable E: Unable to correct problems, you have held broken packages. ----8<----
Cheers,
Ilya Dogolazky
Looks like it is removed from Debian, The depends will have to be removed from k9copy-trinity
The question is whether k9copy without MEncoder is useful? We could move mencoder to Recommends or set variant dependency "mencoder | libav-tools". But the question is whether it will be useful without rewrite k9copy to able use avconv instead of mencoder?
The question is whether k9copy without MEncoder is useful? We could move mencoder to Recommends or set variant dependency "mencoder | libav-tools". But the question is whether it will be useful without rewrite k9copy to able use avconv instead of mencoder?
Basically mencoder is no longer supported in Debian, but it seems it is still available under Ubuntu (at least until Trusty). I think an easy solution is to add mencoder to the list of dependency packages that we maintain and leave everything else as is at the moment. Cheers Michele
On Saturday 06 of September 2014 14:09:23 Michele Calgaro wrote:
The question is whether k9copy without MEncoder is useful? We could move mencoder to Recommends or set variant dependency "mencoder | libav-tools". But the question is whether it will be useful without rewrite k9copy to able use avconv instead of mencoder?
Basically mencoder is no longer supported in Debian, but it seems it is still available under Ubuntu (at least until Trusty). I think an easy solution is to add mencoder to the list of dependency packages that we maintain and leave everything else as is at the moment. Cheers Michele
Mencoder is part of mplayer1. I'm not sure that we want to maintain mplayer1. Therefore, it seems to me to be more appropriate to replace mencoder by libav-tools (avconv). For now I have not examined how difficult task it is.
Mencoder is part of mplayer1. I'm not sure that we want to maintain mplayer1. Therefore, it seems to me to be more appropriate to replace mencoder by libav-tools (avconv). For now I have not examined how difficult task it is.
Ok Slavek, now I get what you mean. It makes sense to do the switch if possible (I also have no clue how long it would require). As a temporary solution until we complete such task we can still consider adding mencoder to the dependency package list, as we did with libotr2. What do you think?
Cheers Michele
On Saturday 06 of September 2014 14:38:35 Michele Calgaro wrote:
Mencoder is part of mplayer1. I'm not sure that we want to maintain mplayer1. Therefore, it seems to me to be more appropriate to replace mencoder by libav-tools (avconv). For now I have not examined how difficult task it is.
Ok Slavek, now I get what you mean. It makes sense to do the switch if possible (I also have no clue how long it would require). As a temporary solution until we complete such task we can still consider adding mencoder to the dependency package list, as we did with libotr2. What do you think?
Cheers Michele
There is one difference from libotr2. For kopete-otr is dependence libotr2 required for build. While mencoder is required for k9copy "only" for some activities at runtime.
As I watched on the deb-multimedia is old mplayer including mencoder still available for Jessie. Thus, users can simply add this apt source that is maintained.
What do you think?
Note: While I was not looking, what is the state with Ubuntu 14.10 (Utopic).
On Saturday 06 September 2014 05:34:27 am you wrote:
On Saturday 06 of September 2014 14:38:35 Michele Calgaro wrote:
Mencoder is part of mplayer1. I'm not sure that we want to maintain mplayer1. Therefore, it seems to me to be more appropriate to replace mencoder by libav-tools (avconv). For now I have not examined how difficult task it is.
Ok Slavek, now I get what you mean. It makes sense to do the switch if possible (I also have no clue how long it would require). As a temporary solution until we complete such task we can still consider adding mencoder to the dependency package list, as we did with libotr2. What do you think?
Cheers Michele
There is one difference from libotr2. For kopete-otr is dependence libotr2 required for build. While mencoder is required for k9copy "only" for some activities at runtime.
As I watched on the deb-multimedia is old mplayer including mencoder still available for Jessie. Thus, users can simply add this apt source that is maintained.
What do you think?
Note: While I was not looking, what is the state with Ubuntu 14.10 (Utopic).
deb-multiedia is not really compatable with Debian, It was/is needed for libdvdcss2 . I don't think its the solution for Jessie.
---- Peace,
Greg
On Sunday 07 of September 2014 01:42:19 Greg Madden wrote:
On Saturday 06 September 2014 05:34:27 am you wrote:
On Saturday 06 of September 2014 14:38:35 Michele Calgaro wrote:
Mencoder is part of mplayer1. I'm not sure that we want to maintain mplayer1. Therefore, it seems to me to be more appropriate to replace mencoder by libav-tools (avconv). For now I have not examined how difficult task it is.
Ok Slavek, now I get what you mean. It makes sense to do the switch if possible (I also have no clue how long it would require). As a temporary solution until we complete such task we can still consider adding mencoder to the dependency package list, as we did with libotr2. What do you think?
Cheers Michele
There is one difference from libotr2. For kopete-otr is dependence libotr2 required for build. While mencoder is required for k9copy "only" for some activities at runtime.
As I watched on the deb-multimedia is old mplayer including mencoder still available for Jessie. Thus, users can simply add this apt source that is maintained.
What do you think?
Note: While I was not looking, what is the state with Ubuntu 14.10 (Utopic).
deb-multiedia is not really compatable with Debian, It was/is needed for libdvdcss2 . I don't think its the solution for Jessie.
Peace,
Greg
I normally use it on many workstations - currently on Squeeze and Wheezy. Workstation with Jessie I do not have one yet. The problems I observed rarely.
Deb multimedia is very compatible with Debian, Infact Christian is Debian Developer. The issue is his packages have, in the past, caused a conflict situation with official Debian packages. Last year he was asked to stop using the name Debian in his repository. Since he changed his domain name I haven't seen a package from Deb-multimedia that has caused any problems with any official Debian packages. Having said that Debian did make his repository obsolete, for many users, with their change of policy on licences. Since then the only package I use now is libdvdcss2
On 7 September 2014 10:02, Slávek Banko slavek.banko@axis.cz wrote:
On Sunday 07 of September 2014 01:42:19 Greg Madden wrote:
On Saturday 06 September 2014 05:34:27 am you wrote:
On Saturday 06 of September 2014 14:38:35 Michele Calgaro wrote:
Mencoder is part of mplayer1. I'm not sure that we want to maintain mplayer1. Therefore, it seems to me to be more appropriate to replace mencoder by libav-tools (avconv). For now I have not examined how difficult task it is.
Ok Slavek, now I get what you mean. It makes sense to do the switch if possible (I also have no clue how long it would require). As a temporary solution until we complete such task we can still consider adding mencoder to the dependency package list, as we did with libotr2. What do you think?
Cheers Michele
There is one difference from libotr2. For kopete-otr is dependence libotr2 required for build. While mencoder is required for k9copy "only" for some activities at runtime.
As I watched on the deb-multimedia is old mplayer including mencoder still available for Jessie. Thus, users can simply add this apt source that is maintained.
What do you think?
Note: While I was not looking, what is the state with Ubuntu 14.10 (Utopic).
deb-multiedia is not really compatable with Debian, It was/is needed for libdvdcss2 . I don't think its the solution for Jessie.
Peace,
Greg
I normally use it on many workstations - currently on Squeeze and Wheezy. Workstation with Jessie I do not have one yet. The problems I observed rarely.
-- Slavek
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Saturday 06 September 2014 04:02:35 pm you wrote:
On Sunday 07 of September 2014 01:42:19 Greg Madden wrote:
On Saturday 06 September 2014 05:34:27 am you wrote:
On Saturday 06 of September 2014 14:38:35 Michele Calgaro wrote:
Mencoder is part of mplayer1. I'm not sure that we want to maintain mplayer1. Therefore, it seems to me to be more appropriate to replace mencoder by libav-tools (avconv). For now I have not examined how difficult task it is.
Ok Slavek, now I get what you mean. It makes sense to do the switch if possible (I also have no clue how long it would require). As a temporary solution until we complete such task we can still consider adding mencoder to the dependency package list, as we did with libotr2. What do you think?
Cheers Michele
There is one difference from libotr2. For kopete-otr is dependence libotr2 required for build. While mencoder is required for k9copy "only" for some activities at runtime.
As I watched on the deb-multimedia is old mplayer including mencoder still available for Jessie. Thus, users can simply add this apt source that is maintained.
What do you think?
Note: While I was not looking, what is the state with Ubuntu 14.10 (Utopic).
deb-multiedia is not really compatable with Debian, It was/is needed for libdvdcss2 . I don't think its the solution for Jessie.
Peace,
Greg
I normally use it on many workstations - currently on Squeeze and Wheezy. Workstation with Jessie I do not have one yet. The problems I observed rarely.
I lack concrete examples of conflicts at this time, it beens to long since I made the deision to stop using deb-multimedia, I could entertain the idea it is different now.
How do users of Jessie+ TDE learn about adding deb-multimedia to sources.list?
Maintaining multiple addition sources is not desirable, Debian only nables 'main' in a default install.
Can TDE provide mencoder-trinity in is repo?
Note: While I was not looking, what is the state with Ubuntu 14.10 (Utopic).
I searched around a while and it seems that mencoder was dropped in Utopic as well. Not sure if the mencoder package from deb-multimedia would install in Ubuntu, since some dependency may not be satisfy. If it installs ok, we can probably stick with the package from deb-multimedia for the time being. If not, we probably need to add mencoder to the depencency package list. Could you do a test on an Utopic installation?
Cheers Michele
On Sunday 07 of September 2014 09:06:17 Michele Calgaro wrote:
Note: While I was not looking, what is the state with Ubuntu 14.10 (Utopic).
I searched around a while and it seems that mencoder was dropped in Utopic as well. Not sure if the mencoder package from deb-multimedia would install in Ubuntu, since some dependency may not be satisfy. If it installs ok, we can probably stick with the package from deb-multimedia for the time being. If not, we probably need to add mencoder to the depencency package list. Could you do a test on an Utopic installation?
Cheers Michele
Tested, can not be used jessie source for utopic. So ok, on the basis of the package deb-multimedia package I prepare packages for jessie and utopic for Trinity build-deps.
Tested, can not be used jessie source for utopic. So ok, on the basis of the package deb-multimedia package I prepare packages for jessie and utopic for Trinity build-deps.
Ok. If we call the package mencoder as the original one (without the -trinity extension), then we do not need to do any change in k9copy control file. Jessie and Utopic users will use our package, while older distros can install either the original mencoder or our version (if we choose to build it for all distros as well). Thanks for testing. Cheers Michele
On Sunday 07 of September 2014 15:35:52 Michele Calgaro wrote:
Tested, can not be used jessie source for utopic. So ok, on the basis of the package deb-multimedia package I prepare packages for jessie and utopic for Trinity build-deps.
Ok. If we call the package mencoder as the original one (without the -trinity extension), then we do not need to do any change in k9copy control file. Jessie and Utopic users will use our package, while older distros can install either the original mencoder or our version (if we choose to build it for all distros as well). Thanks for testing. Cheers Michele
Yes, this is exactly my intention. In addition, I want to set jessie version so that the package will be considered older than versions from deb-multimedia.
I have limited dependencies in mplayer-dmo to the versions contained in the distributions, so it was not necessary to include additional packages from deb-multimedia into Trinity apt source.
-
Greg Madden -
Ilya Dogolazky -
Michael . -
Michele Calgaro -
Slávek Banko