[Ubuntustudio-bugs] [Bug 2062428] Re: Kubuntu 24.04 daily builds - Install randomly hangs/fails/crashes on systems with less than ~3GB of RAM

[Steve Langasek]

Walter, you assigned this to livecd-rootfs, but that's a dead end.  The
memory consumption of the livecd is largely a property of the software
it runs.  Ubuntu and Kubuntu might both fail now on a system with 3GiB
of RAM, but any fix to get under that threshold is likely to be flavor-
specific and not a function of the image build system.

This is not necessarily a calamares issue, but I'm reopening a task
there so that it's somewhat on the radar of Kubuntu folks.

** Also affects: calamares-settings-ubuntu (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calamares-settings-ubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/2062428

Title:
  Kubuntu 24.04 daily builds - Install randomly hangs/fails/crashes on
  systems with less than ~3GB of RAM

Status in calamares-settings-ubuntu package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Invalid

Bug description:
  Since around introduction of Kernel 6.8 to Daily builds, installation
  of Kubuntu / Ubuntu / Ubuntu-Mate builds randomly hangs(mostly),
  crashes or fails on systems with less than 3GB of RAM.

  When the system hangs, VM indicates heavy CPU and CDROM usage. My bet
  is on Kernel killing itself trying to "juggle" data between OverlayFS
  and Filesystem cache without a way to swap-out since someone decided
  that removing zram-config from livefs was a good idea.

  When the system doesn't hang, I can see kernel OOM killing random
  processes like calamares, cryptsetup etc.

  I had 100% success of installing Kubuntu 24.04 daily on VMs with 3GB, 75% 
with 2.5GB and almost 0% on 2GB VMs.
  Lvecd installers prior to Linux 6.8 had no issues with 2GB VMs.

  Once the system is installed it functions satisfactory with 2GB.

  I believe adding zram-config to livefs/casper would allow installation
  on systems with only 2GB of RAM.

  Tested over a couple of months with many snapshots of 24.04 Daily
  builds for Ubuntu, Kubutu and Ubuntu-Mate on VirtualBox and KVM/Qemu
  with default settings except enabled EFI.

  PS,
  The issue is not unique to calamares but I am filing it here since that's 
what I was asked to do by people on #kubuntu-devel and to be honest at the 
moment I don't care about anything but being able to test Kubuntu images on 
small VMs.

  P.P.S
  Specific example #1 (bad):
  * Kubuntu snapshot from 
http://cdimage.ubuntu.com/kubuntu/daily-live/20240418.1/
  * VirtualBox 7.1.16 - VM - Default Ubuntu Profile, Enable EFI, Adjust RAM to 
2.5GB
  * Boot LiveCD, Choose Try option
  * Start Install with default settings
  * Observe Calamares existing mid install without any visual indication
  * Logs show OOM-Killer killing cryptsetup and Calamares

  Specific example #2 (Good):
  * Kubuntu snapshot from 
http://cdimage.ubuntu.com/kubuntu/daily-live/20240418.1/
  * VirtualBox 7.1.16 - VM - Default Ubuntu Profile, Enable EFI, Adjust RAM to 
2.5GB
  * Boot LiveCD, Choose Try option
  * >> Install zram-config, start zram-config service <<
  * Start Install with default settings
  * Observe Calamares finishing install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2062428/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2059075] [NEW] proposed-migration for rakarrack 0.6.1-8build1

[Steve Langasek]

Public bug reported:

rakarrack 0.6.1-8build1 is built in -proposed but not on armhf.  This
will not block migration because armhf binaries are being removed from
the release pocket, but unless addressed will regress armhf availability
of this package in 24.04 LTS.

** Affects: rakarrack (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: time-t update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to rakarrack in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/2059075

Title:
  proposed-migration for rakarrack 0.6.1-8build1

Status in rakarrack package in Ubuntu:
  New

Bug description:
  rakarrack 0.6.1-8build1 is built in -proposed but not on armhf.  This
  will not block migration because armhf binaries are being removed from
  the release pocket, but unless addressed will regress armhf
  availability of this package in 24.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rakarrack/+bug/2059075/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2058813] [NEW] proposed-migration for gimp-plugin-registry 9.20200928build2

[Steve Langasek]

Public bug reported:

gimp-plugin-registry 9.20200928build2 is stuck in -proposed.  It fails
to build on armhf due to implicit function declarations.

** Affects: gimp-plugin-registry (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: time-t update-excuse

** Description changed:

- gimp-plugin-registry 9.20200928build2 is stuck in -proposed.
+ gimp-plugin-registry 9.20200928build2 is stuck in -proposed.  It fails
+ to build on armhf due to implicit function declarations.

** Tags added: time-t

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to gimp-plugin-registry in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/2058813

Title:
  proposed-migration for gimp-plugin-registry 9.20200928build2

Status in gimp-plugin-registry package in Ubuntu:
  New

Bug description:
  gimp-plugin-registry 9.20200928build2 is stuck in -proposed.  It fails
  to build on armhf due to implicit function declarations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp-plugin-registry/+bug/2058813/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2056375] Re: Ubuntu Studio ISO fails to build: "/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'."

[Steve Langasek]

We have a successful daily build without mokutil migrating, so marking
this invalid.

https://cdimage.ubuntu.com/ubuntustudio/dvd/20240307.2/

(mokutil anyway is blocked by openssl transition which will take a bit
yet.)

** Changed in: mokutil (Ubuntu Noble)
   Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2056375

Title:
  Ubuntu Studio ISO fails to build: "/usr/sbin/grub-probe: error: failed
  to get canonical path of `overlay'."

Status in mokutil package in Ubuntu:
  Invalid
Status in mokutil source package in Noble:
  Invalid

Bug description:
  Full build log is at
  
https://launchpadlibrarian.net/717896339/buildlog_ubuntu_noble_amd64_ubuntustudio_BUILDING.txt.gz.
  Relevant section:

  Preconfiguring packages ...
  Fetched 692 MB in 4s (169 MB/s)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%
  (Reading database ... 15%
  (Reading database ... 20%
  (Reading database ... 25%
  (Reading database ... 30%
  (Reading database ... 35%
  (Reading database ... 40%
  (Reading database ... 45%
  (Reading database ... 50%
  (Reading database ... 55%
  (Reading database ... 60%
  (Reading database ... 65%
  (Reading database ... 70%
  (Reading database ... 75%
  (Reading database ... 80%
  (Reading database ... 85%
  (Reading database ... 90%
  (Reading database ... 95%
  (Reading database ... 100%
  (Reading database ... 347331 files and directories currently installed.)
  Removing os-prober (1.81ubuntu3) ...
  Removing memtest86+ (7.00-1) ...
  Removing ubuntustudio-lowlatency-settings (24.04.14) ...
  Removing plymouth-theme-ubuntustudio (24.04.1) ...
  update-alternatives: removing manually selected alternative - switching 
default.plymouth to auto mode
  update-alternatives: using /usr/share/plymouth/themes/bgrt/bgrt.plymouth to 
provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in auto 
mode
  update-alternatives: using 
/usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth to provide 
/usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode
  update-initramfs: deferring update (trigger activated)
  /usr/sbin/grub-probe: error: failed to get canonical path of `overlay'.
  dpkg: error processing package plymouth-theme-ubuntustudio (--remove):
   installed plymouth-theme-ubuntustudio package post-removal script subprocess 
returned error exit status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   plymouth-theme-ubuntustudio
  Processing was halted because there were too many errors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mokutil/+bug/2056375/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2056375] Re: Ubuntu Studio ISO fails to build: "/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'."

[Steve Langasek]

It's not clear why installing mokutil would force install of the
libefivar1 real package, when libefivar1t64 has a versioned Provides: of
it; or why this would happen on one particular flavor when the grub code
is rather generic across flavors.  But if bumping mokutils through
resolves it, we can remove the armhf binary to get this done sooner
rather than later.

** Tags removed: rls-nn-incoming
** Tags added: foundations-todo

** Also affects: mokutil (Ubuntu Noble)
   Importance: Critical
   Status: Fix Committed

** Changed in: mokutil (Ubuntu Noble)
 Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2056375

Title:
  Ubuntu Studio ISO fails to build: "/usr/sbin/grub-probe: error: failed
  to get canonical path of `overlay'."

Status in mokutil package in Ubuntu:
  Fix Committed
Status in mokutil source package in Noble:
  Fix Committed

Bug description:
  Full build log is at
  
https://launchpadlibrarian.net/717896339/buildlog_ubuntu_noble_amd64_ubuntustudio_BUILDING.txt.gz.
  Relevant section:

  Preconfiguring packages ...
  Fetched 692 MB in 4s (169 MB/s)
  (Reading database ... 
  (Reading database ... 5%
  (Reading database ... 10%
  (Reading database ... 15%
  (Reading database ... 20%
  (Reading database ... 25%
  (Reading database ... 30%
  (Reading database ... 35%
  (Reading database ... 40%
  (Reading database ... 45%
  (Reading database ... 50%
  (Reading database ... 55%
  (Reading database ... 60%
  (Reading database ... 65%
  (Reading database ... 70%
  (Reading database ... 75%
  (Reading database ... 80%
  (Reading database ... 85%
  (Reading database ... 90%
  (Reading database ... 95%
  (Reading database ... 100%
  (Reading database ... 347331 files and directories currently installed.)
  Removing os-prober (1.81ubuntu3) ...
  Removing memtest86+ (7.00-1) ...
  Removing ubuntustudio-lowlatency-settings (24.04.14) ...
  Removing plymouth-theme-ubuntustudio (24.04.1) ...
  update-alternatives: removing manually selected alternative - switching 
default.plymouth to auto mode
  update-alternatives: using /usr/share/plymouth/themes/bgrt/bgrt.plymouth to 
provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in auto 
mode
  update-alternatives: using 
/usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth to provide 
/usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode
  update-initramfs: deferring update (trigger activated)
  /usr/sbin/grub-probe: error: failed to get canonical path of `overlay'.
  dpkg: error processing package plymouth-theme-ubuntustudio (--remove):
   installed plymouth-theme-ubuntustudio package post-removal script subprocess 
returned error exit status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   plymouth-theme-ubuntustudio
  Processing was halted because there were too many errors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mokutil/+bug/2056375/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2056313] Re: Lubuntu-24.04 Installation failed

[Steve Langasek]

** Project changed: ubuntu-cdimage => calamares (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calamares in Ubuntu.
https://bugs.launchpad.net/bugs/2056313

Title:
  Lubuntu-24.04 Installation failed

Status in calamares package in Ubuntu:
  New

Bug description:
  Fresh installation of Lubuntu 24.04 (Noble Numbat) Daily Build  on
  VirtualBox 7 on March-06-2024. Installation failed. See attached
  screenshot. The same happend on March-04-2024.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2056313/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2047656] Re: [SRU] Players terminate after stopping and restarting

[Steve Langasek]

> * Begin midi playback in any midi player using fluidsynth from the
terminal

This is not a reproducible test case that can be actioned by someone
just reading the bug.  Please provide a specific test case showing how
to reproduce the failure.

If possible, it would be best to also provide a reference midi file to
use.

** Changed in: fluidsynth (Ubuntu Mantic)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to fluidsynth in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/2047656

Title:
  [SRU] Players terminate after stopping and restarting

Status in fluidsynth package in Ubuntu:
  Fix Released
Status in fluidsynth source package in Mantic:
  Incomplete
Status in fluidsynth source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop
  of playback of a midi song, causing issues for a multitude of players
  including EasyABC. This will cause said player to be unable to
  playback again and perhaps even crash. See
  https://github.com/FluidSynth/fluidsynth/issues/1272, fix in
  
https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055.
  This is the included patch with the upload of
  2.3.3-2.1ubuntu-0.23.10.1

  [ Test Case ]

  * Begin midi playback in any midi player using fluidsynth from the
  terminal

  * Stop midi playback

  * Attempt start again

  * Error in terminal: fluidsynth: error: The maximum playback duration
  has been reached. Terminating player!

  [ What could go wrong ]

  This is actually a fix for a regression that was found in version
  2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble.
  I think the only thing that can go wrong here is that this patch is
  not the actual fix and we need to find more solutions within.

  I have tested this in my PPA and it *seems* to fix it, but it would be
  nice if the original reporter could verify once this lands in
  proposed.

  [ Other information ]

  Included below is the original report, in which case the reporter
  deduces that the problem is the binary being spat-out is the 2.3.2
  version from the 2.3.3 sources. This is not the case, as it appears to
  be confusion due to the -2.1 Debian revision number. I assure, this is
  definitely the 2.3.3, and the bug, per the github link in the Impact
  section, is pertinent to this version.

  ---

  The latest package of fluidsynth should include the sources from
  version 2.3.3 but the binary includes only version 2.3.2

  This version has a bug (see
  https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to
  problems in EasyABC.

  Please include the latest version 2.3.3 from upstream in the ubuntu
  package.

  --

  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  $ apt-cache policy libfluidsynth3
  libfluidsynth3:
    Installiert:   2.3.3-2.1
    Installationskandidat: 2.3.3-2.1
    Versionstabelle:
   *** 2.3.3-2.1 500
  500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

[Steve Langasek]

I do not see what this change was supposed to solve.  I disagree with
the *existing* version check in germinate, and do not want to see more
of these - it imposes needless barriers for updating the metapackages.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/2017786

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  New
Status in kubuntu-meta package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989611] Update Released

[Steve Langasek]

The verification of the Stable Release Update for plasma-distro-release-
notifier has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989611

Title:
  [SRU] plasma-distro-release-notifier for Jammy, Focal

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in plasma-distro-release-notifier package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta source package in Focal:
  Confirmed
