fonts-nanum,Korean Nanum-Fonts

[Ulrich Moser]

fonts-namum has dependencies ubuntu-mate core and ubuntu-mate desktop
although these are not listed in the Dependencies tab of the package
properties. This dependencies should be removed.

Regards
Ulrich
-- 


ZPK Logo

*ZPK Moser UG* (haftungsbeschränkt)

Ulrich Moser - Geschäftsführer
Schlossstraße 7 - 78244 Gottmadingen

Tel.:   +49 (0)7734 395 494
Mobil:  +49 (0)179 915 54 18
Fax:+49 (0)7734 395 303
Mail:   ulrich.mo...@zpk-moser.de
Web:www.zpk-moser.de

HRB 707123 Amtsgericht Freiburg
USt.-ID DE278278037



0xAC98C870.asc
Description: application/pgp-keys
-- 
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: fonts-nanum,Korean Nanum-Fonts

[Gunnar Hjalmarsson]

On 2017-03-13 11:03, Ulrich Moser wrote:

fonts-namum has dependencies ubuntu-mate core and ubuntu-mate
desktop although these are not listed in the Dependencies tab of the
package properties.


Ubuntu MATE recommends (not depends on) fonts-nanum. So do most of the 
desktop meta packages:


$ apt rdepends fonts-nanum
fonts-nanum
Reverse Depends:
  Suggests: poppler-data (>= 20131007~)
  Recommends: xubuntu-desktop
  Recommends: ubuntustudio-desktop
  Recommends: ubuntukylin-desktop
  Depends: ubuntu-touch
  Recommends: ubuntu-mate-desktop
  Recommends: ubuntu-mate-core
  Recommends: ubuntu-gnome-desktop
  Recommends: ubuntu-budgie-desktop
  Suggests: tuxpaint-data
  Depends: renpy
 |Suggests: mlterm-tiny
 |Suggests: mlterm
  Depends: lubuntu-qt-desktop
  Depends: lubuntu-desktop
  Recommends: ltsp-client
  Recommends: kubuntu-full
  Recommends: kubuntu-desktop
  Suggests: fonts-nanum-eco
  Depends: firefox-testsuite
  Recommends: ubuntu-desktop
  Recommends: fonts-nanum-extra

I'm not sure which dependencies tab you refer to, but it's shown here:
http://packages.ubuntu.com/zesty/ubuntu-mate-desktop


This dependencies should be removed.


Why?

--
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

NEW: Source PPA grouping for bileto tickets during proposed-migration

[Robert Park]

Hi all,

On Friday we went live with the actually-working version of source PPA
grouping in proposed-migration.

What this means:

If you have a bileto ticket with 2 or more packages in it, and this
gets published, you should now no longer see some of your packages
migrate to Release pocket while some stay stuck behind in Proposed
pocket. Now nothing will migrate to Release pocket until the entire
PPA is ready to migrate to release pocket.

If you're looking in update_excuses, you'll now start seeing "Blocking
because foo-package from the same PPA
~ci-train-ppa-service/+archive/ubuntu/1234 is invalid"

Enjoy!

-- 
robru

-- 
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

issues installing Lubuntu 17.04 beta 1

[B S]

I installed Lubuntu 17.04 beta 1 on a private label Intel NUC with a core 
i5-6260U and a 250G SSD that came with Windows 10.  I did not use wifi, though 
the system has it.  Hooked it up to the LAN with an ethernet patch cable.  The 
issues I ran into are:


Twice, DNS didn't work after booting from the installation media (which I put 
on a USB flash drive).  The system connected to the network.  It even found 
some DNS servers.  ping 8.8.8.8 worked.  But somehow, DNS queries weren't 
working.  ping google.com did not work.  I edited /etc/resolv.conf to add 
8.8.8.8 as a nameserver, and then it worked.


Apparently, the first time I tried to install, it didn't detect that the system 
is UEFI.  It asked me where to install GRUB.  I am not familiar with UEFI, and 
didn't understand that it wasn't supposed to ask.  I told it to put GRUB on 
/dev/sda.  That didn't work, and I tried installing again, this time putting 
GRUB on /dev/sda1.  That didn't work either, and I tried to edit the Windows 
boot with bcdedit.  Didn't work, and broke Windows.  Ended up zeroing out the 
start of the SSD, and scrounging up an external DVD drive so I could do a fresh 
install of Windows 10. Then I tried installing Lubuntu again, from the flash 
drive, and that time it worked, didn't ask where to install GRUB.  From what I 
read, seems it's not easy to tell if a UEFI system is in UEFI mode, or in 
legacy BIOS mode.  To me, it doesn't make sense that this is hard.  Surely UEFI 
has some identifying feature to distinguish it from BIOS, that is easily 
queried, if only one knows how?


Finally, I used rsync to copy my files.  Some power saving, screen locking, 
and/or hibernating feature kicked in after a while (15 minutes?) and caused 
rsync to abort.


That's all the issues I've run into so far.  No doubt I'll see more problems 
when I start trying to use it.
-- 
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: issues installing Lubuntu 17.04 beta 1

[Colin Law]

The DNS problem could be this, particularly if you are using a fairly old
router.

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609546

Colin

On 13 March 2017 at 16:40, B S  wrote:

> I installed Lubuntu 17.04 beta 1 on a private label Intel NUC with a core
> i5-6260U and a 250G SSD that came with Windows 10.  I did not use wifi,
> though the system has it.  Hooked it up to the LAN with an ethernet patch
> cable.  The issues I ran into are:
>
>
> Twice, DNS didn't work after booting from the installation media (which I
> put on a USB flash drive).  The system connected to the network.  It even
> found some DNS servers.  ping 8.8.8.8 worked.  But somehow, DNS queries
> weren't working.  ping google.com did not work.  I edited
> /etc/resolv.conf to add 8.8.8.8 as a nameserver, and then it worked.
>
>
> Apparently, the first time I tried to install, it didn't detect that the
> system is UEFI.  It asked me where to install GRUB.  I am not familiar
> with UEFI, and didn't understand that it wasn't supposed to ask.  I told
> it to put GRUB on /dev/sda.  That didn't work, and I tried installing
> again, this time putting GRUB on /dev/sda1.  That didn't work either, and I
> tried to edit the Windows boot with bcdedit.  Didn't work, and broke
> Windows.  Ended up zeroing out the start of the SSD, and scrounging up an
> external DVD drive so I could do a fresh install of Windows 10. Then I
> tried installing Lubuntu again, from the flash drive, and that time it
> worked, didn't ask where to install GRUB.  From what I read, seems it's not
> easy to tell if a UEFI system is in UEFI mode, or in legacy BIOS mode.  To
> me, it doesn't make sense that this is hard.  Surely UEFI has some
> identifying feature to distinguish it from BIOS, that is easily queried, if
> only one knows how?
>
>
> Finally, I used rsync to copy my files.  Some power saving, screen
> locking, and/or hibernating feature kicked in after a while (15 minutes?)
> and caused rsync to abort.
>
>
> That's all the issues I've run into so far.  No doubt I'll see more
> problems when I start trying to use it.
>
> --
> 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
>
>
-- 
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