@seb128: would you take care of uploading that patch, or should somebody
else do it?
I'm not a core-dev, so I would still need a sponsor for the actual
upload (though I have them already), so if you have the tuits it might
just be quicker/easier if you could do it ^^
--
You received this bug not
(moving back to "triaged" while we wait on the SRU team's answer on this
new point)
** Changed in: telegram-desktop (Ubuntu Focal)
Status: Won't Fix => Triaged
** Changed in: libtgowt (Ubuntu Focal)
Status: Won't Fix => Triaged
--
You received this bug notification because you are
Very well, thank you.
I uploaded the package to ubuntu focal-proposed, and it's now pending
review from the Stable Release Team.
You'll asked to test again using the package from focal-prosed later on.
Unfortunately I forgot to use a different version in my PPA, so please
pay attention that you `
@Dan: i don't think it's proper to close 3-years old bugs as "the bug is
old" - especially not when the request looks very fine and senseful to me. ?
On Thu, 14 Oct 2021, 12:16 am Dan Streetman, <1756...@bugs.launchpad.net>
wrote:
> as this is years old, closing as wontfix
>
> ** Changed in: ubun
"to meat upstream requirements" 🍖🥩
I'm not going to let you fix that, accepted! :)
** Changed in: libreoffice (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
I'd say ACK, this fits the scope of backports perfectly.
@mvo: note that the process from backports changed, so you are supposed
to do the upload and eventually maintain it, see the page
http://wiki.ubuntu.com/UbuntuBackports
--
You received this bug notification because you are a member of Ubun
pushed to git for the next release, thank you!
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2096956
Title:
fixing minor
wrote:
> Thanks @Mattia - I tried to upload this but it seems I no longer have
> the required permissions. This is unfortunate, I used to be ubuntu-core-
> dev but for some reason that seems to have been removed. Well, the
> debdiff is here, this will now need sponsoring. Sorry for that.
>
oh, sorry, yesterday I was looking at the wrong queue!
accepted :)
** Changed in: hydrogen (Ubuntu Noble)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098
I see that the changelog says it's a "no change"; if that is so, then
I'm good with this, please go through with the upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098723
Title:
[BPO] hydrog
@tsimonq2: acqully no, in backports we follow the security team
recommendation about versioning, and we also explicitly document on
https://wiki.ubuntu.com/UbuntuBackports#Preparing_the_Backported_Package
an example which has two ubuntu releases in the version string.
I agree it is a bit jarring t
I'm subscribing ~ubuntu-sponsors and "starting the timeout"
** Changed in: pymodbus (Ubuntu)
Status: New => Invalid
** Also affects: pymodbus (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: pymodbus (Ubuntu Noble)
Status: New => Incomplete
--
You receive
** Also affects: sigil (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: sigil (Ubuntu Oracular)
Importance: Undecided
Status: New
** No longer affects: sigil (Ubuntu Oracular)
** Changed in: sigil (Ubuntu)
Status: New => Fix Released
--
You received
this looks like a reasonable request. would this be a no-change rebuild
(minus changelog entry) compared to the version in plucky? We normally
appreciate a debdiff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
nope, sbuild -d is a clear override of what's in the changelog:
"Explicitly set the distribution for the package build. This will be
selecting the correct chroot to use and also sets the value of the
Distribution field in the created .changes file"
Indeed I checked the .changes file that was in th
It's in the wrong queue, it has "Distribution: jammy" instead of
"Distribution jammy-backports".
Now it will need somebody from the SRU team to reject it, a rebuild and
re-upload.
I'm not sure how that happened, it used to be the case when somebody
used sbuild with `-d DIST` instead of `-c DIST`
(just a small note that also a backport is a commitment, and you aren't
supposed to one-shot the upload... although I suppose one could see it
as a smaller commitment than an SRU given the smaller impact.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Public bug reported:
Error while updating to kernel version 3.13.0-44 using apt-get dist-
upgrade.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-updates 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
A
*** This bug is a duplicate of bug 478245 ***
https://bugs.launchpad.net/bugs/478245
Same problem on ubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940124
Title:
Remmina numlock bu
1601 - 1619 of 1619 matches
Mail list logo