Status in plasma-distro-release-notifier source package in Focal:
  Fix Released
Status in ubuntustudio-meta source package in Focal:
  Invalid
Status in kubuntu-meta source package in Jammy:
  Confirmed
Status in plasma-distro-release-notifier source package in Jammy:
  Fix Released
Status in ubuntustudio-meta source package in Jammy:
  In Progress
Status in kubuntu-meta source package in Kinetic:
  Fix Released
Status in plasma-distro-release-notifier source package in Kinetic:
  Fix Released
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * The status-quo for current Ubuntu Studio and Kubuntu users (all
  users of Ubuntu running the KDE Plasma Desktop) is that there is no
  mechanism to warn them of new releases. This is especially problematic
  for LTS releases when a new LTS release comes out, or if it is set to
  look for a new regular release.

   * This is resolved by a new package included in Kinetic - plasma-
  distro-release-notifier - which uses the backend of update-manager-
  common to identify whether or not a new version of Ubuntu has been
  released.

  [ Test Plan ]

   * Install Ubuntu Studio 22.04 -OR- Kubuntu 22.04 -OR- Kubuntu 20.04

   * Notice 20.04 does not notify of a new release despite being set to
  "lts" in /etc/update-manager/release-upgrades.

   * For 22.04 releases, change /etc/update-manager/release-upgrades
  "Prompt=" line to "Prompt=normal"

   * Also, notice no prompt for updates on 22.04 releases.

  [ Where problems could occur ]

   * This will require introducing an entirely new package and adding
  the package to the kubuntu-desktop metapackage and the ubuntustudio-
  desktop metapackage for Jammy, and the kubuntu-desktop metapackage for
  focal. Things could go wrong if there is a failure to upgrade.

   * Additional failures can happen if the patch in d/patches of plasma-
  distro-release-notifier for the version number fails to point to the
  correct version number upon upload. This is easily fixed, but also
  something to keep an eye on and would be human error.

  [ Other Info ]

   * plasma-distro-release-notifier was initially tested to work inside
  of 20.04 with positive results. The same is expected for 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989611/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1990823] Re: Drop package gsfonts

[Steve Langasek]

Removing packages:
gsfonts 1:8.11+urwcyr1.0.7~pre44-4.5 in kinetic
Comment: (From Debian) RoQA; binaries now built by fonts-urw-base35; Debian bug 
#1020503
Remove [y|N]? y


** Changed in: gsfonts (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to gsfonts in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1990823

Title:
  Drop package gsfonts

Status in gsfonts package in Ubuntu:
  Fix Released
Status in gsfonts package in Debian:
  Fix Released

Bug description:
  Binary package gsfonts is supplied by source package fonts-urw-base35
  20200910-4 which is currently stuck in kinetic-proposed.

  Debian has remove source package gsfonts with #1020503.

  We should do the same.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsfonts/+bug/1990823/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1990823] Re: Drop package gsfonts

[Steve Langasek]

ok, figured out what was meant regarding the binary package.

** Changed in: gsfonts (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to gsfonts in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1990823

Title:
  Drop package gsfonts

Status in gsfonts package in Ubuntu:
  Fix Released
Status in gsfonts package in Debian:
  Fix Released

Bug description:
  Binary package gsfonts is supplied by source package fonts-urw-base35
  20200910-4 which is currently stuck in kinetic-proposed.

  Debian has remove source package gsfonts with #1020503.

  We should do the same.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsfonts/+bug/1990823/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1990823] Re: Drop package gsfonts

[Steve Langasek]

Also:

$ reverse-depends src:gsfonts -a source
Reverse-Testsuite-Triggers
* botch (for gsfonts)
* gscan2pdf (for gsfonts)
* imagemagick   (for gsfonts)
* lemonldap-ng  (for gsfonts)
* php-imagick   (for gsfonts)

Reverse-Build-Depends
* axiom (for gsfonts)
* drawtiming(for gsfonts)
* gloox (for gsfonts)
* graphicsmagick(for gsfonts)
* gri   (for gsfonts)
* groff (for gsfonts)
* hylafax   (for gsfonts)
* imagemagick   (for gsfonts)
* ipe   (for gsfonts)
* lilypond  (for gsfonts)
* minexpert2(for gsfonts)
* moviepy   (for gsfonts)
* redmine   (for gsfonts)
* routino   (for gsfonts)
* ruby-gruff(for gsfonts)
* ruby-mojo-magick  (for gsfonts)
* ruby-rmagick  (for gsfonts)
* scalable-cyrfonts (for gsfonts)

Reverse-Build-Depends-Indep
* gprolog   (for gsfonts)
* gscan2pdf (for gsfonts)
* lemonldap-ng  (for gsfonts)
* libforms  (for gsfonts)
* sdcc  (for gsfonts)

Reverse-Build-Depends-Arch
* botch (for gsfonts)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to gsfonts in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1990823

Title:
  Drop package gsfonts

Status in gsfonts package in Ubuntu:
  Triaged
Status in gsfonts package in Debian:
  Fix Released

Bug description:
  Binary package gsfonts is supplied by source package fonts-urw-base35
  20200910-4 which is currently stuck in kinetic-proposed.

  Debian has remove source package gsfonts with #1020503.

  We should do the same.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsfonts/+bug/1990823/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1990823] Re: Drop package gsfonts

[Steve Langasek]

$ reverse-depends src:gsfonts
Reverse-Recommends
* libgraphicsmagick-q16-3 [amd64 arm64 armhf ppc64el s390x]
* liblemonldap-ng-portal-perl   (for gsfonts)
* libmagickcore-6.q16-6 (for gsfonts)
* libmagickcore-6.q16hdri-6 (for gsfonts)
* texworks [amd64 arm64 armhf ppc64el s390x]
* ubuntustudio-fonts [amd64 arm64 armhf ppc64el s390x]

Reverse-Depends
* abiword [amd64 arm64 armhf ppc64el s390x]
* dvd-slideshow (for gsfonts)
* gnumeric [amd64 arm64 armhf ppc64el s390x]
* gsfonts-x11   (for gsfonts)
* hylafax-client [amd64 arm64 armhf ppc64el s390x]
* ipe [amd64 arm64 armhf ppc64el s390x]
* ruby-gruff(for gsfonts)
* ruby-mojo-magick  (for gsfonts)
* webmagick (for gsfonts)

Packages without architectures listed are reverse-dependencies in:
amd64, arm64, armhf, i386, ppc64el, s390x


** Changed in: gsfonts (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to gsfonts in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1990823

Title:
  Drop package gsfonts

Status in gsfonts package in Ubuntu:
  Triaged
Status in gsfonts package in Debian:
  Fix Released

Bug description:
  Binary package gsfonts is supplied by source package fonts-urw-base35
  20200910-4 which is currently stuck in kinetic-proposed.

  Debian has remove source package gsfonts with #1020503.

  We should do the same.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsfonts/+bug/1990823/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983862] Re: RM: Audacity 2.4.2 FTBFS with ffmpeg 5.x)

[Steve Langasek]

Removing packages from kinetic:
audacity 2.4.2~dfsg0-5 in kinetic
audacity 2.4.2~dfsg0-5 in kinetic amd64
audacity 2.4.2~dfsg0-5 in kinetic arm64
audacity 2.4.2~dfsg0-5 in kinetic armhf
audacity 2.4.2~dfsg0-5 in kinetic ppc64el
audacity 2.4.2~dfsg0-5 in kinetic riscv64
audacity 2.4.2~dfsg0-5 in kinetic s390x
audacity-data 2.4.2~dfsg0-5 in kinetic amd64
audacity-data 2.4.2~dfsg0-5 in kinetic arm64
audacity-data 2.4.2~dfsg0-5 in kinetic armhf
audacity-data 2.4.2~dfsg0-5 in kinetic i386
audacity-data 2.4.2~dfsg0-5 in kinetic ppc64el
audacity-data 2.4.2~dfsg0-5 in kinetic riscv64
audacity-data 2.4.2~dfsg0-5 in kinetic s390x
Comment: FTBFS with ffmpeg 5; LP: #1983862
1 package successfully removed.
Removing packages from kinetic-proposed:
audacity 2.4.2~dfsg0-5build1 in kinetic
Comment: FTBFS with ffmpeg 5; LP: #1983862
1 package successfully removed.


** Changed in: audacity (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1983862

Title:
  RM: Audacity 2.4.2 FTBFS with ffmpeg 5.x)

Status in audacity package in Ubuntu:
  Fix Released
Status in audacity package in Debian:
  Confirmed

Bug description:
  Audacity is a very high-profile, cross-platform application. As it
  stands. Audacity has been stagnant at 2.4.2 for several releases. 3.1
  has been out for some time and is compatible with ffmpeg 5.

  At this point, we are finding our hand forced. 2.4.2 is incompatible
  with ffmpeg 5, and as such we must upgrade, patch, or remove. Users of
  Audacity would much rather see an upgrade, as I have seen in bug
  reports as of late, or in the #ubuntustudio chat.

  The biggest hurdles have been the telemetry which can be disabled by
  default as discussed via
  https://github.com/audacity/audacity/discussions/889.

  Note that the biggest requirement, wxwidgets, only recently got
  uploaded post-Feature Freeze, which otherwise would have made this FFe
  moot. This bug has been being worked on since prior to FFe, so IMO
  this is a bug fix that just happens to carry features with it, similar
  to what you'd find if wxwidgets had been uploaded prior to Feature
  Freeze.

  Basically, I'm hoping that some of the logic that can be applied here
  is that the exception is based mostly on the late upload of wxwidgets
  which was beyond the control of those involved.

  I think that having new features in an application is a better option
  than having it removed completely for the sake of a feature freeze in
  this case, especially when it's as high-profile of an application as
  this one.

  
  
  Original Description:

  https://launchpadlibrarian.net/615233650/buildlog_ubuntu-kinetic-
  amd64.audacity_2.4.2~dfsg0-5build1_BUILDING.txt.gz

  (...)
  In file included from /<>/src/AudacityApp.cpp:82:
  /<>/src/FFmpeg.h: In constructor ‘AVPacketEx::AVPacketEx()’:
  /<>/src/FFmpeg.h:892:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    892 |   av_init_packet(this);
    |   ~~^~
  In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
   from /<>/src/FFmpeg.h:53:
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~
  /<>/src/FFmpeg.h: In member function ‘void AVPacketEx::reset()’:
  /<>/src/FFmpeg.h:919:7: error: ‘av_free_packet’ was not declared 
in this scope; did you mean ‘av_new_packet’?
    919 |   av_free_packet(this);
    |   ^~
    |   av_new_packet
  /<>/src/FFmpeg.h: In member function ‘void 
AVPacketEx::steal(AVPacketEx&&)’:
  /<>/src/FFmpeg.h:926:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    926 |   av_init_packet();
    |   ~~^~~
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~

  FFmpeg 5.0 changed the API and it required a big patch for audacity:
  https://github.com/audacity/audacity/pull/3121/files

  Note that patch is on top of master, and Debian/Ubuntu still carry old
  version 2.4.2. To fix this, the package needs to be first updated to
  3.1.3 (or later), and then have that patch applied.

  Upstream issue (now resolved): 
https://github.com/audacity/audacity/issues/2445
  Debian RC bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598

  audacity was removed from debian testing today:
  

[Ubuntustudio-bugs] [Bug 1983862] Re: RM: Audacity 2.4.2 FTBFS with ffmpeg 5.x)

[Steve Langasek]

** Summary changed:

- Audacity 2.4.2 FTBFS with ffmpeg 5.x)
+ RM: Audacity 2.4.2 FTBFS with ffmpeg 5.x)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1983862

Title:
  RM: Audacity 2.4.2 FTBFS with ffmpeg 5.x)

Status in audacity package in Ubuntu:
  Confirmed
Status in audacity package in Debian:
  Confirmed

Bug description:
  Audacity is a very high-profile, cross-platform application. As it
  stands. Audacity has been stagnant at 2.4.2 for several releases. 3.1
  has been out for some time and is compatible with ffmpeg 5.

  At this point, we are finding our hand forced. 2.4.2 is incompatible
  with ffmpeg 5, and as such we must upgrade, patch, or remove. Users of
  Audacity would much rather see an upgrade, as I have seen in bug
  reports as of late, or in the #ubuntustudio chat.

  The biggest hurdles have been the telemetry which can be disabled by
  default as discussed via
  https://github.com/audacity/audacity/discussions/889.

  Note that the biggest requirement, wxwidgets, only recently got
  uploaded post-Feature Freeze, which otherwise would have made this FFe
  moot. This bug has been being worked on since prior to FFe, so IMO
  this is a bug fix that just happens to carry features with it, similar
  to what you'd find if wxwidgets had been uploaded prior to Feature
  Freeze.

  Basically, I'm hoping that some of the logic that can be applied here
  is that the exception is based mostly on the late upload of wxwidgets
  which was beyond the control of those involved.

  I think that having new features in an application is a better option
  than having it removed completely for the sake of a feature freeze in
  this case, especially when it's as high-profile of an application as
  this one.

  
  
  Original Description:

  https://launchpadlibrarian.net/615233650/buildlog_ubuntu-kinetic-
  amd64.audacity_2.4.2~dfsg0-5build1_BUILDING.txt.gz

  (...)
  In file included from /<>/src/AudacityApp.cpp:82:
  /<>/src/FFmpeg.h: In constructor ‘AVPacketEx::AVPacketEx()’:
  /<>/src/FFmpeg.h:892:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    892 |   av_init_packet(this);
    |   ~~^~
  In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
   from /<>/src/FFmpeg.h:53:
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~
  /<>/src/FFmpeg.h: In member function ‘void AVPacketEx::reset()’:
  /<>/src/FFmpeg.h:919:7: error: ‘av_free_packet’ was not declared 
