Public bug reported:

Scheduled-For: ubuntu-25.11
Ubuntu: 2:4.36-1ubuntu2
Debian Unstable: 2:4.37-1

A new release of nspr is available for merging from Debian Unstable.

If it turns out this needs a sync rather than a merge, please change the
tagging from ['dcr-merge'] to ['dcr-sync'], and (optionally) update the
title as desired.

If this merge pulls in a new upstream version, also consider adding an
entry to the resolute Release Notes:
https://discourse.ubuntu.com/t/resolute-raccoon-release-notes/

### New Debian Changes ###

nspr (2:4.37-1) unstable; urgency=medium

  * New upstream release.

 -- Mike Hommey <[email protected]>  Thu, 02 Oct 2025 10:45:55 +0900


### Old Ubuntu Delta ###

nspr (2:4.36-1ubuntu2) questing; urgency=medium

  * No-change rebuild for IEEE long double on ppc64el

 -- Graham Inggs <[email protected]>  Mon, 22 Sep 2025 11:23:23 +0000

nspr (2:4.36-1ubuntu1) plucky; urgency=medium

  * Merge from Debian Unstable. Remaining changes:
    - Drop explicit -Wl,--as-needed linker flag. It's the default.
    - Drop explicit CFLAGS that are checked by configure.
    - Also use non-hardening flags from dpkg-buildflags to pick up flags
      like -fno-omit-frame-pointer.
  * Dropped change (included upstream):
    - d/p/fix-ftbfs-incompatible-thread-start-type.patch: Fix FTBFS due
      to incompatible native thread start types (LP: #2081110)

 -- Simon Quigley <[email protected]>  Tue, 11 Feb 2025 16:23:06 -0600

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


** Tags: dcr-merge

** Changed in: nspr (Ubuntu)
    Milestone: None => ubuntu-25.11

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

Title:
  Merge nspr from Debian Unstable for resolute

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to