[Group.of.nepali.translators] [Bug 1415701] Re: apt is unable to handle CDROMS with default mount option
** Changed in: apt (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1415701 Title: apt is unable to handle CDROMS with default mount option Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Bug description: I have found i am almost completely unable to use CDROM as an apt repository on Ubuntu 14.04 I found the command apt-cdrom add by default, was unable to detect CDROMs it was attempting to find them in /media/cdrom/ by default ubuntu now seems to mount cds in /media/$USER/ and this is not something set via fstab i was able to get them to add with the command apt-cdrom add -m --cdrom /media/$USER/ I seem to have been able to pull the package list from the CD, but when it comes to installing from it, apt encounters a similar error it ask you to insert the disc in drive /media/cdrom/ again I also am completely unable to add cds via the software & updates setting manager, it always fails to find the cd, which is presumably part of the same issue. manually remounting with sudo mount /dev/cdrom /media/cdrom get some things to work, but most of the actions trigger a remount which goes back to the default location I was finally able to get things working again properly by adding the fstab line /dev/cdrom /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0 resolves the problem for me but this is a work around not a fix, it may break other stuff In apt conf i have tried setting Acquire::cdrom::mount "file/path/"; with various file paths, the file paths, to try and make it work with the default mount behaviour,this looked to be the right setting to change as the message changed accordingly to what i was setting, but i could not get it to work for actually installing packages, even by setting an absolute file path for my user in the media directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1415701/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1589204] Re: apt-get dist-upgrade and apt full-upgrade not reporting held back package
** Changed in: apt (Ubuntu Xenial) Status: Confirmed => Won't Fix ** Changed in: apt (Ubuntu Trusty) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1589204 Title: apt-get dist-upgrade and apt full-upgrade not reporting held back package Status in apt package in Ubuntu: Confirmed Status in apt source package in Trusty: Won't Fix Status in apt source package in Xenial: Won't Fix Bug description: I have the situation where a package cannot be upgraded because of missing dependencies. However sudo apt-get dist-upgrade and sudo apt full-upgrade and sudo apt upgrade all show 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Only sudo apt-get upgrade shows 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. I believe all of the above commands should show that 1 cannot be upgraded. This bug is not about the particular package I am trying to install, but about the way apt reports the problem. The details, for reference, are that I am trying to upgrade mosquitto from the mosquitto ppa. After apt-get update I see $ apt-cache policy mosquitto mosquitto: Installed: 1.4.8-1build1 Candidate: 1.4.9-0mosquitto1 Version table: 1.4.9-0mosquitto1 500 500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu xenial/main amd64 Packages *** 1.4.8-1build1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status but if I try to manually install mosquitto I get The following packages have unmet dependencies. mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable and $ apt-cache policy libwebsockets3 libwebsockets3: Installed: (none) Candidate: (none) Due to the fact that libwebsockets3 is not available for Xenial. As I said this bug is not about the problem with this particular package but about the fact that apt does not report that there is a package to be upgraded, but it cannot be done. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 5 08:45:33 2016 InstallationDate: Installed on 2014-10-21 (592 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1589204/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1916211] Re: xenial/linux-aws: 4.4.0-1123.137 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Ian (ian-may) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916211 Title: xenial/linux-aws: 4.4.0-1123.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: main: build#1 meta: build#1 kernel-stable-master-bug: 1916222 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 25. February 2021 14:27 UTC promote: - main - meta proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Fix Released trackers: xenial/linux-aws/aws-kernel: bug 1916210 variant: debs versions: main: 4.4.0-1123.137 meta: 4.4.0.1123.128 source: 4.4.0-1123.137 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1916211/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1915536] Re: one grub
This bug was fixed in the package grub2 - 2.04-1ubuntu44 --- grub2 (2.04-1ubuntu44) hirsute; urgency=medium * Compile grub-efi-amd64 installable i386 platform on hirsute, to make it available in bionic and earlier as part of onegrub builds. -- Dimitri John Ledkov Wed, 03 Mar 2021 11:42:28 + ** Changed in: grub2 (Ubuntu Hirsute) Status: In Progress => Fix Released ** Changed in: grub2-signed (Ubuntu Hirsute) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1915536 Title: one grub Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in grub2-unsigned package in Ubuntu: New Status in grub2 source package in Xenial: Fix Committed Status in grub2-signed source package in Xenial: Fix Committed Status in grub2-unsigned source package in Xenial: New Status in grub2 source package in Bionic: Fix Committed Status in grub2-signed source package in Bionic: Fix Committed Status in grub2-unsigned source package in Bionic: New Status in grub2 source package in Focal: Fix Committed Status in grub2-signed source package in Focal: Fix Committed Status in grub2-unsigned source package in Focal: New Status in grub2 source package in Groovy: Fix Committed Status in grub2-signed source package in Groovy: Fix Committed Status in grub2-unsigned source package in Groovy: New Status in grub2 source package in Hirsute: Fix Released Status in grub2-signed source package in Hirsute: Fix Released Status in grub2-unsigned source package in Hirsute: New Bug description: [Impact] The proposal is to split src:grub2 into two source packages. src:grub2 will continue to build most things, apart from bin|dbg |signing-tempate binary packages for platforms that get signed. src:grub2-unsigned source package is source-full copy of src:grub2 that only builds bin|dbg|signing-tempate binary packages for platforms that get signed and submits monolithic binaries for signing. src:grub2-signed is built as before, but its maintainer scripts should be compatible across grub2-common from precise and up. Stable series will receive grub2 update that drops building bin|dbg |signing-template. Stable series will receive binary-copy of grub2-unsigned & grub2-signed, thus on signed platforms EFI apps and modules will be the same across all series. [Caveats] * In devel series, always upload grub2 with matching src:grub2-unsigned and src:grub2-signed. The unsigned package can be build with ./debian/rules generate-grub2-unsigned command from src:grub2. * In stable series, only upload src:grub2 when fixes needed in update- grub / grub.cfg / grub-install / etc, but not in the efi modules & apps. * As needed, binary copy grub2-unsigned & grub2-signed from later series to stable series. [Test Case] * Upgrade to new packages * Observe that system boots, one can use grub-mkimage / grub-mkrescue without issues. [Where problems could occur] * There might be regression on the EFI platforms with grub 2.04 that have not so far been caught on Focal / Groovy / Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1892275] Re: [sync][sru] sos upstream 4.0
** Changed in: sosreport (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: sosreport (Ubuntu Bionic) Assignee: Eric Desrochers (slashd) => (unassigned) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 Status in sosreport: Unknown Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Xenial: Won't Fix Status in sosreport source package in Bionic: Won't Fix Status in sosreport source package in Focal: Fix Released Bug description: [Impact] The sos team is pleased to announce the release of sos-4.0. This is a major version release that represents a significant change to the sos project, new features, and bug fixes. https://github.com/sosreport/sos/releases/tag/4.0 [Test Case] * Install sosreport 4.0-1* package ** Test new main binary 'sos' and it's former binary still present 'sosreport' (e.g. sosreport -a --all-logs & sos report -a --all-logs) ** Test new features: *** sos-collect (Collect sosreport from multiple node simultaneously) *** sos-clean || sos-mask (It's aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already.) Replacement of the former project called 'soscleaner' which no longer deliver development. [Regression Potential] Main binary formerly known as 'sosreport' has been officially renamed to 'sos' but 'sosreport' still exist and has been carried over for now to help to transition for package maintainer. No impact nor behavioural change for existing user. They are welcome to use the new binary or the former one as they wish. -rwxr-xr-x 1 root root 1057 Aug 25 16:24 /usr/bin/sosreport -rwxr-xr-x 1 root root 596 Aug 25 16:24 /usr/bin/sos New functionalities has been added which could lead to possible bugs ,since they are fairly new addition, if not already caught by the travis/autopkg tests but if a problem arise it will be limited to the components itself and won't affect the main behaviour (which by the way remain the same, which is to collect a tarball using 'sosreport' or/and now 'sos report' subcommand. To resume, main known existing behaviour remain the same but some new features which are limited/independent to each other has been added to offer new features such as : * sos collect is a new sub command in this release, and is an integration of the standalone sos-collector project, with the aim being to collect sosreports from multiple systems simultaneously. Note that this sub-command requires python3-pexpect to be available. If the module is not available, sos collect will abort with an appropriate error message * sos clean, also available as sos mask, is a newly added sub-command in this release and is an implementation of the standalone soscleaner project. Its aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already. https://wiki.ubuntu.com/SosreportUpdates sos4.0 now enforces archives to be stored in /var/tmp. A debian patch has been made to continue to store in /tmp (current behaviour) to stay align with current behaviour but also because debian's systemd implementation doesn't provide a tmpfiles.d cleaner for /var/tmp. So /tmp remains the default "tmp-dir" location. During the testing, I found a py38 incompatibility related to dictionnary order, that I fixed upstream and cherry-pick for Ubuntu release having py38 found in : d/p/0002-fix-dict-order- py38-incompatibility.patch. Upstream commit: https://github.com/sosreport/sos/pull/2207/commits/86dfd99931ac0199895cf5e41711fc9b1ab6feaf The old config (/etc/sos.conf) contents will not be carried over after update. Users will have to modify the new file (/etc/sos/sos.conf) instead (if needed). [Other Information] https://github.com/sosreport/sos/releases/tag/4.0 [Original Description] https://github.com/sosreport/sos/releases/tag/4.0 Major changes Sos has been redesigned to provide functionality beyond the well known report data collection usage. It has been updated to provide more functionality via sub-commands. A new sos binary has replaced the former sosreport binary as the main entry point for the utility. sos report is now used to generate sosreport tarballs. A sosreport binary is maintained as a redirection point and will now invoke sos report. sos collect formally brings sos-collector into the main sos project, and is used to collect sosreports from multiple nodes simultaneously. A sos-collector binary is maintained as a redirection point and will invoke sos collect. This means the standalone sos-collector utility will no longer be
[Group.of.nepali.translators] [Bug 1878969] Re: time-epoch never changes in SRUs
with core-initrd v40, each new initrd build increases time epoch.
This still means that for brand new account keys, one needs to wait or
build a new kernel to be able to boot in UC20.
** Changed in: ubuntu-core-initramfs
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1878969
Title:
time-epoch never changes in SRUs
Status in ubuntu-core-initramfs:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
New
Status in systemd source package in Bionic:
New
Status in systemd source package in Focal:
New
Bug description:
[Impact]
* Systems without hwclock come up with a fixed time epoch which is not
updated in SRUs
* Ideally booting with a newer built of systemd should move time epoch to be
at least when systemd was last built. For example to the value of
SOURCE_DATE_EPOCH.
[Test Case]
* Boot without network NTP or hwclock
* Observe that the epoch is the same as the time when NEWS entry in the
systemd source code was last touched.
* Boot newer update of systemd, observe that the time epoch is at least 2020
[Regression Potential]
* Bad epoch, may result in unable to perform TLS connections,
validated GPG signatures, and snapd assertions. Changing epoch to be
more recent is desired. Some machines may rely on the fact that
"bionic" without hwclock always comes up in year 2018. But in practice
that is incorrect thing to do.
[Other Info]
* By default
option('time-epoch', type : 'integer', value : '-1',
description : 'time epoch for time clients')
in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()
If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
to be compliant with the https://reproducible-
builds.org/docs/timestamps/ specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1915722] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
This bug was fixed in the package rustc - 1.50.0+dfsg1+llvm-0ubuntu1 --- rustc (1.50.0+dfsg1+llvm-0ubuntu1) hirsute; urgency=medium * New upstream release. (LP: #1915722) * Update patches. * Update d/copyright. -- Michael Hudson-Doyle Thu, 04 Mar 2021 10:17:58 +1300 ** Changed in: rustc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1915722 Title: rustc 1.50 and cargo 0.51 will be required by a future version of firefox Status in cargo package in Ubuntu: New Status in rustc package in Ubuntu: Fix Released Status in cargo source package in Xenial: New Status in rustc source package in Xenial: New Status in cargo source package in Bionic: New Status in rustc source package in Bionic: New Status in cargo source package in Focal: New Status in rustc source package in Focal: New Status in cargo source package in Groovy: New Status in rustc source package in Groovy: New Bug description: This is not yet a hard requirement, but builders in the Mozilla infrastructure have already been upgraded to rustc 1.50¹, so we should start preparing this update for hirsute and all supported releases (xenial, bionic, focal, and groovy). This will also benefit other projects that are packaged in Ubuntu and are bumping their build dependency on rustc, see e.g. https://gitlab.gnome.org/GNOME/librsvg/-/commit/513a575a839342f46bca713ac4eac37fbab9a7b7. ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1692352 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1916222] Re: xenial/linux: 4.4.0-204.236 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true built: main: build#1 meta: build#1 signed: build#1 packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 25. February 2021 08:52 UTC promote: - signed - meta - main proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress kernel-signoff: Stalled -- waiting for signoff regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Fix Released trackers: trusty/linux-aws: bug 1916220 trusty/linux-lts-xenial: bug 1916221 xenial/linux-aws: bug 1916211 xenial/linux-cascade: bug 1916213 xenial/linux-fips: bug 1916214 xenial/linux-kvm: bug 1916215 xenial/linux-raspi2: bug 1916217 xenial/linux-snapdragon: bug 1916219 xenial/linux/caracalla-kernel: bug 1916207 xenial/linux/pc-kernel: bug 1916208 xenial/linux/stlouis-kernel: bug 1916209 variant: debs versions: main: 4.4.0-204.236 meta: 4.4.0.204.210 signed: 4.4.0-204.236 source: 4.4.0-204.236 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916222 Title: xenial/linux: 4.4.0-204.236 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow kernel-signoff series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true built: main: build#1 meta: build#1 signed: build#1 packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 25. February 2021 08:52 UTC promote: - signed - meta - main proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress kernel-signoff: Stalled -- waiting for signoff regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Fix Released trackers: trusty/linux-aws: bug 1916220 trusty/linux-lts-xenial: bug 1916221 xenial/linux-aws: bug 1916211 xenial/linux-cascade: bug 1916213 xenial/linux-fips: bug 1916214 xenial/linux-kvm: bug 1916215 xenial/linux-raspi2: bug 1916217 xenial/linux-snapdragon: bug 1916219 xenial/linux/caracalla-kernel: bug 1916207 xenial/linux/pc-kernel: bug 1916208 xenial/linux/stlouis-kernel: bug 1916209 variant: debs versions: main: 4.4.0-204.236 meta: 4.4.0.204.210 signed: 4.4.0-204.236 source: 4.4.0-204.236 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1916222/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