in this scope; did you mean ‘av_new_packet’?
    919 |   av_free_packet(this);
    |   ^~
    |   av_new_packet
  /<>/src/FFmpeg.h: In member function ‘void 
AVPacketEx::steal(AVPacketEx&&)’:
  /<>/src/FFmpeg.h:926:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    926 |   av_init_packet();
    |   ~~^~~
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~

  FFmpeg 5.0 changed the API and it required a big patch for audacity:
  https://github.com/audacity/audacity/pull/3121/files

  Note that patch is on top of master, and Debian/Ubuntu still carry old
  version 2.4.2. To fix this, the package needs to be first updated to
  3.1.3 (or later), and then have that patch applied.

  Upstream issue (now resolved): 
https://github.com/audacity/audacity/issues/2445
  Debian RC bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598

  audacity was removed from debian testing today:
  https://tracker.debian.org/news/1352473/audacity-removed-from-testing/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1983862/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970270] Re: [SRU] LibreOffice localization is not working out of the box

[Steve Langasek]

Hello Aaron, or anyone else affected,

Accepted calamares-settings-ubuntu into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/calamares-settings-
ubuntu/1:22.04.4.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: calamares-settings-ubuntu (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1970270

Title:
  [SRU] LibreOffice localization is not working out of the box

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in calamares-settings-ubuntu source package in Impish:
  Won't Fix
Status in calamares-settings-ubuntu source package in Jammy:
  Fix Committed
Status in calamares-settings-ubuntu source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

   * Due to an error in our configuration, users who install Lubuntu in a
 language other than English end up with LibreOffice still displaying in
 English. The localization package for the user's language must be
 installed manually in order to make LibreOffice display properly.
   
   * This is because our Calamares configuration does not allow the 
 installed system to access the Internet during the installation
 process, as the resolv.conf file of the installed system is left as a
 dangling symlink. While our configuration is designed to automatically
 download and install the proper localization files during installation,
 it fails to actually download those files due to this problem. This bug
 has been verified to affect both Lubuntu and Ubuntu Studio.
 
   * Additionally, the current configuration only installs the LibreOffice
 help files for the chosen language, pulling in the localization package
 as a dependency. This fails on languages such as Icelandic where the
 localization package exists but the help package doesn't.
   
   * This SRU resolves the issue by bind-mounting /run/systemd/resolve from
 the live environment to the installed system. This provides the
 installed system the required resolv.conf file, permitting it to access
 the Internet and install packages during the initial installation
 process. Additionally, the localization package is explicitly pulled
 in, ensuring that the localization package is installed regardless of
 whether or not the help package for the selected language exists.

  [Test plan]

   * Create a VM using Lubuntu or Ubuntu Studio 22.04's ISO, and boot into
 the live environment.
   
   * Double-click the installation icon on the VM's desktop.
   
   * Select a language other than English to install in (I usually use
 German, but French and Icelandic will work too).
 
   * Continue with the rest of the installation in your selected language.
 This bug appears to occur whether you use the defaults or install in
 an advanced configuration.
   
   * When the installation is complete, allow the VM to reboot.
   
   * Once the VM has rebooted, launch any LibreOffice app (like LibreOffice
 writer). You will see the user interface is in English despite your
 language choice during the installation process.
   
   * Boot back into the live ISO of your chosen flavor, and install the
 calamares-settings-ubuntu-common package from this SRU into the live
 environment of the VM.
   
   * Install either the calamares-settings-lubuntu or
 calamares-settings-ubuntustudio package into the live environment of
 the VM, depending on which flavor you are testing.
   
   * Repeat the steps to reproduce the bug. This time, when you launch a
 LibreOffice app after installing the flavor, the user interface will
 appear in your desired language (if the proper localization 

[Ubuntustudio-bugs] [Bug 1983862] Re: FTBFS with ffmpeg 5.x

[Steve Langasek]

Note that there is a freeness concern with the new upstream version,
under new ownership AIUI - as shipped by upstream the code will phone
home to a third party without the user opting in to this behavior.
Please do not package the new upstream version of audacity for Ubuntu
without addressing this (preferably with Debian maintainer involvement).

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1983862

Title:
  FTBFS with ffmpeg 5.x

Status in audacity package in Ubuntu:
  New
Status in audacity package in Debian:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/615233650/buildlog_ubuntu-kinetic-
  amd64.audacity_2.4.2~dfsg0-5build1_BUILDING.txt.gz

  (...)
  In file included from /<>/src/AudacityApp.cpp:82:
  /<>/src/FFmpeg.h: In constructor ‘AVPacketEx::AVPacketEx()’:
  /<>/src/FFmpeg.h:892:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
892 |   av_init_packet(this);
|   ~~^~
  In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
   from /<>/src/FFmpeg.h:53:
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
506 | void av_init_packet(AVPacket *pkt);
|  ^~
  /<>/src/FFmpeg.h: In member function ‘void AVPacketEx::reset()’:
  /<>/src/FFmpeg.h:919:7: error: ‘av_free_packet’ was not declared 
in this scope; did you mean ‘av_new_packet’?
919 |   av_free_packet(this);
|   ^~
|   av_new_packet
  /<>/src/FFmpeg.h: In member function ‘void 
AVPacketEx::steal(AVPacketEx&&)’:
  /<>/src/FFmpeg.h:926:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
926 |   av_init_packet();
|   ~~^~~
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
506 | void av_init_packet(AVPacket *pkt);
|  ^~

  FFmpeg 5.0 changed the API and it required a big patch for audacity:
  https://github.com/audacity/audacity/pull/3121/files

  Note that patch is on top of master, and Debian/Ubuntu still carry old
  version 2.4.2. To fix this, the package needs to be first updated to
  3.1.3 (or later), and then have that patch applied.

  Upstream issue (now resolved): 
https://github.com/audacity/audacity/issues/2445
  Debian RC bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598

  audacity was removed from debian testing today:
  https://tracker.debian.org/news/1352473/audacity-removed-from-testing/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1983862/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

[Steve Langasek]

fuse has been demoted from Ubuntu main in favor of fuse3; it would not
be appropriate to re-promote it to main and expand the security surface
of a default Ubuntu install (fuse is a very security-relevant facility),
and Ubuntu images build only from main.  So this is a wontfix for the
Ubuntu desktop, libfuse2 is not going to be brought back into the
default install and users who want to use libfuse2-dependent AppImages
will need to install this library themselves beforehand.

Our community flavors are free to make their own decisions about whether
to bundle libfuse2 by default, as several of them did before the
release.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ubuntu-meta (Ubuntu Jammy)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1965636

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in ubuntukylin-meta package in Ubuntu:
  Confirmed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta source package in Jammy:
  Fix Released
Status in lubuntu-meta source package in Jammy:
  Confirmed
Status in ubuntu-budgie-meta source package in Jammy:
  Fix Released
Status in ubuntu-meta source package in Jammy:
  Won't Fix
Status in ubuntukylin-meta source package in Jammy:
  Confirmed
Status in ubuntustudio-meta source package in Jammy:
  Fix Released
Status in xubuntu-meta source package in Jammy:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1952918] Re: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed

[Steve Langasek]

since all packages are now rebuild against liburing2 that need to be,
without the fluidsynth dependency, I've re-copied fluidsynth to jammy-
proposed now.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to fluidsynth in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1952918

Title:
  Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed

Status in fluidsynth package in Ubuntu:
  Fix Released

Bug description:
  fluidsynth 2.2.4-2 (currently in jammy-proposed) has a SONAME bump:

    libfluidsynth2 -> libfluidsynth3

  which is a fairly large transition:

  $ reverse-depends -b -l src:fluidsynth | wc -l
  30

  This list of reverse-dependencies has exactly one package in common
  with other two currently ongoing transitions:

  $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l 
src:libidn)
  vlc

  $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l 
src:liburing)
  mpd

  These other two transitions are almost done, hopefully just requiring
  couple of minor uploads (merging a new Debian revision of ghostscript
  and uploading a new Ubuntu revision of exim4 to resolve a components-
  mismatch).

  I think it it would be better to finish these other two transitions
  first, without fluidsynth, and then sync fluidsynth again, to be
  handled separately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1952918/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 998156] Re: GTK Print dialog sends broken custom page size attribute: "PageSize=Custom.Custom.x"

[Steve Langasek]

The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: Ubuntu Precise
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/998156

Title:
  GTK Print dialog sends broken custom page size attribute:
  "PageSize=Custom.Custom.x"

Status in GTK+:
  Fix Released
Status in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Invalid
Status in gimp package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in inkscape package in Ubuntu:
  Invalid
Status in The Precise Pangolin:
  Won't Fix
Status in firefox source package in Precise:
  Invalid
Status in gimp source package in Precise:
  Invalid
Status in gtk+3.0 source package in Precise:
  Won't Fix
Status in inkscape source package in Precise:
  Invalid
Status in The Quantal Quetzal:
  Won't Fix
Status in firefox source package in Quantal:
  Invalid
Status in gimp source package in Quantal:
  Invalid
Status in gtk+3.0 source package in Quantal:
  Fix Released
Status in inkscape source package in Quantal:
  Invalid
Status in gtk+2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  When trying to print a photo, the printer stops with status "rendering 
completed". I have to remove all printing jobs and restart CUPS to be able to 
print again. This error does not occur when printing other documents, i.e. 
simple text.

  I use a HP PhotoSmart b109a connected to a Fritz!Box 7390 wireless
  router ("socket://fritz.box:9100").

  This bug is also present in Debian: http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=664031

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/998156/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 998156] Re: GTK Print dialog sends broken custom page size attribute: "PageSize=Custom.Custom.x"

[Steve Langasek]

The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gtk+3.0 (Ubuntu Precise)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/998156

Title:
  GTK Print dialog sends broken custom page size attribute:
  "PageSize=Custom.Custom.x"

Status in GTK+:
  Fix Released
Status in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Invalid
Status in gimp package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in inkscape package in Ubuntu:
  Invalid
Status in The Precise Pangolin:
  Won't Fix
Status in firefox source package in Precise:
  Invalid
Status in gimp source package in Precise:
  Invalid
Status in gtk+3.0 source package in Precise:
  Won't Fix
Status in inkscape source package in Precise:
  Invalid
Status in The Quantal Quetzal:
  Won't Fix
Status in firefox source package in Quantal:
  Invalid
Status in gimp source package in Quantal:
  Invalid
Status in gtk+3.0 source package in Quantal:
  Fix Released
Status in inkscape source package in Quantal:
  Invalid
Status in gtk+2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  When trying to print a photo, the printer stops with status "rendering 
completed". I have to remove all printing jobs and restart CUPS to be able to 
print again. This error does not occur when printing other documents, i.e. 
simple text.

  I use a HP PhotoSmart b109a connected to a Fritz!Box 7390 wireless
  router ("socket://fritz.box:9100").

  This bug is also present in Debian: http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=664031

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/998156/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 937561] Re: H264 MOV files from Canon DSLR resolution reported as 1920x1088

[Steve Langasek]

The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: libav (Ubuntu Precise)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libav in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/937561

Title:
  H264 MOV files from Canon DSLR resolution reported as 1920x1088

Status in libav package in Ubuntu:
  Fix Released
Status in libav source package in Precise:
  Won't Fix
Status in libav source package in Quantal:
  Fix Released

Bug description:
  I'm not sure exactly when this happened, but sometime since February
  10 or so, GStreamer is reporting these 1920x1080 videos as being
  1920x1088.  This might be an libavcodecs but, not sure yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gstreamer0.10-ffmpeg 0.10.13-1
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  ApportVersion: 1.92-0ubuntu1
  Architecture: amd64
  Date: Tue Feb 21 01:05:01 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120122)
  SourcePackage: gstreamer0.10-ffmpeg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/937561/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 983835] Re: jackdbus sigsegv handling itself crashes [SRU]

[Steve Langasek]

The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: jackd2 (Ubuntu Precise)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to jackd2 in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: jackd2
https://bugs.launchpad.net/bugs/983835

Title:
  jackdbus sigsegv handling itself crashes [SRU]

Status in jackd2 package in Ubuntu:
  Expired
Status in jackd2 source package in Precise:
  Won't Fix
Status in jackd2 source package in Quantal:
  Expired

Bug description:
  [Problem]
  <1-2 sentence summary of the issue>

  [Impact]
  

  [Development Fix]
  

  [Stable Fix]
  

  [Text Case]
  
  1.
  2.
  3.
  Broken Behavior: 
  Fixed Behavior: 

  [Regression Potential]
  

  [Original Report]
  On shutdown (calling stop from qjackctl) jackdbus crashes. The (first?) error 
seems to be in the sigsegv chain itself. See attached patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: jackd2 1.9.8~dfsg.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 17 12:26:00 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120103)
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/983835/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1945855] Re: Please remove inkscape from the i386 whitelist

[Steve Langasek]

The decision was taken based on community feedback to keep i386 around
for binary compatibility.

That includes compatibility with i386-only packages in the Ubuntu
archive itself, for which ports to other architectures are not
forthcoming.

Given that inkscape is building fine on i386, I don't see any reason
that would prompt reconsidering this for the packages in question.  We
continue to get the expected benefits of a reduced i386 architecture,
with respect to builder capacity and development throughput.  Trimming 2
more packages is inconsequential.

If you stil think it's important to remove inkscape on i386, please
bring this up for discussion in a broader forum (either ubuntu-devel
mailing list or the Ubuntu discourse).

** Changed in: inkscape (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1945855

Title:
  Please remove inkscape from the i386 whitelist

Status in inkscape package in Ubuntu:
  Won't Fix

Bug description:
  I don't know why inkscape was kept in i386, but honestly I don't think
  it has any reason to stay in an arch that is more and more dead and
  not really cared of in Ubuntu.

  reverse-depends -r impish -a i386 src:inkscape

  is not giving me anything, so please consider dropping it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1945855/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1945855] Re: Please remove inkscape from the i386 whitelist

[Steve Langasek]

I don't know why you are seeing that output, because this is what I see:

$ reverse-depends src:inkscape -a i386 -r impish
Reverse-Recommends
* cinnamon-desktop-environment
* games-content-dev (for inkscape)
* junior-art(for inkscape)
* latex-make(for inkscape)
* openshot-qt   (for inkscape)

Reverse-Depends
* daps  (for inkscape)
* ink-generator (for inkscape)
* inkscape-open-symbols (for inkscape)
* inkscape-speleo   (for inkscape)
* inkscape-survex-export(for inkscape)
* inkscape-textext  (for inkscape)
* open-font-design-toolkit  (for inkscape)
* python3-sphinxcontrib.svg2pdfconverter
* sreview-encoder   (for inkscape)

And https://people.canonical.com/~ubuntu-archive/germinate-
output/i386.impish/all also specifically lists:

inkscape  | inkscape
| game-data-packager (Build-Depend)   | Ubuntu Developers
  |16992888 |
86800


** Changed in: inkscape (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1945855

Title:
  Please remove inkscape from the i386 whitelist

Status in inkscape package in Ubuntu:
  Invalid

Bug description:
  I don't know why inkscape was kept in i386, but honestly I don't think
  it has any reason to stay in an arch that is more and more dead and
  not really cared of in Ubuntu.

  reverse-depends -r impish -a i386 src:inkscape

  is not giving me anything, so please consider dropping it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1945855/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1942607] Re: unifont-bin not installable on i386

[Steve Langasek]

Removing packages from impish-proposed:
unifont-bin 1:13.0.06-1 in impish i386
Comment: Not for i386
1 package successfully removed.


** Changed in: unifont (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to unifont in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1942607

Title:
  unifont-bin not installable on i386

Status in unifont package in Ubuntu:
  Fix Released

Bug description:
  It seems unifont was added to the i386 whitelist for hirsute some time
  after 2020-12-27, when 1:13.0.05-1 was uploaded.

  1:13.0.06-1 was imported when the archive opened for impish and
  unifont-bin built on i386.

  Attempting to install unifont-bin:i386 from -proposed results in:

  The following packages have unmet dependencies:
   unifont-bin:i386 : Depends: fontforge:i386
  Depends: libwx-perl:i386 but it is not installable
  Depends: libgd-perl:i386 but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unifont/+bug/1942607/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1942607] Re: unifont-bin not installable on i386

[Steve Langasek]

looks like a bug in the whitelist.  The only package that's seeded is
xfonts-unifont; this shouldn't require unifont-bin to be built on i386
in order for the seed requirements to be satisfied.  I'll deal with this
by fixing the tooling to exclude unifont from the seed (like we already
do for a few other packages, e.g. frei0r).

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to unifont in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1942607

Title:
  unifont-bin not installable on i386

Status in unifont package in Ubuntu:
  New

Bug description:
  It seems unifont was added to the i386 whitelist for hirsute some time
  after 2020-12-27, when 1:13.0.05-1 was uploaded.

  1:13.0.06-1 was imported when the archive opened for impish and
  unifont-bin built on i386.

  Attempting to install unifont-bin:i386 from -proposed results in:

  The following packages have unmet dependencies:
   unifont-bin:i386 : Depends: fontforge:i386
  Depends: libwx-perl:i386 but it is not installable
  Depends: libgd-perl:i386 but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unifont/+bug/1942607/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1928087] Re: Please remove src:jack-rack

[Steve Langasek]

Removing packages from impish:
jack-rack 1.4.8~rc1-2ubuntu4 in impish
jack-rack 1.4.8~rc1-2ubuntu4 in impish amd64
jack-rack 1.4.8~rc1-2ubuntu4 in impish arm64
jack-rack 1.4.8~rc1-2ubuntu4 in impish armhf
jack-rack 1.4.8~rc1-2ubuntu4 in impish ppc64el
jack-rack 1.4.8~rc1-2ubuntu4 in impish riscv64
jack-rack 1.4.8~rc1-2ubuntu4 in impish s390x
Comment: Ubuntu-specific, no longer used by UbuntuStudio, removed from Debian 
in 2014, depends on python2; LP: #1928087
1 package successfully removed.


** Changed in: jack-rack (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to jack-rack in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1928087

Title:
  Please remove src:jack-rack

Status in jack-rack package in Ubuntu:
  Fix Released

Bug description:
  Removal request
  ---

  Please remove the "jack-rack" source package from the archive. It
  blocks the python2-rm transition, has been removed from Debian
  testing/unstable and seems rather unmaintained upstream.

  The binary package names are:
  jack-rack

  The (release) arch that should get targeted for removal is:
  source

  It was removed from Debian as well:
  
https://tracker.debian.org/news/409981/bug740123-removed-packages-from-unstable/

  It does not have reverse depends:
  $ reverse-depends -b jack-rack
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jack-rack/+bug/1928087/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1928087] Re: Please remove src:jack-rack

[Steve Langasek]

The reason this was not removed 7 years ago when it was removed in
Debian was because Ubuntu Studio referenced it and so the Ubuntu Studio
team picked it up as the maintainers.  We should check if they still
care about having it in Ubuntu and if they are going to do the work to
migrate it to python3.

If not, or if there is no timely response, we will proceed with the
removal, since jack-rack is no longer seeded in ubuntustudio.

** Changed in: jack-rack (Ubuntu)
   Status: New => Incomplete

** Changed in: jack-rack (Ubuntu)
 Assignee: (unassigned) => Ubuntu Studio Development (ubuntustudio-dev)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to jack-rack in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1928087

Title:
  Please remove src:jack-rack

Status in jack-rack package in Ubuntu:
  Incomplete

Bug description:
  Removal request
  ---

  Please remove the "jack-rack" source package from the archive. It
  blocks the python2-rm transition, has been removed from Debian
  testing/unstable and seems rather unmaintained upstream.

  The binary package names are:
  jack-rack

  The (release) arch that should get targeted for removal is:
  source

  It was removed from Debian as well:
  
https://tracker.debian.org/news/409981/bug740123-removed-packages-from-unstable/

  It does not have reverse depends:
  $ reverse-depends -b jack-rack
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jack-rack/+bug/1928087/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1897729] Re: FeatureFreeze exception for new Pitivi release

[Steve Langasek]

** Changed in: pitivi (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to pitivi in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1897729

Title:
  FeatureFreeze exception for new Pitivi release

Status in pitivi package in Ubuntu:
  Triaged

Bug description:
  This exception is necessary because otherwise Pitivi will not be
  available at all in Ubuntu to GNOME users.

  Upstream does not have a ChangeLog. The ChangeLog diff would have been
  huge. Many new features have been introduced past three years without
  being included in any official release. The new features are part of
  the upstream flatpak build since they have been merged. The new
  features have had user exposure, so the risk of introducing buggy
  features is minimal. Also, Pitivi has an extensive set of tests for
  both the functionality and the UI.

  As we're about to make a new release, the Debian package is not ready
  yet. I'm filing this issue in advance.

  Sorry for the timing, we did our best given the resources, at the time
  we found out Pitivi risks not being included in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1897729/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1757659] Re: RM: Please port your package away from Qt 4

[Steve Langasek]

Current hydrogen in Ubuntu uses qt5, so we should not remove this
despite it being removed from Debian.

** Changed in: hydrogen (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to hydrogen in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1757659

Title:
  RM: Please port your package away from Qt 4

Status in hydrogen package in Ubuntu:
  Fix Released
Status in hydrogen package in Debian:
  Confirmed

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hydrogen/+bug/1757659/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1595358] Re: [SRU] Update to maintenance release 2.1.5 in Xenial

[Steve Langasek]

** Description changed:

  IMPACT
  ---
  http://www.lyx.org/announce/2_1_5.txt
  
  LyX 2.1.5 is the fifth, and final, maintenance release in the 2.1.x series.
  You can download LyX 2.1.5 from http://www.lyx.org/Download/.
  
  LyX 2.1.5 is the result of ongoing efforts to make our stable version
  even more reliable and stable. We have fixed a number of bugs and made
  a number of improvements. Many of these were minor, but there were a
  few crashes we fixed, too. We strongly encourage all LyX users who wish
  to continue using 2.1.x to upgrade to this version.
  
  What's new
  ==
  
  ** Updates:
  ***
  
  * USER INTERFACE
  
  - Add \ensuremath to the list of math completions.
  
  - The entries in the outliner are no longer truncated at 40 chars (bug
  9579).
  
  - The indentation of beamer frame contents has been decreased and
  unified.
  
  - In mathed, select only current cell on double-click (bug 9747).
  
  * DOCUMENTATION AND LOCALIZATION
  
  - New German translation of the PDF-comment example file.
  
  - Updated Brazilian Portuguese, French and German user interface
  localization.
  
  - Updated example file for PDF-comments.
  
  - Improved example file for the moderncv document class.
  
  - Updated French translation of Linguistics manual.
  
  - Revised Spanish Tutorial manual.
  
  - Revised French UserGuide manual.
  
  ** Bug fixes:
  *
  
  * DOCUMENT INPUT/OUTPUT
  
  - Fixed a typo in the tutorial.
  
  - Tex2lyx: fix bug with comments immediately folowed by some test (bug
  9551).
  
  * USER INTERFACE
  
  - Fix crash when activating "Close All" while an export process is
  running in the background (bug 9711).
  
  - Fix crash when unfolding/copying macros containing other macros (bug
  9490).
  
  - Fix crash when inserting a line in multline math environment (bug
  9902).
  
  - Fix crash when closing buffer one of whose children is also a child of
  other master (bug 9907).
  
  - Fix crash when clicking to the left of a tabular inset (bug 9955).
  
  - Fix assertion when selecting text just after loading document (bug
  9912).
  
  - Fix automatic insertion of longtable captions (bug 9692).
  
  - Fix crash with previewed math shown in two views of the same document
  (bug 9957).
  
  - Fix setting of nested minipage via the dialog (bug 8716).
  
  - Reset cursor language when changing document-wide language (bug 9586).
  
  - Reset cursor font when leaving an inset to the left (bug 6032).
  
  - Reset cursor font when navigating with find or spellcheck (bug 9500).
  
  - Reset cursor font after inset-select-all (bug 9719).
  
  - Fix one case where cursor does not enter insets correctly (bug 9913).
  
  - Correctly update previews when cursor leaves inset (bug 6173).
  
  - Fix subscripts and superscripts of \overrightarrow and related macros
  (bug 1996).
  
  - Fix a crash with the outliner when switching documents (bug 9754).
  
  - Repaired selection of text and search-and-replace in the presence of
  math macros. The selection is no longer cleared unvolontarily (bugs
  6078, 9364).
  
  - Disable setting vertical lines when using a formal table (bug 9816).
  
  - Disable function "layout" when the layout cannot be found (bug 8077).
  
  - Fix two bibliography related bugs: No default style shown in
  bibliography dialog in certain cases, and bad enabling-disabling
  behavior in Document> Settings> Bibliography (bugs 9797 and 9848).
  
  - The math command \sideset is now in the autocomplete list (bug 9810).
  
  - Disable Apply button in InsetParams dialogs if there is no inset to
  apply to (bug 9386).
  
  - Allow to insert program listings to footnotes and margin notes (fixes
  bug 9785, but reintroduces bug 9321).
  
  - Do not output returns and tabs in outliner.
  
  - Fix on-screen font of starred sections in paper text class.
  
  - Fix category of several layouts of the foils text class (UI only).
  
  - Correct minimal size of the view source window (bug 4430).
  
  - Fix that changing the box type could delete the box (bug 8712).
  
  - Fix a crash when introducing a new shortcut (bug 9869).
  
  - Fix initialization problem with default Inset Layout.
  
  - When a counter is stepped, reset recursively all subcounters (bug
  10063).
  
  - Erase correctly math multi-cell selections (bug 9747).
  
  - Fix warning about Undo when an empty subscript is automatically
  deleted in mathed (bug 10022).
  
  - Fix on screen narrow box when using \width as box width unit (bug
  10048).
  
  * INTERNALS
  
  - Fix parsing problems of class and category declaration line in layout
  files that could break the textclass detection (bug 9746).
  
  - Another attempt to fix NSAutoreleasePool related crashes within
  LinkBack driver. Now there is no global static pool used anymore (bug
  8637).
  
  - Allow quotes in PDF text properties (bug 9830).
  
  - Avoid clogging the undo stack with useless entries when using the
  tabular dialog 

Re: [Ubuntustudio-bugs] [Bug 1827288] Re: [Needs Packaging] LSP-Plugins for Eoan

[Steve Langasek]

On Mon, Jun 03, 2019 at 05:03:53PM -, Łukasz Zemczak wrote:
> 2) I still see that override_dh_auto_test disables tests. In comment #6
> you mentioned that you were somehow able to make those working. Do those
> really not work currently? Of course if there's no way of running them
> during build then that's fine, but I want to make sure that they're
> disabled for valid reasons. Especially that there was some discussion
> regarding that previously.

The only way to run the tests is by rebuilding the software with different
build flags and testing that.  So the tests are not a valid test of the
binaries being shipped, and instead triple the package build time for
minimal added value.

This is an upstream issue to sort out before we would want to do build-time
tests.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to Ubuntu Studio.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1827288

Title:
  [Needs Packaging] LSP-Plugins for Eoan

Status in Linux Studio Plugins:
  Fix Committed
Status in Ubuntu Studio:
  Fix Committed
Status in Ubuntu:
  Fix Committed

Bug description:
  From the project page:

  LSP (Linux Studio Plugins) is a collection of open-source plugins
  currently compatible with follwing formats:

   * LADSPA - set of plugins for Linux Audio Developer's Simple Plugin API
   * LV2 - set of plugins and UIs for Linux Audio Developer's Simple Plugin API 
(LADSPA) version 2
   * LinuxVST - set of plugins and UIs for Steinberg's VST 2.4 format ported on 
GNU/Linux Platform
   * JACK - Standalone versions for JACK Audio connection Kit with UI

  The basic idea is to fill the lack of good and useful plugins under the 
GNU/Linux platform.
  
  I have finished packaging this and would like it included in Ubuntu's 
universe repositories, targeting eoan.

  Code is at https://launchpad.net/lsp-plugins

To manage notifications about this bug go to:
https://bugs.launchpad.net/lsp-plugins/+bug/1827288/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1811571] Re: [SRU] Update to maintenance release 2.2.4 in Bionic

[Steve Langasek]

Hello Amr, or anyone else affected,

Accepted lyx into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lyx/2.2.4-0ubuntu0.18.04.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Description changed:

  IMPACT
  ---
  http://www.lyx.org/announce/2_2_4.txt
  
  LyX 2.2.4 is the fourth and final maintenance release in the 2.2.x series.
  You can download LyX 2.2.4 from http://www.lyx.org/Download/.
  
  LyX 2.2.4 is the result of ongoing efforts to make our stable version
  more reliable and more stable. We have fixed a number of bugs and made
  several improvements.
  
  What's new
  ==
  
  ** Updates:
  ***
  
  * USER INTERFACE
  
  - On Windows, allow to automatically bring the LyX window to top (bug
  10469).
  
  - Cache information on exportable formats (bug 9980).
  
  - Shorten the time required to save the session state on exit.
  
  * DOCUMENTATION AND LOCALIZATION
  
  - Updated Arabic, Czech and Japanese user interface localization.
  
  * BUILD/INSTALLATION
  
  - Mark some intentional fall-throughs in order to silence false
  -Wimplicit-fallthrough warnings with gcc7.
  
  ** Bug fixes:
  *
  
  * DOCUMENT INPUT/OUTPUT
  
  - Fix wrong spacing in output when the font size is changed inside a
  center environment or a greyed out note (bugs 9598 and 10650).
  
  - Assure properly nested \begin{lang} and \end{lang} tags even when no
  language package is selected (bug 10685).
  
  - Catch "! Incomplete \if[x]" LaTeX error (bug 10666).
  
  - Ignore LaTeX error on missing ZWNJ (ligature break) characters (bug
  10727).
  
  - Fix PDF output of clipped graphics with recent graphics package (bug
  7910).
  
  - Catch xdvipdfmx driver error that breaks XeTeX compilation (bug
  10076).
  
  - Fix caption handling in listings insets when it is split into multiple
  lines in the LaTeX output (bug 10705).
  
  - Do not let the natbibapa module overwrite what the class or other
  packages add to the preamble.
  
  - Assure the color package is loaded before polyglossia in preview
  snippets. This fixes preview image generation with polyglossia and bidi
  (bug 10716).
  
  - Fix babel name of Vietnamese language. This requires now babel-
  vietnamese (2013ff.) instead of vietnam.ldf that was shipped with vntex
  previously (bug 10743).
  
  - Fix issue with language nesting when using Asian languages (bug
  10778).
  
  - Fix bug that TeX files were not detected when reconfiguring LyX (bug
  11053).
  
  * USER INTERFACE
  
  - Fix crash occurring in certain circumstances when previewing the
  source of a single paragraph containing a language switch (bug 10636).
  
  - Fix crash when closing master file with full view source open (bug
  10560).
  
  - Fix crash when closing master document with dirty child while Document
  Settings dialog is open (bug 9979).
  
  - Fix crash when closing master with children and grandchildren (bug
  10766).
  
  - Fix crash when pasting multiple cells into a multi-paragraph cell of a
  table (bug 9983).
  
  - Fix random crash when dissolving inset (bug 10667).
  
  - Fix potential crash when cursor enters an inset (bug 10691).
  
  - Avoid crash when selecting long text (bug 10324).
  
  - Fix crash with undo and child documents (bug 10643).
  
  - Fix completely broken undo in Advanced Find & Replace edit areas (bug
  10847).
  
  - Fix crash when changing preview preferences while previewable external
  inset is open (bug 10785).
  
  - Fix problem with decimal special height/width values in the Box dialog
  in some localizations (bug 11000).
  
  - Remove duplicate entries from the Symbols dialog (bug 10644).
  
  - Always show the float type in the float inset label (bug 10618).
  
  - Show correct color name for green in the status bar (bug 10656).
  
  - fixes to cursor positioning on mouse click for right-to-left text (bug
  10569).
  
  - Fix metrics of full-width insets when paragraph endings are shown (bug
  

[Ubuntustudio-bugs] [Bug 1827288] Re: [Needs Packaging] LSP-Plugins for Eoan

[Steve Langasek]

Thanks, this looks much better now, but there are a number of lintian
errors that need to be addressed to get this archive-ready.

$ lintian ../lsp-plugins_1.1.9*changes
E: lsp-plugins-vst: binary-or-shlib-defines-rpath 
usr/lib/vst/lsp-plugins-lxvst-1.1.9/lsp-plugins-vst-comp-delay-mono.so 
/usr/local/lib
E: lsp-plugins-vst: binary-or-shlib-defines-rpath 
usr/lib/vst/lsp-plugins-lxvst-1.1.9/lsp-plugins-vst-comp-delay-mono.so /usr/lib
E: lsp-plugins-vst: binary-or-shlib-defines-rpath 
usr/lib/vst/lsp-plugins-lxvst-1.1.9/lsp-plugins-vst-comp-delay-mono.so /lib
E: lsp-plugins-vst: binary-or-shlib-defines-rpath ... use 
--no-tag-display-limit to see all (or pipe to a file/program)
E: lsp-plugins-standalone: binary-or-shlib-defines-rpath 
usr/bin/lsp-plugins-comp-delay-mono /usr/lib
E: lsp-plugins-standalone: binary-or-shlib-defines-rpath 
usr/bin/lsp-plugins-comp-delay-mono /lib
E: lsp-plugins-standalone: binary-or-shlib-defines-rpath 
usr/bin/lsp-plugins-comp-delay-mono /usr/local/lib
E: lsp-plugins-standalone: binary-or-shlib-defines-rpath ... use 
--no-tag-display-limit to see all (or pipe to a file/program)
W: lsp-plugins-standalone: privacy-breach-generic 
usr/share/doc/lsp-plugins/html/video.html [https://www.youtube.com/embed/j-rnb409gyg; frameborder="0" 
allowfullscreen>] (https://www.youtube.com/embed/j-rnb409gyg)
W: lsp-plugins-standalone: privacy-breach-generic 
usr/share/doc/lsp-plugins/html/video.html [https://www.youtube.com/embed/n4ojf2sjuhg; frameborder="0" 
allowfullscreen>] (https://www.youtube.com/embed/n4ojf2sjuhg)
W: lsp-plugins-standalone: privacy-breach-generic 
usr/share/doc/lsp-plugins/html/video.html [https://www.youtube.com/embed/gsnfz0tf-bk; frameborder="0" 
allowfullscreen>] (https://www.youtube.com/embed/gsnfz0tf-bk)
W: lsp-plugins-standalone: privacy-breach-generic ... use 
--no-tag-display-limit to see all (or pipe to a file/program)
W: lsp-plugins-standalone: binary-without-manpage 
usr/bin/lsp-plugins-comp-delay-mono
W: lsp-plugins-standalone: binary-without-manpage 
usr/bin/lsp-plugins-comp-delay-stereo
W: lsp-plugins-standalone: binary-without-manpage 
usr/bin/lsp-plugins-comp-delay-x2-stereo
W: lsp-plugins-standalone: binary-without-manpage ... use 
--no-tag-display-limit to see all (or pipe to a file/program)
E: lsp-plugins-standalone: sharedobject-in-library-directory-missing-soname 
usr/lib/lsp-plugins-jack-core-1.1.9.so
E: lsp-plugins-ladspa: binary-or-shlib-defines-rpath 
usr/lib/ladspa/lsp-plugins-ladspa.so /lib
E: lsp-plugins-ladspa: binary-or-shlib-defines-rpath 
usr/lib/ladspa/lsp-plugins-ladspa.so /usr/lib
E: lsp-plugins-ladspa: binary-or-shlib-defines-rpath 
usr/lib/ladspa/lsp-plugins-ladspa.so /usr/local/lib
E: lsp-plugins-lv2: binary-or-shlib-defines-rpath 
usr/lib/lv2/lsp-plugins.lv2/lsp-plugins-lv2.so /usr/local/lib
E: lsp-plugins-lv2: binary-or-shlib-defines-rpath 
usr/lib/lv2/lsp-plugins.lv2/lsp-plugins-lv2.so /usr/lib
E: lsp-plugins-lv2: binary-or-shlib-defines-rpath 
usr/lib/lv2/lsp-plugins.lv2/lsp-plugins-lv2.so /lib

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to Ubuntu Studio.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1827288

Title:
  [Needs Packaging] LSP-Plugins for Eoan

Status in Linux Studio Plugins:
  In Progress
Status in Ubuntu Studio:
  In Progress

Bug description:
  From the project page:

  LSP (Linux Studio Plugins) is a collection of open-source plugins
  currently compatible with follwing formats:

   * LADSPA - set of plugins for Linux Audio Developer's Simple Plugin API
   * LV2 - set of plugins and UIs for Linux Audio Developer's Simple Plugin API 
(LADSPA) version 2
   * LinuxVST - set of plugins and UIs for Steinberg's VST 2.4 format ported on 
GNU/Linux Platform
   * JACK - Standalone versions for JACK Audio connection Kit with UI

  The basic idea is to fill the lack of good and useful plugins under the 
GNU/Linux platform.
  
  I have finished packaging this and would like it included in Ubuntu's 
universe repositories, targeting eoan.

  Code is at https://launchpad.net/lsp-plugins

To manage notifications about this bug go to:
https://bugs.launchpad.net/lsp-plugins/+bug/1827288/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1827288] Re: [Needs Packaging] LSP-Plugins for Eoan

[Steve Langasek]

The version number in the debian/changelog of the git branch is wrong;
this needs to be a non-native package using the upstream tarball from
sourceforge.

+ libjack-jackd2-dev | libjack-dev,
+ php7.2-cli | php5-cli,
+ cairo-static | libcairo2-dev,

why are you using alternative build-dependencies for a new, Ubuntu-only
package?  You should only list whichever of these build dependencies you
actually expect to be used (and there is no cairo-static package in
Ubuntu anywhere, so that is definitely wrong).

Please use php-cli, not phpN.M-cli, as the build-dependency.

+Provides:
+ lv2-plugin,
+ ladspa-plugin,

Why are these Provides: attached to the lsp-plugins package, when there
are separate lsp-plugins-ladspa and lsp-plugins-lv2 packages?  The
Provides look like they belong on the latter packages.

+Package: lsp-plugins-common
+Architecture: any
+Provides: lsp-plugins-standalone

Something is definitely wrong here given that you also have a binary
package named lsp-plugins-standalone which depends on lsp-plugins-
common.  In fact, lsp-plugins-standalone appears to be an empty package;
so you should not list this binary package at all in debian/control.

+FLAGS=-O3 -pipe -ffast-math -mtune=generic -msse -msse2 -mfpmath=sse
-fPIC -DPIC -fvisibility=hidden -Wno-unused-result

How have you arrived at these flags?  Compiler flags should a) inherit
from dpkg-buildflags by default (You are completely overriding them),
and b) document the reasons for any divergence from the distro defaults.

But actually, it seems that the only thing you're doing is setting these
flags in a make variable called 'dpkg_buildflags', so in fact this has
no effect at all.

Not that you could tell by looking at the build log, which does not show
the compiler commands being invoked.  This is significant for
debuggability of builds in launchpad.  Please figure out how to make
this upstream's build system appropriately verbose.

+override_dh_auto_test:
+   #Tests only work manually, ok to override per 
http://manpages.ubuntu.com/manpages/disco/en/man1/dh_auto_test.1.html
+

what are these tests, and why do they only work manually?  It's
/allowed/ to override tests, but the goal should be to run them.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to Ubuntu Studio.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1827288

Title:
  [Needs Packaging] LSP-Plugins for Eoan

Status in Linux Studio Plugins:
  In Progress
Status in Ubuntu Studio:
  In Progress

Bug description:
  From the project page:

  LSP (Linux Studio Plugins) is a collection of open-source plugins
  currently compatible with follwing formats:

   * LADSPA - set of plugins for Linux Audio Developer's Simple Plugin API
   * LV2 - set of plugins and UIs for Linux Audio Developer's Simple Plugin API 
(LADSPA) version 2
   * LinuxVST - set of plugins and UIs for Steinberg's VST 2.4 format ported on 
GNU/Linux Platform
   * JACK - Standalone versions for JACK Audio connection Kit with UI

  The basic idea is to fill the lack of good and useful plugins under the 
GNU/Linux platform.
  
  I have finished packaging this and would like it included in Ubuntu's 
universe repositories, targeting eoan.

  Code is at https://launchpad.net/lsp-plugins

To manage notifications about this bug go to:
https://bugs.launchpad.net/lsp-plugins/+bug/1827288/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1826413] Re: ALSA Jack Midi bridge off selection not surviving a reboot

[Steve Langasek]

-self.usb_plug_check.set_active(self.usb)
+if self.usb == "True":
+self.usb_plug_check.set_active(True)
+elif self.usb == "False":
+self.usb_plug_check.set_active(False)


I think this could be instead written as

self.usb_plug_check.set_active(self.usb == "True")

to cast from a string to a boolean (unless you expect there to be other
possible values besides "True" and "False")

would you want to make this change in devel and reupload to the queue?

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-controls.
Matching subscriptions: UbuntuStudio Bugs, ubuntustudio-bugs
https://bugs.launchpad.net/bugs/1826413

Title:
  ALSA Jack Midi bridge off selection not surviving a reboot

Status in ubuntustudio-controls:
  Fix Committed
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-controls source package in Disco:
  In Progress
Status in ubuntustudio-controls source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * As the status of the jack-midi and pulseaudio-jack bridges are not
  updated correctly from the config file, users have to open
  ubuntustudio-controls to set the required status every time they
  login/logout/reboot.

   * The bug is very annoying for users that need to adjust their jack
  settings to cater for different audio software and hardware.

   * The statuses read from the config file are a string. When
  converting from string to boolean to set the check button status in
  the gui, python will always evaluate the boolean as "True" for any
  string except "None". Now the strings are parsed with some if/elif
  statments to set the correct boolean status for the check button.

  [Test Case]

   * Run ubuntustudio-controls

   * The first time ubuntustudio-controls is run, the 4 tick boxes in
  the gui (e.g. "Auto Start Jack at Session Start") should be set to the
  recommended defaults for Ubuntu Studio. Change the tick boxes to
  something else (e.g. all off).

   * Click Apply Audio Settings (saves the settings to a configuration
  file).

   * Close Ubuntu Studio Controls.

   * Restart Ubuntu Studio Controls. The previous settings should be
  remembered. Previously to the fix, the recommended defaults were set
  (ignoring the settings saved in the configuration file).

  [Regression Potential]

   * The changes are limited to the ubuntustudio-controls app, and this
  package is only ever installed for Ubuntu Studio users, or users that
  want to add the Ubuntu Studio settings to their favourite flavour. The
  only reverse dependency is the Ubuntu Studio meta-package.

   * The changes have been tested in my ppa
  (https://launchpad.net/~rosco2/+archive/ubuntu/testing) for Disco with
  no apparent regressions.

  [Other Info]

   * The same changes (uploaded to Eoan) have been backported in our
  Ubuntu Studio Backports PPA (https://launchpad.net/~ubuntustudio-
  ppa/+archive/ubuntu/backports) and is therefore already in the hands
  of many users.

  [Original Description]

  Several users on the Ubuntu Studio list have reported that they only
  want the ALSA Jack Midi bridge to be active sometimes.

  When switched off in ubuntustudio-controls it always restarts with it
  enabled again which is very inconvenient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio-controls/+bug/1826413/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1826413] Re: ALSA Jack Midi bridge off selection not surviving a reboot

[Steve Langasek]

-self.usb_plug_check.set_active(self.usb)
+if self.usb == "True":
+self.usb_plug_check.set_active(True)
+elif self.usb == "False":
+self.usb_plug_check.set_active(False)


I think this could be instead written as

self.usb_plug_check.set_active(self.usb == "True")

to cast from a string to a boolean (unless you expect there to be other
possible values besides "True" and "False")

would you want to make this change in devel and reupload to the queue?

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-controls.
Matching subscriptions: UbuntuStudio Bugs, ubuntustudio-bugs
https://bugs.launchpad.net/bugs/1826413

Title:
  ALSA Jack Midi bridge off selection not surviving a reboot

Status in ubuntustudio-controls:
  Fix Committed
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-controls source package in Disco:
  In Progress
Status in ubuntustudio-controls source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * As the status of the jack-midi and pulseaudio-jack bridges are not
  updated correctly from the config file, users have to open
  ubuntustudio-controls to set the required status every time they
  login/logout/reboot.

   * The bug is very annoying for users that need to adjust their jack
  settings to cater for different audio software and hardware.

   * The statuses read from the config file are a string. When
  converting from string to boolean to set the check button status in
  the gui, python will always evaluate the boolean as "True" for any
  string except "None". Now the strings are parsed with some if/elif
  statments to set the correct boolean status for the check button.

  [Test Case]

   * Run ubuntustudio-controls

   * The first time ubuntustudio-controls is run, the 4 tick boxes in
  the gui (e.g. "Auto Start Jack at Session Start") should be set to the
  recommended defaults for Ubuntu Studio. Change the tick boxes to
  something else (e.g. all off).

   * Click Apply Audio Settings (saves the settings to a configuration
  file).

   * Close Ubuntu Studio Controls.

   * Restart Ubuntu Studio Controls. The previous settings should be
  remembered. Previously to the fix, the recommended defaults were set
  (ignoring the settings saved in the configuration file).

  [Regression Potential]

   * The changes are limited to the ubuntustudio-controls app, and this
  package is only ever installed for Ubuntu Studio users, or users that
  want to add the Ubuntu Studio settings to their favourite flavour. The
  only reverse dependency is the Ubuntu Studio meta-package.

   * The changes have been tested in my ppa
  (https://launchpad.net/~rosco2/+archive/ubuntu/testing) for Disco with
  no apparent regressions.

  [Other Info]

   * The same changes (uploaded to Eoan) have been backported in our
  Ubuntu Studio Backports PPA (https://launchpad.net/~ubuntustudio-
  ppa/+archive/ubuntu/backports) and is therefore already in the hands
  of many users.

  [Original Description]

  Several users on the Ubuntu Studio list have reported that they only
  want the ALSA Jack Midi bridge to be active sometimes.

  When switched off in ubuntustudio-controls it always restarts with it
  enabled again which is very inconvenient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio-controls/+bug/1826413/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1818373] Re: [needs-packaging] [FFe] grub2-themes-ubuntustudio

[Steve Langasek]

Feedback on the grub2-themes-ubuntustudio package in NEW:
 - please review the output of 'lintian -I *changes' on packages.  In 
particular, in this case:
W: grub2-themes-ubuntustudio source: newer-standards-version 4.3.0 (current is 
4.2.1)
   (there should be no reason for an out-of-date standards version on a 
completely new package)
 - why is src/grub2-themes-ubuntu-mate.svg present in the source? this is 
obviously not even the right package name.
 - debian/copyright includes a lot of redundancy.  Files: *, Files: debian/*, 
and Files: theme.txt all have the same copyright and license; there is no 
reason for separate stanzas vs. a single glob. (I realize this is inherited 
from the grub2-themes-ubuntu-mate source package, but that is not the package 
I'm currently reviewing in the NEW queue, this one is.)
 - I don't know what the debian/post{inst,rm} scripts here are supposed to do - 
they are not inherited from the ubuntu-mate theme package, and there is nothing 
in the packaging which contains integration that would change the grub theme 
selection.  I also see that you are calling update-grub2; but this is not the 
preferred name for the command, you should be invoking it as 'update-grub'.  
Furthermore, since the package depends on grub-common, I don't think there's 
any reason for guarding the update-grub call with a 'which' check for the 
command.

Since this last point is a potential integration issue, and we are past
FF, I am going to reject the package currently in the NEW queue.  Once
this is resolved, I can either sponsor a new upload or rescue the
previous package from the rejected queue as appropriate.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: UbuntuStudio Bugs, UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1818373

Title:
  [needs-packaging] [FFe] grub2-themes-ubuntustudio

Status in grub2-themes-ubuntustudio:
  Fix Committed
Status in Ubuntu Studio:
  Fix Committed
Status in ubuntustudio-meta:
  Fix Committed
Status in ubuntustudio-meta package in Ubuntu:
  Triaged

Bug description:
  This is simply a fork of grub2-themes-ubuntu-mate, already in the
  repos.

  This package is required for many of the newer versions of
  ubuntustudio-* packages awaiting upload, on which this is a
  dependency.

  All code is in the lp:grub2-theme-ubuntustudio git repo.
  We have been testing it using our autobuild ppa:
  ppa:ubuntustudio-dev/autobuilds 
(https://launchpad.net/~ubuntustudiodev/+archive/ubuntu/autobuild)

  The package is a grub theme and should not interfere with anything
  else. We would appreciate an acknowledgement from the release team
  ASAP, as we need sponsorship to get it uploaded.

  Additionally, this is a dependency on packages in ubuntustudio-look,
  so this must be in the repos for that package to get updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub2-theme-ubuntustudio/+bug/1818373/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1818366] Re: [FFe] Carla: Please Upload to Universe

[Steve Langasek]

new package, to be swapped out in the seed for another; trivial FFe
approval.

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: UbuntuStudio Bugs, UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1818366

Title:
  [FFe] Carla: Please Upload to Universe

Status in Carla:
  New
Status in Ubuntu Studio:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Triaged

Bug description:
  New package for Ubuntu, specifically, Ubuntu Studio, to replace jack-
  rack in functionality and provide even more functionality. This
  package has been a long-requested feature that we believe fits
  perfectly into the Ubuntu Studio ecosystem.

  All code is in the lp:carla git repo. We have been testing it using our 
autobuild ppa:
  ppa:ubuntustudio-dev/autobuilds 
(https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild)

  We plan to upload to Debian after the Buster freeze, but would like
  Carla to be part of Disco. The package is an application and should
  not interfere with anything else. We would appreciate an
  acknowledgement from the release team ASAP, as we need sponsorship to
  get it uploaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/carla/+bug/1818366/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1818373] Re: [FFe] grub2-themes-ubuntustudio

[Steve Langasek]

Entirely new package; trivially approved.

** Changed in: grub2-theme-ubuntustudio
   Status: New => Triaged

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: UbuntuStudio Bugs, UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1818373

Title:
  [FFe] grub2-themes-ubuntustudio

Status in grub2-themes-ubuntustudio:
  Triaged
Status in Ubuntu Studio:
  New
Status in ubuntustudio-meta:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Triaged

Bug description:
  This is simply a fork of grub2-themes-ubuntu-mate, already in the
  repos.

  This package is required for many of the newer versions of
  ubuntustudio-* packages awaiting upload, on which this is a
  dependency.

  All code is in the lp:grub2-theme-ubuntustudio git repo.
  We have been testing it using our autobuild ppa:
  ppa:ubuntustudio-dev/autobuilds 
(https://launchpad.net/~ubuntustudiodev/+archive/ubuntu/autobuild)

  The package is a grub theme and should not interfere with anything
  else. We would appreciate an acknowledgement from the release team
  ASAP, as we need sponsorship to get it uploaded.

  Additionally, this is a dependency on packages in ubuntustudio-look,
  so this must be in the repos for that package to get updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub2-theme-ubuntustudio/+bug/1818373/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1818373] Re: [FFe] grub2-themes-ubuntustudio

[Steve Langasek]

(basically, I think this doesn't require an FFe at all since it's just a
theme - it would fall under UIFe but not FFe.)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: UbuntuStudio Bugs, UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1818373

Title:
  [FFe] grub2-themes-ubuntustudio

Status in grub2-themes-ubuntustudio:
  Triaged
Status in Ubuntu Studio:
  New
Status in ubuntustudio-meta:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Triaged

Bug description:
  This is simply a fork of grub2-themes-ubuntu-mate, already in the
  repos.

  This package is required for many of the newer versions of
  ubuntustudio-* packages awaiting upload, on which this is a
  dependency.

  All code is in the lp:grub2-theme-ubuntustudio git repo.
  We have been testing it using our autobuild ppa:
  ppa:ubuntustudio-dev/autobuilds 
(https://launchpad.net/~ubuntustudiodev/+archive/ubuntu/autobuild)

  The package is a grub theme and should not interfere with anything
  else. We would appreciate an acknowledgement from the release team
  ASAP, as we need sponsorship to get it uploaded.

  Additionally, this is a dependency on packages in ubuntustudio-look,
  so this must be in the repos for that package to get updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub2-theme-ubuntustudio/+bug/1818373/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1800817] Re: Ubuntu Studio seeds switched to git

[Steve Langasek]

Also I notice this in the debian/copyright diff:

 Copyright: 2006, Joseph Jackson IV 

That's an invalid URL, and anyway there's no requirement to list
anything other than the name for a copyright holder when contact
information is unavailable.  (But there was previously an email address
of jjackso...@fluxbuntu.org listed, so maybe that should be preserved.)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1800817

Title:
  Ubuntu Studio seeds switched to git

Status in ubuntustudio-meta package in Ubuntu:
  Incomplete

Bug description:
  We have switched the Ubuntu Studio seeds to git from bzr, coordinated
  with the Ubuntu Release Team.

  Now that the Disco Dingo is open (to be 19.04), we need to update the
  ubuntustudio-meta package to match.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1800817/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1800817] Re: Ubuntu Studio seeds switched to git

[Steve Langasek]

This debdiff has reintroduced powerpc as an architecture.  Why is this?

It also introduces a font-meta seed which I don't find anywhere in the
source.

So this doesn't look ready for sponsorship as-is.

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: Fix Committed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1800817

Title:
  Ubuntu Studio seeds switched to git

Status in ubuntustudio-meta package in Ubuntu:
  Incomplete

Bug description:
  We have switched the Ubuntu Studio seeds to git from bzr, coordinated
  with the Ubuntu Release Team.

  Now that the Disco Dingo is open (to be 19.04), we need to update the
  ubuntustudio-meta package to match.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1800817/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1746406] Re: demote packages not ready for python-pil (still using python-imaging)

[Steve Langasek]

** No longer affects: twms (Ubuntu)

** No longer affects: trac-wikiprint (Ubuntu)

** No longer affects: fofix-dfsg (Ubuntu)

** No longer affects: comix (Ubuntu)

** No longer affects: trac-diavisview (Ubuntu)

** No longer affects: photon (Ubuntu)

** No longer affects: keysync (Ubuntu)

** No longer affects: python-trml2pdf (Ubuntu)

** No longer affects: trac-odtexport (Ubuntu)

** No longer affects: cfv (Ubuntu)

** No longer affects: oboinus (Ubuntu)

** No longer affects: utopia-documents (Ubuntu)

** No longer affects: impressive (Ubuntu)

** No longer affects: psychopy (Ubuntu)

** No longer affects: python-aalib (Ubuntu)

** No longer affects: phatch (Ubuntu)

** No longer affects: griffith (Ubuntu)

** No longer affects: ibid (Ubuntu)

** No longer affects: streamtuner2 (Ubuntu)

** No longer affects: weboob (Ubuntu)

** No longer affects: impressive-display (Ubuntu)

** No longer affects: kraft (Ubuntu)

** No longer affects: pyepl (Ubuntu)

** No longer affects: pylibtiff (Ubuntu)

** Changed in: python-uniconvertor (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to phatch in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1746406

Title:
  demote packages not ready for python-pil (still using python-imaging)

Status in python-uniconvertor package in Ubuntu:
  Fix Released

Bug description:
  demote packages not ready for python-pil (still using python-imaging),
  usually not in testing in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-uniconvertor/+bug/1746406/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1746406] Re: demote packages not ready for python-pil (still using python-imaging)

[Steve Langasek]

** No longer affects: htmlgen (Ubuntu)

** No longer affects: mcomix (Ubuntu)

** No longer affects: pisa (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to phatch in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1746406

Title:
  demote packages not ready for python-pil (still using python-imaging)

Status in cfv package in Ubuntu:
  New
Status in comix package in Ubuntu:
  New
Status in fofix-dfsg package in Ubuntu:
  New
Status in griffith package in Ubuntu:
  New
Status in ibid package in Ubuntu:
  New
Status in impressive package in Ubuntu:
  New
Status in impressive-display package in Ubuntu:
  New
Status in keysync package in Ubuntu:
  New
Status in kraft package in Ubuntu:
  New
Status in oboinus package in Ubuntu:
  New
Status in phatch package in Ubuntu:
  New
Status in photon package in Ubuntu:
  New
Status in psychopy package in Ubuntu:
  New
Status in pyepl package in Ubuntu:
  New
Status in pylibtiff package in Ubuntu:
  New
Status in python-aalib package in Ubuntu:
  New
Status in python-trml2pdf package in Ubuntu:
  New
Status in python-uniconvertor package in Ubuntu:
  New
Status in streamtuner2 package in Ubuntu:
  New
Status in trac-diavisview package in Ubuntu:
  New
Status in trac-odtexport package in Ubuntu:
  New
Status in trac-wikiprint package in Ubuntu:
  New
Status in twms package in Ubuntu:
  New
Status in utopia-documents package in Ubuntu:
  New
Status in weboob package in Ubuntu:
  New

Bug description:
  demote packages not ready for python-pil (still using python-imaging),
  usually not in testing in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfv/+bug/1746406/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1746406] Re: demote packages not ready for python-pil (still using python-imaging)

[Steve Langasek]

** No longer affects: python-sponge (Ubuntu)

** No longer affects: pkpgcounter (Ubuntu)

** No longer affects: virtualbricks (Ubuntu)

** No longer affects: openshot (Ubuntu)

** No longer affects: opensesame (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to openshot in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1746406

Title:
  demote packages not ready for python-pil (still using python-imaging)

Status in cfv package in Ubuntu:
  New
Status in comix package in Ubuntu:
  New
Status in fofix-dfsg package in Ubuntu:
  New
Status in griffith package in Ubuntu:
  New
Status in htmlgen package in Ubuntu:
  New
Status in ibid package in Ubuntu:
  New
Status in impressive package in Ubuntu:
  New
Status in impressive-display package in Ubuntu:
  New
Status in keysync package in Ubuntu:
  New
Status in kraft package in Ubuntu:
  New
Status in mcomix package in Ubuntu:
  New
Status in oboinus package in Ubuntu:
  New
Status in phatch package in Ubuntu:
  New
Status in photon package in Ubuntu:
  New
Status in pisa package in Ubuntu:
  New
Status in psychopy package in Ubuntu:
  New
Status in pyepl package in Ubuntu:
  New
Status in pylibtiff package in Ubuntu:
  New
Status in python-aalib package in Ubuntu:
  New
Status in python-trml2pdf package in Ubuntu:
  New
Status in python-uniconvertor package in Ubuntu:
  New
Status in streamtuner2 package in Ubuntu:
  New
Status in trac-diavisview package in Ubuntu:
  New
Status in trac-odtexport package in Ubuntu:
  New
Status in trac-wikiprint package in Ubuntu:
  New
Status in twms package in Ubuntu:
  New
Status in utopia-documents package in Ubuntu:
  New
Status in weboob package in Ubuntu:
  New

Bug description:
  demote packages not ready for python-pil (still using python-imaging),
  usually not in testing in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfv/+bug/1746406/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1746406] Re: demote packages not ready for python-pil (still using python-imaging)

[Steve Langasek]

** No longer affects: xmms2tray (Ubuntu)

** No longer affects: aafigure (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to openshot in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1746406

Title:
  demote packages not ready for python-pil (still using python-imaging)

Status in cfv package in Ubuntu:
  New
Status in comix package in Ubuntu:
  New
Status in fofix-dfsg package in Ubuntu:
  New
Status in griffith package in Ubuntu:
  New
Status in htmlgen package in Ubuntu:
  New
Status in ibid package in Ubuntu:
  New
Status in impressive package in Ubuntu:
  New
Status in impressive-display package in Ubuntu:
  New
Status in keysync package in Ubuntu:
  New
Status in kraft package in Ubuntu:
  New
Status in mcomix package in Ubuntu:
  New
Status in oboinus package in Ubuntu:
  New
Status in opensesame package in Ubuntu:
  New
Status in openshot package in Ubuntu:
  New
Status in phatch package in Ubuntu:
  New
Status in photon package in Ubuntu:
  New
Status in pisa package in Ubuntu:
  New
Status in pkpgcounter package in Ubuntu:
  New
Status in psychopy package in Ubuntu:
  New
Status in pyepl package in Ubuntu:
  New
Status in pylibtiff package in Ubuntu:
  New
Status in python-aalib package in Ubuntu:
  New
Status in python-sponge package in Ubuntu:
  New
Status in python-trml2pdf package in Ubuntu:
  New
Status in python-uniconvertor package in Ubuntu:
  New
Status in streamtuner2 package in Ubuntu:
  New
Status in trac-diavisview package in Ubuntu:
  New
Status in trac-odtexport package in Ubuntu:
  New
Status in trac-wikiprint package in Ubuntu:
  New
Status in twms package in Ubuntu:
  New
Status in utopia-documents package in Ubuntu:
  New
Status in virtualbricks package in Ubuntu:
  New
Status in weboob package in Ubuntu:
  New

Bug description:
  demote packages not ready for python-pil (still using python-imaging),
  usually not in testing in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfv/+bug/1746406/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1746406] Re: demote packages not ready for python-pil (still using python-imaging)

[Steve Langasek]

** No longer affects: pycaptcha (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to openshot in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1746406

Title:
  demote packages not ready for python-pil (still using python-imaging)

Status in cfv package in Ubuntu:
  New
Status in comix package in Ubuntu:
  New
Status in fofix-dfsg package in Ubuntu:
  New
Status in griffith package in Ubuntu:
  New
Status in htmlgen package in Ubuntu:
  New
Status in ibid package in Ubuntu:
  New
Status in impressive package in Ubuntu:
  New
Status in impressive-display package in Ubuntu:
  New
Status in keysync package in Ubuntu:
  New
Status in kraft package in Ubuntu:
  New
Status in mcomix package in Ubuntu:
  New
Status in oboinus package in Ubuntu:
  New
Status in opensesame package in Ubuntu:
  New
Status in openshot package in Ubuntu:
  New
Status in phatch package in Ubuntu:
  New
Status in photon package in Ubuntu:
  New
Status in pisa package in Ubuntu:
  New
Status in pkpgcounter package in Ubuntu:
  New
Status in psychopy package in Ubuntu:
  New
Status in pyepl package in Ubuntu:
  New
Status in pylibtiff package in Ubuntu:
  New
Status in python-aalib package in Ubuntu:
  New
Status in python-sponge package in Ubuntu:
  New
Status in python-trml2pdf package in Ubuntu:
  New
Status in python-uniconvertor package in Ubuntu:
  New
Status in streamtuner2 package in Ubuntu:
  New
Status in trac-diavisview package in Ubuntu:
  New
Status in trac-odtexport package in Ubuntu:
  New
Status in trac-wikiprint package in Ubuntu:
  New
Status in twms package in Ubuntu:
  New
Status in utopia-documents package in Ubuntu:
  New
Status in virtualbricks package in Ubuntu:
  New
Status in weboob package in Ubuntu:
  New

Bug description:
  demote packages not ready for python-pil (still using python-imaging),
  usually not in testing in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfv/+bug/1746406/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1746406] Re: demote packages not ready for python-pil (still using python-imaging)

[Steve Langasek]

** No longer affects: nautilus-image-manipulator (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to openshot in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1746406

Title:
  demote packages not ready for python-pil (still using python-imaging)

Status in aafigure package in Ubuntu:
  New
Status in cfv package in Ubuntu:
  New
Status in comix package in Ubuntu:
  New
Status in fofix-dfsg package in Ubuntu:
  New
Status in griffith package in Ubuntu:
  New
Status in htmlgen package in Ubuntu:
  New
Status in ibid package in Ubuntu:
  New
Status in impressive package in Ubuntu:
  New
Status in impressive-display package in Ubuntu:
  New
Status in keysync package in Ubuntu:
  New
Status in kraft package in Ubuntu:
  New
Status in mcomix package in Ubuntu:
  New
Status in oboinus package in Ubuntu:
  New
Status in opensesame package in Ubuntu:
  New
Status in openshot package in Ubuntu:
  New
Status in phatch package in Ubuntu:
  New
Status in photon package in Ubuntu:
  New
Status in pisa package in Ubuntu:
  New
Status in pkpgcounter package in Ubuntu:
  New
Status in psychopy package in Ubuntu:
  New
Status in pyepl package in Ubuntu:
  New
Status in pylibtiff package in Ubuntu:
  New
Status in python-aalib package in Ubuntu:
  New
Status in python-sponge package in Ubuntu:
  New
Status in python-trml2pdf package in Ubuntu:
  New
Status in python-uniconvertor package in Ubuntu:
  New
Status in streamtuner2 package in Ubuntu:
  New
Status in trac-diavisview package in Ubuntu:
  New
Status in trac-odtexport package in Ubuntu:
  New
Status in trac-wikiprint package in Ubuntu:
  New
Status in twms package in Ubuntu:
  New
Status in utopia-documents package in Ubuntu:
  New
Status in virtualbricks package in Ubuntu:
  New
Status in weboob package in Ubuntu:
  New
Status in xmms2tray package in Ubuntu:
  New

Bug description:
  demote packages not ready for python-pil (still using python-imaging),
  usually not in testing in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aafigure/+bug/1746406/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntustudio-bugs] [Bug 1698225] Re: zynjacku is seeded in ubuntustudio but removed from Debian

[Steve Langasek]

On Fri, Sep 01, 2017 at 07:55:19AM -, Ross Gammon wrote:
> I attach a debdiff for sponsorship to refresh the Ubuntu Studio meta
> package for artful.

Not much point in a debdiff since the changes are autogenerated by the
update script.  Uploading, thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to zynjacku in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1698225

Title:
  zynjacku is seeded in ubuntustudio but removed from Debian

Status in ubuntustudio-meta package in Ubuntu:
  Confirmed
Status in zynjacku package in Ubuntu:
  Confirmed

Bug description:
  The zynjacku package is in sync with Debian, but was removed from
  Debian in 2013.  Normally we would also remove it from Ubuntu, but
  this package is seeded in ubuntustudio.

  If the Ubuntu Studio team wishes to maintain zynjacku, please upload
  it to Ubuntu with a changed maintainer field.

  If you do ont wish to maintain it, please remove it from the
  ubuntustudio seed and reassign this bug to the ~ubuntu-archive team
  for removal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1698225/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1698225] Re: zynjacku is seeded in ubuntustudio but removed from Debian

[Steve Langasek]

** Changed in: zynjacku (Ubuntu)
 Assignee: (unassigned) => Ubuntu Studio Development (ubuntustudio-dev)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to zynjacku in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1698225

Title:
  zynjacku is seeded in ubuntustudio but removed from Debian

Status in zynjacku package in Ubuntu:
  New

Bug description:
  The zynjacku package is in sync with Debian, but was removed from
  Debian in 2013.  Normally we would also remove it from Ubuntu, but
  this package is seeded in ubuntustudio.

  If the Ubuntu Studio team wishes to maintain zynjacku, please upload
  it to Ubuntu with a changed maintainer field.

  If you do ont wish to maintain it, please remove it from the
  ubuntustudio seed and reassign this bug to the ~ubuntu-archive team
  for removal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zynjacku/+bug/1698225/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1698225] [NEW] zynjacku is seeded in ubuntustudio but removed from Debian

[Steve Langasek]

Public bug reported:

The zynjacku package is in sync with Debian, but was removed from Debian
in 2013.  Normally we would also remove it from Ubuntu, but this package
is seeded in ubuntustudio.

If the Ubuntu Studio team wishes to maintain zynjacku, please upload it
to Ubuntu with a changed maintainer field.

If you do ont wish to maintain it, please remove it from the
ubuntustudio seed and reassign this bug to the ~ubuntu-archive team for
removal.

** Affects: zynjacku (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to zynjacku in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1698225

Title:
  zynjacku is seeded in ubuntustudio but removed from Debian

Status in zynjacku package in Ubuntu:
  New

Bug description:
  The zynjacku package is in sync with Debian, but was removed from
  Debian in 2013.  Normally we would also remove it from Ubuntu, but
  this package is seeded in ubuntustudio.

  If the Ubuntu Studio team wishes to maintain zynjacku, please upload
  it to Ubuntu with a changed maintainer field.

  If you do ont wish to maintain it, please remove it from the
  ubuntustudio seed and reassign this bug to the ~ubuntu-archive team
  for removal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zynjacku/+bug/1698225/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1678417] Re: Please rebuild pd-aubio against libaubio5

[Steve Langasek]

For no-change rebuilds, we version packages as 'build1' instead of
'ubuntu1', so that we can detect that there is no Ubuntu delta in the
source and we can safely overwrite it with a sync.

This also means we do not need to run update-maintainer on the source.

Finally, I have added a reference to this bug in the changelog so it
will auto-close when pd-audio reaches zesty.

Thank you for your contribution to Ubuntu!

** Changed in: pd-aubio (Ubuntu)
   Status: New => In Progress

** Changed in: pd-aubio (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to pd-aubio in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1678417

Title:
  Please rebuild pd-aubio against libaubio5

Status in pd-aubio package in Ubuntu:
  In Progress

Bug description:
  Ardour and aubio are currently stuck in zesty proposed. Rik Mills's
  analysis:

  "From update-output.txt

  trying: denemo aubio ardour
  skipped: denemo aubio ardour (0, 0, 13)
  got: 42+0: a-19:a-4:a-4:i-5:p-4:s-6
  * amd64: pd-aubio

  Seems to migrate it needs to do that with newer aubio etc.

  e.g. looking at
  https://launchpad.net/ubuntu/zesty/amd64/ardour/1:5.5.0~dfsg-1

  new ardour built against and depends on the libaubio5 in proposed, so
  needs that to migrate with it.

  But the update-output.txt is saying that would break  pd-aubio, which
  makes sense if you dig into it as pb-aubio in release depends on
  libaubio4 which would be replaced by libaubio5.

  http://packages.ubuntu.com/zesty/pd-aubio

  So as a first guess, maybe pb-audio could have a rebuild against the new
  aubio to depend on the newer lib in proposed instead, so all that
  migrating does not break it? I don't know this stack and it's deps, so I
  am somewhat guessing here if that would work or rebuild ok."

  I can confirm that pd-aubio builds fine against libaubio5 in Debian
  sid. We need to start the transition and then rebuild pd-aubio against
  the aubio currently in zesty-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pd-aubio/+bug/1678417/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntustudio-bugs] [Bug 1652882] Re: Sync 8~dfsg0-3 from Debian Sid

[Steve Langasek]

On Wed, Dec 28, 2016 at 04:29:23PM -, Mattia Rizzolo wrote:

> @vorlon Except that that's the wrong version (and therefor FTBFSed on
> arm64) :)

Heh, indeed, sorry :)

> Anyway, guess now it's going to sync by itself once launchpad notices the
> newest version.

Yep!

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to a2jmidid in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1652882

Title:
  Sync 8~dfsg0-3 from Debian Sid

Status in a2jmidid package in Ubuntu:
  Fix Released

Bug description:
  Changelog since the last merge:

  a2jmidid (8~dfsg0-3) unstable; urgency=medium

* Team upload.
* d/control:
  + Drop obsolete field DM-Upload-Allowed
  + Drop pointless field 'X-Python-Version: >= 2.5'
  + Canonicalize Vcs-* fields, and use https.
  + Add build-depepndency on dh-python to avoid a build warning
  + Add dependency on python-dbus.  Closes: #824070
  + Bump Standards-Version to 3.9.8, no changes needed
* d/rules:
  + Use the -S option of dpkg-parsechangelog to get the field, instead of 
sed.
* Bump debhelper compat level to 10
* d/watch: use @ARCHIVE_EXT@ to look for eventually different archive types.
* Pull patch from Ubuntu to fix FTBFS in arm64.  Closes: #773088
  Thanks to Logan Rosen  for the patch.

   -- Mattia Rizzolo   Wed, 28 Dec 2016 09:50:56
  +0100

  a2jmidid (8~dfsg0-2.1) unstable; urgency=medium

* Non-maintainer upload.
* debian/patches:
  - ppc64-sigsegv.patch: sigsegv.c: added condition to use ucontext.h
for ppc64, which wasn't being covered. (Closes: #769141)

   -- Fernando Seiti Furusato   Mon, 05 Dec
  2016 11:51:07 -0200

  
  With the 2 uploads both the patches there were in Ubuntu (fixes for ppc64 and 
arm64 FTBFS) have been incorporated, so we can go back in sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/a2jmidid/+bug/1652882/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1652882] Re: Sync 8~dfsg0-3 from Debian Sid

[Steve Langasek]

This bug was fixed in the package a2jmidid - 8~dfsg0-2.1
Sponsored for Mattia Rizzolo (mapreri)

---
a2jmidid (8~dfsg0-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * debian/patches:
- ppc64-sigsegv.patch: sigsegv.c: added condition to use ucontext.h
  for ppc64, which wasn't being covered. (Closes: #769141)

 -- Fernando Seiti Furusato   Mon, 05 Dec
2016 11:51:07 -0200

** Changed in: a2jmidid (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to a2jmidid in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1652882

Title:
  Sync 8~dfsg0-3 from Debian Sid

Status in a2jmidid package in Ubuntu:
  Fix Released

Bug description:
  Changelog since the last merge:

  a2jmidid (8~dfsg0-3) unstable; urgency=medium

* Team upload.
* d/control:
  + Drop obsolete field DM-Upload-Allowed
  + Drop pointless field 'X-Python-Version: >= 2.5'
  + Canonicalize Vcs-* fields, and use https.
  + Add build-depepndency on dh-python to avoid a build warning
  + Add dependency on python-dbus.  Closes: #824070
  + Bump Standards-Version to 3.9.8, no changes needed
* d/rules:
  + Use the -S option of dpkg-parsechangelog to get the field, instead of 
sed.
* Bump debhelper compat level to 10
* d/watch: use @ARCHIVE_EXT@ to look for eventually different archive types.
* Pull patch from Ubuntu to fix FTBFS in arm64.  Closes: #773088
  Thanks to Logan Rosen  for the patch.

   -- Mattia Rizzolo   Wed, 28 Dec 2016 09:50:56
  +0100

  a2jmidid (8~dfsg0-2.1) unstable; urgency=medium

* Non-maintainer upload.
* debian/patches:
  - ppc64-sigsegv.patch: sigsegv.c: added condition to use ucontext.h
for ppc64, which wasn't being covered. (Closes: #769141)

   -- Fernando Seiti Furusato   Mon, 05 Dec
  2016 11:51:07 -0200

  
  With the 2 uploads both the patches there were in Ubuntu (fixes for ppc64 and 
arm64 FTBFS) have been incorporated, so we can go back in sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/a2jmidid/+bug/1652882/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1546979] Re: [MIR] new font dependencies for texlive-fonts-extra

[Steve Langasek]

MIR for fonts-stix is already handled via bug #1487148.

** Changed in: fonts-stix (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to fonts-sil-gentium-basic in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs, Ubuntu Studio 
Bugs, Ubuntu Studio Bugs, Ubuntu Studio Bugs, Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1546979

Title:
  [MIR] new font dependencies for texlive-fonts-extra

Status in fonts-cabin package in Ubuntu:
  New
Status in fonts-comfortaa package in Ubuntu:
  New
Status in fonts-crosextra-caladea package in Ubuntu:
  New
Status in fonts-crosextra-carlito package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  New
Status in fonts-ebgaramond package in Ubuntu:
  New
Status in fonts-font-awesome package in Ubuntu:
  New
Status in fonts-freefont package in Ubuntu:
  New
Status in fonts-gfs-artemisia package in Ubuntu:
  New
Status in fonts-gfs-complutum package in Ubuntu:
  New
Status in fonts-gfs-didot package in Ubuntu:
  New
Status in fonts-gfs-neohellenic package in Ubuntu:
  New
Status in fonts-gfs-olga package in Ubuntu:
  New
Status in fonts-gfs-solomos package in Ubuntu:
  New
Status in fonts-junicode package in Ubuntu:
  New
Status in fonts-lato package in Ubuntu:
  New
Status in fonts-linuxlibertine package in Ubuntu:
  New
Status in fonts-lobstertwo package in Ubuntu:
  New
Status in fonts-oflb-asana-math package in Ubuntu:
  New
Status in fonts-roboto package in Ubuntu:
  New
Status in fonts-sil-gentium package in Ubuntu:
  New
Status in fonts-sil-gentium-basic package in Ubuntu:
  New
Status in fonts-sil-gentiumplus package in Ubuntu:
  New
Status in fonts-stix package in Ubuntu:
  Invalid
Status in ttf-adf package in Ubuntu:
  New

Bug description:
  new font dependencies for texlive-fonts-extra:

  maintained by the Debian fonts team:

  fonts-cabin
  fonts-comfortaa
  fonts-crosextra-caladea
  fonts-crosextra-carlito
  fonts-dejavu
  fonts-ebgaramond
  fonts-font-awesome
  fonts-freefont
  fonts-gfs-artemisia
  fonts-gfs-complutum
  fonts-gfs-didot
  fonts-gfs-neohellenic
  fonts-gfs-olga
  fonts-gfs-solomos
  fonts-junicode
  fonts-lato
  fonts-linuxlibertine
  fonts-lobstertwo
  fonts-oflb-asana-math
  fonts-roboto
  fonts-sil-gentium
  fonts-sil-gentium-basic
  fonts-sil-gentiumplus

  maintained by others:

  fonts-stix
  ttf-adf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-cabin/+bug/1546979/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1469221] Re: Move to webkit2gtk in main

[Steve Langasek]

The devhelp package in main has just dropped the delta to use webkitgtk
instead of webkit2gtk:

  https://launchpad.net/ubuntu/+source/devhelp/3.18.1-1ubuntu1

Laney, what's the status of this bug?  Is this transition moving forward
for xenial?  Do we need an MIR for webkit2gtk or just a committment to
remove webkitgtk from main in favor of w2g?  Should we pre-promote
webkit2gtk to main to unblock things like devhelp, and mark this a
critical bug against webkitgtk?

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to shotwell in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1469221

Title:
  Move to webkit2gtk in main

Status in Shotwell:
  Confirmed
Status in apturl package in Ubuntu:
  Fix Released
Status in shotwell package in Ubuntu:
  Confirmed
Status in software-center package in Ubuntu:
  In Progress
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in webkitgtk package in Ubuntu:
  Confirmed

Bug description:
  Look at porting things to the new webkit2 API. Upstream has dropped
  wk1 and so webkitgtk is not receiving updates any more.

  We should aim to move webkit2gtk to main and webkitgtk to universe,
  eventually removing it once everything is ported.

  Reverse-Depends
  ===
  * apturl(for gir1.2-webkit-3.0)
  * empathy   (for libwebkitgtk-3.0-0)
  * evolution (for libwebkitgtk-3.0-0)
  * evolution-dev (for libwebkitgtk-3.0-dev)
  * libdevhelp-3-2(for libwebkit2gtk-3.0-25)
  * libdevhelp-dev(for libwebkit2gtk-3.0-dev)
  * libevolution  (for libwebkitgtk-3.0-0)
  * libgoa-backend-1.0-1  (for libwebkitgtk-3.0-0)
  * librhythmbox-core9(for libwebkitgtk-3.0-0)
  * libwebkit1.1-cil  (for libwebkitgtk-1.0-0)
  * libyelp-dev   (for libwebkitgtk-3.0-dev)
  * libyelp0  (for libwebkitgtk-3.0-0)
  * rhythmbox-plugins (for gir1.2-webkit-3.0)
  * shotwell  (for libwebkitgtk-3.0-0)
  * software-center   (for gir1.2-webkit-3.0)
  * ubiquity-frontend-gtk (for gir1.2-webkit-3.0)
  * ubuntu-release-upgrader-gtk   (for gir1.2-webkit-3.0)
  * unity-control-center  (for libwebkitgtk-3.0-0)
  * yelp  (for libwebkitgtk-3.0-0)
  * zenity(for libwebkitgtk-3.0-0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/shotwell/+bug/1469221/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1382843] Re: uoa publishing on flickr, corrupted double-linked list error

[Steve Langasek]

package removed from trusty-proposed.

** Changed in: libsignon-glib (Ubuntu Trusty)
   Status: Fix Committed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to shotwell in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1382843

Title:
  uoa publishing on flickr, corrupted double-linked list error

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in shotwell package in Ubuntu:
  Fix Released
Status in libsignon-glib source package in Trusty:
  Invalid
Status in libsignon-glib source package in Utopic:
  Fix Committed
Status in shotwell source package in Utopic:
  Fix Committed

Bug description:
  * Impact
  Trying to upload photos makes shotwell hit a segfault

  * Test case
  Try to publish a photo to an online configured through online-accounts

  * Regression potential
  Check that you can add and use online accounts without issues (in shotwell 
and other unity7 desktop components)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1382843/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp